One interesting side not, is that if EPCglobal ever chooses to use one of these bits, the llrp.xsd schema will not be backward compatible (nor will the abstract LLRP definition). However, one could argue that the llrp binary protocol will still be backward compatible. E.g. a reserved bit which must be zero in llrp 1.0 means "I support new feature X" in llrp 1.1.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John R. Hogerhuis Sent: Wednesday, November 14, 2007 3:34 PM To: LLRP Toolkit Development List Subject: Re: [ltk-d] "Reserved" in llrpdef.xml and llrp.xsd On Nov 14, 2007 3:21 PM, Christian Floerkemeier <[EMAIL PROTECTED]> wrote: > > I have a question regarding the use of the reserved field in llrpdef.xml and > llrp.xsd. > Llrpdef.xml allows for multiple "reserved" elements in a message definition: These are unrelated. The reserved field you describe in LLRP.xsd is the reserved bits from the binary LLRP message header, reserved by EPC Global in the LLRP standard. There is only one reserved field in the header, so an attribute makes sense there. The reserved fields described in llrpdef.xml are a description of reserved bit fields or alignment padding per message or parameter type. There may be an arbitrary number of reserved fields in a message or parameter. These do not appear in the XML representation described by LLRP.xsd since they are not relevant at the abstract XML level... they are only of use in building binary packets. -- John. ------------------------------------------------------------------------ - 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 ------------------------------------------------------------------------- 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
