A major purpose of LTK-XML is to make a human-readable form of binary
LLRP. So, I suggest to leave it as a string when outputting XML.
Practically I can see how using an enum here will appreciably increase
the size of lists in the textual format. Perhaps we could change
<xs:simpleType name="AirProtocols">
<xs:restriction base="xs:string">
<xs:enumeration value="EPCGlobalClass1Gen2"/>
<xs:enumeration value="Unspecified"/>
</xs:restriction>
</xs:simpleType>
to something like:
<xs:simpleType name="AirProtocols">
<xs:restriction base="xs:string">
<xs:enumeration value="C1G2"/>
<xs:enumeration value="Unspec"/>
</xs:restriction>
</xs:simpleType>
This is a deviation from the indentifier spellings used in the spec,
which we have tried to maintain, but if this is a problem I wouldn't
be opposed to this change.
Other than size of the XML text file I cannot see any good reason to
display integers instead of the enumerated strings.
-- John.
-------------------------------------------------------------------------
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
