1. Description

In eDelivery, the OASIS ebCore Party Id Type specification is the recommended notation for party addressing. It can be used in the AS4 PartyId header, in the e-SENS AS4 originalSender and finalRecipient message attributes specified in eDelivery AS4, in eDelivery BDXL records and in eDelivery SMP. This eDelivery specification provides additional implementation guidelines for the OASIS ebCore Party Id Type specification.

The OASIS ebCore Party Id Type specification provides a standard URN-based syntax [RFC8141] for party identifiers and identifier types using the formally IANA-registered [URNFN] OASIS namespace [RFC3121]. It is used in Australia, Europe and Japan. A variety of naming identifier schemes are in existence and used internationally, such as GS1 Global Location Numbers (GLN), Dun & Bradstreet DUNS numbers, and various national business registry numbers. ISO is a global registration authority for such schemes and maintains the ISO 6523 catalog. The ebCore Party Id Type standards define a standard URN syntax for entities registered in schemes registered in ISO 6523 and other schemes. The ebCore Party Id Type is recommended in CWA 16036 and 16464-1.

2. Base Specifications

This specification is based on the following specifications:

• OASIS ebCore Party Id Type Technical Specification. OASIS Committee Specification. September 2010. http://docs.oasis-open.org/ebcore/PartyIdType/v1.0/PartyIdType-1.0.pdf
• ISO/IEC 6523-1:1998. Information technology – Structure for the Identification of organizations and organization parts – Part 1: Identification of organization identification schemes. http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=25773

The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this specification are to be interpreted as described in [RFC2119].

3. Implementation Guidelines

The OASIS ebCore specification supports the ISO 6523, ISO 9735 and ISO 20022 schemes. In e-SENS, the ISO 9735 MUST NOT be used (all domains in this scheme are also in ISO 6523). The ISO 20022 scheme MUST NOT be used for domains also registered in ISO 6523.

When using the ebCore party identifier syntax described in section 2.7 of the ebCore Party Id Type specification, the identifier type and the identifier value MUST be separated using a single ":" colon character. The double colon syntax described in section 2.4.5 of the OASIS SMP specification and subsections of that section is not a valid ebCore party identifier and MUST NOT be used.

For ISO 6523, the ebCore specification supports multiple identifier prefixes. In Delivery, prefixes other than urn:oasis:names:tc:ebcore:partyid-type:iso6523: MUST NOT be used.

Identifier domains not yet registered in ISO 6523, but needed for use with eDelivery, MAY be identified using the urn:oasis:names:tc:ebcore:partyid-type:unregistered: prefix. However, it is RECOMMENDED that organizations representing any such domains register with the ISO 6523 registry.

4. Ownership

The ebCore Party Id Type Technical Specification is Copyright © OASIS® 2010. All Rights Reserved.

The ebCore Party Id Type Technical Specification was created by the OASIS ebXML Core (ebCore) TC which operates under the RF on Limited Terms Mode of the OASIS IPR Policy. OASIS is not aware of any statements or declarations regarding IPR related to the work of this technical committee.

This specification was created in the former EU e-SENS project. The e-SENS project completed in March 2017. The EU e-SENS project formally transferred ownership of its specifications to the European Commission, which accepted it for further maintenance initially in the context of the CEF Programme and then of the Digital Europe Programme. Information on governance and procedures for eDelivery is available from Governance and Procedures.

5. References

[CWA16036] CWA 16036, Unique Identification Systems For Organizations and Parts Thereof. November 2009.  ftp://ftp.cen.eu/CEN/Sectors/TCandWorkshops/Workshops/CWA16036CyberID.pdf.

[CWA16464-1] CWA 16464-1 Electronic invoicing - Part 1: Addressing and Routing. CEN WS on E-Invoicing. May 2012. ftp://ftp.cen.eu/CWA/CEN/eInv/CWA_16464-1.pdf.   

[ISO6523] ISO/IEC 6523-1:1998. Information technology – Structure for the identification of organizations and organization parts – Part 1: Identification of organization identification schemes. http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=25773

[PARTYIDTYPE] OASIS ebCore Party ID Type Technical Specification. September 2010. http://docs.oasis-open.org/ebcore/PartyIdType/v1.0/PartyIdType-1.0.pdf

[RFC2119] A. Ramos. Key words for use in RFCs to Indicate Requirement Levels. IETF RFC 2119. January 1998. http://www.ietf.org/rfc/rfc2119.txt

[RFC3121] A URN namespace for OASIS. June 2001. IETF RFC 3121. http://tools.ietf.org/html/rfc3121

[RFC8141] URN Syntax. April 2017. IETF RFC 8141. http://www.ietf.org/rfc/rfc2141.txt. https://tools.ietf.org/html/rfc8141

[SMP-v1.0] OASIS Service Metadata Publishing (SMP) Version 1.0. http://docs.oasis-open.org/bdxr/bdx-smp/v1.0/bdx-smp-v1.0.pdf

[URNFN] IANA. Uniform Resource Names (URN) Formal Namespaces. http://www.iana.org/assignments/urn-namespaces/urn-namespaces.xml#urn-namespaces-1.

6. Contributors

The eDelivery team is in charge of maintaining the current version of this specification.

Details about contributors of previous versions can be consulted on the e-SENS website.

7. History

Details about previous versions of the specifications can be consulted on the e-SENS website.