GS1 EPCIS and CBV Tutorial, Auto-ID Labs, KAIST (Apr 28, 2020)

GS1 EPCIS & CBV
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 3
EPCIS/CBV Introduction
• Goal of EPCIS
• is to enable disparate applications to create and share visibility event
data, both within and across enterprises.
Ultimately, this sharing is aimed at enabling users to gain a shared
view of physical or digital objects within a relevant business context
• Physical objects include trade items (products), logistic units, returnable
assets, fixed assets, physical documents, etc. .
• Digital objects include digital trade items (music downloads, electronic books,
etc.), digital documents (electronic coupons, etc.) etc. .

Slide 4
• The EPCIS standard defines:
• A data model for visibility event data
• Open, standardized interfaces to enable visibility event data to be
captured and queried using a defined set of service operations and
associated data standards
• A capture interface
• A query interface
• The CBV standard provides definitions of data values that
may be used to populate the data structures defined in the
EPCIS standard

Slide 5
• Example of EPCIS Visibility
Data
• EPCIS data can provide a
detailed record of any or all
of these steps.
• A unit of EPCIS data that
describes the completion of
one business step is called an
EPCIS event
• The information content of
this event is organized into
four dimensions
• What
• When
• Where
• Why

Slide 6
• EPCIS in business applications
• Anti-counterfeiting
• Chain of custody/ownership
• Couponing
• Customs clearance
• Recall
• Sales Promotion
• Traceability
• Business Process Optimization
• Exception Management
• Food Freshness
• Asset Management
• Inventory Management
• Process Documentation

Slide 7
• Anatomy of EPCIS events
The four dimension of EPCIS:
• When
• What
• Where
• why
CBV Vocabulary types:
• Standard
• User defined

Slide 8
• EPCIS Versions
• 1.1 :- May 2014
• 1.2 :- September 2016
• 2.0 :- Expected to be published in 2020
• CBV Versions
• 1.1 :- May 2014
• 1.2 :- October 2017
• 2.0 :- Expected to be published in 2020

Slide 10
Introduction – RFID & GS1 EPCglobal
• Radio Frequency IDentification (RFID)
• Identifiable and Traceable everyday-objects
• The Internet of Things (IoT)
• GS1 EPCglobal
• A complete suite of RFID standards

Slide 11
Introduction – EPCIS Standard
• EPC Information Service (EPCIS)
• to enable disparate applications to create and share visibility event data,
both within and across enterprises
• enabling users to gain a shared view of physical or digital objects within a
relevant business context
• Objects identified either at a class or instance level
• Physical Objects
• Products, logistic units, returnable assets, fixed assets, physical documents
• Digital Objects
• Digital trade items(music downloads, e-books), digital documents (e-coupons, etc.)
• The EPCIS standard applies to all situations in which visibility event data is to be
captured and shared
• No EPC, no RFID requirement

Slide 12
• GS1 Core Business Vocabulary (CBV) standard
• provides definitions of data values that may be used to populate the data
structures defined in the EPCIS standard
• critical to interoperability
• critical to provide for EPC Information Services (EPCIS) querying of data by
reducing the variation in how different businesses express common intent
 Business Step
 Business process
 e.g. Loading, Packing, Shipping, Receiving
 Disposition
 Status of object
 Available for sale, in Storage
 Business Transaction
 Transaction information
 e.g. Purchase, Invoice

Slide 13
• Recent version: version 1.2, Sep. 2016
• A distributed repository, which can capture and share EPC-based
event/vocabulary accompanying 4W
(i.e. What, When, Where and Why)

Slide 14
Introduction –
EPCIS Standard
EPC Information Service (EPCIS)
- deals explicitly with historical data (in
addition to current data)
- deals not just with raw data captured
from data carriers such as bar codes
and RFID tags, but also in contexts
that imbue those observations with
meaning relative to the physical or
digital world and to specific steps in
operational or analytical business
processes
; EPCIS event may indicate
that a perishable trade item has
just crossed its expiration date
(generated by software)

