GS1 ONS and Digital Link Tutorial, Auto-ID Labs, KAIST (Apr 28, 2020)

GS1 Object Name Service
Daeyoung Kim
Apr. 28, 2020
Professor, School of Computing, KAIST
Director, Auto-ID Labs, KAIST
• kimd@kaist.ac.kr, http://oliot.org, http://autoidlab.kaist.ac.kr, http://resl.kaist.ac.kr http://autoidlabs.org http://gs1.org

© Auto-ID Lab Korea / KAIST
Slide 2
ONS Motivation [1/2]
By FDA policy, all medical equipment should have UDI from GS1

Slide 3
ONS Motivation [2/2]
I don’t know what
it exactly means..
Also it’s not enough..
When you try to use it, however,
I have an UDI reader machine,
but..

Slide 4
ONS Intro [1/2]
Service server
Access
Object Name Service
(ONS)
GS1 ID
from clients
Service List
manual
html
epcis
…

Slide 5
ONS Intro [2/2]
Object Name Service
(ONS)
Available for all other things which have GS1 ID
GS1 ID
from clients
Service server
Access
Service List

Slide 6
Object Name Service
(ONS)
SGLN
GIAI
GSRN
manual
html
epcis
…
Tour bus in Busan(GIAI)
Tour bus station at Busan station(SGLN)
Tour bus drivers(GSRN)
ONS Application
Access
Service List
https://play.google.com/store/apps/details?id=com.AutoIDLabs.KAIST.GS1Beacon&hl=en_US

Slide 7
Object Name Service 2.0 Specification
 ONS (Object Name Service) uses DNS (Domain Name System)
 GS1 takes advantage of existing standards and infrastructure.
 ONS use internet DNS to look up GS1 identification key.
 GS1 identification keys are converted to domain names.
 The results are returned in a valid DNS Resource Record (RR).
 Dynamic Delegation Discovery System (DDDS) algorithm
 to find trusted metadata and services associated with a given GS1 identification key.

Slide 8
Difference between DNS and ONS
 Domain Name System (DNS)
 DNS translates domain names to IP addresses so browsers can load Internet resources
 Object Name Service (ONS)
 Finds services related with a GS1 identification key using DNS

Slide 9
Domain Name System (DNS)
Client’s View
 Used to determine the IP address of a fully qualified domain name (FQDN) such as
"www.gs1.org"
 Minimum information required for DNS Resolver to obtain information about a query: the
domain name being queried and the type of resource record (RR) requested.
 In the above example, to obtain Mail Exchange information, a Resource Record can be obtained
