Current approved method for PartyId/@type values derived from ISO6523 code list.

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

From the Appendix F

 

Method to Generate Values for the “type” Attribute from Information Items in the [ISO6523] ICD List

 

While both [ebMS] and [ebCPPA] mention the idea that the URN for the PartyId/@type attribute would come from a well-known directory of organization identifiers,  no example is given  except in tp:type="urn:oasis:names:tc:ebxml-cppa:partyid-type:duns". The following method provides standardization for the URNs used as PartyId/@type values when using [ISO6523]. The example value for DUNS from the specification may, of course, be used but so may the standardized values found below. None of the rules,  requirements or recommendations of either [ebMS] or [ebCPPA] are modified by the standardization suggested below. It is recommended that implementers provide support, and be able to accommodate, the usage of the “type” values standardized by following the method next described.

 

1. If an abbreviated name is described in the item titled “Name of Coding System” within the ICD list, a “type” attribute can be constructed by prepending “urn:oasis:names:tc:ebxml-cppa:partyid-type:” to the abbreviated name and appending a colon “:” followed by the ICD value.

 

Example:

Using abbreviated name D-U-N-S Number:

Abbreviated Name: “D-U-N-S Number”

Upper-camel-case resultant string: “D-U-N-SNumber”

tp:type=" urn:oasis:names:tc:ebxml-cppa:partyid-type:D-U-N-SNumber:0060"

 

Note: “0060” is the ICD value of D-U-N-S Number. Also, the value

“urn:oasis:names:tc:ebxml-cppa:partyid-type:duns” remains a valid type attribute value for the PartyId element.

This value was specified previously in the version 2.0 CPPA specification.

 

2. Because an abbreviated name may be omitted from the ICD list, the “type” attribute can always contain the string derived from “Name of Coding System” expressed ininto upper-camel-case. A value can always be constructed by prepending “urn:oasis:names:tc:ebxml-cppa:partyid-type:” to the upper-camel-case name and appending a colon “:” followed by the ICD value.

 

Example:

Using formal name:

 

Name of Coding System(formal name): “Data Universal Numbering System”

Transformed Camel-case: “DataUniversalNumberingSystem”

 

tp:type=" urn:oasis:names:tc:ebxml-cppa:partyid-type:DataUniversalNumberingSystem:0060"

 

3. Punctuation marks in these formal names (such as, “/”, “-“ or “’” ) should be included unless they are not allowed in URNs  [RFC 2141]. If the punctuation characters are not allowed in URNs, then the hexadecimal escaping convention explained in [RFC 2141] should be followed for characters not allowed in URNs. However, spaces are not allowed in URNs and should be consumed during the production of an upper-camel-case string, rather than preserved in an escaped form. Words in names that are all upper-case should remain so when converted to an upper-camel-case string.

 

4. The ICD value should be appended as the last field of the URN so that any collision between formal or abbreviated names is avoided.