[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Tag Languages, UID's etc.
Curt/all: Sorry - I should have jumped in sooner on this thread. Here is a quick demo. Here is an XML message. Most mail clients will not display the characters properly. </xml version="1.0" encoding="UTF-16"?> <ñoÅÌ> <vf[X>01</vf[X> <ïÐÅ è>01</ïÐÅ è> <AÅVÌCAI>01</AÅVÌCAI> <µÄAeí»i>12.99</µÄAeí»i> </ñoÅÌ> A little criptic? Not only do you have to understand it but your application might too. Unfortunately, your application cannot even recognize <Element> is really the same as <element> (in enlgish) becuase to a machine, one letter case insensetive will make the app barf. Those of us who occassionally write XML with a text editor spend a lot of time tracking down small mistakes like this case mismatch too (expecially me with my Canadian grammar and bad spelling ;-) Okay - let's try again. This time with UIDs as fixed attributes of the DTD: </xml version="1.0" encoding="UTF-16"?> <ñoÅÌ UID=GXL:10021> <vf[X UID=GXL:10022>01</vf[X> <ïÐÅ è UID=GXL:10023>01</ïÐÅ è> <AÅVÌCAI UID=GXL:10024>01</AÅVÌCAI> <µÄAeí»i UID=GXL:10025>12.99</µÄAeí»i> </ñoÅÌ> But this time a quick Registry lookup (or local cache lookup so we don't have to keep using the registry) gives us the following xml fragments: ... <UID>UID:10021</UID> <Description xml:lang="EN-US">The element container hold a date and stock quote</Description> <EquivalentTo YUID="cXML:10023>YourKnownElementName</EquivalentTo> ... ... <UID>UID:10022</UID> <Description xml:lang="EN-US">The element container hold the current month</Description> <EquivalentTo YUID="cXML:10023>YourKnownElementName</EquivalentTo> ... UID:10023 is the day element, 10024 the year and 10025 the price of the stock expressed in Thailand Baht etc. Now both you and your application can understand the message. The key here is that the elements YOU chose to use are always able to convey the human and sometimes machine knowledge base for the content whiel the UID will always be primarily a machine reference but can also be used by humans to grab the true semantics by browsing a registry. The mechanism is simple and effective and once you and your app understand the UID, you don't have to query the registry each time it comes in or another trading partner requests it. <SideNote> I will likely not be able to respond to this thread for 48 hours. </SideNote> Cheers! Great work going on here. Duane Nickull Technical Architecture
Powered by eList eXpress LLC