William:
Your kind offer to pen this document is without equal, therefore, I
would formally request that it be done. One minor alteration I would
like to bring up.
Since the BPSS, Core Components, Registry and CPP/A all make use of a
unqiue identifier, I would like to ask you to consider expanding the
scope of your work to include these others. The needs are similar -
unquely identify a certain item (whether it be a party, core component
or a specific BPSSS) and allow the following:
1. A URN based UID or OID that can be used to retrieve additional
metadata about the item.
2. Identify it uniquely.
Would you consider such?
Also - it has been suggested that this document belong in the
Archtiecture becuase it spans so many of the other work groups. This
makes sense to me and we have agreed to add this work within the
UN/CEFACT architecture specification. If no one has any grievances with
this, I would like to suggest that is its' home.
Duane
"William J. Kammerer" wrote:
>
> I brought the issue up to Dale Moberg for a separate document describing
> the oasis:names:tc:ebxml-cppa:partyid-type URN. It can be maintained
> independently of the CPP/A specification, and referred to from any of
> the CPP/A, Registry and Messaging Services specs. If someone would ask
> me nicely to devise the document, I might consider volunteering!
>
> William J. Kammerer
> Novannet, LLC.
> +1 (614) 487-0320
> +1 (614) 638-4384 (c)
> +1 (928) 396-6310 (FAX)
>
>