[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-cppa] CPP identification revisited
I think we should definitely drop the entire Note about Registry identifiers for CPPs. The cppid identifier is supposed to be unique, as we now say in v1.07. That should give implementers an identifier for a CPP. Do we need to add a scope for globally, universally, cross-all actual-and-alternative-universes uniqueness? The original uniqueness intent was unique within CPPs of a Party, which is less than globally unique. Maybe we should state the scope within which uniqueness is to be assured? URN resolution process is still not very well-defined, standardized, or even with a de facto practice, as far as I can tell from the IETF URN WG RFC list. I think that is a 3.0 goal to explain how using URNs will support interop while allowing extensions. Dale Moberg -----Original Message----- From: Duane Nickull [mailto:duane@xmlglobal.com] Sent: Monday, February 11, 2002 1:58 PM To: Martin W Sachs Cc: ebxml-cppa@lists.oasis-open.org Subject: Re: [ebxml-cppa] CPP identification revisited Martin W Sachs wrote: > It would appear that if the CPP has a globally unique identifier, we would > remove the statements about a registry-assigned identifier but it may not > be that simple. >>>>> It's far from that simple. The Registry assigned unique identifier identifies it uniquely within one specific registry instance, not globally. Does anyone remember the arguments on this from last year? > Duane if you are looking here, I think you were involved in the > discussions. >>>>>>>>>>> Yes - it is a bone of contention accross a few teams. CC, BP and Architecture are all affected. I have an action item to discuss this within architecture. A URN resolution shceme may be our best bet although no single consistent methodology exists for this. Duane > Regards, > Marty > > ************************************************************************ ************* > > Martin W. Sachs > IBM T. J. Watson Research Center > P. O. B. 704 > Yorktown Hts, NY 10598 > 914-784-7287; IBM tie line 863-7287 > Notes address: Martin W Sachs/Watson/IBM > Internet address: mwsachs @ us.ibm.com > ************************************************************************ ************* > > Tony Weida <rweida@hotmail.com> on 02/11/2002 02:20:35 PM > > To: CPPA <ebxml-cppa@lists.oasis-open.org> > cc: > Subject: [ebxml-cppa] CPP identification revisited > > Now that CPPs have a REQUIRED cppid attribute, we may want to revisit > text such as the following: > > NOTE: This specification makes the assumption that a CPP that has been > registered in an ebXML or other Registry will be referenced by some > Registry-assigned globally-unique identifier that MAY be used to > distinguish among multiple CPPs belonging to the same Party. See Section > 8.1for more information. > > Comments? > > Tony > > ---------------------------------------------------------------- > To subscribe or unsubscribe from this elist use the subscription > manager: <http://lists.oasis-open.org/ob/adm.pl> -- CTO, XML Global Technologies **************************** Transformation - http://www.xmlglobal.com/prod/foundation/ ebXML Central - http://www.xmlglobal.com/prod/central/ ---------------------------------------------------------------- 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