by specifying the domain name (“dns: //corp.example.com”) and the desired type of information
(“MX”).
Java coding example

Slide 10
Domain Name System (DNS)
Publisher’s View
 Data related to the
domain name is
included in the
resource records (RR)
 RR defines some
attributes of domain
names such as IP
addresses, text strings,
and mail routes

Slide 11
Object Name Service (ONS)
 A service that looks up static information
(services) for a specified GS1
identification key using the Internet's
existing Domain Name System (DNS)
protocol.
ONS in Oliot
(Open Language for Internet of Things)
ONS lookup for service
information (E.g. product
information service)

Slide 12
ONS Application ONS Client
EPCIS Server
ONS Peer Roots
(1)
(2)
(3)
(6) (7)
Local caching
nameserver
(5)
(8)
(4)
ONS Structure
Federated ONS Infrastructure
GS1 ID AUS
Application unique
string
FQDN
Fully qualified
domain name
NAPTR records
Name authority
pointer
The result is returned in the DNS
record type NAPTR
(Naming Authority PoinTeR)
[RFC 3403].

Slide 13
 ONS does not support serial number level queries, but supports class level queries.
 Queries requesting things information of the same type but not identical to each other, that is, instance
level queries
 Instance level vs. Class level
 How to process instance level queries?
 Can be obtained by additionally querying the serial number for the application layer service specified by
ONS
Serial Number level query?
Class level(Coca Cola)
Instance level
(Coca Cola B)
Instance level
(Coca Cola A)
Class level(Pepsi)
Instance level
(Pepsi B)
Instance level
(Pepsi A)

Slide 14
• Extract the desired GS1 ID key type and GS1 ID key from the GS1 list read from the reader.
• (00)306141417782246356(02)50614141322607(37)20
Type: GTIN (02) Key: 50614141322607
• Structure of AUS
• Language code | Country code | GS1 ID Type | GS1 ID Key
• Optional fields without values are encoded using an empty string and all field delimiters are required
• AUS Conversion example
• GTIN 0614141665815, English service in Canada
AUS: en|ca|gtin|0614141665815
ONS Application
GS1 ID AUS
Convert GS1 ID to Application Unique String (AUS)

Slide 15
• According to RFC 3402, AUS becomes the initial input for DDDS applications
• AUS consists of:
 Lowercase ISO 639-1 language code for the client querying the database (optional)
 Lowercase ISO 3166-1 alpha-2 country code for clients querying the database (optional)
 Lowercase GS1 identification key type abbreviation
 Full length GS1 identification key itself and serial number
 Each field in AUS is separated by a vertical bar ('|', ASCII 124: 10 decimal or 0x7C: 16 decimal)
Convert GS1 ID to Application Unique String
(AUS)

Slide 16
• From AUS to FQDN
AUS
FQDN
||gtin|00614141322602
0 0614141 32260 2
indicator company prefix itemref check
00614141322602 Strip checksum
0.061414132260 Hold indicator
0.062231414160 Reverse all remaining characters
0.0.6.2.2.3.1.4.1.4.1.6.0. Append a ‘.’
0.0.6.2.2.3.1.4.1.4.1.6.0.gtin Append ID key type
0.0.6.2.2.3.1.4.1.4.1.6.0.gtin.gs1.id
0.0.6.2.2.3.1.4.1.4.1.6.0.gtin.gs1.id.onsepc.com
Append ‘.gs1.id.’
Append peer root
ONS Application ONS Client
AUS FQDN
Convert AUS to Fully Qualified Domain Name
(FQDN)

Slide 17
• ONS query
• Fully Qualified Domain Name (FQDN) Query for ONS Query Response
• ONS query response
• A series of Naming Authority PoinTeR (NAPTR) records
ONS Formal Specification
- ONS query response
ONS Query
ONS Query response
ONS Client
Local caching
nameserver
ONS Peer Roots
0.0.6.2.2.3.1.4.1.4.1.6.0.gtin.gs1.id.onsepc.com

Slide 18
Why Federated Model?
• DNS-based ONS lookup functionality is implemented by distributed servers with a single
(replicated) Root ONS currently on onsepc.com
• However, ONS’s governance model and architecture raises concern within some industrial and
political communities.
• One Root ONS is more likely to encounter security issues
• Fatal if problems occur in weapons, nuclear waste or sensitive application product recalls, anti-
counterfeiting applications, or logistics applications that may mean food or drug safety controls.
• Also, because laws vary from country to country, there is a lot of trouble for one Root ONS to
follow the laws of various countries.
• Therefore, each country has a peer root ONS and exchanges information between it.

Slide 19
• Nameserver (NS) delegation
• When the target Name Server is currently under ONS Peer Root
• Delegation name (DNAME) delegation
• When the target Name Server is under another ONS Peer Root
• Using the GS1 prefix (last 3 digits), delegate to the ONS Peer Root of target country
Federated ONS
- Delegation
GS1 Prefix Domain Country
1.6.0 onsepc.com America
0.8.8 onsepc.kr Korea
0.0.3 onsepc.fr France
Korean
ONS Peer Root
American
ONS Peer Root
French
ONS Peer Root
ONS Server
In Korea
ONS Server
In America
ONS Server
In France
NS Delegation
DNAME Delegation
~.1.4.1.4.X.X.X.gtin.gs1.id.onsepc.XXX

Slide 20
ONS peer Roots
Local system
ONS
Application
ONS
Client
Recursive Name
Server
EPCIS Server
DNS
Query
DNS
Response
Korean Root
onsepc.kr
Local ONS
American Root
onsepc.com
Local ONS
Local ONS
French Root
onsepc.fr
Federated ONS
- NS Delegation
1
2
3
4
5 6
~.0.8.8.onsepc.kr.
Resolution
Success

Slide 21
ONS peer Roots
Local system
ONS
Application
ONS
Client
Recursive Name
Server
EPCIS Server
DNS
Query
DNS
Response
Korean Root
onsepc.kr
Local ONS
American Root
onsepc.com
Local ONS
Local ONS
French Root
onsepc.fr
Federated ONS
- DNAME Delegation
1
2
3
45
6 7
~.1.6.0.onsepc.kr.
Resolution
Success

Slide 22
ONS peer Roots
Local system
ONS
Application
ONS
Client
Recursive Name
Server
EPCIS Server
DNS
Query
DNS
Response
Korean Root
onsepc.kr
Local ONS
American Root
onsepc.com
Local ONS
Local ONS
French Root
onsepc.fr
Local ONS
Chinese ONS Root
ons.epcglobal.cn
Federated ONS
- GS1 Prefix Updated Case : Not Synchronized
1
2
3
~.0.9.6.onsepc.kr.
Resolution
Failure

Slide 23
Peer Delegation file
• Peer Delegation File
• File that exchanges information needed for DNAME delegation between
ONS Peer Roots
• Notify other ONS Peer Roots via this file when there is a change in
information on any ONS Peer Root
• All ONS Peer Roots can share a table that allows GS1 Prefix and Domain to
match each other.
• Example
• If Chinese ONS Peer Root is added, Peer Delegation File is notified to other ONS
Peer Root so that all ONS Peer Root can share the same table as below.
0.9.6 ons.epcglobal.cn China

Slide 24
Peer Delegation file example (1/2)

Slide 25
Peer Delegation file example (2/2)

Slide 26
ONS peer Roots
Local system
ONS
Application
ONS
Client
Recursive Name
Server
EPCIS Server
DNS
Query
DNS
Response
Korean Root
onsepc.kr
Local ONS
American Root
onsepc.com
Local ONS
Local ONS
French Root
onsepc.fr
Local ONS
Chinese ONS Root
ons.epcglobal.cn
Federated ONS
- GS1 Prefix Updated case: Synchronized
1
2
3
5
6 7
4
0.9.6 ons.epcglobal.cn China
~.0.9.6.onsepc.kr.
Resolution
Success

Slide 27
ONS DDDS Database [1/7]
• NAPTR RR
• ONS contains pointers to trusted information about GS1 identification keys in the DNS
database.
• DNS Type Code 35 (NAPTR) Record [RFC 3403]
Format of NAPTR RR

Slide 28
• NAPTR RR field definitions
• Pref –Nonnegative integer
• When a service in one record has the same service field, this indicates the priority with services in the
other record
• For example, to specify a secondary backup server so that it is used only when the primary server
fails.
• Flags
• Set to "u" to indicate that the Regexp field contains a URI, or "t" to indicate that the Regexp field
contains plain text.
• Services
• URI to access service type
• Regexp
• Specify regular expressions and service addresses to be applied for AUS language and country codes
• Replacement
• Not used, simply appoint “.”

Slide 29
• ServiceType
• ONS supports a dynamic service definition model that allows you to define GS1 Global, the GS1
Member Organization, industry groups, members, service providers, or any component that actually
wants to publish services based on GS1 identification.
• Service definitions can be scoped at the global and local level.
• The service type URL represents an XML document describing the service, which may not be
publicly accessible.
• You may need credentials to access the document (e.g. basic HTTP authentication, FTP
username and password).

Slide 30
• ServiceType.xml Schema

Slide 31
• ServiceType.xml

Slide 32
• Services / Service Type Class
Field Description
ServiceTypeIdentifier Service type identifier, a URL where the XML representation of this structure can be found.
Abstract True if this is an abstract service type; the abstract service type is used as the base type for other service types, not
its own concrete implementation.
Extends Service type identifier extended by this service type
TimeToLive TimeToLive in minutes, cached on client for published time.
WSDL Location (address) of web service description language file
HomePage A page that provides a homepage address, typically a basic overview of a service type, and can contain links to
associated service types.
Documentation Multilingual documentation of the service type.
Obsoletes Service identifier list for service type version management, list of previous version service type of current version
ObsoletedBy Service identifier list for service type version management, list of later version service type of current version

Slide 33
Service Type XML example

Slide 34
Example
- ONS Query Conversion and Response
(1)
ONS Peer Roots
Product Mobile
Shop Infomation
(2)
(3)
(4)
(5)
(6)
Service Type
Server
Service provide server
ONS Infrastructure
ONS Query
flow
Broadcast GTIN of
Product
Product Advertising
Beacon
Provider
Server

Slide 35
Example
- Response of NAPTR

Slide 36
Example
- Description of NAPTR Response
Each column of NAPTR has the following meaning
1. Represents a GS1 Company Prefix in an inquired GS1 code.
-! ^. * $! 06,7! Regexp means GS1 company prefix starting with “06” is 7 digits long.
2. Represents an EPCIS address containing information from the GS1 code.
- Get the URL of the EPCIS server.
3. Represents an Internet page with information about mobile commerce data providers.
- Regexp gets the URL of the mobile commerce server for French and Canadian data.
4. 5. 6. 8. Represents an Internet page with information about mobile commerce data providers.
- Same service type as before, but provides appropriate internet pages based on AUS language and country
code.
7. Represents an Internet page with information about mobile commerce data providers.
- If the first six URLs do not respond, the URL for this record is used.

Slide 37
Example
- Search for GS1 Company Prefix
(1)
ONS Peer Roots
Company Prefix
(2)
(3)
(4)
(5)
(6)
Service Type
Server
ONS Infrastructure
GTIN
50614141322607
Product Advertising
Beacon
Provider
Server
5.0.6.2.2.3.1.4.1.4.1.6.0.gtin.
gs1.id.onsepc.com
Company
Prefix
0614141

Slide 38
Example
- Search for EPCIS Server
(1)
ONS Peer Roots
EPCIS
Information
(2)
(3)
(4)
(5)
(6)
Service Type
Server
ONS Infrastructure
GTIN
50614141322607
Product Advertising
Beacon
Provider
Server
5.0.6.2.2.3.1.4.1.4.1.6.0.gtin.
gs1.id.onsepc.com
http://epcis.example
.com/
EPCIS

Slide 39
Example
- Search for a mobile commerce service
(1)
ONS Peer Roots
Product Mobile
Shop Information
(2)
(3)
(4)
(5)
(6)
Service Type
Server
ONS Infrastructure
GTIN
50614141322607
Product Advertising
Beacon
Provider
Server
5.0.6.2.2.3.1.4.1.4.1.6.0.gtin.
gs1.id.onsepc.com
http://es-
us1.example.com

Slide 40
Web Based ONS Record Management and Access
Delegation
• Oliot-ONS
• Web based ONS records management
• Secure access delegation to others
• ONS Managing API
• Add/edit/delete records
• Manage access control
• Authentication
• PostgreSQL based oauth 2.0 server
• Store users’ authentication information (e.g.
ID, PW, token)
• Access Control
• Neo4j based access control
• Dynamic modification and easy
visualization of access relationships
• ONS Server
• PowerDNS : process ONS query
• MySql : back-end DB storing ONS records
Web Enabled Devices
ONS Managing API
Access ControlWeb Server
ONS Server
Back-end DB
PowerDNS
ONS Server
Back-end DB
PowerDNS
Manage
ONS Infrastructure
Authentication

Slide 41
Oliot ONS System Overview
ONS ServerONS Management Web Server
ons_wep
_app
ons_web
_api
ons_db_
api
PostgreSQL Neo4j MySQL
PowerDNS
ONS
Manager
Web GUI based
Records management
Web API based
Records management
User
ONS query/response

Slide 42
ONS Tutorial
- Oliot-ONS source code
• How to get Source code?
• Using GIT
• $ git clone https://github.com/gs1oliot/oliot-ons-1.1.git
• Components of Oliot-ONS source code
• oliot-ons-web-app
• User friendly GUI based web application
• oliot-ons-web-api
• Restful web API managing ONS records and access control
• oliot-ons-db-api
• Restful web API accessing back-end DB of ONS server
• oliot-ons-docker-config
• Set of shell scripts for building and running pdns & DB containers on Docker
engine

Slide 43
ONS Tutorial
- Oliot-ONS PDNS and DB Set Up
• Prerequisite
• Docker
• Manual for installation of Docker on Ubuntu
• https://docs.docker.com/engine/installation/linux/ubuntulinux/
• oliot-ons-docker-config
• mysql_docker, postgre_docker, neo4j_docker, pdns_docker
• Build docker image (mysql_docker, postgre_docker only)
• $ sh docker_build_image.sh
• Modify docker_run_container.sh for your purpose (you need to change
environment parameters for password at least)
• $ vi docker_run_container.sh
• Run docker image
• $ sh docker_run_container.sh

Slide 44
ONS Tutorial
- Oliot-ONS Web Services Set Up
• oliot-ons-web-api, oliot-ons-db-api, oliot-ons-web-app
• Build docker image
• $ sh docker_build_image.sh
• Make config dir. & Copy example_conf.json to ./config/conf.json
• $ cp example_conf.json ./config/conf.json
• Modify ./config/conf.json for your purpose
• $ vi ./config/conf.json
• Run docker container (you may need to change path for ./config folder if
you do not clone oliot-ons-1.1 in home folder)
• $ sh docker_run_container.sh
• Bug exists for oliot-ons-web-api. You need to retry this several times until container is
correctly ran.
• Reference
• Docker information:
https://docs.docker.com/engine/reference/commandline/cli/
• Pdns information: https://doc.powerdns.com/3/

Slide 45
Example: ONS Record Management
- Main page
• Open web app in the browser
• http://localhost:4000
• Since you do not have ID yet, click ‘sign up’

Slide 46
– Sign up
• Sign up page opens
• http://localhost:4000/signup
• Select user type
• Choose company now
• Type your own ID and password and click ‘sign up’ button
• If sign up is correctly finished, automatically back to login page
• Otherwise, stay in this page with error
• Tip: your authentication (PostgreSQL) and access control (Neo4j) database may have problem

Slide 47
- Log in
• If login page is showed up normally
• Type you ID and password
• You would get temporally valid token from authentication server
• But, after token is expired, you need to re-log in to get new token

Slide 48
- ONS server list
• If ID and password are correct, browser shows ONS server list you manage
• You can add, edit, and delete your ONS server

Slide 49
- Add ONS server
• If ‘add new server’ is selected, ‘addserver’ page opens
• http://localhost:4000/addserver
• Type server information
• Server Address: server address where oliot-ons-db-api is installed
• Do not designate localhost or 127.0.0.1, only public address (ex.www.xxx.yyy.zzz) is possible
• Server Port: server port (default: 4002)
• Database Username: ID for mysql (default: poweruser)
• Database Password: PW for mysql

Slide 50
- New ONS server list after adding server
• If adding new ONS server is correctly finished, new ONS server list is shown
• You can see new ONS server is correctly added (143.248.56.xxx:4002)
• If click ‘delete’ button, clicked ONS server is removed from list
New ONS Server

Slide 51
- Edit ONS server
• If click ‘edit’ button on ONS server list, edit server page opens and domain list is showed up
• http://locahost:4000/server/143.248.56.xxx:4002
• You can also add, edit, and delete your domains for specific ONS server

Slide 52
- Add domain
• If ‘add new domain’ is selected, ‘addDomain’ page opens
• http://localhost:4000/server/143.248.56.164:4002/addDomain
• Type domain name you want add
• Domain name should follow DNS syntax (dotted string)
• ex) 1.8.0.0.0.0.1.2.3.4.5.8.8.gtin.gs1.id.onsepc.kr

