GFTBL Identifers

The Global Traceability Framework for Beef & Leather uses the following identifiers:

• Product Definition Identifier
  • Global Trade Item Number (GTIN)
• Product Identifier
  • Electronic Product Code (EPC)
• Location Identifier
  • Global Location Number (GLN)
• Party Location Identifier
  • Party Global Location Number (PGLN)
• Logistical Unit Identifier
  • Serail Shipping Container Code (SSCC)

Within the Global Traceability Framework for Beef & Leather, identifiers use the formats established by GS1 and expanded upon by the Global Dialogue on Seafood Traceability (GDST).

GS1 Identifiers

GS1 Identifiers (e.g. GTIN, GLN, etc...) require the use of a GS1 registered company prefix. However, neither EPCIS 2.0 nor this framework require the use of GS1 Identifiers. EPCIS-compatible identifiers can be created and used according the method described below; these identifiers are referred to as GDST Identifiers.

EPCIS 2.0 has introduced digital link identifiers as the preferred format for representing identifiers such as a GTIN, GTIN+Lot, GTIN+Serial Number, GLN, or Party GLN. The following are examples of the identifiers in the Digital Link Format:

• EPC Class (GTIN + LOT)
  • https://id.gs1.org/01/00860003130308/10/L 1234567890
• EPC Instance (GTIN + SERIAL NUMBER)
  • https://id.gs1.org/01/00860003130308/21/S 1234567890
• GTIN
  • https://id.gs1.org/01/00860003130308
• GLN
  • https://id.gs1.org/416/0860003130308
• Party GLN
  • https://id.gs1.org/417/0860003130308

Framework users that have GS1 registered prefix, should use Digital Link URI identifiers. Per the recommendation of EPCIS 2.0, this framework will REQUIRE that all GS1 Digital Link Identifiers use the canonical resolver domain “https://id.gs1.org,” meaning that the part of the URL prior to the first application identifier must be https://id.gs1.org. This only applies when including the identifiers within an EPCIS event of traceability data. When using the identifiers to request data from a trading partner’s Digital Link resolver it is necessary to use the domain of the trading partner. The GTFBL recommends that Digital Link URI identifiers are used instead of the traditional URN format since the Digital Link URI does not require placing a “.” between the company prefix and the item/location reference of the GTIN/GLN/Party GLN.

GDST Identifiers

Using GS1 Identifiers typically requires an organization to become a GS1 member and license a GS1 Company Prefix. This prefix forms the foundation for all GS1 Identifiers registered to that organization. However, GS1 standards allow for the use of non-GS1 identifiers, as long as they are compatible with GS1-based systems. The Global Directory for Standardized Traceability (GDST) has introduced this type of identifier that does not require a GS1 company prefix to create.

The GDST identifiers may populate an EPCIS event instead of identifiers built with a GS1 prefix (e.g., GTINs, GLNs, PGLNs). They follow the pattern of private or industry-wide URNs for identifiers that are defined in GS1’s Core Business Vocabulary (sections 8.2.3, 8.3.3, 8.4.3, etc.). The URN format is a type of Uniform Resource Identifier which is designed to ensure an identifier is globally unique when referenced between more than one system.

When a company is requesting data through their trading partner’s Digital Link resolver, the GDST identifiers can fill the same role in the GS1 Digital Link URI syntax as a GTIN or other GS1 Identifier:

• https://resolve.example.org/417/urn:gdst:example.org:party:ABC.12345
• https://resolver.example.org/01/urn:gdst:example.org:product:class:FARM1.white_shrimp

These identifiers are meant to only be constructed using URL compatible characters. This allows them to be easily inserted into a URL without any encoding. This is useful for inserting them into the URL when resolving with the Digital Link Resolver.