All,
I have modified the Authorization.docx to have examples for the URIs for the web screens. This allows the reference document and the live API project to be consistent. I also added a paragraph and link to the API to the document.
You can retrieve the current document at http://osgug.ucaiug.org/sgsystems/OpenADE/Shared%20Documents/Testing%20and%20Certification/GreenButtonTestPlan/referenceMaterial/GreenButtonAuthorization.docx.
Note that the API is really shaping up. But it still needs sanity check to ensure it is consistent with the consensus document to date.
A point of clarity about which is normative. Our goal, I think is to make it so that the API is a normative reference. However that is not yet the case until we have it polished and checked for consistency. However, it is very close at this point. Therefore it is reasonable to use it because it is very easy to understand, albeit with some finite risk of error and correction after use.
Cheers,
Marty
Dr. Martin J. Burns, Hypertek Inc. for NIST
Technical Champion, Green Button
email: ma...@hypertek.us
--
You received this message because you are subscribed to the Google Groups "greenbutton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to greenbutton-d...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Look at the summary of urls. There the only ones that are ambiguous are the screens and we added the example URI fragments to the table. If you want to do a gotomeeting, I could show you right now and you could tell me what is missing. /marty