Slide 53
- New domain list after adding new domain
• If adding new domain is correctly finished, new domain list is shown
• You can see new domain is correctly added (1.8.0.0.0.0.1.2.3.4.5.8.8.gtin.gs1.id.onsepc.kr)
• If click ‘delete’ button, clicked ONS domain is removed from list
New domain

Slide 54
- Edit domain
• If click ‘edit’ button on the domain list, edit domain page opens
• http://locahost:4000/server/143.248.56.xxx:4002/domain/1.8.0.0.0.0.1.2.3.4.5.8.8.gtin.gs1.id.onsepc.kr
• You can edit this zone by adding or deleting records
• Click ‘save’ button after fill in the blanks, then new record is added
• The record should follow DNS syntax
• Click ‘delete’ button located on the right side of each record, then the record is removed
0 0 "U" "http://www.gs1.org/ons/epcis" "!^.*$!http://stis.iotlab.eu:8
080/epcis-repository-0.6.4/query!" .
New record

Slide 55
Example: ONS query test
• nslookup
• $ nslookup -type=NAPTR <gs1code> localhost(or public IP of localhost)
• If you correctly set up all, you can see NAPTR typed ONS records in response to
the above command including the gs1code (<gs1code>)
• Screenshot

GS1 Digital Link
Daeyoung Kim
Professor, School of Computing, KAIST
Director, Auto-ID Labs, KAIST
• kimd@kaist.ac.kr, http://oliot.org, http://autoidlab.kaist.ac.kr, http://resl.kaist.ac.kr http://autoidlabs.org http://gs1.org
https://www.gs1.org/standards/gs1-digital-link