Slide 15
Introduction
“Share” Layer of GS1 Standards
RFID Reader
& Antenna
Barcode
Reader
ALE – Event Capturing
Everyday
Object
EPCIS – Visibility Event Data
TDS – Unification of GS1 Codes
Attaching
EPC Tag
Attaching
Bar Code
GSDN – Master Data
Vocabulary
(EPC, CBV)
Attributes
urn:epc:id:sgtin:1.1.1
urn:epc:id:sgln:1.1.1
Name = Black Coat
Manufacturer = RESL
…
Address = 123 Elm st
City = Anytown
Postal = 12345
Transaction Events
Orders
Invoice
…
EANCOM – Transactional Data
Capturing Interface
Query Interface
Business Apps.

Slide 16
Introduction
Interface & Role of EPCIS
16
EPCIS Capturing Application
EPCIS Capture Interface
EPCIS
Repository
EPCIS Query Interface
(Control and Callback)
Business App.
Fig. EPCIS and its scope
• EPCIS Capturing Application ( Role )
• Capturing Low-level architecture elements
• Providing information source to upper layer
• No redundancy & Filtering using some evaluation
• EPCIS Capture Interface ( Interface )
• Defining a means to transfer
from EPCIS Capturing Application
to EPCIS Repository or EPCIS Accessing App
• EPCIS Repository ( Role )
• Saving One or more event generated by EPCIS Capturing Apps
• Making EPC level event available by EPCIS Accessing Application

Slide 17
Introduction
Interface & Role of EPCIS
17
• EPCIS Query Interface : Control and Callback
( Interface )
• Defining a means for EPCIS Accessing Application
• Providing “Bypass for real-time push”
from EPCIS Capturing Application
to EPCIS Accessing Application
• EPCIS Accessing Application ( Rule )
• Responsibility of Enterprises
• Managing Warehouse
• Managing Shipping
• And so on. EPCIS Capturing Application
EPCIS Capture Interface
EPCIS
Repository
EPCIS Query Interface
(Control and Callback)
Business App.
Fig. EPCIS and its scope

Slide 18
Introduction –
EPCIS Standard
• EPCIS in Relation to
Trading partners
• the flow of data between
trading partners,
emphasizing the parts of
the EPCIS standard
involved in the flow of
visibility event data

Slide 19
Introduction –
EPCIS Standard
• EPCIS Specification
Framework

Slide 20
Introduction – Abstract Data Model Layer
• EPCIS deals in two kinds of data: event
data and master data
• Event data arises in the course of carrying
out business processes, and is captured
through the EPCIS Capture Interface and
made available for query through the
EPCIS Query Interfaces
• Master data is additional data that
provides the necessary context for
interpreting the event data

Slide 21
• Vocabulary Kinds
• to model physical, digital, and conceptual entities that exist in the real
world
• location names, object class names, business step names
• Standard vocabulary
• a set of Vocabulary Elements whose definition and meaning must be agreed to in advance by
trading partners who will exchange events using the vocabulary
• defined by organizations of multiple end users, such as GS1, industry consortia outside GS1,
private trading partner groups, and so on
• User vocabulary
• a set of Vocabulary Elements whose definition and meaning are under the control of a single
organization

Slide 22
Introduction – EPCIS Vocabulary
• Vocabulary (i.e. Master Data)
• Represent static information on EPC
• Core Business Vocabulary (CBV)
• supports base vocabularies for Supply Chain Management
• User Vocabulary
• defined by user
• Vocabularies
• Location: address, zip code, etc
• Business Semantic
• Business Step: activity within a business
process
• Disposition: business state of an object
• Business Transaction: purchase order
• Class-level item
[Examples of CBV]

Slide 23
• Extension Mechanisms
• key feature of EPCIS is its ability to be extended by different organizations to adapt to
particular business situations

Slide 24
• Extension Mechanisms
• key feature of EPCIS is its ability to be extended by different organizations to adapt to
particular business situations

Slide 25
• Identifier Representation
• Event Type names, Event Field names, Vocabulary names, Vocabulary Elements, and Master Data
Attribute Names
• Because all of these namespaces are open to extension, this specification imposes some rules on
the construction of these names so that independent organizations may create extensions
without fear of name collision
• a Vocabulary Element is represented as Uniform Resource Identifier (URI) whose general
syntax is defined in [RFC2396]
• Hierarchical Vocabularies
• Some Vocabularies have a hierarchical
or multi-hierarchical structure
• Store #23 is the parent and the latter two
Store #23 Back Room and Store #23
Front Room are children
• Hierarchical relationships between vocabulary elements are represented through master data.
Specifically, a parent identifier carries, in addition to its master data attributes, a list of its
children identifiers.

