[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?
I support Martin's basic formulation. I'd support more going the extra INCH to an RDF statement of type. Presuming that the type is defined by an RDF Schema statement, which I hope it is, decorated as it can be with business rules stated using DAML (DARPA's Actor Markup Language) and RuleML. <docRef rdf:type="http://www.ebXML.org/Messages/Invoice">ABC-12345</docRef> In RDF, this is equivalent to <docRef>ABC-12345 <rdf:type rdf:resource="http://www.ebXML.org/Messages/Invoice"/> </docRef> In the DCN, there is no need for a "docRef" element. Assuming that ABC-12345 is some sort of URI, then simply do <Document rdf:type="http://www.ebXML.org/Messages/Invoice" rdf:resource='ABC-12345'/> Someone asked how does this benefit the SME? Simplicity. Few elements. Not much to learn. Table-driven. Reuse. More tools. NO WRETCHED CODES. > -----Original Message----- > From: Martin Bryan [mailto:firstname.lastname@example.org] > Sent: Tuesday, April 10, 2001 12: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: email@example.com >
Powered by eList eXpress LLC