Slide 57
UPC/EAN

Slide 58
GS1 Data Matrix

Slide 59
QR

Slide 60
QR with GS1 Digital Link URI

Slide 61

Slide 62

Slide 63

Slide 64
GS1 Digital Link
•Digital Link syntax B2B video: https://adobe.ly/31urWRu

Slide 65
• GS1 Digital Link allows multiple services to be connected via a single data carrier by creating a standard
for URI information that includes URLs that can be inserted into existing data carriers, such as 1D and 2
D bar codes, QR codes, datamatrix, RFID, NFC, etc
• GS1 Digital Link is a standard for combining service links (URIs) related to GS1 code into existing data
carriers. Just as the URL address points to a specific website, GS1 Digital Link can connect all objects in
the world to associated services via GS1 code.
GS1 Digital Link

Slide 66
Why GS1 Digital Link?
• Multi-functional data carriers
• It is increasingly common to see multiple data
carriers on a single item. This is because each
one is placed there for a single purpose such as
supply chain operations, point of sale, extended
consumer information and promotional
interaction.
• GS1 DL enables a single code to perform
multiple functions, both online and offline,
reducing the need for multiple codes on a pack
and has the future potential to realize a single
data carrier for all functions.

Slide 67
• Simpler data sharing
• Barcodes and other data carriers have always
been a reference to data about the identified object
stored in a computer.
• GS1 DL connects identified items to limitless
sources of data, whether stored locally or remotely,
whoever they are curated by, enabling many new
possibilities in addition to the data carrier's current
role in supply chain and POS tasks.
• GS1 DL syntax effectively provides a common API
for multiple points on the Web making it easy to
query different sources for information about the
same item.