Slide 26
Introduction – EPCIS Event
• EPCISEvent – Base event type
• See. 7.2. section
Object Event Aggregation Event Transaction Event Transformation Event
Receiving time at Capturing Application
Receiving time at EPCIS repository
TimeZone, offset from UTC
Extends

Slide 27
• ObjectEvent
• Observation of object(s)
(Optional)
Instance level master data: e.g. expiration date
(Optional)
(Optional)
List of Observed objects
e.g. Created, Observed, Destroyed
c.f Red: new in EPCIS v1.1

Slide 28
• AggregationEvent
• Association between containing/contained object(s)
Aggregation Event
(e.g. box, case, pallet)
e.g. Box, case, pallet
e.g. Trade items in box
e.g. child added, observed, or deleted from parents
(Optional)

Slide 29
• Transaction Event
• (Dis)Association of object(s) to business transaction(s)
Transaction Event
(Optional)
e.g. Item (dis)associated to the BizTransaction
 Business Step
 Business process
 e.g. Loading, Packing, Shipping, Receiving
 Disposition
 Status of object
 Available for sale, in Storage
 Business Transaction
 Transaction information
 e.g. Purchase, Invoice

Slide 30
• Transformation Event
• Capture the relationship between the input (source) and the outputs
(product)
Input Outputs
(Optional)
c.f Red: new in EPCIS v1.1
COW  Slides of Beef

Slide 31
Introduction –
EPCIS Event

Slide 32
Introduction – EPCIS Service
• EPCIS Services
• Event Capture
• Immediate Query
• Scheduled Query

Slide 33
EPCIS Service
Capture Interface
• Capture Interface
• Receiving EPCIS event from ALE
• Storing it into EPCIS distributed repository
33
RFID Reader
& Antenna
Barcode
Reader
ALE – Event Capturing
EPCIS – Visibility Event Data
Capturing Interface
Query Interface
Business Apps.
<<interface>>
CoreCaptureService
Capture(event : List<EPCISEvent> ) : void
<<extension point>>
Argument Type Description
Event List of EPCISEvent Event for Capturing
Event has All related information
( time, EPC , and so on ) except recordTime. RecordT
ime is saved by EPCIS repository or EPCIS Access Ap
plication

Slide 34
EPCIS Service
Query Interface
34
• Query Interface
• Receiving query from Business Apps.
• Returning corresponding data
• Two Types of Query
• On-demand query / Synchronous
• Request and Response way
• By EPCIS Query Control Interface
• Standing Query / Asynchronous
• By establishing a subscription for a periodic query
• By EPCIS Query Callback Interface

Slide 35
EPCIS Service
Query Interface
• Query Interface (Cont.)
• Query Control Interface
• Subscribe/Unsubscribe
• For Standing Query
• Result is transferred to destination descripted by Query Callback Interface
• Poll
• For On-demand Query
35
<<interface>>
EPCISQueryControlInterface
subscribe(queryName : String, params : QueryParams, dest : URI, controls : SubscriptionControls,
subscriptionID : String)
unsubscribe(subscriptionID : String)
poll(queryName : String, params : QueryParams) : QueryResults
…

Slide 36
EPCIS Service
Query Interface
• Query Interface (Cont.)
• Query Callback Interface
• Procedure
• EPCIS executes subscribed query in a periodic manner or a triggered manner
• If success  results go to designated URL
• Else  error messages go to designated URL
36
<<interface>>
EPCISQueryCallbackInterface
callbackResults(resultData : QueryResults) : void
callbackQueryTooLargeException(e : QueryTooLargeException) : void
callbackImplementationException(e : ImplementationException) : void

Slide 37
• EPCIS Next (v1.2)
• Highlights
1. Error Declaration
2. Hierarchical Extension Field

Slide 38
• Highlights
1. Error Declaration
• Enable to capture the revised event for the erroneous event
1. One object is omitted 2. Capture revised one 3. Capture to indicate erroneous event
added

Slide 39
• Highlights
2. Hierarchical Extension Field
• Until v1.1, ‘flat’ extension field only permitted
• From v1.2, Extension field can have a hierarchy
• Extension field can be applied to
• Basic Extension
• ILMD extension
• Error declaration extension

Slide 40
Introduction – EPCIS Application 1
• How to capture the business events of beef cuts
• Based on GS1 Global Forum 2015 tutorial
How?
Guide three fundamental events

