[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [ebxml-cppa] CPP identification revisited
The problem with a UUID is that it gives no clue as to what authority created it! Sure, the value space is unique, but absent the context in which it was assigned, one has little recourse to learn more about the artifact to which the identifier was assigned. IMO, what is needed beyond a UUID is a resolvable URI that can be used absent any further context to dereference it. Cheers, Chris Nikola Stojanovic wrote: > <Duane> > The Registry assigned unique identifier identifies it uniquely within one > specific registry instance, not globally. > </Duane> > >>From the OASIS/ebXML Registry Services Specification v2.0 > http://www.oasis-open.org/committees/regrep/documents/2.0/specs/ebrs.pdf > lines 648-650 > > <snip> > As specified by [ebRIM], all objects in the registry have a unique id. The > id must be a Universally Unique Identifier (UUID) and must conform to the to > the format of a URN that specifies a DCE 128 bit UUID as specified in > [UUID]. > </snip> > > Being UUID it is Universally (Globally) Unique. Some call it GUID (Globally > Unique). > > Regards, > > Nikola Stojanovic > Lead Technologist, Research and Development > Encoda Systems, Inc. > 101 Pineview Terrace > Ithaca, NY 14850 USA > nikola.stojanovic@encodasystems.com > Tel: 607-273-2224 > > ---------------------------------------------------------------- > To subscribe or unsubscribe from this elist use the subscription > manager: <http://lists.oasis-open.org/ob/adm.pl> >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC