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

["CRAWFORD, Mark" <MCRAWFORD@lmi.org>]

This isd a very interesting question. CCTS calls for the assognmentv of A unique temp identifier. This temp I'd is independent of the registry I'd. Should we store both? Should we replace the T3mp I'd with the registry I'd? My inclination is with the latter, except I am not sure what the impact on tracability is.  Thoughts?
Mark Crawford
Research Fellow - LMI XML Lead
W3C Advisory Committee, OASIS, RosettaNet Representative
Vice Chair - OASIS UBL TC & Chair Naming and Design Rules Subcommittee
Chair - UN/CEFACT XML Syntax Working Group
Editor - UN/CEFACT Core Components
______
Logistics Management Institute
2000 Corporate Ridge, McLean, VA 22102-7805
(703) 917-7177   Fax (703) 917-7481 
Wireless (703) 655-4810
mcrawford@lmi.org
http://www.lmi.org
"Opportunity is what you make of it"


-----Original Message-----
From: Farrukh Najmi <farrukh.najmi@sun.com>
To: Chiusano Joseph <chiusano_joseph@bah.com>
CC: CCRev <regrep-cc-review@lists.oasis-open.org>
Sent: Fri Aug 22 22:17:05 2003
Subject: Re: [regrep-cc-review] Issue #1: Unique Identifiers

Chiusano Joseph wrote:

>Team,
>
>Here is the first issue from the 8/21 Registry TC review: 
>
>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).
>
>  
>
I would personally like to see our specs allow use of any URN for an id 
in future. This would require making provisions for maximizing the 
chances that any such URNs are universally unique.

If CCRIM forces our hand on this then I would be OK with it.

-- 
Farrukh



You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/regrep-cc-review/members/leave_workgroup.php