Slide 41
• Capture your event 1

Slide 42
• Standard XML format for Event 1

Slide 43

Slide 44

Slide 45

Slide 46

Slide 47
• Visualize it via queries to Oliot EPCIS

Slide 48
Introduction – Oliot EPCIS
open source
• Oliot EPCIS
• Open source web service compatible with EPCIS
• How implemented
• Model Generation
• JAXB on standard XSD
• Service Binding
• SOAP based on standard WSDL
• Verification
• XSD verification
• Running Environment
• Java Web Service ( Java v1.8, Servlet v3.1 )
• Tomcat WAS ( v8.x )
• MongoDB ( v3.2 )
• Services
• Service Bindings: SOAP, REST
• Capture Service
• Event data / Master data
• Query Service
• Standard ‘SimpleEventQuery’ (See EPCIS 8.2.7 )
Backend
Repository
Event Data Master Data
Capture Service Listener
CaptureLayer
Application
QueryLayer
Poll Subscription
Scheduler
Schedule Destination
App
Query Service Receiver
Oliot-EPCIS
SOAP/HTTP
REST/HTTP
Object-Relational Mapper
(POJO  Storage Unit)
JAXB Marshaller
(XMLPOJO)
Document Validator
Capture
Immediate Query
Standing Query
EPCIS DOC
ResultSOAP/HTTP
REST/HTTP
JAXB Unmarshaller (POJO  XML)
(Storage Unit  POJO)
XML/JSON

Slide 49
Installation - Prerequisite
• Install Java 8
• Install Tomcat 8
• Install MongoDB 3.2
• Download ‘epcis.war’ from
• Root folder of https://github.com/JaewookByun/epcis
• Locate ‘epcis.war’ into [tomcat-folder]/webapps
• Visit http://oliot.org to access the latest information and tutorial.

Slide 50
Installation
• Run MongoDB
• Run Tomcat Server
• See it starts
• Access [ip:port]/epcis

Slide 51
Learn how to use
• Access EPCIS clients
http://143.xx.yy.zz:8080/epcis/

Slide 52
Learn how to use
Load existing examples
Insert your events here
Change URL
Capture and see the result
• Access EPCIS capture client

Slide 53
Learn how to use
Add the parameters with UI
See the result
Change base URL
• Access EPCIS query client
Add parameters
Click to query

Slide 54
Learn how to use
• Example 1: eventType=ObjectEvent
1. Add ObjectEvent
2. See the param. Added
and Click Poll
3. See the result

Slide 55
Learn how to use
• Example 2: eventType=ObjectEvent | AggregationEvent

Slide 56
Learn how to use
• Example 3: GE_eventTime=1900-03-23T14:03:45.000Z

Slide 57
Learn how to use
• Example 4: EQ_action=ADD

Slide 58
Learn how to use
• Example 5: EQ_bizStep=urn:epcglobal:cbv:bizstep:receiving

Slide 59
Learn how to use
• Example 6: EQ_disposition=urn:epcglobal:cbv:disp:in_progress

Slide 60
Learn how to use
• Example 7: EQ_eventID=57df3d635d8a88785775ff83

Slide 61
Learn how to use
• Example 8: orderBy=eventTime
Several events are ordered by
eventTime (DESC)

Slide 62
Learn how to use
• Example 9: EXISTS_http://ns.example.com/epcis0%23a=true
namespace

Slide 63
Learn how to use
• Example 10: EQ_http://ns.example.com/epcis0%23a=15^int (for extension field)
namespace Value, type

Slide 64
Programming Guide
• Oliot EPCIS is web service
• Previous slides just for the educational purpose
• Write a code in language independent way
• e.g. C++, Java, Javascript, Python and etc.
• Postman
• Good Tool for your testing
• Sending your HTTP call
• e.g. POST, GET
Now download native app.
• https://www.getpostman.com/downloads/
Method Description
GetStandardVersion Return the standard version of EPCIS
EventCapture Capture your EPCIS Document into your backend storage
VocabularyCapture
Capture your EPCIS Master Data Document into your backend
storage
GetQueryNames Return a list of all query names available
Poll
Return events/vocabularies stored in repository in interest
immediately
GetSubscriptionIDs
Return a list of all subscriptionIDs currently subscribed to the
specified named query
Subscribe
Register a subscriber for a previously defined query having
the specified name
Unsubscribe
Remove a previously registered subscription having the
specified subscriptionID