Slide 68
• Granular identification
• There is a growing demand for more data to be
encoded in the data carrier such as the batch/lot,
expiry date, measured weight and, in some cases,
individual item level identification through
serialization.
• GS1 DL is applicable at all levels of identification
including batch/lot and serialised level.
• GS1 DL can be used with any data carrier, such as
URL, such as QR, NFC or non-GS1 Data Matrix,

Slide 69
• Reduced latency
• When data is copied and aggregated, there is
almost always a delay between the facts on the
ground changing and copies of the data being
updated. This inherent latency can mean that
important updates to the data on which a business
depends are not reflected with due speed.
• Because GS1 DL avoids the need for data
aggregation and simply points to the original
source data, latency is eliminated.

Slide 70
What is Web URI?
• Uniform Resource Identifiers (URIs) consist of URNs and URLs, URLs (Uniform Resource Locators)
refer to addresses to tell you where resources are on the network, and URN (Uniform Resource Name) is
used to refer to the only name worldwide.
• Web URI is a intersection of URN and URLs, which means accessing the data (URL) of a Web service
using the name of an object (URN).

Slide 71
Internal structure of a Web URI
• The Web URI consists of Scheme, Hostname, Path Information, Query String and Fragment ID.
• The service provider can access multiple services using a single URI by inserting a URI up to Path
Information with GS1 code information in the QR code and adding the service user's desired service
to the URI.

