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:


Forwarded on behalf of Diego.

Joe

Diego Ballvé wrote:
> 
> Mark,
> 
> > 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.
> 
> It depends on how "temp" the CCTS team considers the this uid.
> If you are worried about tracability then I think that you
> expect CCs to be reached using this id. If that's the case we
> would need both, or an external mapping table. I'd hope that
> DictionaryEntryName would suffice for human-readable identifier
> and RIM UUID (or as Farruck suggested, any-UUID) would be the
> RegistryClass.uid.
> 
> Diego
> 
> Original msg from http://www.oasis-open.org/archives/regrep-cc-review/200308/msg00097.html:
> --------------------------------------------------------------------------------
> 
> Subject: Re: [regrep-cc-review] Issue #1: Unique Identifiers
> 
> From: "CRAWFORD, Mark" <MCRAWFORD@lmi.org>
> To: <farrukh.najmi@sun.com>,<chiusano_joseph@bah.com>
> Date: Sun, 24 Aug 2003 17:03:17 -0400
> 
> --------------------------------------------------------------------------------
> 
> 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
begin:vcard 
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@bah.com
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard


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