Slide 65
Programming Guide
• Postman Example (GetStandardVersion)
• Return the standard version of EPCIS
• Set URL
• Then, Send with GET
• See a version if succeed

Slide 67
Programming Guide
• Postman Example (Event Capture)
• Make you capture your events
• Set URL
• Prepare EPCIS document
• Then, Send with POST
• See HTTP.OK (200) if succeed

Slide 68

Slide 69
Programming Guide
• Postman Example (Poll Event
Data)
• Provide you stored events under
conditions you made
• Set URL with Parameter
• See result if succeed
• For more query examples
• See [url:port]/epcis/rest-like-query-
examples.html

Slide 70

Slide 71
Programming Guide
• Postman Example (GetQueryNames)
• Return a list of all query names available
• Set URL

Slide 72

Slide 73
Programming Guide
• Postman Example (Vocabulary Capture)
• Make you capture your vocabularies
• Set URL
• Prepare EPCIS document
• Then, Send with POST
• See HTTP.OK (200) if succeed

Slide 74
Programming Guide
• Postman Example (Poll
Master Data)
• Provide you stored
vocabularies under
conditions you made
• For more query examples
• See [url:port]/epcis/rest-like-master-
query-examples.html

Slide 75
Programming Guide
• Postman Example (Subscribe)
• Provide you ‘periodically’ stored events
to ‘designated URL’
under conditions you made
• You can use ‘Poll’ parameters
• Set additional Parameter
• e.g. dest: Your callback URL
• e.g. cronExpression:
• See Rationale
• See Cron Expression
• Receive periodic result in Callback URL

Slide 76
Programming Guide
• Postman Example (GetSubscriptionIDs)
• Returns a list of all subscriptionIDs currently
subscribed to the specified named query.
• Set URL
• See ID list if succeed

Slide 77
Programming Guide
• Postman Example (Unsubscribe)
• Receive periodic result in Callback URL

스마트시티 (시흥시 실증 도시 예제)

Core Business vocabulary Standard
(CBV)

Slide 80
• The goal of this standard is to specify various vocabulary elements and
their values for use in conjunction with the EPCIS standard [EPCIS1.2],
which defines mechanisms to exchange information both within and
across organization boundaries.
• The CBV provides definitions of data values that may be used to
populate the data structures defined in the EPCIS standard
• The vocabulary identifiers and definitions in this standard will ensure
that all parties who exchange EPCIS data using the Core Business
Vocabulary will have a common understanding of the semantic
meaning of that data.
• It defines vocabularies that are core to the EPCIS abstract data
model and are applicable to a broad set of business scenarios
common to many industries that have a desire or requirement to share
data.
Core Business Vocabulary

Slide 81
Vocabulary kinds
• Standard Variables
• A Standard Vocabulary is a set of Vocabulary Elements whose definition
and meaning must be agreed to in advance by trading partners who will
exchange events using the vocabulary.
• Standard Vocabulary elements tend to be defined by organisations of
multiple end users, such as GS1, industry consortia outside GS1, private
trading partner groups, and so on.
• User Variables
• A User Vocabulary is a set of Vocabulary Elements whose definition and
meaning are under the control of a single organisation.
• For example, the EPCIS standard defines a vocabulary called “business
location,” whose elements are identifiers denoting such things as “Acme
Corp. Distribution Centre #3.”

Slide 82
• Standard Vocabularies
• Business step identifiers
• Disposition identifiers
• Business transaction types
• Source/Destination types
• Error reason identifiers
• User variables
• Objects
• Locations
• Business transactions
• Source/Destination identifiers
• Transformation identifiers
• Event identifiers
Vocabulary kinds

Slide 83
Use of Uniform Resource Identifiers (URIs)

Slide 84
Use of Uniform Resource Identifiers (URIs)

Slide 85
Standard Vocabularies
- Business steps

Slide 86
Business steps

Slide 87
Business steps - Element values

Slide 88
- Dispositions

Slide 89
Dispositions – Element Values

Slide 90
-Business Transaction Types

Slide 91
-Business Transaction Types

Slide 92
-Source/Destination types

Slide 93
-Source/Destination types

Slide 94
-Error reason identifiers

Slide 95
-Error reason identifiers

