[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: PartyId and Context
To answer Charlie's and Duane's emails at one go. There is a VERY GOOD REASON why we should NOT use domain and that is that we would need to set up and create our own registration authority when we can leverage IANA if we use URIs. Please read my original post on this point at ... http://lists.ebxml.org/archives/ebxml-transport/200009/msg00246.html ... and let me know if you think I am wrong to require the use of URIs unless the codes are mutually agreed between the parties. It's just that if we want to set up our own registration authority then we are talking about a lot of expense and effort that, IMO, is just not necessary when you can use a URN as the umbrella for other domains such as DUNS. Regards David -----Original Message----- From: Charlie Fineman [mailto:fineman@arzoon.com] Sent: Thursday, December 14, 2000 9:33 AM To: 'Duane Nickull'; Burdett, David Cc: ebxml-tp@lists.ebxml.org; ebxml-transport@lists.ebxml.org Subject: RE: PartyId and Context Is there a good reason why the tags shouldn't just have the same name (in TRP and Rep)? Obviously they don't mean the same exact thing but are they close enough in intent to share the same name? Duane wrote: > This is similar to the RegRep information model ( not syntactically). > > eg. > > <fromPartyID domain="duns">12774493</fromPartyID> > > <toPartyID domain="CanadianTaxID">GAED440392</toPartyID> >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC