Hoi Matthias, ich bin gerade auch etwas verwirrt betreffend den verschiedenen xmls/xsds. Also vorallem sehe ich momentan nicht, wo das llrpdef.xml rein passt. Also, das llrpdef.xsd definiert doch, wie das Protokol definiert sein muss. Also sagt z.B. eine Message besteht aus parametern und parameter aus paramtern oder feldern und so weiter. Das llrp-1x0-def.xml ist nun das Protokoll als xml dargestellt. Und zwar die Version 1.0 des Protokolls, richtig? Daraus könnte man das llrp-1x0.xsd generieren, welches wiederum sagt, wie eine einzelne Nachricht als XML auszusehen hat (so wie die Graphiken im PDF sagen, wie das ganze als binary aussieht). Soweit richtig? Was macht dann llrpdef.xml?? Für mich heisst das, die Klassen aus llrpdef.xsd generieren, abfüllen mit llrpdef-1x0-def.xml. Richtig? viele Grüsse, Basil
Matthias Lampe schrieb: > I think there is a little confusion about the xsd file. > > As I understand it, the llrp-1x0.xsd (/LTK/Definitions/Core/llrp-1x0.xsd) > could be created out of the llrp-1x0-def.xml > (/LTK/Definitions/Core/llrp-1x0-def.xml). llrp-1x0.xsd is the schema of LLRP > messages that are represented in XML format and not the binary format. > > The llrpdef.xsd (/LTK/Definitions/llrpdef.xsd) is of course a schema to > validate e.g. llrp-1x0-def.xml and will not be generated. > > Best > Matthias > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Matt > Poduska > Sent: Montag, 20. August 2007 18:19 > To: [email protected] > Subject: Re: [ltk-d] Summary of Java Toolkit Progress [heur] > > I disagree. > > The purpose of a schema is to define the structure of an XML file, not the > converse. The definition of a schema according to W3C: > > "XML Schemas express shared vocabularies and allow machines to carry out > rules made by people. They provide a means for defining the structure, > content and semantics of XML documents. in more detail." > > llrpdef.xsd should be used to validate that llrpdef.xml and any other LLRPv1 > XML file (such an XML file created to define vendor extensions) is correct. > > - Matt > > >> From: "Joel Peshkin" <[EMAIL PROTECTED]> >> Reply-To: LLRP Toolkit Development List >> <[email protected]> >> To: "LLRP Toolkit Development List" >> <[email protected]> >> Subject: Re: [ltk-d] Summary of Java Toolkit Progress [heur] >> Date: Mon, 20 Aug 2007 09:08:52 -0700 >> >> >> >> >>>> Of course there is duplication between LLRP.xsd and llrpdef.xml. >>>> LLRP.xsd can in fact be autogenerated from llrpdef.xml. >>>> >> That means that LLRP.xsd is really "object code", we should look at >> providing sufficient instructions to regenerate it so that it does not >> need to be checked in and we can ensure that changes to llrpdef.xml >> propagate automatically to LLRP.xsd >> >> >> > > > ------------------------------------------------------------------------- > 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
