- From: Mark Baker <distobj@acm.org>
- Date: Sun, 12 Jan 2003 21:27:11 -0500
- To: Duane Nickull <duane@xmlglobal.com>
- Cc: "www-ws-arch@w3.org" <www-ws-arch@w3.org>
Hi Duane, On Thu, Jan 09, 2003 at 11:59:28AM -0800, Duane Nickull wrote: > IN ebXML, a lot of work has been done in the area of semantics. IN > particular, ebXML has devised a list of business element meta-data > called "core components". These are things like "Telephone Number" or > "Invoice Sub Total" etc. Because many disparate vocabularies exist > today and all use their own element names for these items, the business > requirements of ebXML users was to be able to positively identify that > element "x" in one vocabulary was equivalent to element "y" in another > vocabulary. (within certain contexts - heirarchal and other). The way > we decided to do this was to use a Globaly Unique Identifier. Many > different ideas were submitted for what these GUID's should be but most > favored some sort of URI based scheme. Could you give an example of how it might be used? Would it be something like this? <ns1:x guid="urn:foo:8228d4928d4283d4892"/> <ns2:y guid="urn:foo:8228d4928d4283d4892"/> FWIW, in RDF-land, you might see something like this (an N-triple, subject/predicate/object); <ns1:x> daml:equivalentTo <ns2:y> Also FWIW, an Internet Draft that Dan Connolly and I wrote may be relevant here. It references some of the DDDS work (which I assume you were talking about), though in order to disagree with its premise; http://www.ietf.org/internet-drafts/draft-connolly-w3c-accessible-registries-00.txt MB -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Web architecture consulting, technical reports, evaluation & analysis
Received on Sunday, 12 January 2003 21:26:26 UTC