We've talked about annotating the llrpdef.xml with the appropriate document from LLRP. I wrote an example of how we could annotate in the Wiki under
http://llrp-toolkit.wiki.sourceforge.net/LLRP+Protocol+Definition+%28llr pdef.xml%29 EPCglobal's copyright does not allow this without permission, so we'll have to get formal permission for this annotation. Let's agree on the technical representation below and then I'll submit for official approval to EPCglobal. I'll attach the snippet below, but here is what I am thinking. Include within the annotation tag in llrpdef.xml: 1) A documentation tag which includes a string which by convention will point to the section of the specification. This is to remain compatible with the llrpdef.xml we have now 2) A description tag which contains a string describing the element (message, parameter etc) 3) A compliance tag which contains a string with the compliance message from the LLRP spec 4) A copyright tag which holds the copyright string for 1-3 above. These would also be available for vendor extensions (1-4 would not be required by the schema) Here is an example annotation. <annotation> <documentation> reference 12.1.3 and 16.1.38 </documentation> <description> This command is issued by the Client to the Reader. This command sets the Reader configuration using the parameters specified in this command. Values passed by the SET_READER_CONFIG SHALL apply for the duration of the LLRP connection, or until the values are changed by additional SET_READER_CONFIG messages. For example, ROReportSpec defines the reporting of ROReport format and trigger for a ROSpec. ROReportSpec sent as part of SET_READER_CONFIG becomes the default ROReportSpec for the Reader. A ROReportSpec sent as part of ROSpec in the ADD_ROSPEC command overrides the default value for that ROSpec. However, in cases where there is no ROReportSpec specified in a ROSpec sent as part of ADD_ROSPEC, that particular ROSpec inherits the default ROReportSpec. The data field ResetToFactoryDefault informs the Reader to set all configurable values to factory defaults before applying the remaining parameters. </description> <Compliance> Compliant Reader and Clients SHALL implement this message </Compliance> <Copyright> Copyright 2006, 2007 EPCglobal Inc. </Copyright> </annotation> ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