Slide 96
User Vocabularies

Slide 97
User Vocabularies

Slide 98
Location and party master data

Slide 99
Location and party master data

EPCIS 2.0
This presentation is based on the latest
discussion, so it is subjected to change!

Slide 101
EPCIS/CBV 2.0
• EPCIS 2.0
• New Event Type
• Sensor Element Data
• JSON-LD
• REST Interface
• CBV 2.0
• New Vocabularies

Slide 102
EPCIS 2.0 - New Event Type
• AssociationEvent (subclass of EPCISEvent)
• capture associations where there is a strong physical relationship
between the containing and the contained objects such that they
will all occupy the same location at the same time, until such time
as they are disaggregated.

Slide 103
EPCIS 2.0 – New Event Type
AssociationEvent

Slide 104
EPCIS 2.0
• SensorElement

Slide 105
EPCIS 2.0 – SensorElement
New Query Parameters

Slide 106

Slide 107

Slide 108

Slide 109

Slide 110
EPCIS 2.0 – JSON
EPCIS-JSON-Schema:
https://github.com/gs1/EPCIS/blob/master/JSON/EPCIS-JSON-Schema.json
Example_9.6.1-ObjectEvent
https://github.com/gs1/EPCIS/blob/master/JSON/Example_9.6.1-ObjectEvent.json
Example_9.6.3-AggregationEvent
https://github.com/gs1/EPCIS/blob/master/JSON/Example_9.6.3-AggregationEvent.json
Example_9.6.4-TransformationEvent
https://github.com/gs1/EPCIS/blob/master/JSON/Example_9.6.4-TransformationEvent.json
Example_9.8.1-MasterData
https://github.com/gs1/EPCIS/blob/master/JSON/Example_9.8.1-MasterData.json

Slide 111
EPCIS 2.0 – REST Binding
Server URL

Slide 112
• Capture interface
• Capture Endpoint:
• POST /capture
• Events interface
• Event types Endpoint:
• GET /{optionalTopLevelResource}/events
• optionalTopLevelResource: [epcs|bizSteps|bizLocations|readPoints|dispositions]
• EPCIS events collections Binding:
• GET /{optionalTopLevelResource}/events/{eventType}
• EPCIS eventIds endpoints Endpoint:
• GET /{optionalTopLevelResource}/events/{eventType}/{eventId}

Slide 113
• Event filter control interface
• EPCIS query as URL query parameters
• https://example.com/events/all?filter=EQ_bizStep=urn:epcglobal:cbv:bizstep:shipping
• Query control interface
• Named queries Endpoint:
• GET /queries Returns a list of active queries.
• POST /queries. Creates a new named query.
• Execute named queries Endpoint:
• GET /queries/{queryName}/events.
• Returns a list of EPCIS events that match the query named in the path
• POST /queries/{queryName}/subscriptions
• Create a new query subscription. You must specify either a trigger parameter or schedule
parameter
https://github.com/evrythng/gs1-epcis-2.0/blob/master/openapi.yaml

Slide 114
CBV 2.0
Location and party master data attributes

Slide 115
CBV 2.0

Slide 116
Let’s build
EPCIS 2.0 together on
Backend
Repository
Event Data Master Data
Capture Service Listener
CaptureLayer
Application
QueryLayer
Poll Subscription
Scheduler
Schedule Destination
App
Query Service Receiver
Oliot-EPCIS
SOAP/HTTP
REST/HTTP
(POJO  Storage Unit)
JAXB Marshaller
(XMLPOJO)
Document Validator
Capture
Immediate Query
Standing Query
EPCIS DOC
ResultSOAP/HTTP
REST/HTTP
JAXB Unmarshaller (POJO  XML)
(Storage Unit  POJO)
XML/JSON

Slide 117
• Any questions?
Thank you

GS1 EPCIS and CBV Tutorial, Auto-ID Labs, KAIST (Apr 28, 2020)

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a GS1 EPCIS and CBV Tutorial, Auto-ID Labs, KAIST (Apr 28, 2020)

Semelhante a GS1 EPCIS and CBV Tutorial, Auto-ID Labs, KAIST (Apr 28, 2020) (20)

Mais de Daeyoung Kim

Mais de Daeyoung Kim (20)

Último

Último (20)

GS1 EPCIS and CBV Tutorial, Auto-ID Labs, KAIST (Apr 28, 2020)