ISO/IEC 19987:2017
(Main)Information technology — EPC Information Services (EPCIS) Standard
Information technology — EPC Information Services (EPCIS) Standard
ISO/IEC 19987:2017 defines Version 1.2 of EPC Information Services (EPCIS). The goal of EPCIS is to enable disparate applications to create and share visibility event data, both within and across enterprises.
Technologies de l'information — Norme relative aux services d'information sur les codes de produit électronique
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 19987
Second edition
2017-10
Information technology — EPC
Information Services (EPCIS) Standard
Technologies de l’information — Norme relative aux services
d’information sur les codes de produit électronique
Reference number
©
ISO/IEC 2017
© ISO/IEC 2017, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2017 – All rights reserved
Foreword
ISO (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized system for worldwide standardization.
National bodies that are members of ISO or IEC participate in the development of International
Standards through technical committees established by the respective organization to deal with
particular fields of technical activity. ISO and IEC technical committees collaborate in fields of
mutual interest. Other international organizations, governmental and non‐governmental, in
liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO
and IEC have established a joint technical committee, ISO/IEC JTC 1.
The procedures used to develop this document and those intended for its further maintenance
are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria
needed for the different types of document should be noted. This document was drafted in
accordance with the editorial rules of the ISO/IEC Directives, Part 2
(see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the
subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such
patent rights. Details of any patent rights identified during the development of the document will
be in the Introduction and/or on the ISO list of patent declarations received (see
www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and
does not constitute an endorsement.
For an explanation on the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see the
following URL: www.iso.org/iso/foreword.html.
This document was prepared by the GS1 and was adopted, under the PAS procedure, by Joint
Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval by
national bodies of ISO and IEC.
This second edition cancels and replaces the first edition (ISO/IEC 19987:2015), which has been
technically revised.
The main changes compared to the previous edition are as follows:
— A mechanism is introduced to declare that a prior EPCIS event is in error, for use when it is
impossible to correct the historical trace by means of ordinary EPCIS events.
— An optional eventID is added to all EPCIS events.
— The Simple Event Query is enhanced to clarify that queries for extension or ILMD fields
apply only to top‐level XML elements, and a new set of query parameters is introduced to
query for XML elements nested within top‐level elements.
— The role of an EPCIS document as a means to transmit events point‐to‐point is clarified.
© ISO/IEC 2017 – All rights reserved iii
— The EPCIS Header in the XML schemas is enhanced to allow for optional inclusion of master
data.
— The use of extension elements within and is deprecated.
— Section 12 regarding conformance is added.
iv © ISO/IEC 2017 – All rights reserved
EPC Information Services (EPCIS) Standard
Document Summary
Document Item Current Value
Document Name EPC Information Services (EPCIS) Standard
Document Date Sep 2016
Document Version 1.2
Document Issue
Document Status Ratified
Document Description enables disparate applications to create and share visibility event data,
both within and across enterprises.
Log of Changes
Release Date of Change Changed By Summary of Change
1.0 Initial version
1.1 May 2014 EPCIS 1.1 is fully backward compatible with EPCIS 1.0.1.
EPCIS 1.1 includes these new or enhanced features:
Support for class-level identification is added to
ObjectEvent, AggregationEvent, and
TransformationEvent through the addition of quantity lists.
A new event type, TransformationEvent, provides for the
description of events in which inputs are consumed and
outputs are produced.
The “why” dimension of all event types are enhanced so that
information about the sources and destinations of business
transfers may be included.
The “why” dimension of certain event types are enhanced so
that item/lot master data may be included.
The SimpleEventQuery is enhanced to encompass the above
changes to event types.
The introductory material is revised to align with the GS1
System Architecture.
The XML extension mechanism is explained more fully.
The QuantityEvent is deprecated, as its functionality is fully
subsumed by ObjectEvent with the addition of quantity lists.
Release 1.2, Ratified, Sep 2016 © 2016 GS1 AISBL Page 2 of 131
© ISO/IEC 2017 – All rights reserved
EPC Information Services (EPCIS) Standard
Release Date of Change Changed By Summary of Change
1.2 Sep 2016 EPCIS 1.2 is fully backward compatible with EPCIS 1.1 and
1.0.1.
EPCIS 1.2 includes these new or enhanced features:
A mechanism is introduced to declare that a prior EPCIS
event is in error, for use when it is impossible to correct the
historical trace by means of ordinary EPCIS events. This
mechanism includes the errorDeclaration structure in an
EPCIS event and associated query parameters.
An optional eventID is added to all EPCIS events. Its main
intended use is to allow for an error declaration event to
(optionally) refer to one or more corrective events.
The Simple Event Query is enhanced to clarify that queries
for extension or ILMD fields apply only to top-level XML
elements, and a new set of query parameters is introduced
to query for XML elements nested within top-level elements.
The role of an EPCIS document as a means to transmit
events point-to-point is clarified.
The EPCIS Header in the XML schemas is enhanced to allow
for optional inclusion of master data.
The use of extension elements within and
is deprecated.
Section 12 regarding conformance is added.
Disclaimer ®
GS1 , under its IP Policy, seeks to avoid uncertainty regarding intellectual property claims by requiring the participants in
the Work Group that developed this EPC Information Services (EPCIS) Standard to agree to grant to GS1 members a
royalty-free licence or a RAND licence to Necessary Claims, as that term is defined in the GS1 IP Policy. Furthermore,
attention is drawn to the possibility that an implementation of one or more features of this Specification may be the subject
of a patent or other intellectual property right that does not involve a Necessary Claim. Any such patent or other
intellectual property right is not subject to the licencing obligations of GS1. Moreover, the agreement to grant licences
provided under the GS1 IP Policy does not include IP rights and any claims of third parties who were not participants in the
Work Group.
Accordingly, GS1 recommends that any organisation developing an implementation designed to be in conformance with this
Specification should determine whether there are any patents that may encompass a specific implementation that the
organisation is developing in compliance with the Specification and whether a licence under a patent or other intellectual
property right is needed. Such a determination of a need for licencing should be made in view of the details of the specific
system designed by the organisation in consultation with their own patent counsel.
THIS DOCUMENT IS PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OF
MERCHANTABILITY, NONINFRINGMENT, FITNESS FOR PARTICULAR PURPOSE, OR ANY WARRANTY OTHER WISE ARISING
OUT OF THIS SPECIFICATION. GS1 disclaims all liability for any damages arising from use or misuse of this Standard,
whether special, indirect, consequential, or compensatory damages, and including liability for infringement of any
intellectual property rights, relating to use of information in or reliance upon this document.
GS1 retains the right to make changes to this document at any time, without notice. GS1 makes no warranty for the use of
this document and assumes no responsibility for any errors which may appear in the document, nor does it make a
commitment to update the information contained herein.
GS1 and the GS1 logo are registered trademarks of GS1 AISBL.
Release 1.2, Ratified, Sep 2016 © 2016 GS1 AISBL Page 3 of 131
© ISO/IEC 2017 – All rights reserved
EPC Information Services (EPCIS) Standard
Table of Contents
1 Introduction . 7
2 Relationship to the GS1 System Architecture . 7
2.1 Overview of GS1 standards . 8
2.2 EPCIS in relation to the “Capture” and “Share” layers . 8
2.3 EPCIS in Relation to trading partners . 10
2.4 EPCIS in relation to other GS1 System Architecture components . 11
3 EPCIS specification principles . 13
4 Terminology and typographical conventions . 14
5 EPCIS specification framework . 14
5.1 Layers . 14
5.2 Extensibility . 16
5.3 Modularity . 16
6 Abstract data model layer . 16
6.1 Event data and master data . 17
6.1.1 Transmission of master data in EPCIS . 19
6.2 Vocabulary kinds . 20
6.3 Extension mechanisms . 21
6.4 Identifier representation . 22
6.5 Hierarchical vocabularies . 22
7 Data definition layer . 23
7.1 General rules for specifying data definition layer modules . 23
7.1.1 Content . 23
7.1.2 Notation . 24
7.1.3 Semantics . 25
7.2 Core event types module – overview . 25
7.3 Core event types module – building blocks . 29
7.3.1 Primitive types . 29
7.3.2 Action type . 29
7.3.3 The “What” dimension . 30
7.3.4 The “Where” Dimension – read point and business location . 33
7.3.5 The “Why” dimension . 36
7.3.6 Instance/Lot master data (ILMD) . 39
7.4 Core event types module – events . 40
7.4.1 EPCISEvent . 40
7.4.2 ObjectEvent (subclass of EPCISEvent) . 43
7.4.3 AggregationEvent (subclass of EPCISEvent) . 46
7.4.4 QuantityEvent (subclass of EPCISEvent) – DEPRECATED . 49
7.4.5 TransactionEvent (subclass of EPCISEvent) . 50
7.4.6 TransformationEvent (subclass of EPCISEvent) . 53
8 Service layer . 55
Release 1.2, Ratified, Sep 2016 © 2016 GS1 AISBL Page 4 of 131
© ISO/IEC 2017 – All rights reserved
EPC Information Services (EPCIS) Standard
8.1 Core capture op
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.