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

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-cc-review message

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


Subject: RE: [regrep-cc-review] Issue #1: Unique Identifiers


I'm wondering about the situations where Core Component work is provided to a registry after the developers have been tracking CC IDs without taking into account the potential registry UUIDs.  The developers will want to retain the CC IDs they are familiar with during their development work.

Thinking that through some more I'm not sure that precludes the mapping defining the UUID as the CC's ID.  The developers could still map their internal CC ID to an ExternalIdentifier class.  In practicality it would be a situational mapping. If the development took the registry into account in assigning their CC IDs, then the UUID is likely going to be treated as the ID within the community anyways.  If the developers used their own ID scheme for the CCs, then the that ID gets relegated to the ExternalIdentifier but the UUID still stands as the CC's ID.

Or would that be too confusing and we should just request that all developer CC IDs be mapped to ExternalIdentifier?

-Paul

-----Original Message-----
From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
Sent: Friday, August 22, 2003 2:14 PM
To: Carl Mattocks
Cc: CCRev
Subject: Re: [regrep-cc-review] Issue #1: Unique Identifiers


Thanks Carl. 

Team, please see below for Carl's response to issue #1.

Joe

Carl Mattocks wrote:
> 
> I believe that UUID is sufficient.
> 
> The use of a Namespace should be enough for  "human-readability"
> 
> >
> > ISSUE: Requirement [S1] states that Core Components should have a Unique
> > Identifier. In our Registry, we already have a 128-bit UUID.
> >
> > QUESTION: Will the UUID suffice? Or should this unique identifier be
> > more "human-readable", for example: "BCC00003" (Basic Core Component
> > #3).
> 
> carl
> Carl Mattocks
> CEO CHECKMi
> e-mail: CarlMattocks@checkmi.com
> *******************************************
> Business Agent Software that
> Secures Knowledge for Reputation:Protection
> *******************************************
> CHECKMi Compendium the shortcut to Valued & Trusted Knowledge
> *******************************************
> www.checkmi.com
> (usa)1-908-322-8715
> CarlCheckMi (I M)


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