Slide 72
Explicit links to related URIs, ideally expressed with
semantic annotation, using Linked Data properties
https://lov.linkeddata.es/dataset/lov/vocabs/dcterms
https://en.wikipedia.org/wiki/Dublin_Core

Slide 73
Explicit links to related URIs, ideally expressed with
semantic annotation, using Linked Data properties
• GS1 Web URI provides a new syntax
• for expressing GS1 Identifier Keys, Key qualifiers and data attributes
in a format that can be used on the Web in an intuitive manner to
enable consumers and others to directly access relevant information
and services about products, assets, locations, etc.

Slide 74
Use of barcodes containing GS1 Web URI and
GS1 barcodes
• One barcode instead of two, therefore increasing supply
chain scanning performance and making consumer
experiences easier and more beneficial than today.

Slide 75
Examples of GS1 Web URIs - GTIN
• (01)00614141123452 - GS1 Element String
• https://id.gs1.org/gtin/614141123452
• https://id.gs1.org/01/614141123452
• https://brand.example.com/gtin/614141123452
• https://brand.example.com/some-extra/pathinfo/gtin/614141123452
• https://retailer.example.com/some-extra/pathinfo/gtin/614141123452

Slide 76
Examples of GS1 Web URIs
- GTIN + Batch/Lot + Serial Number + Expiry Date
• (01)00614141123452(17)180426(10)ABC1(21)12345 - GS1 Element String
• https://id.gs1.org/gtin/614141123452/lot/ABC1/ser/12345?exp=180426
• https://id.gs1.org/01/614141123452/10/ABC1/21/12345?17=180426
• https://example.com/gtin/614141123452/lot/ABC1/ser/12345?exp=180426
• https://example.com/01/614141123452/10/ABC1/21/12345?17=180426

