OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-architecture message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: Comments on TA doc v1.0


I personally would welcome a conversation to be started around this.

/stefano

> -----Original Message-----
> From: Duane Nickull [mailto:duane@xmlglobal.com]
> Sent: 05 February 2001 18:30
> To: Karsten Riemer
> Cc: Stefano POGLIANI; Brian Eisenberg; hha@mosaic-ag.com; Petit, John;
> ebxml-architecture@lists.ebxml.org
> Subject: Re: Comments on TA doc v1.0
> 
> 
> 
> 
> Karsten Riemer wrote:
> > 
> > Please settle this by moving the offending text as is into the 
> RegRep chapter.
> ...
> > >Q: What mechanism do we use to locate a Registry Item from its' UID?
> > >A: The best suggestion we have had is from Jon Bosak who pointed Brian
> > >and I at the work done by M. Mealling (URN's and DNS).
> >>>>
> 
> Karsten:
> 
> You may not be understanding this completely.  The point I am trying to
> make is that there is no mechanism available (as a formal standard) to
> resolve a UID to a Registry Item.  I spoke in detail to Jon Bosak about
> this and he suggested the use of Michael Mealling's RFC for using URN's
> combined with a now-blank entry in DNS to create a location independant
> mechnism for consistently resolving UID's.  UDDI can also benefit from
> this.  XLink is really the only possible candidate however hard links
> are seldom 100% reliable.  I would not advocate adopting XLink in its'
> current state.
> 
> I wished to start a conversation around this.  Simply moving the
> question to another section will not resolve the issue.
> 
> Duane
> 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC