I meant to include one more issue in my previous email:
In llrpdef.xml, the parameterDefinition of "PerAntennaAirProtocol" does not
define that the ProtocolID field (with the list of ProtocolIDs) contains
instances of the enumeration type "AirProtocols". This is in contrast to
those parameterDefinitions that have only a single ProtocolID listed such as
the "AccessSpec":
<parameterDefinition name="PerAntennaAirProtocol" typeNum="140"
required="true">
.......
<field type="u8v" name="ProtocolID"/>
</parameterDefinition>
<parameterDefinition name="AccessSpec" typeNum="207" required="true">
.....
<field type="u8" name="ProtocolID" enumeration="AirProtocols"/>
.....
</parameterDefinition>
Could we add the enumeration attribute to the parameterDefinition of
PerAntennaAirProtocol in llrpdef.xml as well?
<parameterDefinition name="PerAntennaAirProtocol" typeNum="140"
required="true">
.......
<field type="u8v" name="ProtocolID" enumeration="AirProtocols"/>
</parameterDefinition>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Christian Floerkemeier
> Sent: Donnerstag, 6. Dezember 2007 19:13
> To: 'LLRP Toolkit Development List'
> Subject: [ltk-d] Inconsistency in LLRP.xsd?
>
>
> Hi,
>
> In Section 9.2.1.4, the LLRP Spec says that the
> PerAntennaAirProtocol Parameter is comprised of
>
> "Air protocols supported: List of Procol Ids enumerated based
> on Table 3."
>
> The corresponding LLRP.xsd complex type only allows for a
> single occurence of the element ProtocolID though:
>
> <xs:complexType name="PerAntennaAirProtocol">
> <xs:sequence>
> <xs:element name="AntennaID" type="xs:unsignedShort" />
> <xs:element name="ProtocolID" type="rp:AirProtocols" />
> </xs:sequence>
> <xs:attributeGroup ref="rp:paramAttrs"/> </xs:complexType>
>
>
> I guess this could be fixed by specifying maxOccurs:
>
> <xs:complexType name="PerAntennaAirProtocol">
> <xs:sequence>
> <xs:element name="AntennaID" type="xs:unsignedShort" />
> <xs:element name="ProtocolID" type="rp:AirProtocols"
> maxOccurs="256"/>
> </xs:sequence>
> <xs:attributeGroup ref="rp:paramAttrs"/> </xs:complexType>
>
> Table 3 in the LLRP Spec allows at most 256 different
> protocol Id values and while the LLRP spec does not say
> anything about duplicates in the list, it might be reasonable
> to assume that there will be at most 256 occurences.
>
> - Christian
>
>
> --
> Christian Floerkemeier
> Auto-ID Lab, Massachusetts Institute of Technology
> phone: +1-617-324-1984
> email: <[EMAIL PROTECTED]>
>
>
> --------------------------------------------------------------
> -----------
> 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://sourceforge.net/services/buy/index.php
> _______________________________________________
> 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://sourceforge.net/services/buy/index.php
_______________________________________________
llrp-toolkit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