Slide 77
- GTIN + Typed Link
• Redirect directly to the instruction manual for the product
• https://id.gs1.org/gtin/614141123452?linkType=gs1_instructionsForUse
• https://id.gs1.org/01/614141123452?linkType =gs1_instructionsForUse
• https://example.com/gtin/614141123452?linkType =gs1_instructionsForUse
• https://example.com/01/614141123452&linkType =gs1_instructionsForUse
• Note that at this stage, “linkType” is only an example of a key.
Its values have not yet been standardized by GS1

Slide 78
- SSCC with specified Content, Count and Batch/Lot
• GS1 Web URIs for SSCC 106141412345678908 containing a count [ AI (37) ] of
25 instances of Content [ AI (02) ] 00614141123452 having Batch/Lot identifier
[ AI (10) ] 'ABC123'
• https://id.gs1.org/sscc/106141412345678908?02=00614141123452&37=25&10=ABC123
• https://id.gs1.org/00/106141412345678908?02=00614141123452&37=25&10=ABC123

Slide 79
- Physical location represented by a GLN or GLN + GLN Extension
• (414)0614141123452(254)32a%2Fb - GS1 Element String
• https://id.gs1.org/gln/0614141123452
• https://id.gs1.org/414/0614141123452
• https://id.gs1.org/gln/0614141123452/glnx/32a%2Fb
• https://id.gs1.org/414/0614141123452/254/32a%2Fb

Slide 80
Resolving Protocol
• For redirection, use of HTTP response 302 (Found) is not recommended because of a number of
inconsistent implementations in clients. It is safer and more flexible to use HTTP response 307 (Temporary
Redirect) since this has been implemented more consistently and also provides greater flexibility in
changing redirections, since it is not cached by the client or web browser.

Slide 81
Resolving Protocol
- Simple Resolution

Slide 82
Resolving Protocol
- Chained Resolution

Slide 83
Resolving Protocol
- Replacing the domain to call an alternative resolver
• To provide additional information from other parties, including information about price
comparison, availability and promotions, as well as comparisons with related products.
• Link to independent accreditation agencies who certify claims about the product. (such as
organic status, fair trade status, sustainable sourcing etc.)

Slide 84
Resolving Protocol
- Retailer operates their own resolver

Slide 85
Thank you, new version 1.1 published

GS1 ONS and Digital Link Tutorial, Auto-ID Labs, KAIST (Apr 28, 2020)

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à GS1 ONS and Digital Link Tutorial, Auto-ID Labs, KAIST (Apr 28, 2020)

Similaire à GS1 ONS and Digital Link Tutorial, Auto-ID Labs, KAIST (Apr 28, 2020) (20)

Plus de Daeyoung Kim

Plus de Daeyoung Kim (20)

Dernier

Dernier (20)

GS1 ONS and Digital Link Tutorial, Auto-ID Labs, KAIST (Apr 28, 2020)