Basil, ProtocolID appears in two other locations within the LLRP Specification as the same enumeration. Namely, in InventoryParameterSpec as a field u8 and AccessSpec, also as a u8. If we change PerAntennaAirProtocol to be a u8v without the enumerated strings, then it would stand to reason these other two locations should also have the enumeration removed and be instead represented by integers. Personally I would rather see the XSD remain consistent with respect to enumerations and utilize the strings rather than the bare integers.
I should point out that this is the only instance within the entire LLRP Specification of an enumerated vector type. All other vectored types are bare integers. So I know that this one type presents a unique challenge that is a one-of within the Spec. But I would still rather see enumerated vectors handled properly within the LTK. Thanks, C -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Basil Gasser Sent: Monday, December 17, 2007 5:30 PM To: [EMAIL PROTECTED]; LLRP Toolkit Development List Subject: [ltk-d] XML encoding of PerAntennaAirProtocol - inconsistency between llrp-1x0.xsd and llrp-1x0.xml? PerAntennaAirProtocol (Type number 140, reference 9.2.1.3 and 16.2.3.1.3) has field ProtocolID. According to the specification this should be a list of Protocol IDs. Protocol IDs are an enumeration of possible Air Protocols (currenty 0 for unspecified and 1 for EPCGlobal C1 G2). The llrp-1x0-def.xml contains field ProtocolID of parameter PerAntennaAirProtocol with the declaration <field type="u8v" name="ProtocolID"/> The u8v makes perfectly sense as a protocol id is of an enumerated byte value. However, llrp-1x0.xsd for XML encoded messages requires the message to contain a string value such as "EPCGlobalClass1Gen2" instead of the integer representing it (1 in this case). At the end of this email I included the relevant parts from xsd and xml. My suggestion was to change xsd to expect an array of integer. This because the name "ProtocolID" (at least to me) implies a number but not a string. thanks for your thoughts. Basil ------------------------------------------------------------------------ - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketp lace _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
