[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Getting Back to Basics - How to describe Dates and Times andEvents?
Martin,
How does a URI pointer in lieu of a simple tag/data set facilitate the requirement to support solutions appropriate for SME's?
Mark
Mark Crawford
Research Fellow - XML Lead
E-business Strategies
______
Logistics Management Institute
2000 Corporate Ridge, McLean, VA 22102-7805
(703) 917-7177 Fax (703) 917-7518
Wireless (703) 655-4810
mcrawford@lmi.org
http://www.lmi.org
"Opportunity is what you make of it"
> -----Original Message-----
> From: Martin Bryan [mailto:mtbryan@sgml.u-net.com]
> Sent: Tuesday, April 10, 2001 3:36 AM
> To: William J. Kammerer; ebXML Core
> Subject: Re: Getting Back to Basics - How to describe Dates and Times
> andEvents?
>
>
> William suggested:
>
> > <docRef>
> > <docType>Invoice</docType> (required)
> > <docNum>ABC-12345</docNum> (required)
> > </docRef>
>
> I would prefer the much simpler
>
> <docRef
> docType="http://www.ebXML.org/Messages/Invoice">ABC-12345</docRef>
>
> Note two things about this example:
>
> 1) There is only a single element, with no substructure
>
> 2) The element references a URI that uniquely identifies the
> type. This
> value is neither an uninterpretable code or a language specific
> representation. It is simply a pointer to an information
> resource which is
> already stored in an ebXML registry.
>
> Martin Bryan
>
>
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: ebxml-core-request@lists.ebxml.org
>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC