We were not planning to implement (or make any API changes) at this time. Paul
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Basil Gasser Sent: Friday, March 21, 2008 9:48 AM To: LLRP Toolkit Development List Subject: [ltk-d] inconsitency between spec and llrpdef (CLIENT_REQUEST_OP etal) The pdf specification (http://www.epcglobalinc.org/standards/llrp/llrp_1_0_1-standard-20070813 .pdf) contains two message (CLIENT_REQUEST_OP and CLIENT_REQUEST_OP_RESPONSE, see 11.1.11 et seq.)but those do not appear in the latest llrpdef xml. Further, there is an llrp capabilities field called SupportsClientRequestOpSpec which references to these messages. Further, the AccessCommand Parameter (11.2.1.2) may have a ClientRequestOpSpec Parameter (11.2.1.2.1) which again does not appear in the xml. I guess that either they have to be deleted from the spec or added to the llrpdef.xml best. Basil ------------------------------------------------------------------------ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel ------------------------------------------------------------------------- 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
