1 Introduction
ISO/IEC 6523 is a standard whose aim is to define a structure for uniquely identifying organisations and parts thereof in computer data interchange and specify the registration procedure to obtain an International Code Designator (ICD) value for an identification scheme. Some organisations including PEPPOL (Pan-European Public Procurement On-Line) and the European Commission have adopted this standard to discriminate identifiers issued by different organisations. More than 200 ICDs have been allocated so far. These include ICD 0088 for the GS1 Location Number (GLN) and 0160 for the GS1 Global Trade Identification Number (0160). GS1 requested and obtained ICD 0209 to generically refer to other GS1 identification keys.
Previously, only GS1 identifiers GLN (088) and GTIN (0160) could be used in transactional data exchanges based on ISO 6523 (European Norm on eInvoicing EN 16931, Peppol standards, European eProcurement workgroup TC440, …). To be able to use all GS1 identifiers, a new code (0209) has been introduced to provide possibility on using all (and even combined) GS1 identifiers.
2 Purpose
The purpose of this document is to specify the data structure to be used in conjunction with ICD 0209.
2.1 Principles
The following shall be respected:
1. The GS1 Global Location Number (GLN) shall be used with ICD 0088 if not used in combination with extension
2. The GS1 Global Trade Item Number (GTIN) shall be used with ICD 0160 if not combined with any other Application Identifier
3. GS1 ID keys other than GLN and GTIN can be represented using ICD 0209 followed by the appropriate Application Identifier
4. The ICD 0209 shall not be used as an alternative to the normal use of data in a standard EDI message. It shall be restricted to GS1 identification keys
Standard representation of GS1 identification keys with International Code Designators
3 Implementation
The syntax to be used with ICD 0209 is based on:
■ GS1 General Specifications
https://www.gs1.org/standards/barcodes-epcrfid-id-keys/gs1-general-specifications
Implementation based on element strings is possible in two environments:
- Addressing registry:
Rules for 0209 identifiers:
■ MUST be at least 1 character long
■ MUST only contain letters and numeric digits from the invariant character set of ISO-8859-1
■ MUST NOT be more than 50 characters long
■ Values MUST be treated case insensitive
■ Only 1 primary (party) identifier allowed (see chapter 5.2 & 5.4 in GS1 Digital Link Standard)
Examples:
■ Currently used GLN:
<cbc:EndpointID schemeID="0088">5410000999993</cbc:EndpointID>
■ When using GLN with extension:
<cbc:EndpointID schemeID="0209">414541000099999325412345678901234567890</cbc:EndpointID>
■ Same principle can be used with e.g. GSRN:
<cbc:EndpointID schemeID="0209">8018541448820046951753</cbc:EndpointID>
- Data exchange:
Rules for 0209 identifiers:
■ UTF-8
Examples:
■ Currently used GTIN:
<cac:StandardItemIdentification>
<cbc:ID schemeID="0160">7733018600000</cbc:ID>
</cac:StandardItemIdentification>
■ Serialised GTIN using code 0209:
<cac:StandardItemIdentification>
<cbc:ID schemeID="0209">0107733018600000211WUXWGWDX5</cbc:ID>
</cac:StandardItemIdentification>
3.1 Information Sequencing
When encoded, the string must:
■ Start with the ”0209”
■ Followed by the GS1 Key AI
■ Followed by the key value
■ If applicable, followed by the next GS1 Key AI
■ Followed by the key value (according to rules defined in GS1 General Specifications)
A Extract of ICD registry
International Code Designator: 0209
Contributors & Change Log
Contributors
Log of Changes
