RE: [ebxml-cppa] PartyId/@type minor revision proposal

["Dale Moberg" <dmoberg@us.axway.com>]

The March 30 teleconference (a rescheduled meeting) will have this item on the agenda and we will have at least a preliminary vetting.

 

The point that Pim raises is well-taken, and is an unfortunate side-effect of the fashionable use of verbose URNs as identifiers for semantic constants or collections of such constants. Perhaps a revival of ISO OIDs--the dotted decimal identifiers that served much the same function many generations ago—should be scheduled. Anyway,

 

Because this item references a TC approved appendix for the next release, we will need to get representatives from ECOM to review this proposal as well.

 

Those who have ECOM current contacts should forward references to this issue to the interested parties for their comments.

 

Dale Moberg

Chair, OASIS ebCPPA TC

 

 

---

From: Pim van der Eijk [mailto:pim.vandereijk@oasis-open.org]
Sent: Monday, March 19, 2007 8:36 AM
To: 'OASIS ebXML CPPA TC'
Subject: [ebxml-cppa] PartyId/@type minor revision proposal

 

 

Hello,

 

Section 24 of the CPPA editor's draft http://www.oasis-open.org/committees/download.php/12208/ebcpp-2.1-april-5-2005-draft.doc describes how to construct a PartyId/@type for organizations registered in a classification system itself registered in ISO 6523.  It concatenates "urn:oasis:names:tc:ebxml-cppa:partyid-type:" with the ISO 6523 name in Upper Camel Code followed by the code.  ISO 6523 organizations are listed at:  http://asn1.elibel.tm.fr/oid/doc/ICD-list.htm.  

I have some comments and a small change request:

 

The use of both name and code is redundant and will result in extremely long names. The full name of the coding system ICD 0106 is "Vereniging van Kamers van Koophandel en Fabrieken in Nederland (Association of Chambers of Commerce and Industry in the Netherlands) Scheme (EDIRA compliant)".  Even leaving out the English translation, this would produce the following very long PartyId :

 

<eb:PartyId eb:type="urn:oasis:names:tc:ebxml-cppa:partyid-type:VerenigingvanKamersvanKoophandelenFabriekeninNederland:0106">30173541</eb:PartyId>

The RosettaNet MMS uses the mechanism specified in the CPP 2.1 draft, but the value used is not the literal name string from the 6523, which is "Data Universal Numbering System (D-U-N-S Number)" but just "D-U-N-SNumber". If the names are not literally copied from the registry but abbreviated, this list of abbreviated 6523 names itself would need to be managed to be interoperable.

 

<tp:PartyId tp:type=" urn:oasis:names:tc:ebxml-cppa:partyid-type:D-U-N-SNumber:0060">123456789</tp:PartyId>

 

Second, there are other registration systems than ISO 6523.  ISO 15459 also defines some system of Issuing Agency Codes.

Values are provided in Annex 4 of http://repository.edifice.org/Cross%20Business%20Area%20Library/GUI_2.pdf.

Section 5.2 of that document also describes a way of constructing RosettaNet GlobalBusinessIdentifiers using this mechanism: 

 

<GlobalBusinessIdentifier>LEMFT</GlobalBusinessIdentifier>

LE: Issuing Agency Code for EDIFICE
MFT : Company identification number for : Manufacturer of EC devices

 

It would be nice if the ebXML PartyId system could support both ISO 6523 and 15459 codes.

 

Proposal:

1) Introduce an intermediate level to indicate which system for classification registries used.

Initial values could be "iso6523" or "iso15459".  Other values than "iso6523" and "iso15459" are possible too, and as long as the values aren't 6523 names, a system could support both the proposal in the CPPA 2.1 draft and this proposal (when backward compatibility is important).

 

2) Only use the code, not code and name. 

 

Examples:

<eb:PartyId eb:type="urn:oasis:names:tc:ebxml-cppa:partyid-type:iso6523:0106">30173541</eb:PartyId>

<eb:PartyId eb:type="urn:oasis:names:tc:ebxml-cppa:partyid-type:iso6523:0060">123456789</eb:PartyId>

<eb:PartyId eb:type="urn:oasis:names:tc:ebxml-cppa:partyid-type:iso15459:LE">MFT</eb:PartyId>

 

Variants:

If there is a preference to keep the "partyid-type" level reserved to 6523 agencies, it would still be possible to just use the code.

The examples would then look like:

 

<eb:PartyId eb:type="urn:oasis:names:tc:ebxml-cppa:partyid-type:0106">30173541</eb:PartyId>

<eb:PartyId eb:type="urn:oasis:names:tc:ebxml-cppa:partyid-type:0060">123456789</eb:PartyId>

 

Interpretation of the value would be the same a specific to the issuing agency (e.g. GLNs are concatenations of company prefixes and location references).

 

Pim