Core Business Vocabulary
Standard
specifies the structure of vocabularies and specific values for
the vocabulary elements to be utilised in conjunction with the
GS1 EPCIS standard
Release 1.2.1, Ratified, May 2017
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 2 of 62
Document Summary 1
Document Item Current Value
Document Name Core Business Vocabulary Standard
Document Date May 2017
Document Version 1.2
Document Issue 1
Document Status Ratified
Document Description specifies the structure of vocabularies and specific values for the
vocabulary elements to be utilised in conjunction with the GS1 EPCIS
standard
Contributors 2
Name Company
Andrew Kennedy, Co-chair FoodLogiQ
Ralph Troeger, Co-chair GS1 Germany
Gena Morgan, Facilitator GS1 Global Office
Ken Traub, Editor Ken Traub Consulting LLC
Philip Allgaier bpcompass GmbH
Paul Arguin r-pac international
Karla Biggs-Gregory Oracle
Zsolt Bocsi GS1 Hungary
Jonas Buskenfried GS1 Sweden
Jaewook Byun Auto-ID Labs, KAIST
Karolin Catela GS1 Sweden
Mario Chavez GS1 Guatemala
Luiz Costa GS1 Brasil
Deniss Dobrovolskis GS1 Sweden
Michael Dols MET Laboratories
Hussam El-Leithy GS1 US
Jürgen Engelhardt Robert Bosch GmbH
Heinz Graf GS1 Switzerland
Danny Haak Nedap
Tany Hui GS1 Hong Kong, China
Jianhua Jia GS1 China
Peter Jonsson GS1 Sweden
Art Kaufmann Frequentz LLC
Janice Kite GS1 Global Office
Jens Kungl METRO Group
Roar Lorvik GS1 Norway
Paul Lothian Tyson
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 3 of 62
Name Company
Fargeas Ludovic Courbon
Noriyuki Mama GS1 Japan
Kevan McKenzie McKesson
Reiko Moritani GS1 Japan
Alice Mukaru GS1 Sweden
Mauricio Munoz Axway
Falk Nieder EECC
Juan Ochoa GS1 Columbia
Ted Osinski MET Laboratories
Ben Östman GS1 Finland
James Perng GS1 Chinese Taipei
Craig Alan Repec GS1 Global Office
Chris Roberts GlaxoSmithKline
Thomas Rumbach SAP AG
Chuck Sailer Frequentz
Michael Sarachman GS1 Global Office
Hans Peter Scheidt GS1 Germany
Michael Smith Merck & Co., Inc.
Michele Southall GS1 US
Peter Spellman TraceLink
Peter Sturtevant GS1 US
Hristo Todorov Axway
Geir Vevle HRAFN AS
Elizabeth Waldorf TraceLink
Ruoyun Yan GS1 China
Tony Zhang FSE, Inc.
Mike Zupec Abbvie
Log of Changes 3
Release Date of
Change
Changed By Summary of Change
1.0 Oct 2010 Initial release
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 4 of 62
Release Date of
Change
Changed By Summary of Change
1.1 March 2014 A new standard vocabulary for EPCIS source/destination type is added.
Templates for new user vocabularies for EPCIS source/destination identifier,
EPCIS transformation identifier, and object classes are added.
New business step, disposition, and business transaction type values are
added. The definitions of existing values are also clarified.
Disposition values non_sellable_expired, non_sellable_damaged,
non_sellable_disposed, non_sellable_no_pedigree_match, and
non_sellable_recalled defined in CBV 1.0 are deprecated in favour of new
disposition values expired, damaged, disposed, no_pedigree_match, and
recalled introduced in CBV 1.1.
RFC5870-compliant geocoordinate URIs are now permitted as location
identifiers.
The introductory material is revised to align with the GS1 System
Architecture.
1.2 Sep 2016 CBV 1.2 is fully backward compatible with CBV 1.1 and 1.0.
CBV 1.2 includes these new or enhanced features:
A new standard vocabulary for EPCIS error declaration reason identifiers is
added.
The URI structure for EPCIS event identifiers is specified.
New business step values dispensing and voidShipping added.
New disposition values dispensed and partially_dispensed added.
A new section for trade item master data attributes is added, and the section
on location and party master data attributes is expanded.
1.2.1 May 2017 Consistency issue corrected in a non-normative example.
Disclaimer 4
GS1
®
, under its IP Policy, seeks to avoid uncertainty regarding intellectual property claims by requiring the participants in 5
the Work Group that developed this Core Business Vocabulary Standard to agree to grant to GS1 members a royalty-6
free licence or a RAND licence to Necessary Claims, as that term is defined in the GS1 IP Policy. Furthermore, attention is 7
drawn to the possibility that an implementation of one or more features of this Specification may be the subject of a patent 8
or other intellectual property right that does not involve a Necessary Claim. Any such patent or other intellectual property 9
right is not subject to the licencing obligations of GS1. Moreover, the agreement to grant licences provided under the GS1 10
IP Policy does not include IP rights and any claims of third parties who were not participants in the Work Group. 11
Accordingly, GS1 recommends that any organisation developing an implementation designed to be in conformance with this 12
Specification should determine whether there are any patents that may encompass a specific implementation that the 13
organisation is developing in compliance with the Specification and whether a licence under a patent or other intellectual 14
property right is needed. Such a determination of a need for licencing should be made in view of the details of the specific 15
system designed by the organisation in consultation with their own patent counsel. 16
THIS DOCUMENT IS PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OF 17
MERCHANTABILITY, NONINFRINGMENT, FITNESS FOR PARTICULAR PURPOSE, OR ANY WARRANTY OTHER WISE ARISING 18
OUT OF THIS SPECIFICATION. GS1 disclaims all liability for any damages arising from use or misuse of this Standard, 19
whether special, indirect, consequential, or compensatory damages, and including liability for infringement of any 20
intellectual property rights, relating to use of information in or reliance upon this document. 21
GS1 retains the right to make changes to this document at any time, without notice. GS1 makes no warranty for the use of 22
this document and assumes no responsibility for any errors which may appear in the document, nor does it make a 23
commitment to update the information contained herein. 24
GS1 and the GS1 logo are registered trademarks of GS1 AISBL. 25
26
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 5 of 62
Table of Contents 27
1 Introduction – Core Business Vocabulary ..................................................... 8 28
2 Relationship to the GS1 System Architecture ................................................ 8 29
3 Relationship to EPCIS ................................................................................... 9 30
3.1
EPCIS event structure ...................................................................................................... 9 31
3.2 Vocabulary kinds ........................................................................................................... 10 32
3.2.1
Standard Vocabulary ............................................................................................. 10 33
3.2.2
User Vocabulary ................................................................................................... 11 34
4 Terminology and typographical conventions ............................................... 11 35
5 Compliance and compatibility ..................................................................... 12 36
5.1
CBV Compliant .............................................................................................................. 12 37
5.2
CBV compatible ............................................................................................................ 14 38
6 Use of Uniform Resource Identifiers (URIs) ............................................... 15 39
6.1
URI prefix for Standard Vocabularies in the CBV................................................................ 15 40
6.2
Limitation on Use of the URI prefix .................................................................................. 15 41
6.2.1
Example of limitation of use of URI prefix (non-normative) .................................. 15 42
7 Standard Vocabularies ................................................................................ 16 43
7.1
Business steps .............................................................................................................. 16 44
7.1.1
URI structure ....................................................................................................... 16 45
7.1.2
Compliant usage ................................................................................................... 16 46
7.1.3 Element values and definitions – Business step......................................................... 17 47
7.2
Dispositions .................................................................................................................. 23 48
7.2.1
URI structure ....................................................................................................... 23 49
7.2.2
Compliant usage ................................................................................................... 24 50
7.2.3
Element Values and definitions – Dispositions ........................................................... 24 51
7.3
Business Transaction Types ............................................................................................ 28 52
7.3.1 URI structure ....................................................................................................... 28 53
7.3.2
Compliant usage ................................................................................................... 28 54
7.3.3
Element Values and Definitions – Business Transaction Types .................................... 28 55
7.4
Source/Destination types ............................................................................................... 29 56
7.4.1
URI structure ....................................................................................................... 29 57
7.4.2
Compliant usage ................................................................................................... 29 58
7.4.3
Element Values and Definitions – Source/Destination Types ....................................... 29 59
7.5 Error reason identifiers .................................................................................................. 30 60
7.5.1
URI structure ....................................................................................................... 30 61
7.5.2
Compliant usage ................................................................................................... 30 62
7.5.3
Element Values and Definitions – Error reason identifiers ........................................... 30 63
8 User vocabularies ....................................................................................... 30 64
8.1
General considerations ................................................................................................... 30 65
8.1.1
General Considerations for EPC URIs as User Vocabulary Elements ............................. 31 66
8.1.2
General Considerations for Private or Industry-wide URN as User Vocabulary elements . 32 67
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 6 of 62
8.1.3 General Considerations for HTTP URLs as User Vocabulary elements ........................... 32 68
8.2
Physical or digital objects (Instance-Level Identification) .................................................... 33 69
8.2.1
EPC URI for Instance-level identification of objects .................................................... 34 70
8.2.2
Private or Industry-wide URN for Instance-level identification of objects ...................... 34 71
8.2.3 HTTP URLs for Instance-level identification of objects ................................................ 34 72
8.3
Physical or digital objects (Class-level identification) .......................................................... 35 73
8.3.1
EPC URI for Class-level identification of objects ........................................................ 35 74
8.3.2
Private or Industry-wide URN for Class-level identification of objects ........................... 36 75
8.3.3
HTTP URLs for Class-level identification of objects ..................................................... 37 76
8.4
Locations ..................................................................................................................... 37 77
8.4.1
EPC URI for Location identifiers .............................................................................. 38 78
8.4.2 Private or Industry-wide URN for Location identifiers ................................................. 38 79
8.4.3
HTTP URLs for Location identifiers ........................................................................... 38 80
8.4.4
Geographic Location URIs for Location identifiers ...................................................... 39 81
8.5
Business transactions .................................................................................................... 39 82
8.5.1
EPC URI for Business transaction identifiers ............................................................. 40 83
8.5.2
GLN-based identifier for legacy system business transaction identifiers ........................ 40 84
8.5.3
Private or Industry-wide URN for business transaction identifiers ................................ 41 85
8.5.4 HTTP URLs for business transaction identifiers .......................................................... 41 86
8.6
Source/Destination identifiers ......................................................................................... 41 87
8.6.1
EPC URI for Source/Destination identifiers ............................................................... 42 88
8.6.2
Private or Industry-wide URN for Source/Destination identifiers .................................. 42 89
8.6.3
HTTP URLs for Source/Destination identifiers ............................................................ 42 90
8.7
Transformation identifiers .............................................................................................. 43 91
8.7.1 EPC URI for Transformation identifiers ..................................................................... 43 92
8.7.2
GLN-based Identifier for Legacy System Transformation identifiers ............................. 43 93
8.7.3
Private or Industry-wide URN for Transformation identifiers ....................................... 44 94
8.7.4
HTTP URLs for Transformation identifiers ................................................................. 44 95
8.8
Event identifiers ............................................................................................................ 44 96
8.8.1
Universally Unique Identifier (UUID) URIs for Event identifiers ................................... 45 97
9 Trade item master data .............................................................................. 45 98
9.1
Trade item master data attribute names .......................................................................... 46 99
9.2
Trade item master data attributes ................................................................................... 46 100
9.2.1
Trade item master data attributes – trade item level ................................................. 47 101
9.2.2
Trade item master data attributes – lot level ............................................................ 48 102
9.2.3
Trade item master data attributes – instance-level .................................................... 50 103
9.2.4 Values of type measurement .................................................................................. 50 104
10 Location and party master data ............................................................. 51 105
10.1
Location and party master data attribute names ............................................................... 51 106
10.2
Location and party master data attributes ........................................................................ 52 107
10.3
Location master data code list values .............................................................................. 53 108
10.3.1 Sub-Site Type ...................................................................................................... 54 109
10.3.2
Sub-Site Attributes ............................................................................................... 54 110
11 Example EPCIS Documents (non-normative) ................................... 56 111
11.1
CBV-Compliant object event using standard vocabulary ..................................................... 56 112
11.2
CBV-Compliant object event using HTTP URLs and Private or Industry-wide URNs ................. 57 113
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 7 of 62
11.3 CBV-Compatible event ................................................................................................... 58 114
11.4
Location master data ..................................................................................................... 59 115
12 References ............................................................................................ 59 116
13 Contributors to earlier versions ............................................................. 60 117
118
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 8 of 62
1 Introduction – Core Business Vocabulary 119
This GS1 standard defines the Core Business Vocabulary (CBV). The goal of this standard is to 120
specify various vocabulary elements and their values for use in conjunction with the EPCIS standard 121
[EPCIS1.2], which defines mechanisms to exchange information both within and across organisation 122
boundaries. The vocabulary identifiers and definitions in this standard will ensure that all parties 123
who exchange EPCIS data using the Core Business Vocabulary will have a common understanding of 124
the semantic meaning of that data. 125
This standard is intended to provide a basic capability that meets the above goal. In particular, this 126
standard is designed to define vocabularies that are core to the EPCIS abstract data model and are 127
applicable to a broad set of business scenarios common to many industries that have a desire or 128
requirement to share data. This standard intends to provide a useful set of values and definitions 129
that can be consistently understood by each party in the supply chain. 130
Additional end user requirements may be addressed by augmenting the vocabulary elements herein 131
with additional vocabulary elements defined for a particular industry or a set of users or a single 132
user.
Additional values for the standard vocabulary types defined in this standard may be included 133
in follow-on versions of this standard. 134
This standard includes identifier syntax and specific vocabulary element values with their definitions 135
for these Standard Vocabularies: 136
■ Business step identifiers 137
■ Disposition identifiers 138
■ Business transaction types 139
■ Source/Destination types 140
■ Error reason identifiers 141
This standard provides identifier syntax options for these User Vocabularies: 142
■ Objects 143
■ Locations 144
■ Business transactions 145
■ Source/Destination identifiers 146
■ Transformation identifiers 147
■ Event identifiers 148
This standard provides Master Data Attributes and Values for describing Physical Locations 149
including: 150
■ Site Location 151
■ Sub-Site Type 152
■ Sub-Site Attributes 153
■ Sub-Site Detail 154
Additional detailed master data regarding locations (addresses, etc.) are not defined in this 155
standard. 156
2 Relationship to the GS1 System Architecture 157
The Core Business Vocabulary is a companion standard to the EPCIS standard. EPCIS is the 158
standard that defines the technical interfaces for capturing and sharing event data. EPCIS defines a 159
framework data model for event data. The Core Business Vocabulary is a GS1 data standard that 160
supplements that framework by defining specific data values that may populate the EPCIS data 161
model. As such, the CBV exists in the “Share” group of GS1 standards. 162
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 9 of 62
3 Relationship to EPCIS 163
This section specifies how the Core Business Vocabulary standard relates to the EPC Information 164
Services (EPCIS) standard. 165
3.1 EPCIS event structure 166
The EPCIS 1.2 standard [EPCIS1.2] specifies the data elements in an EPCIS event. The following 167
lists these data elements, and indicates where the Core Business Vocabulary provides identifiers 168
that may be used as values for those data elements. 169
■ The “what” dimension: The what dimension for most event types contains one or more 170
unique identifiers for physical or digital objects or classes of physical or digital objects. 171
Identifiers for physical or digital objects in the Core Business Vocabulary are specified in 172
Section 8.2 (instance-level) and Section 8.3
(class-level). In the case of an EPCIS 173
TransformationEvent, an optional TransformationID may be used to link together multiple 174
events that describe the same transformation. The Core Business Vocabulary includes 175
TransformationIDs in Section
8.7. 176
■ The “when” dimension: The moment in time at which an EPCIS event occurred. Event time is 177
fully specified in the EPCIS standard. 178
■ The “where” dimension: The “where” dimension consists of two identifiers that describe 179
different aspects of where an event occurred: 180
□ Read Point: The location where the EPCIS event took place. In the case of an EPCIS event 181
arising from reading a barcode or RFID tag, the Read Point is often the location where the 182
barcode or RFID tag was read. Identifiers for read points in the Core Business Vocabulary 183
are specified in Section 8.3
. 184
Example: A reader is placed at dock door #3 at the London Distribution Centre (DC). 185
Product passed through the dock door. Read point = <The identifier that stands for London 186
DC Dock Door #3> 187
□ Business Location: The location where the subject of the event is assumed to be following 188
an EPCIS event, until a new event takes place that indicates otherwise. Identifiers for 189
business locations in the Core Business Vocabulary are specified in Section 8.3
. 190
Example: A product is read through the sales floor transition door at store #123. The 191
product is now sitting on the sales floor. Business location = <The identifier that stands for 192
store #123 Sales Floor> 193
■ The “why” dimension: The “why” dimension consists of two identifiers and a list of business 194
transaction identifiers, which collectively provide the business context or “why” the event 195
occurred: 196
□ Business Step: Denotes a specific activity within a business process. The business step 197
field of an event specifies what business process step was taking place that caused the 198
event to be captured. Identifiers for business steps in the Core Business Vocabulary are 199
specified in Section 7.1
. 200
Example: an EPCIS event is generated as a product departs the location identified by the 201
Read Point. Business Step = <The identifier that denotes “shipping”>
202
□ Disposition: Denotes the business state of an object. The disposition field of an event 203
specifies the business condition of the subject of the event (the things specified in the 204
“what” dimension), subsequent to the event. The disposition is assumed to hold true until 205
another event indicates a change of disposition. Identifiers for dispositions in the Core 206
Business Vocabulary are specified in Section 7.2
. 207
Example: an EPCIS event is generated and afterward the products can be sold as-is and 208
customers can access product for purchase. Disposition = <The identifier that denotes 209
“sellable and accessible”> 210
□ Business Transaction References: An EPCIS event may refer to one or more business 211
transaction documents. Each such reference consists of two identifiers: 212
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 10 of 62
- Business Transaction Type: Denotes a particular kind of business transaction. 213
Example: the identifier that denotes “purchase order”. Identifiers for business 214
transaction types in the Core Business Vocabulary are specified in Section 7.3. 215
- Business Transaction Identifier: Denotes a specific business transaction document of 216
the type indicated by the Business Transaction Type. 217
Example: <The identifier that denotes Example Corp purchase order #123456> 218
Identifiers for business transactions in the Core Business Vocabulary are specified in 219
Section 8.5. 220
□ Source and Destination References: An EPCIS event may refer to one or more sources 221
and/or destinations that describe the endpoints of a business transfer of which the event is a 222
part. Each source or destination reference consists of two identifiers: 223
- Source or Destination Type: Denotes a particular kind of source or destination. 224
Example: the identifier that denotes “owning party”. Identifiers for source and 225
destination types in the Core Business Vocabulary are specified in Section 7.4. 226
- Source or Destination Identifier: Denotes a source or destination of the type 227
indicated by the Business Transaction Type. Example: <The identifier that denotes 228
Example Corp as an owning party> Identifiers for sources and destinations in the Core 229
Business Vocabulary are specified in Section 8.6
. 230
3.2 Vocabulary kinds 231
(The material in this section is adapted directly from [EPCIS1.2], Section 6.2.) 232
Vocabularies are used extensively within EPCIS to model conceptual, physical, and digital entities 233
that exist in the real world. 234
Examples of vocabularies defined in the EPCIS standard are business steps, dispositions, location 235
identifiers, physical or digital object identifiers, business transaction type names, and business 236
transaction identifiers. In each case, a vocabulary represents a finite (though open-ended) set of 237
alternatives that may appear in specific fields of events. 238
It is useful to distinguish two kinds of vocabularies, which follow different patterns in the way they 239
are defined and extended over time: 240
■ Standard Vocabulary: A Standard Vocabulary is a set of Vocabulary Elements whose definition 241
and meaning must be agreed to in advance by trading partners who will exchange events using 242
the vocabulary. 243
■ User Vocabulary: A User Vocabulary is a set of Vocabulary Elements whose definition and 244
meaning are under the control of a single organisation. 245
These concepts are explained in more detail below. 246
3.2.1 Standard Vocabulary 247
A Standard Vocabulary is a set of Vocabulary Elements whose definition and meaning must be 248
agreed to in advance by trading partners who will exchange events using the vocabulary. For 249
example, the EPCIS standard defines a vocabulary called “business step,” whose elements are 250
identifiers denoting such things as “shipping,” “receiving,” and so on. One trading partner may 251
generate an event having a business step of “shipping,” and another partner receiving that event 252
through a query can interpret it because of a prior agreement as to what “shipping” means. 253
Standard Vocabulary elements tend to be defined by organisations of multiple end users, such as 254
GS1, industry consortia outside GS1, private trading partner groups, and so on. The master data 255
associated with Standard Vocabulary elements, if any master data is defined at all, are defined by 256
those same organisations, and tend to be distributed to users as part of a standard or by some 257
similar means. New vocabulary elements within a given Standard Vocabulary tend to be introduced 258
through a very deliberate and occasional process, such as the ratification of a new version of a 259
standard or through a vote of an industry group. 260
The Standard Vocabularies specified in the Core Business Vocabulary standard are: business steps 261
(Section
7.1), dispositions (Section 7.2), business transaction types (Section 7.3), and source and 262
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 11 of 62
destination types (Section 7.4). The elements and definitions are agreed to by parties prior to 263
exchanging data, and there is general agreement on their meaning. 264
Example: the following is a business step identifier defined in Section 7.1 herein: 265
urn:epcglobal:cbv:bizstep:receiving 266
This identifier is defined by the GS1 Core Business Vocabulary standard, and its meaning is known 267
and accepted by those who implement the standard. 268
While an individual end user organisation acting alone may introduce a new Standard Vocabulary 269
element, such an element would have limited use in a data exchange setting, and would probably 270
only be used within an organisation’s four walls. On the other hand, an industry consortium or other 271
group of trading partners may define and agree on standard vocabulary elements beyond those 272
defined by the Core Business Vocabulary, and these may be usefully used within that trading group. 273
3.2.2 User Vocabulary 274
A User Vocabulary is a set of Vocabulary Elements whose definition and meaning are under the 275
control of a single organisation. For example, the EPCIS standard defines a vocabulary called 276
“business location,” whose elements are identifiers denoting such things as “Acme Corp. Distribution 277
Centre #3.” The location identifier and any associated master data is assigned by the user. Acme 278
Corp may generate an event whose business location field contains the identifier that denotes 279
“Acme Corp. Distribution Centre #3,” and another partner receiving that event through a query can 280
interpret it either because the partner recognises the identifier as being identical to the identifier 281
received in other events that took place in the same location, or because the partner consults 282
master data attributes associated with the location identifier, or both. 283
Example: 284
urn:epc:id:sgln:0614141.12345.400 285
This identifier is assigned by the End User who owns the GS1 Company Prefix 0614141, and the 286
meaning of the identifier (that is, what location it denotes) is determined exclusively by that end 287
user. Another End User can understand the meaning of this identifier by consulting associated 288
master data. 289
User Vocabulary elements are primarily defined by individual end user organisations acting 290
independently. The master data associated with User Vocabulary elements are typically defined by 291
those same organisations, and are usually distributed to trading partners through the EPCIS Query 292
Interface or other data exchange / data synchronisation mechanisms. New vocabulary elements 293
within a given User Vocabulary are introduced at the sole discretion of an end user, and trading 294
partners must be prepared to respond accordingly. 295
While the Core Business Vocabulary standard does not (and as the discussion above makes clear, 296
cannot) specify particular user vocabulary elements, the Core Business Vocabulary does provide 297
syntax templates that are recommended for use by End Users in constructing their own user 298
vocabulary elements. See Section 8.1
. The user vocabularies for which templates are specified in 299
this standard are: physical or digital objects (Sections
8.2 and 8.3), locations which include both 300
read points and business locations (Section
8.4), business transaction identifiers (Section 8.5), 301
source/destination identifiers (Section
8.6), and transformation identifiers (Section 8.7). 302
4 Terminology and typographical conventions 303
Within this standard, the terms SHALL, SHALL NOT, SHOULD, SHOULD NOT, MAY, NEED NOT, CAN, 304
and CANNOT are to be interpreted as specified in Annex G of the ISO/IEC Directives, Part 2, 2001, 305
4th edition [ISODir2]. When used in this way, these terms will always be shown in ALL CAPS; when 306
these words appear in ordinary typeface they are intended to have their ordinary English meaning. 307
All sections of this document, with the exception of Sections 2, 3 and 3 are normative, except where 308
explicitly noted as non-normative. 309
The following typographical conventions are used throughout the document: 310
■ ALL CAPS type is used for the special terms from [ISODir2] enumerated above. 311
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 12 of 62
■ Monospace type is used to denote programming language, UML, and XML identifiers, as well as 312
for the text of XML documents. 313
Placeholders for changes that need to be made to this document prior to its reaching the final 314
stage of approved GS1 standard are prefixed by a rightward-facing arrowhead, as this 315
paragraph is. 316
5 Compliance and compatibility 317
The GS1 Core Business Vocabulary is designed to facilitate interoperability in EPCIS data exchange 318
by providing standard values for vocabulary elements to be included in EPCIS data. The standard 319
recognises that the greatest interoperability is achieved when all data conforms to the standard, and 320
also recognises that individual End Users or groups of trading partners may need to extend the 321
standard in certain situations. 322
To that end, this standard defines two levels of conformance for EPCIS documents: 323
■ CBV-Compliant: An EPCIS document that only uses vocabulary identifiers specified in the Core 324
Business Vocabulary standard in the standard fields of EPCIS events. 325
■ CBV-Compatible: An EPCIS document that uses a combination of vocabulary identifiers 326
specified in the Core Business Vocabulary standard and other identifiers that are outside the 327
standard. 328
An EPCIS document is neither CBV-Compliant nor CBV-Compatible if it wrongly uses identifiers 329
defined in the Core Business Vocabulary standard or if it violates any other rules specified herein. 330
The formal definition of these terms is specified below. 331
5.1 CBV Compliant 332
A “CBV-Compliant Document” is a document that conforms to the schema and other constraints 333
specified in [EPCIS1.2], and which furthermore conforms to all the normative language in this 334
standard that pertains to a “CBV-Compliant Document.” 335
A “CBV-Compliant Application” is any application for which both of the following are true: 336
■ If it operates in a mode where it claims to accept a CBV-Compliant Document as an input, the 337
application SHALL accept any document that is a CBV-Compliant Document according to this 338
standard, and furthermore in processing that input SHALL interpret each CBV identifier 339
according to the meaning specified herein. 340
■ If it operates in a mode where it claims to produce a CBV-Compliant Document as an output, 341
the application SHALL only produce a document that is a CBV-Compliant Document according to 342
this standard, and furthermore in generating that output SHALL only use CBV identifiers to 343
denote their meaning as specified herein. 344
The following list summarises the requirements for an EPCIS document to be a “CBV-Compliant 345
Document,” as specified elsewhere in this standard: 346
■ A CBV-Compliant Document SHALL conform to the schema and other constraints specified in 347
[EPCIS1.2]. 348
■ A CBV-Compliant Document SHALL NOT use any URI beginning with
urn:epcglobal:cbv: 349
except as specified in this standard. 350
■ Each EPCIS event in a CBV-Compliant Document SHALL include a bizStep field, and the value 351
of the
bizStep field SHALL be a URI consisting of the prefix urn:epcglobal:cbv:bizstep: 352
followed by the string specified in the first column of some row of the table in Section 7.1.3. 353
■ A CBV-Compliant Document MAY include a disposition field. If the disposition field is 354
present, the value of the
disposition field SHALL be a URI consisting of the prefix 355
urn:epcglobal:cbv:disp: followed by the string specified in the first column of some row of 356
the table in Section 7.2.3.
357
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 13 of 62
■ Each EPCIS event in a CBV-Compliant Document MAY include one or more bizTransaction 358
elements. If
bizTransaction elements are present, each such element MAY include a type 359
attribute. If a given
bizTransaction element includes a type attribute, the value of the type 360
attribute SHALL be a URI consisting of the prefix
urn:epcglobal:cbv:btt: followed by the 361
string specified in the first column of some row of the table in Section 7.3.3.
362
■ Each EPCIS event in a CBV-Compliant Document MAY include one or more source or 363
destination elements. The value of the type attribute of each such element SHALL be a URI 364
consisting of the prefix
urn:epcglobal:cbv:sdt: followed by the string specified in the first 365
column of some row of the table in Section 7.4.3. 366
■ Each EPCIS event in a CBV-Compliant Document MAY include an ErrorDeclaration element, 367
and when present, the
ErrorDeclaration element MAY include a reason field. When present 368
in a CBV-Compliant Document, the value of the reason field of the
ErrorDeclaration 369
element SHALL be a URI consisting of the prefix
urn:epcglobal:cbv:er: followed by the 370
string specified in the first column of some row of the table in Section 7.5.3.
371
■ URIs defined in the EPC Tag Data standard SHALL only be used in a CBV-Compliant Document 372
as specified in Section 8.1.1
. 373
■ A CBV-Compliant document SHALL use one of the three URI forms specified in Section 8.2 to 374
populate instance-level identifiers in the “what” dimension of EPCIS events (that is, the 375
epcList, parentID, childEPCs, inputEPCList, and outputEPCList fields in EPCIS 376
ObjectEvents, AggregationEvents, TransacationEvents, and 377
TransformationEvents), for every such field that is not null. A CBV-Compliant document 378
SHOULD use the EPC URI form as specified in Section 8.2.1 unless there is a strong reason to 379
do otherwise. 380
■ A CBV-Compliant document SHALL NOT use an SGLN EPC (urn:epc:id:sgln:…) as an object 381
identifier. 382
■ A CBV-Compliant document SHALL use one of the three URI forms specified in Section 8.3
to 383
populate class-level identifiers in the “what” dimension of EPCIS events (that is, the
epcClass 384
fields in all EPCIS event types), for every such field that is not null. A CBV-Compliant document 385
SHOULD use the EPC URI form as specified in Section
8.3.1 unless there is a strong reason to 386
do otherwise. 387
■ A CBV-Compliant document SHALL use one of the four URI forms specified in Section 8.4 to 388
populate the “where” dimension of EPCIS events (that is, the
readPoint and 389
businessLocation fields in all EPCIS event types), for every such field that is not null. A CBV-390
Compliant document SHOULD use the EPC URI form as specified in Section
8.4.1 unless there is 391
a strong reason to do otherwise. 392
■ When using an EPC URI as a location identifier (Section 8.4.1), a CBV-Compliant document 393
SHOULD NOT use EPC schemes other than SGLN (
urn:epc:id:sgln:…), unless there is a 394
strong reason to do so. 395
■ A CBV-Compliant document SHALL use one of the four URI forms specified in Section 8.5 to 396
populate the business transaction identifier field (that is, the text content of the 397
bizTransaction element) of EPCIS events, for every such field that is not null. 398
■ When using an EPC URI as a business transaction identifier, a CBV-Compliant Documents 399
SHOULD NOT use EPC schemes other than GDTI EPCs (
urn:epc:id:gdti:…) or GSRN EPCs 400
(
urn:epc:id:gsrn:…), unless there is a strong reason to do so. GDTI EPCs SHOULD only be 401
used as business transaction identifiers when they have been assigned to denote a business 402
transaction, rather than a physical document not connected with any business transaction. 403
■ A CBV-Compliant document SHALL use one of the three URI forms specified in Section 8.6
to 404
populate a source or destination identifier field (that is, the text content of a
source or 405
destination element), for every such field that is not null. A CBV-Compliant document 406
SHOULD use the EPC URI form as specified in Section
8.6.1 unless there is a strong reason to 407
do otherwise. 408
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 14 of 62
■ When using an EPC URI as a source or destination identifier (Section 8.6.1), a CBV-Compliant 409
document SHOULD NOT use EPC schemes other than SGLN (
urn:epc:id:sgln:…), unless 410
there is a strong reason to do so. 411
■ A CBV-Compliant document SHALL use one of the four URI forms specified in Section 8.7 to 412
populate the transaction identifier field (that is, the text content of the transformationID 413
element) of EPCIS
TransformationEvents, for every such field that is not null. 414
■ When using an EPC URI as a transformation identifier, a CBV-Compliant Document SHOULD NOT 415
use EPC schemes other than GDTI EPCs (
urn:epc:id:gdti:…) unless there is a strong reason 416
to do so. GDTI EPCs SHOULD only be used as transformation identifiers when they have been 417
assigned to denote a transformation, rather than a physical document not connected with any 418
transformation. 419
■ A CBV-Compliant document SHALL use one of the URI forms specified in Section 8.8.1 to 420
populate the event identifier field (that is, the text content of the eventID element) of an EPCIS 421
event, whenever that field is not null. 422
5.2 CBV compatible 423
A “CBV-Compatible Document” is a document that conforms to the schema and other constraints 424
specified in [EPCIS1.2], and which furthermore conforms to all the normative language in this 425
standard that pertains to a “CBV-Compatible Document.” 426
A “CBV-Compatible Application” is any application for which both of the following are true: 427
■ If it operates in a mode where it claims to accept a CBV-Compatible Document as an input, the 428
application SHALL accept any document that is a CBV-Compatible Document according to this 429
standard, and furthermore in processing that input SHALL interpret each CBV identifier 430
according to the meaning specified herein. 431
■ If it operates in a mode where it claims to produce a CBV-Compatible Document as an output, 432
the application SHALL only produce a document that is a CBV-Compatible Document according 433
to this standard, and furthermore in generating that output SHALL only use CBV identifiers to 434
denote their meaning as specified herein. 435
The following list summarises the requirements for an EPCIS document to be a “CBV-Compatible 436
Document,” as specified elsewhere in this standard. 437
■ A CBV-Compatible Document SHALL conform to the schema and other constraints specified in 438
[EPCIS1.2]. 439
■ A CBV-Compatible Document SHALL NOT use any URI beginning with
urn:epcglobal:cbv: 440
except as specified in this standard. 441
■ URIs defined in the EPC Tag Data standard SHALL only be used in a CBV-Compatible Document 442
as specified in Section 8.1.1
. 443
■ A CBV-Compatible Document SHOULD use the EPC URI form as specified in Section 8.2.1 for 444
each instance-level object identifier unless there is a strong reason to do otherwise. 445
■ A CBV-Compatible Document SHOULD use the EPC URI form as specified in Section 8.3.1 for 446
each class-level object identifier unless there is a strong reason to do otherwise. 447
■ A CBV-Compatible Document SHALL NOT use an SGLN EPC (urn:epc:id:sgln:…) as an 448
object identifier. 449
■ A CBV-Compatible Document SHOULD use the EPC URI form as specified in Section 8.4.1 for 450
each location identifier unless there is a strong reason to do otherwise. 451
■ When using an EPC URI as a location identifier (Section 8.4.1), a CBV-Compatible Document 452
SHOULD NOT use EPC schemes other than SGLN (
urn:epc:id:sgln:…), unless there is a 453
strong reason to do so. 454
■ When using an EPC URI as a business transaction identifier, a CBV-Compatible Document 455
SHOULD NOT use EPC schemes other than GDTI EPCs (
urn:epc:id:gdti:…) or GSRN EPCs 456
(
urn:epc:id:gsrn:…), unless there is a strong reason to do so. GDTI EPCs SHOULD only be 457
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 15 of 62
used as business transaction identifiers when they have been assigned to denote a business 458
transaction, rather than a physical document not connected with any business transaction. 459
■ When using an EPC URI as a source or destination identifier (Section 8.6.1
), a CBV-Compatible 460
document SHOULD NOT use EPC schemes other than SGLN (
urn:epc:id:sgln:…), unless 461
there is a strong reason to do so. 462
■ When using an EPC URI as a transformation identifier, a CBV-Compatible Document SHOULD 463
NOT use EPC schemes other than GDTI EPCs (
urn:epc:id:gdti:…) unless there is a strong 464
reason to do so. GDTI EPCs SHOULD only be used as transformation identifiers when they have 465
been assigned to denote a transformation, rather than a physical document not connected with 466
any transformation. 467
In general, every CBV-Compliant Document is also a CBV-Compatible Document, though not every 468
CBV-Compatible Document is a CBV-Compliant Document. A CBV-Compatible Document may 469
include an identifier that is compliant with [EPCIS1.2] but which is not permitted for CBV-Compliant 470
Documents, provided that it meets the requirements above. A CBV-Compatible Document may also 471
include an event in which the
bizStep field is omitted, whereas that field is always required for 472
CBV-Compliant Documents. 473
6 Use of Uniform Resource Identifiers (URIs) 474
This section specifies general rules that apply to all uses of URIs in this standard. 475
6.1 URI prefix for Standard Vocabularies in the CBV 476
All URIs for standard vocabulary elements specified in the Core Business Vocabulary standard have 477
the following syntax: 478
urn:epcglobal:cbv:qualifier:payload 479
where the qualifier denotes the type of the vocabulary the vocabulary element belongs to and 480
payload the vocabulary element unambiguously identifies an element of the vocabulary. 481
6.2 Limitation on Use of the URI prefix 482
The Core Business Vocabulary standard is the only GS1 standard in which URIs beginning with 483
urn:epcglobal:cbv: are defined. 484
A CBV-Compliant or CBV-Compatible document SHALL NOT use any URI beginning with 485
urn:epcglobal:cbv: or urn:epc: except as specified in this standard. 486
Both CBV-Compliant and CBV-Compatible documents MAY contain URIs that do not begin with 487
urn:epcglobal:cbv:, provided that the requirements specified elsewhere in this standard are 488
met. These SHALL be used to identify vocabulary elements not defined by the CBV standard. URIs 489
beginning with
urn:epcglobal: SHALL NOT be used except as specified herein or in another GS1 490
standard. 491
6.2.1 Example of limitation of use of URI prefix (non-normative) 492
Suppose a user needs a new disposition value to stand for “quarantined.” The user may NOT use 493
the following URI: 494
urn:epcglobal:cbv:disp:quarantined 495
In this case the particular URI above is NOT part of this standard and therefore may not be used. 496
Instead a URI like the following could be used and considered CBV-Compatible. However, it must be 497
noted that this vocabulary would have limited meaning to supply chain participants receiving this 498
unless a prior understanding had been established. 499
http://epcis.example.com/disp/quarantined 500
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 16 of 62
7 Standard Vocabularies 501
This section specifies standard vocabulary elements for four EPCIS standard vocabularies: business 502
steps, dispositions, business transaction types, and source/destination types. 503
7.1 Business steps 504
This section specifies standard identifiers for the EPCIS BusinessStepID vocabulary. These 505
identifiers populate the
bizStep field in an EPCIS event, as specified below. 506
7.1.1 URI structure 507
All business step values specified in this section have the following form: 508
urn:epcglobal:cbv:bizstep:payload 509
where the
payload part is a string as specified in the next section. Every payload string defined 510
herein contains only lower case letters and the underscore character. 511
7.1.2 Compliant usage 512
Each EPCIS event in a CBV-Compliant Document SHALL include a bizStep field, and the value of 513
the
bizStep field SHALL be a URI consisting of the prefix urn:epcglobal:cbv:bizstep: followed 514
by the string specified in the first column of some row of the table in Section 7.1.3 below. The
515
portion following the prefix SHALL be written exactly as specified in the table below, in all lowercase 516
letters (possibly including underscores, as indicated). 517
Each EPCIS event in a CBV-Compatible Document MAY include a bizStep field, and the value of the 518
bizStep field MAY be a URI as specified above for a CBV-Compliant document, and MAY be any 519
other URI that meets the general requirements specified in [EPCIS1.2], Section 6.4, except for 520
those URIs which in this standard are forbidden or designated for a different purpose. 521
7.1.2.1 Example of correct and incorrect usage (non-normative) 522
The following shows an excerpt of a CBV-Compliant EPCIS document in XML format containing a 523
single event, where the business step of that event is the Core Business Vocabulary “shipping” 524
value: 525
<epcis:EPCISDocument xmlns:epcis="urn:epcglobal:epcis:xsd:1" ...> 526
<EPCISBody> 527
<EventList> 528
<ObjectEvent> 529
... 530
<bizStep>urn:epcglobal:cbv:bizstep:shipping</bizStep> 531
... 532
</ObjectEvent> 533
</EventList> 534
</EPCISBody> 535
</epcis:EPCISDocument> 536
The following example is NOT CBV-Compliant, because it does not use the full URI string in the 537
business step field. It is also not CBV-Compatible, because the value of the business step field is not 538
a URI with an owning authority, as required by Section 6.4 of [EPCIS1.2]. 539
<epcis:EPCISDocument xmlns:epcis="urn:epcglobal:epcis:xsd:1" ...> 540
<EPCISBody> 541
<EventList> 542
<ObjectEvent> 543
... 544
<bizStep>shipping</bizStep> WRONG 545
... 546
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 18 of 62
Business steps
Value Definition Examples
accepting
Denotes a specific activity within a
business process where an object
changes possession and/or ownership.
Retailer X unloads a pallet on to the receiving
dock. The numbers of cases on the pallet are
counted. The pallets are disaggregated from
the shipping conveyance. The quantity is
verified against the delivery document (Freight
Bill or Bill of Lading), notating any over, short
or damaged product at the time of delivery.
Typically this process releases freight payment
and completes the contractual agreement with
the carrier of delivering the product/assets to a
specified location.
A parcel carrier drops off five boxes at
Distributor Y's DC. A person on the Receiving
Dock signs that they accept the five boxes
from the parcel carrier.
A wholesaler is assigned a lot of fish at a fish
auction, verifies the quantity and acknowledges
receipt.
A manufacturer’s fork lift driver scans the IDs
of components which have been removed from
a consignment warehouse. In doing so, the
components are added to the manufacturer’s
inventory
arriving
Denotes a specific activity within a
business process where an object arrives
at a location.
Truckload of a shipment arrives into a yard.
Shipment has not yet been received or
accepted.
assembling
Denotes an activity within a business
process whereby one or more objects are
combined to create a new finished
product.
In contrast to transformation, in the
output of
assembling the original
objects are still recognisable and/or the
process is reversible; hence,
assembling would be used in an
Aggregation Event, not a Transformation
Event.
Computer parts (hard drive, battery, RAM)
assembled into a consumer ready computer
Healthcare kitting: a surgical kit including drug,
syringe, and gauze are combined to create a
new ‘product’: a kit
collecting
Denotes a specific activity within a
business process where an object is
picked up and collected for future
disposal, recycling or re-used.
An organisation picks up disposed consumer
electronics in an end of life state from various
different organisations. After the goods are
picked up, they typically are brought back and
received into a Collection Centre
Rented or leased pallets are picked up and
brought to a collection centre.
2
Cnt
2
Cnt
Syringe
Gauze
2
Cnt
2
Cnt
Syringe
Gauze
Before
Kit with Serial Number
(New Finished Good)
Kit Serial Nbr: 1234566789
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 19 of 62
Business steps
commissioning
Process of associating an instance-level
identifier (such as an EPC) with a specific
object, or the process of associating a
class-level identifier, not previously
used, with one or more objects. A tag
may have been encoded and applied in
this step, or may have been previously
encoded.
In the case of a class-level identifier,
commissioning differs from
creating_class_instance in that
commissioning always indicates that
this is the first use of the class-level
identifier, whereas
creating_class_instance does not
specify whether the class-level identifier
has been used before.
On a packaging line, an encoded EPC is applied
to a case and associated to the product.
An individual virtual document (e.g. digital
coupon, digital voucher, etc.) is assigned an
EPC
One hundred bottles of a particular batch of
pharmaceutical product are produced, those
being the first bottles of that batch to be
produced.
Sides of beef are transformed into individual
packaged steaks. This may be an EPCIS 1.2
TransformationEvent if the input sides of
beef are also tracked.
consigning
Indicates the overall process of
staging_outbound, loading,
departing, and accepting. It may be
used when more granular process step
information is unknown or inaccessible.
The use of
consigning is mutually
exclusive from the use of
staging_outbound, loading,
departing, and accepting.
Note: This business step is similar to
shipping, but includes a change of
possession and/or ownership at the
outbound side.
A wholesaler comes aboard a fishing vessel,
selects and buys boxes of fish, and brings them
to his premises.
A manufacturer retrieves components from a
consignment warehouse for use in its assembly
line. In the logical second of leaving the
consignment warehouse, the components pass
into the ownership of the manufacturer.
A manufacturer stages products for loading,
loads them into a container, the container is
sealed, and the container departs. Ownership
transfers to the receiver sometime during this
overall process. If this is done in a single step,
then business step
consigning
is used.
creating_clas
s_instance
Denotes a step in a business process
where an instance or increased quantity
of a class-level identifier is produced.
Unlike
commissioning, this business
step may be repeated for the same
class-level identifier.
Water, sugar, and other ingredients are
combined to produce a single batch of soda
over a single shift on a single production line.
This may be an EPCIS 1.2
TransformationEvent if the input
ingredients are tracked.
Potatoes are sorted by size and quality,
washed, and packed into cases of a single lot in
a single packaging facility on a single date.
cycle_countin
g
Process of counting objects within a
location in order to obtain an accurate
inventory for business needs other than
accounting purposes (e.g.,
replenishment and allocation).
A preselected subset of objects (for instance,
all products belonging to a certain brand owner
or a specific object class) within a retail store,
are counted by a handheld reader.
All objects of a specific sub-location (sales floor
or a shelf on the sales floor, e.g.) are counted
by a handheld reader.
decommissioni
ng
Process of disassociating an instance-
level identifier (such as an EPC) with an
object. The object may be re-
commissioned at some point in the
future – however only with a new
instance-level identifier.
An eSeal on a reusable container is broken
when the container is opened, so that the
container is no longer identified by the
instance-level identifier that was in the eSeal.
A digital coupon or an empties refund voucher
is redeemed at retail point-of-sale
departing
Denotes a specific activity within a
business process where an object leaves
a location on its way to a destination.
Truckload of a shipment departs a yard,
typically through a gate and begins transit to
another location
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 20 of 62
Business steps
destroying
Process of terminating an object. For an
instance-level identifier, the object
should not be the subject of subsequent
events; subsequent events are likely
indicative of error (such as a stray read
of a tag inside an incinerator). For a
class level identifier, quantities are
reduced; however, the class-level
identifier may still be used in subsequent
events (referring to different instances
that were not destroyed).
Distributor or Retailer puts empty case in the
incinerator or box crusher.
disassembling
Denotes a specific activity within a
business process where an object is
broken down into separate, uniquely
identified component parts.
Before feeding a consumer electronics end of
life item (a computer) into recycling operation
line, it is necessary to disassemble the parts
for the purpose of being recycled or disposed
of in an environmentally sound manner.
A surgical kit (e.g. 2- 50 count bottles of
medication and 1 syringe gauze) is broken
down into its separate component parts
dispensing
Denotes a specific activity within a
business process where a product is
made available in full or part to a
consumer.
A pharmacist dispenses a pharmaceutical to fill
a specific prescription written by a physician, to
a consumer or patient.
A deli manager slices a 5 pound package of
turkey for sale.
encoding
Process of writing an instance-level
identifier (typically an EPC) to a barcode
or RFID tag, where the identifier is not
yet associated with an object at this step
in the process.
3rd Party writes tags and returns spool of case
tags to Manufacturer
entering_exit
ing
Denotes a specific activity at the
Entrance/Exit door of a facility where
customers are either leaving with
purchased product or entering with
product to be returned to the facility.
Customer leaves the facility of Retailer X with
their purchased items through a customer
entrance/exit door.
holding
Denotes a specific activity within a
business process where an object is
segregated for further review.
Retailer X unloads a second pallet on to their
receiving dock, and, finding no purchase order
for the pallet, moves the pallet to a holding
area on the dock
Distributor Y obtains a shipment of
pharmaceutical product. Distributor Y finds that
their supplier cannot provide a complete
pedigree. Distributor Y moves the shipment to
a quarantine area on their dock.
Shipper Z is told by Customs to move a
container to a special area until Customs can
inspect and clear the container.
inspecting
Process of reviewing objects to address
potential physical or documentation
defects.
Manufacturer A pulls 10 bottles from every
batch to ensure that the product and pill count
in the bottles match expectations
Distributor Y checks all returned products to
designate them either as saleable or as
damaged
Regulator R pulls 3 bottles from a shelf to
determine if the bottles have a correct
pedigree
Customs Agent C uses a machine to scan the
contents of a shipping container
Pallet pool operator Z checks if certain pallets
comply with quality standards.
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 21 of 62
Business steps
installing
Denotes a specific activity within a
business process where an object is put
into a composite object (not merely a
container).
In
installing the composite object
exists prior to this step, whereas in
assembling the composite object is
created during the step.
Additional memory chips and a rechargeable
battery are installed within a computer
A duplexing unit is installed on a laser printer
Additional safety equipment is installed within
the cabin of an aircraft or vehicle (e.g. fire
extinguishers)
killing
Process of terminating an RFID tag
previously associated with an object. The
object and its instance-level identifier
may continue to exist and be the subject
of subsequent events (via a barcode,
manual data entry, replacement tag,
etc.).
Kill Command is issued to the tag to prevent
any further reading of the tag or the
information on the tag.
loading
Denotes a specific activity within a
business process where an object is
loaded into shipping conveyance.
Manufacturer A loads pallets into a container.
The pallets are aggregated to the container.
Distributor Y loads racks full of totes on to a
truck
other
A business step not identified by any of
the values listed in the core business
vocabulary.
“Other” may be used for terms that have yet to
be added to the core business vocabulary from
an industry or a user
packing
Denotes a specific activity within a
business process that includes putting
objects into a larger container – usually
for shipping. Aggregation of one unit to
another typically occurs at this point.
12 packs of soda are placed into a case
Loose potatoes are placed into a tote.
picking
Denotes a specific activity within a
business process that includes the
selecting of objects to fill an order.
Distributor Y places three units into a tote to
meet the requirements of a purchase order
Manufacturer A pulls three pallets from its
racks to fulfil a purchase order
receiving
Denotes a specific activity within a
business process that indicates that an
object is being received at a location and
is added to the receiver's inventory.
The use of
receiving is mutually
exclusive from the use of
arriving and
accepting.
Retailer X confirms that the count of cases on
the pallet equals the expected count in a
purchase order. Retailer X takes the cases into
inventory. Typically, this process matches the
product to the purchase order for payment to
the supplier.
A shipment from a manufacturer factory site to
manufacturer distribution centre, is matched
against the transaction record then added to
local inventory.
removing
Denotes a specific activity within a
business process where an object is
taken out of a composite object.
A defective airplane part is taken out of the
engine
repackaging
Denotes a specific activity within a
business process where an object’s
packaging configuration is changed.
Distributor Y receives one box full of batteries
and another box full of laptops without
batteries. Distributor Y ships out new boxes
containing one laptop and one battery.
repairing
Denotes a specific activity within a
business process where a malfunctioning
product is repaired (typically by a post-
sales service), without replacing it by a
new one.
A computer is brought to a repair centre to fix
a problem
An airplane part is in maintenance centre to
diagnose an issue
replacing
Denotes a specific activity within a
business process where an object is
substituted or exchanged for another
object.
A defective airplane part is replaced by a new
part.
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 22 of 62
Business steps
reserving
Process in which a set of instance-level
identifiers, not yet commissioned, are
provided for use by another party.
Manufacturer provides set of case EPC
numbers to a 3rd Party labeller
retail_sellin
g
Denotes a specific activity within a
business process at a point-of-sale for
the purpose of transferring ownership to
a customer in exchange for something of
value (currency, credit, etc.).
Retailer X sells a screwdriver to a customer by
checking it out through a point-of-sale system.
shipping
Indicates the overall process of
staging_outbound, loading and
departing. It may be used when more
granular process step information is
unknown or inaccessible. It may indicate
a final event from a shipping point.
The use of
shipping is mutually
exclusive from the use of
staging_outbound, departing, or
loading.
Manufacturer A loads and reads product into
the shipping container and closes the door. The
product has been read out of the shipping
facility. The shipment is immediately picked up
and a BOL is associated at this point. (The
shipment has left the yard)
At Distributor Y, the truck containing racks full
of totes pulls away from the shipping dock or
staging area.
Manufacturer A completes loading product into
trailer and seals door. The trailer is ready for
pickup. The generation of a Despatch Advice /
ASN triggers a “shipping” event.
A 3PL picks and tags the product. The product
is loaded into a trailer and signed over to a
transportation carrier. The 3PL notifies
the manufacturer who generates a “shipping”
event. NOTE: This would be the case if there
were NO departing step at a read point at the
gate.
Typical Process flow:
staging_outbound
loading
departing
The above steps assume an organisation’s
ability and desire to share all steps in the
process. If those process steps are not
captured, the single business step of
shipping
would be used.
staging_outbo
und
Denotes a specific activity within a
business process in which an object
moves from a facility to an area where it
will await transport pick-up.
Container is being closed and will be
subsequently loaded onto a vehicle in the yard.
Container is being closed and seal is applied,
and will be subsequently loaded onto a vehicle
in the yard
Product has been picked and is now in a
staging lane waiting for loading into a container
stock_taking
Process of counting objects within a
location following established rules
and/or standards to serve as a basis for
accounting purposes.
All EPCs in a retail store are read by a
handheld reader following a procedure
accepted by the organisation’s accounting firm.
stocking
Denotes a specific activity within a
business process within a location to
make an object available to the customer
or for order fulfilment within a DC.
Retailer X places cans from a case on to a shelf
on the sales floor
Dist X moves goods from a storage area to a
picking area
storing
Denotes a specific activity within a
business process where an object is
moved into and out of storage within a
location.
Manufacturer A moves a pallet from the
receiving area to a rack
Retailer X moves a case from the receiving
dock to a shelf in the backroom
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 23 of 62
Business steps
transforming
(Deprecated)
Denotes a specific activity within a
business process where one or more
objects are an input into a process that
irreversibly changes that object / those
objects into a new object or objects; the
output has a new identity and
characteristics.
This business step is deprecated for use
with EPCIS 1.2. The EPCIS 1.2 standard
has an event type,
TransformationEvent, dedicated to
transformations. The business steps
commissioning,
creating_class_instance, or other
business steps may be used with
TransformationEvent
.
Meat packer X cuts a whole cow into two sides
of beef (1 to many)
Food processor Y combines water, vegetables,
and meat to create a unit of soup (many to
one)
Butcher Z combines meat from multiple
carcasses, grinds them together, and creates
individual packages of ground beef (many to
many)
transporting
Process of moving an object from one
location to another using a vehicle (e.g.,
a ship, a train, a lorry, an aircraft).
Carrier X conveys 150 sea containers from
Hong Kong seaport to Hamburg seaport with a
container vessel.
A train with 20 goods wagons goes from one
train station to another.
A lorry moves a swap trailer from a depot to a
distribution centre.
unloading
Denotes a specific activity within a
business process where an object is
unloaded from a shipping conveyance.
Manufacturer A unloads pallets from a shipping
conveyance. The pallets are disaggregated
from the shipping conveyance.
Distributor Y unloads racks full of totes from a
truck
unpacking
Denotes a specific activity within a
business process that includes removing
products (individuals, inners, cases,
pallets) from a larger container – usually
after receiving or accepting.
Disaggregation of one unit from another
typically occurs at this point.
12 packs of soda are removed from a case
Loose potatoes are taken off from a tote.
void_shipping
Denotes a process of declaring that one
or more objects in a prior outbound
process (captured in an EPCIS event
having business step
shipping,
departing
, or consigning) were not
shipped (or departed or consigned) as
previously indicated.
A sender cancels a shipment after a prior
shipping event.
A sender discovers, either by notification from
a recipient or on their own, that a shipment
they believed occurred and created a shipping
event for, did not actually occur. The record is
updated to reflect this.
A sender discovers that three out of ten items
previously shipped were not included in the
shipment. The
voidShipping event indicates
that those three items were not shipped.
553
7.2 Dispositions 554
This section specifies standard identifier values for the EPCIS DispositionID vocabulary. These 555
identifiers populate the
disposition field in an EPCIS event, as specified below. 556
7.2.1 URI structure 557
All disposition values specified in this section have the following form: 558
urn:epcglobal:cbv:disp:payload 559
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 24 of 62
where the payload part is a string as specified in the next section. Every payload string defined 560
herein contains only lower case letters and the underscore character.
561
7.2.2 Compliant usage 562
Each EPCIS event in a CBV-Compliant Document MAY include a disposition field. If the 563
disposition field is present, the value of the disposition field SHALL be a URI consisting of the 564
prefix
urn:epcglobal:cbv:disp: followed by the string specified in the first column of some row 565
of the table below. The portion following the prefix SHALL be written exactly as specified in the table 566
below, in all lowercase letters (possibly including underscores, as indicated). 567
Each EPCIS event in a CBV-Compatible Document MAY include a disposition field, and the value 568
of the
disposition field MAY be a URI as specified above for a CBV-Compliant document, and MAY 569
be any other URI that meets the general requirements specified in [EPCIS1.2], Section 6.4, except
570
for those URIs which in this standard are forbidden or designated for a different purpose. 571
7.2.2.1 Example of correct and incorrect usage (non-normative) 572
The following shows an excerpt of a CBV-Compliant EPCIS document in XML format containing a 573
single event, where the disposition of that event is the Core Business Vocabulary “in progress” 574
value: 575
<epcis:EPCISDocument xmlns:epcis="urn:epcglobal:epcis:xsd:1" ...> 576
<EPCISBody> 577
<EventList> 578
<ObjectEvent> 579
... 580
<disposition>urn:epcglobal:cbv:disp:in_progress</disposition> 581
... 582
</ObjectEvent> 583
</EventList> 584
</EPCISBody> 585
</epcis:EPCISDocument> 586
The following example is NOT CBV-Compliant, because it does not use the full URI string in the 587
disposition field. It is also not CBV-Compatible, because the value of the disposition field is not a 588
URI with an owning authority, as required by Section 6.4 of [EPCIS1.2].
589
<epcis:EPCISDocument xmlns:epcis="urn:epcglobal:epcis:xsd:1" ...> 590
<EPCISBody> 591
<EventList> 592
<ObjectEvent> 593
... 594
<disposition>in_progress</disposition> WRONG 595
... 596
</ObjectEvent> 597
</EventList> 598
</EPCISBody> 599
</epcis:EPCISDocument> 600
Additional examples may found in Section 11.1
. 601
7.2.3 Element Values and definitions – Dispositions 602
Dispositions
Value Definition Examples
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 25 of 62
Dispositions
active
A commissioned object has
just been introduced into
the supply chain.
Manufacturer A commissions tags for 10 cases of product.
A virtual document has been assigned an EPC
Business step:
commissioning
container_clo
sed
Object has been loaded onto
a container, the doors have
been closed and the
shipment sealed.
Container is being closed and will be awaiting pickup in the yard.
Container is being closed and electronic seal is applied.
Business step:
staging_outbound
damaged
Object is impaired in its
usefulness and/or reduced
in value due to a defect.
Pallet pool operator P notices that a plank of a pallet is broken and
records this incident by scanning the EPC of the pallet.
Retailer R receives a shipment where the product packages on the
pallet have been dented
Business step:
accepting
inspecting
receiving
removing
repairing
replacing
destroyed
Object has been fully
rendered non-usable.
Incinerator Operator B indicates that product and packaging have
been incinerated
Business step:
destroying
dispensed
A full quantity of product is
distributed to a consumer.
A pharmacist dispenses a pharmaceutical in a container’s totality
to fill a specific prescription written by a physician, to a consumer
or patient.
A deli manager slices the complete contents of a 5 pound package
of turkey for sale.
NOTE: this disposition reflects the disposition of the original object,
not what was dispensed.
disposed
Object has been returned
for disposal.
A package of pharmaceuticals has been picked up by a distributor
and will be subsequently destroyed
encoded
An instance-level identifier
has been written to a
barcode or RFID tag, but not
yet commissioned.
3rd Party has written EPCs to tags and returns spool of case tags
to Manufacturer
Business step:
encoding
expired
Object is past expiration
date.
Distributor Y indicates that a product is past its expiration date
Business step:
holding
staging_outbound
storing
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 26 of 62
Dispositions
in_progress
Default disposition for object
proceeding through points in
the supply chain.
Product arrives at a location and is being accepted and verified.
Product is being prepared for shipment.
Business step:
receiving
picking
loading
accepting
staging_outbound
arriving
void_shipping
in_transit
Object being shipped
between two trading
partners.
Shipper Z pulled a container/product out of a manufacturer’s yard
on to a road
Business step:
shipping
departing
inactive
Decommissioned object that
may be reintroduced to the
supply chain.
A reusable tag is removed from a reusable transport item.
A digital coupon or an empties refund voucher has been redeemed
at retail point-of-sale
Business step:
decommissioning
no_pedigree_m
atch
In validating the pedigree
for the object, no match was
found, causing the product
to be quarantined for further
investigation and
disposition.
Distributor Y could not obtain a valid pedigree for a product from
its Manufacturer A
Business step:
holding
staging_outbound
storing
non_sellable_
other
Object cannot be sold to a
customer.
A product is not sellable pending further evaluation.
A product is not sellable, and one of the other dispositions
(
expired, recalled, damaged, no_pedigree_match) does
not apply.
Product has been sold and is awaiting customer pick-up.
Business step:
holding
inspecting
staging_outbound
storing
partially_dis
pensed
A portion of a product is
distributed to a customer,
while additional product is
retained for subsequent
distribution.
A pharmacist dispenses 10 pills from a 100-count bottle to fill a
customer prescription.
A deli manager slides and packages one pound of a 10 pound ham
for customer purchase.
NOTE: This disposition reflects the disposition of the original
object, not what was dispensed.
recalled
Object is non-sellable
because of public safety
reasons.
Manufacturer A requested that all Retailers and Distributors return
its batteries that could overheat and explode
Business step:
holding
staging_outbound
storing
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 27 of 62
Dispositions
reserved
Instance-level identifier has
been allocated for a third
party.
Distributor receives EPC numbers and can encode tag with the
numbers.
Business step:
reserving
retail_sold
Product has been purchased
by a customer.
A customer at Retailer X purchased a screwdriver by checking it
out through the point of sale system
Business step:
retail_selling
returned
Object has been sent back
for various reasons. It may
or may not be sellable.
Product is received at a returns centre from a customer because of
an over-shipment, recall, expired product, etc.
Business step:
receiving
holding
shipping
sellable_acce
ssible
Product can be sold as is
and customer can access
product for purchase.
Retailer X puts a case of screwdrivers on to a shelf or display
within customer reach
Business step:
stocking
receiving
sellable_not_
accessible
Product can be sold as is,
but customer cannot access
product for purchase.
Retailer X puts a case of screwdrivers on to a shelf in a store
backroom
Business step:
receiving
storing
loading
holding
inspecting
stolen
An object has been taken
without permission or right.
A pharmaceutical manufacturer completes an investigation of serial
numbers that are missing from inventory, and concludes that they
have been stolen
unknown
An object’s condition is not
known.
603
7.2.3.1 CBV 1.0 Disposition Values deprecated in CBV 1.1 604
CBV 1.0 defined several disposition values that are deprecated in CBV 1.1. The following table lists 605
the deprecated dispositions and the values which replace them in CBV 1.1. Each CBV 1.1 value 606
applies to all the situations that the corresponding CBV 1.0 value did, but may also be applied to 607
similar situations where the concept of “sellable” is not relevant. For example, in CBV 1.1 the 608
disposition damaged may be applied to a returnable asset, which was never considered “sellable” 609
even when it was undamaged. 610
CBV 1.0 Disposition (deprecated) CBV 1.1 Disposition
non_sellable_expired
expired
non_sellable_damaged
damaged
non_sellable_disposed
disposed
non_sellable_no_pedigree_match
no_pedigree_match
non_sellable_recalled
recalled
611
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 28 of 62
7.3 Business Transaction Types 612
This section specifies standard identifier values for the EPCIS BusinessTransactionTypeID 613
vocabulary. These identifiers may be used to populate the type attribute of a bizTransaction 614
element in an EPCIS event. See Section 8.5
for details of when these identifiers should be used. 615
7.3.1 URI structure 616
All business transaction type values specified in this section have the following form: 617
urn:epcglobal:cbv:btt:payload 618
where the
payload part is a string as specified in the next section. Every payload string defined 619
herein contains only lower case letters and the underscore character. 620
7.3.2 Compliant usage 621
Each EPCIS event in a CBV-Compliant Document MAY include one or more bizTransaction 622
elements. If
bizTransaction elements are present, each such element MAY include a type 623
attribute. If a given
bizTransaction element includes a type attribute, the value of the type 624
attribute SHALL be a URI consisting of the prefix
urn:epcglobal:cbv:btt: followed by the string 625
specified in the first column of some row of the table below. The portion following the prefix SHALL 626
be written exactly as specified in the table below, in all lowercase letters (possibly including 627
underscores, as indicated). See Section 8.5
for more compliance requirements concerning business 628
transaction types. 629
Non-Normative: Example (non-normative): An EPCIS document in XML format containing a 630
usage sample may be found in Section 11.1. 631
Each EPCIS event in a CBV-Compatible Document MAY include one or more bizTransaction 632
elements. If
bizTransaction elements are present, each such element MAY include a type 633
attribute. If a given
bizTransaction element includes a type attribute, the value of the type 634
attribute MAY be a URI as specified above for a CBV-Compliant document, and MAY be any other 635
URI that meets the general requirements specified in [EPCIS1.2], Section 6.4, except for those URIs
636
which in this standard are forbidden or designated for a different purpose. 637
7.3.3 Element Values and Definitions – Business Transaction Types 638
Business Transaction Types
Value Definition
bol
Bill of Lading. A document issued by a carrier to a shipper, listing and acknowledging receipt of goods
for transport and specifying terms of delivery
desadv
Despatch Advice. A document/message by means of which the seller or consignor informs the
consignee about the despatch of goods. Also called an “Advanced Shipment Notice,” but the value
desadv
is always used regardless of local nomenclature.
inv
Invoice. A document/message claiming payment for goods or services supplied under conditions
agreed by the seller and buyer.
pedigree
Pedigree. A record that traces the ownership or custody and transactions of a product as it moves
among various trading partners.
po
Purchase Order. A document/message that specifies details for goods and services ordered under
conditions agreed by the seller and buyer.
poc
Purchase Order Confirmation. A document that provides confirmation from an external supplier to
the request of a purchaser to deliver a specified quantity of material, or perform a specified service, at
a specified price within a specified time.
prodorder
Production Order. An organisation-internal document or message issued by a producer that initiates a
manufacturing process of goods.
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 29 of 62
Business Transaction Types
recadv
Receiving Advice. A document/message that provides the receiver of the shipment the capability to
inform the shipper of actual goods received, compared to what was advised as being sent.
rma
Return Merchandise Authorisation. A document issued by the seller that authorises a buyer to
return merchandise for credit determination.
7.4 Source/Destination types 639
This section specifies standard identifier values for the EPCIS SourceDestTypeID vocabulary. These 640
identifiers may be used to populate the type attribute of a source or destination element in an 641
EPCIS event. See Section 8.6
for details of when these identifiers should be used. 642
7.4.1 URI structure 643
All source/destination type values specified in this section have the following form: 644
urn:epcglobal:cbv:sdt:payload 645
where the
payload part is a string as specified in the next section. Every payload string defined 646
herein contains only lower case letters and the underscore character.
647
7.4.2 Compliant usage 648
Each EPCIS event in a CBV-Compliant Document MAY include one or more source and/or 649
destination elements. The value of the type attribute of the source or destination element 650
SHALL be a URI consisting of the prefix
urn:epcglobal:cbv:sdt: followed by the string specified 651
in the first column of some row of the table below. The portion following the prefix SHALL be written 652
exactly as specified in the table in Section 7.4.3, in all lowercase letters (possibly including 653
underscores, as indicated). See Section 8.6
for more compliance requirements concerning source 654
and destination types. 655
Non-Normative: Example (non-normative): An EPCIS document in XML format containing a 656
usage sample may be found in Section 11.1. 657
Each EPCIS event in a CBV-Compatible Document MAY include one or more source and/or 658
destination elements. The value of the type attribute of the source or destination element 659
MAY be a URI as specified above for a CBV-Compliant document, and MAY be any other URI that 660
meets the general requirements specified in [EPCIS1.2], Section 6.4, except for those URIs which in
661
this standard are forbidden or designated for a different purpose. 662
7.4.3 Element Values and Definitions – Source/Destination Types 663
Source/Destination Types
Value Definition
owning_party
The source or destination identifier denotes the party who owns (or is intended to own) the
objects at the originating endpoint or terminating endpoint (respectively) of the business
transfer of which this EPCIS event is a part.
possessing_party
The source or destination identifier denotes the party who has (or is intended to have) physical
possession of the objects at the originating endpoint or terminating endpoint (respectively) of
the business transfer of which this EPCIS event is a part.
location
The source or destination identifier denotes the physical location of the originating endpoint or
terminating endpoint (respectively) of the business transfer of which this EPCIS event is a part.
When a source of this type is specified on an EPCIS event at the originating endpoint of a
business transfer, the source identifier SHOULD be consistent with the Read Point specified in
that event. When a destination of this type is specified on an EPCIS event at the terminating
endpoint of a business transfer, the destination identifier SHOULD be consistent with the Read
Point specified in that event.
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 30 of 62
7.5 Error reason identifiers 664
This section specifies standard identifier values for the EPCIS ErrorReasonID vocabulary. These 665
identifiers may be used to populate the reason attribute of an errorDeclaration element in an 666
EPCIS event. 667
7.5.1 URI structure 668
All error reason identifier values specified in this section have the following form: 669
urn:epcglobal:cbv:er:payload 670
where the
payload part is a string as specified in the next section. Every payload string defined 671
herein contains only lower case letters and the underscore character. 672
7.5.2 Compliant usage 673
Each EPCIS event in a CBV-Compliant Document MAY include an ErrorDeclaration element, and 674
when present, the
ErrorDeclaration element MAY include a reason field. When present in a 675
CBV-Compliant Document, the value of the reason field of the
ErrorDeclaration element SHALL 676
be a URI consisting of the prefix
urn:epcglobal:cbv:er: followed by the string specified in the 677
first column of some row of the table in Section 7.5.3. The portion following the prefix SHALL be 678
written exactly as specified in the table below, in all lowercase letters (possibly including 679
underscores, as indicated). 680
Each EPCIS event in a CBV-Compatible Document MAY include an ErrorDeclaration element, 681
and when present, the
ErrorDeclaration element MAY include a reason field. When present in a 682
CBV-Compatible Document, the value of the reason attribute of the
ErrorDeclaration element 683
MAY be a URI as specified above for a CBV-Compliant document, and MAY be any other URI that 684
meets the general requirements specified in [EPCIS1.2], Section 6.4, except for those URIs which in
685
this standard are forbidden or designated for a different purpose. 686
7.5.3 Element Values and Definitions – Error reason identifiers 687
Error reason identifiers
Value Definition
did_not_occur
The prior event is considered erroneous because it did not actually occur. There are no
corrective events. (In a CBV-Compliant Document, this error reason SHALL NOT be used in an
error declaration that contains one or more corrective event IDs.)
incorrect_data
The prior event is considered erroneous because some or all of the data in the event are
incorrect. Subsequent events may provide a correct indication of what actually occurred when
the prior event was captured. These events may be linked using the corrective event IDs in the
error declaration.
8 User vocabularies 688
This section specifies syntax templates that end users may use to define vocabulary elements for 689
three EPCIS user vocabularies: physical or digital objects, locations (both read points and business 690
locations), and business transactions. 691
8.1 General considerations 692
Unlike the standard vocabularies discussed in Section 7, a vocabulary element in a User Vocabulary 693
is created by an End User. For example, an End User who creates a new business location such as a 694
new warehouse may create a business location identifier to refer to that location in EPCIS events. 695
The specific identifier string is defined by the End User, and its meaning may be described to trading 696
partners via master data exchange, or via some other mechanism outside of the EPCIS Query 697
Interface. 698
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 31 of 62
The EPCIS standard (Section 6.4) places general constraints on the identifiers that End Users may 699
create for use as User Vocabulary elements. Specifically, an identifier must conform to URI syntax, 700
and must either conform to syntax specified in GS1 standards or must belong to a subspace of URI 701
identifiers that is under the control of the end user who assigns them. 702
The Core Business Vocabulary provides additional constraints on the syntax of identifiers for user 703
vocabularies, so that CBV-Compliant documents will use identifiers that have a predictable 704
structure. This in turn makes it easier for trading partners to understand the meaning of such 705
identifiers. 706
For each user vocabulary considered here, several different syntax templates are provided for 707
constructing vocabulary elements: 708
■ EPC URI: An Electronic Product Code “pure identity” URI may be used as a user vocabulary 709
element. EPCs have a structure and meaning that is widely understood. EPCs may also be 710
encoded into data carriers such as RFID tags and barcodes according to GS1 standards. For this 711
reason, EPCs are often the best choice for creating user vocabulary elements when it is possible 712
to do so. 713
■ Private or Industry-wide URN: A Uniform Resource Name (URN) of the form 714
urn:URNNamespace:… may be used as a user vocabulary element. Doing so requires that the 715
user who creates the vocabulary element be authorised to use the URN namespace that appears 716
following the urn: prefix. For example, the End User may register its own URN namespace with 717
the Internet Assigned Numbers Authority (IANA). Alternatively, an industry consortium or other 718
trading group could register a URN namespace, and define a syntax template beginning with this 719
namespace for use by its members in creating vocabulary elements. Because of the difficulty of 720
registering a URN namespace, this method is typically used by trading groups, not individual 721
end users. 722
■ HTTP URL: A Uniform Resource Locator (URL) of the form 723
http://Domain/
… may be used as a user vocabulary element. Doing so requires that the user 724
who creates the vocabulary element be authorised to use the Internet domain name that 725
appears following the
http: prefix. Often a subdomain of the End User’s organisation domain is 726
used; for example, the Example Corporation may choose to use epcis.example.com as a 727
domain name for constructing user vocabulary identifiers. Because registering an Internet 728
domain name is relatively easy, this method is quite appropriate for use by individual end users 729
as well as by industry groups. 730
Note that HTTP URLs used as EPCIS user vocabulary elements do not necessarily refer to a web 731
page. They are just identifiers (names) that happen to use the HTTP URI scheme for the sake of 732
convenience. 733
734
Further details about each of these three forms are specified below. 735
Non-Normative: Explanation: The reason that several different syntax templates are 736
provided for each user vocabulary is to provide flexibility for end users to meet their business 737
requirements. Use of an EPC is preferred for most end user vocabularies; however, EPC codes 738
are somewhat constrained in syntax (e.g., limitations on character set and number of 739
characters allowed), and may not easily accommodate the construction of identifiers based on 740
codes already in use within legacy business systems. The other forms provide an alternative. 741
8.1.1 General Considerations for EPC URIs as User Vocabulary Elements 742
Where an EPC URI is used as a User Vocabulary Element, both CBV-Compliant and CBV-Compatible 743
documents SHALL use an EPC Pure Identity URI, except as noted below. An EPC Pure Identity URI is 744
a URI as specified in [TDS1.9], Section 6 (specifically, a URI matching the grammar production
745
EPC-URI in [TDS1.9], Section 6.3). EPC “pure identity” URIs begin with urn:epc:id:…. 746
Both CBV-Compliant and CBV-Compatible documents SHALL NOT use any of the other URI forms for 747
EPCs defined in [TDS1.9]. In particular, documents SHALL NOT use EPC Tag URIs 748
(urn:epc:tag:…) , EPC Pure Identity Pattern URIs (urn:epc:idpat:…), or EPC Pattern URIs 749
(urn:epc:
pat:…), except that both CBV-Compliant and CBV-Compatible documents MAY use EPC 750
Pattern URIs for class-level identification of objects as specified in Section 8.3.1
. Both CBV-751
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 32 of 62
Compliant and CBV-Compatible documents MAY use EPC Raw URIs (urn:epc:raw:…) as defined in 752
[TDS1.9], Section 12, provided that the raw value cannot be decoded as an EPC. Both CBV-753
Compliant and CBV-Compatible documents SHALL NOT use an EPC Raw URI representing EPC 754
memory bank contents that could be successfully decoded into an EPC Pure Identity URI according 755
to [TDS1.9]. 756
Non-Normative: Explanation: [EPCIS1.2] specifies that “When the unique identity [for an 757
instance-level identifier in the “what” dimension] is an Electronic Product Code, the 758
[identifier] SHALL be the “pure identity” URI for the EPC as specified in [TDS1.9], Section 6.
759
Implementations MAY accept URI-formatted identifiers other than EPCs.” The above language 760
clarifies this requirement, and provides more specific references to [TDS1.9]. The above 761
language also extends these restrictions to the use of EPC URIs in other dimensions of EPCIS 762
events beyond the “what” dimension. 763
8.1.2 General Considerations for Private or Industry-wide URN as User Vocabulary 764
elements 765
Where specified in Sections 8.2 through 8.5
, a CBV-Compliant document or CBV-Compatible 766
document MAY use a private or industry-wide URN as specified below. 767
A Private or Industry-wide URN SHALL have the following form: 768
urn:URNNamespace:**:qual:Remainder 769
where the components of this template are as follows:
770
Template Component Description
urn:
The characters
u
,
r
,
n
, and
:
(colon).
URNNamespace
A URN Namespace registered with the Internet Assigned Numbers Authority according to
[RFC2141].
:**:
Denotes either a single colon character or any string that conforms to the requirements of
[RFC2141] and any syntax rules defined for the registered URN namespace, and which begins
and ends with a colon character. In other words, any number of additional subfields may be
included between the URN Namespace and the
qual component, in order to provide flexibility
for URN Namespace owners to administer their namespace.
qual
:
A qualifier as specified in Sections 8.2 through 8.5, depending on the type of identifier.
Remainder
The remainder of the identifier as specified in Sections 8.2 through 8.5.
771
In addition, an identifier of this form SHALL be 128 characters or fewer, and SHOULD be 772
60 characters or fewer. 773
Identifiers of this form must be assigned by the owner of the URN Namespace. The owner of the 774
URN Namespace may delegate the authority to assign new identifiers to End Users or other parties, 775
provided that appropriate rules are employed to ensure global uniqueness. 776
8.1.3 General Considerations for HTTP URLs as User Vocabulary elements 777
Where specified in Sections 8.2 through 8.5
, a CBV-Compliant document or CBV-Compatible 778
document MAY use an HTTP URL. 779
An HTTP URL SHALL have the following form: 780
http://[Subdomain.]Domain/**/qual/Remainder 781
where the components of this template are as follows: 782
Template Component Description
http://
The seven characters
h
,
t
,
t
,
p
,
:
(colon),
/
(slash), and
/
(slash).
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 33 of 62
Template Component Description
[Subdomain.]Domain
An Internet Domain name that has been registered with an Internet Domain Name Registrar,
optionally preceded by one or more subdomain names.
For example, if example.com is a registred Internet Domain Name, then the following are
acceptable values for this component:
example.com
epcis.example.com
a.rather.verbose.example.com
Unless there is a reason to do otherwise, epcis.example.com is recommended for most End
Users (where the End User substitutes its own company or organisational Domain Name for
example.com).
Explanation (non-normative): Use of a subdomain dedicated to EPCIS, such as
epcis.example.com, helps to avoid the possibility of conflict with other uses of the company
or organisational domain name, such as URLs of web pages on the company web site. While
HTTP URLs used as identifiers in EPCIS events are not usually intended to be dereferenced via
a web browser, it is usually helpful to emphasise this fact by making the URL distinct from the
URLs used by the company web site.
/**/
Denotes either a single slash character, or any string that matches the grammar rule path-
absolute defined in [RFC3986], Section 3.3. In other words, any number of additional path
components may be included between the authority component and the obj component, in
order to provide flexibility for domain owners to administer their namespace.
qual
/
A qualifier as specified in Sections 8.2 through 8.5, depending on the type of identifier.
Remainder
The remainder of the identifier as specified in Sections 8.2 through 8.5
.
783
In addition, an identifier of this form SHALL be 128 characters or fewer, and SHOULD be 784
60 characters or fewer. 785
Identifiers of this form must be assigned by the owner of the Internet domain Domain. The owner of 786
the domain may delegate the authority to assign new identifiers to other parties, provided that 787
appropriate rules are employed to ensure global uniqueness. 788
8.2 Physical or digital objects (Instance-Level Identification) 789
Instance-level identifiers for physical or digital objects populate the “what” dimension of EPCIS 790
events. This includes the epcList, parentID, childEPCs, inputEPCs, and outputEPCs fields in 791
EPCIS ObjectEvents, AggregationEvents, TransacationEvents, and TransformationEvents. See 792
Section 1 of [EPCIS1.2] for a further definition of “object” in this sense, also reproduced below.
793
A CBV-Compliant document SHALL use one of the three URI forms specified in this section to 794
populate the above fields of EPCIS events, for every such field that is not null. A CBV-Compatible 795
document MAY use one of the three URI forms specified in this section, or MAY use any other URI 796
that meets the general requirements specified in [EPCIS1.2], Section 6.4, except for those URIs
797
which in this standard are forbidden or designated for a different purpose. 798
Both CBV-Compliant and CBV-Compatible documents SHOULD use the EPC URI form as specified in 799
Section 8.2.1
unless there is a strong reason to do otherwise. 800
Non-Normative: Explanation, quoted from [EPCIS1.2]: “Objects” in the context of EPCIS 801
typically refers to physical objects that are identified either at a class or instance level and 802
which are handled in physical handling steps of an overall business process involving one or 803
more organisations. Examples of such physical objects include trade items (products), logistic 804
units, returnable assets, fixed assets, physical documents, etc. “Objects” may also refer to 805
digital objects, also identified at either a class or instance level, which participate in 806
comparable business process steps. Examples of such digital objects include digital trade 807
items (music downloads, electronic books, etc.), digital documents (electronic coupons, etc.), 808
and so forth. Throughout this document the word “object” is used to denote a physical or 809
digital object, identified at a class or instance level, that is the subject of a business process 810
step. Section 8.2
of this CBV standard defines identifier structures for instance-level 811
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 34 of 62
identification of Objects; Section 8.3 defines identifier structures for class-level identification 812
of Objects. 813
8.2.1 EPC URI for Instance-level identification of objects 814
A CBV-Compliant document or CBV-Compatible document MAY use an EPC Pure Identity URI as 815
specified in Section 8.1.1
to populate the epcList, parentID, and childEPCs fields in EPCIS 816
ObjectEvents, AggregationEvents, and TransacationEvents. Both CBV-Compliant and 817
CBV-Compatible documents SHOULD use this form unless there is a strong reason to do otherwise. 818
Both CBV-Compliant and CBV-Compatible documents SHALL NOT use an SGLN EPC 819
(
urn:epc:id:sgln:…) as an Object identifier. 820
Both CBV-Compliant and CBV-Compatible documents SHALL NOT use any of the other URI forms for 821
EPCs defined in [TDS1.9]; see Section 8.1.1 for details. 822
8.2.2 Private or Industry-wide URN for Instance-level identification of objects 823
A CBV-Compliant document or CBV-Compatible document MAY use a private or industry-wide URN 824
as specified below to populate the
epcList, parentID, and childEPCs fields in EPCIS 825
ObjectEvents, AggregationEvents, and TransacationEvents. However, both CBV-826
Compliant and CBV-Compatible documents SHOULD use the EPC URI form (Section 8.2.1
) unless 827
there is a strong reason to do otherwise. See Section
8.1 for general considerations regarding the 828
use of Private or Industry-wide URI identifiers. 829
A Private or Industry-wide URI suitable for populating the epcList, parentID, and childEPCs 830
fields of EPCIS events SHALL have the following form: 831
urn:URNNamespace:**:obj:Objid 832
where the components of this template are as follows:
833
Template Component Description
urn:
URNNamespace
:**:
As specified in Section 8.1.2.
obj:
The characters
o
,
b
,
j
, and
:
(colon).
Objid
An identifier for the object that complies with the requirements of [RFC2141] and any
syntax rules defined for the registered URN namespace
URNNamespace, and which does
not contain a colon character. This identifier must be unique relative to all other
identifiers that begin with the same prefix.
834
Identifiers of this form must be assigned by the owner of the URN Namespace. The owner of the 835
URN Namespace may delegate the authority to assign new identifiers to End Users or other parties, 836
provided that appropriate rules are employed to ensure global uniqueness. 837
Non-Normative: Example (non-normative): An EPCIS document in XML format containing a 838
usage sample may be found in Section 11.2
. 839
8.2.3 HTTP URLs for Instance-level identification of objects 840
A CBV-Compliant document or CBV-Compatible document MAY use an HTTP URL as specified below 841
to populate the
epcList, parentID, and childEPCs fields in EPCIS ObjectEvents, 842
AggregationEvents, and TransacationEvents. However, both CBV-Compliant and CBV-843
Compatible documents SHOULD use the EPC URI form (Section 8.2.1) unless there is a strong 844
reason to do otherwise. See Section
8.1 for general considerations regarding the use of HTTP URL 845
identifiers. 846
An HTTP URL suitable for populating the epcList, parentID, and childEPCs fields of EPCIS 847
events SHALL have the following form: 848
http://[Subdomain.]Domain/**/obj/Objid 849
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 35 of 62
where the components of this template are as follows: 850
Template Component Description
http://
[Subdomain.]Domain/
**/
As specified in Section 8.1.3.
obj/
The characters
o
,
b
,
j
, and
/
(slash).
Objid
An identifier for the object that matches the grammar rule
segment-nz defined in [RFC3986], Section 3.3 (among other
things, this means Objid may not contain a slash character),
and which is unique relative to all other identifiers that begin
with the same prefix.
851
Identifiers of this form must be assigned by the owner of the Internet domain Domain. The owner of 852
the domain may delegate the authority to assign new identifiers to other parties, provided that 853
appropriate rules are employed to ensure global uniqueness. 854
Non-Normative: Example (non-normative): An EPCIS document in XML format containing a 855
usage sample may be found in Section 11.2
. 856
8.3 Physical or digital objects (Class-level identification) 857
Class-level identifiers for physical or digital objects populate the “what” dimension of EPCIS events. 858
This includes the
epcClass field within the EPCIS QuantityEvent (deprecated in EPCIS 1.1) and 859
within the
quantityElement structures of EPCIS ObjectEvents, AggregationEvents, 860
TransacationEvents, and TransformationEvents. See Section 1 of [EPCIS1.2] for a further 861
definition of “object” in this sense, also reproduced below. 862
A CBV-Compliant document SHALL use one of the three URI forms specified in this section to 863
populate the above fields of EPCIS events, for every such field that is not null. A CBV-Compatible 864
document MAY use one of the three URI forms specified in this section, or MAY use any other URI 865
that meets the general requirements specified in [EPCIS1.2], Section 6.4, except for those URIs
866
which in this standard are forbidden or designated for a different purpose. 867
Both CBV-Compliant and CBV-Compatible documents SHOULD use the EPC URI form as specified in 868
Section 8.3.1
unless there is a strong reason to do otherwise. 869
Non-Normative: Explanation (non-normative), quoted from [EPCIS1.2]: “Objects” in the 870
context of EPCIS typically refers to physical objects that are identified either at a class or 871
instance level and which are handled in physical handling steps of an overall business process 872
involving one or more organisations. Examples of such physical objects include trade items 873
(products), logistic units, returnable assets, fixed assets, physical documents, etc. “Objects” 874
may also refer to digital objects, also identified at either a class or instance level, which 875
participate in comparable business process steps. Examples of such digital objects include 876
digital trade items (music downloads, electronic books, etc.), digital documents (electronic 877
coupons, etc.), and so forth. Throughout this document the word “object” is used to denote a 878
physical or digital object, identified at a class or instance level, that is the subject of a 879
business process step. Section 8.2
of this CBV standard defines identifier structures for 880
instance-level identification of Objects; Section
8.3 defines identifier structures for class-level 881
identification of Objects. 882
8.3.1 EPC URI for Class-level identification of objects 883
A CBV-Compliant document or CBV-Compatible document MAY use one of the following URI forms 884
specified in the EPC Tag Data standard to populate the
epcClass field within the EPCIS 885
QuantityEvent (deprecated in EPCIS 1.1) and within the quantityElement structures of EPCIS 886
ObjectEvents, AggregationEvents, TransacationEvents, and TransformationEvents: 887
Identifier Type URI Form Normative Reference
GTIN
urn:epc:idpat:sgtin:
CCC
.
III
.*
[TDS1.9, Section 8]
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 36 of 62
Identifier Type URI Form Normative Reference
GTIN+batch/lot
urn:epc:class:lgtin:
CCC
.
III
.
LLL
[TDS1.9, Section 6]
GRAI (no serial)
urn:epc:idpat:grai:
CCC
.
TTT
.*
[TDS1.9, Section 8]
GDTI (no serial)
urn:epc:idpat:gdti:
CCC
.
TTT
.*
[TDS1.9, Section 8]
GCN (no serial)
urn:epc:idpat:sgcn:
CCC
.
TTT
.*
[TDS1.9, Section 8]
CPI (no serial)
urn:epc:idpat:cpi:
CCC
.
TTT
.*
[TDS1.9, Section 8]
where: 888
■ CCC is the GS1 Company Prefix portion of an EPC Pure Identity Pattern URI 889
■ III is the Indicator + Item Reference portion of an SGTIN EPC Pure Identity Pattern URI or the 890
Indicator + Item Reference portion of an LGTIN EPC Class URI 891
■ TTT is the Returnable Asset Type, Document Type, Coupon Reference, or Component/Part Type 892
portion of an EPC Pure Identity Pattern for GRAI, GDTI, SGCN, or CPI, respectively. 893
A CBV-Compliant document or CBV-Compatible document SHALL NOT use any other Pure Identity 894
Pattern URI form specified in [TDS1.9, Section 8]. This includes, for example, an SSCC Pure Identity
895
Pattern URI, or an SGTIN Pure Identity Pattern URI with two “*” wildcards. 896
Both CBV-Compliant and CBV-Compatible documents SHALL NOT use any of the other URI forms for 897
EPCs defined in [TDS1.9]; see Section 8.1.1
for details. 898
8.3.1.1 Explanation (non-normative) 899
The EPC Tag Data standard defines EPC Pure Identity Pattern URIs as a way to specify a pattern 900
that matches many instance-level EPCs. For example, the EPC Pure Identity Pattern URI 901
urn:epc:idpat:sgtin:0614141.112345.* matches any SGTIN URI that begins with 902
urn:epc:idpat:sgtin:0614141.112345, for example the specific SGTIN URI 903
urn:epc:idpat:sgtin:0614141.112345.400. In the EPCIS Simple Event Query, such a 904
pattern may be used to match EPCIS events whose “what” dimension contains instance-level 905
identifiers that have a specified GTIN and any serial number. 906
The table above specifies the use of EPC Pure Identity Pattern URIs to achieve a second purpose, 907
namely as class-level identifiers for use in the Quantity Element fields of EPCIS events. In this 908
usage, the URI
urn:epc:idpat:sgtin:0614141.112345.* refers to the object class identified 909
by GTIN 10614141123459. 910
Not all EPC Pure Identity Pattern URIs make sense as class-level identifiers. For example, when 911
urn:epc:idpat:sgtin:0614141.*.* is used in an EPCIS query to match instance-level 912
identifiers, it matches all SGTIN identifiers that include GS1 Company Prefix 0614141. This is valid 913
as a matching condition for a query, but there is no corresponding object class and so this is not a 914
valid class-level identifier. A similar argument applies to a URI such as 915
urn:
epc:idpat:sscc:0614141.*, and the other EPC Pattern URIs not included in the table 916
above. 917
8.3.2 Private or Industry-wide URN for Class-level identification of objects 918
A CBV-Compliant document or CBV-Compatible document MAY use a private or industry-wide URN 919
as specified below to populate the
epcClass field within the EPCIS QuantityEvent (deprecated in 920
EPCIS 1.1) and within the quantityElement structures of EPCIS ObjectEvents, 921
AggregationEvents, TransacationEvents, and TransformationEvents. However, both 922
CBV-Compliant and CBV-
Compatible documents SHOULD use the EPC URI form (Section 8.3.1) 923
unless there is a
strong reason to do otherwise. See Section 8.1 for general considerations 924
regarding the use of Private or Industry-wide URI identifiers. 925
A Private or Industry-wide URI suitable for populating the epcClass field of EPCIS events SHALL 926
have the following form: 927
urn:URNNamespace:**:class:ObjClassid 928
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 37 of 62
where the components of this template are as follows: 929
Template Component Description
urn:
URNNamespace
:**:
As specified in Section 8.1.2.
class:
The characters
c
,
l
,
a
,
s
,
s
, and
:
(colon).
ObjClassid
An identifier for the object class that complies with the requirements of [RFC2141] and
any syntax rules defined for the registered URN namespace
URNNamespace, and which
does not contain a colon character. This identifier must be unique relative to all other
identifiers that begin with the same prefix.
Identifiers of this form must be assigned by the owner of the URN Namespace. The owner of the 930
URN Namespace may delegate the authority to assign new identifiers to End Users or other parties, 931
provided that appropriate rules are employed to ensure global uniqueness. 932
Non-Normative: Example (non-normative): An EPCIS document in XML format containing a 933
usage sample may be found in Section 11.2
. 934
8.3.3 HTTP URLs for Class-level identification of objects 935
A CBV-Compliant document or CBV-Compatible document MAY use an HTTP URL as specified below 936
to populate the
epcClass field within the EPCIS QuantityEvent (deprecated in EPCIS 1.1) and 937
within the quantityElement structures of EPCIS
ObjectEvents, AggregationEvents, 938
TransacationEvents, and TransformationEvents. However, both CBV-Compliant and CBV-939
Compatible documents SHOULD use the EPC URI form (Section 0
) unless there is a strong reason to 940
do otherwise. See Section
8.1 for general considerations regarding the use of HTTP URL identifiers. 941
An HTTP URL suitable for populating the epcClass fields of EPCIS events SHALL have the following 942
form: 943
http://[Subdomain.]Domain/**/class/ObjClassid 944
where the components of this template are as follows: 945
Template Component Description
http://
[Subdomain.]Domain/
**/
As specified in Section 8.1.3.
class/
The characters
c
,
l
,
a
,
s
,
s
, and
/
(slash).
ObjClassid
An identifier for the object class that matches the grammar rule segment-
nz defined in [RFC3986],
Section 3.3 (among other things, this means
ObjClassid may not contain a slash character), and which is unique relative
to all other identifiers that begin with the same prefix.
946
Identifiers of this form must be assigned by the owner of the Internet domain Domain. The owner of 947
the domain may delegate the authority to assign new identifiers to other parties, provided that 948
appropriate rules are employed to ensure global uniqueness. 949
Non-Normative: Example: An EPCIS document in XML format containing a usage sample 950
may be found in Section 11.2
. 951
8.4 Locations 952
Identifiers for locations populate the “where” dimension of EPCIS events. This includes the 953
readPoint and businessLocation fields in all EPCIS event types. 954
A CBV-Compliant document SHALL use one of the four URI forms specified in this section to 955
populate the above fields of EPCIS events, for every such field that is not null. A CBV-Compatible 956
document MAY use one of the four URI forms specified in this section, or MAY any other URI that 957
meets the general requirements specified in [EPCIS1.2], Section 6.4, except for those URIs which in
958
this standard are forbidden or designated for a different purpose. 959
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 38 of 62
Both CBV-Compliant and CBV-Compatible documents SHOULD use the EPC URI form as specified in 960
Section 8.4.1
unless there is a strong reason to do otherwise. 961
8.4.1 EPC URI for Location identifiers 962
A CBV-Compliant document or CBV-Compatible document MAY use an EPC Pure Identity URI as 963
specified in Section 8.1.1
to populate the readPoint and businessLocation fields in all EPCIS 964
event types. Both CBV-Compliant and CBV-Compatible documents SHOULD use this form unless 965
there is a strong reason to do otherwise. 966
Both CBV-Compliant and CBV-Compatible documents SHOULD NOT use EPC schemes other than 967
SGLN EPCs (
urn:epc:id:sgln:…) for location identifiers, unless there is a strong reason to do so. 968
Both CBV-Compliant and CBV-Compatible documents SHALL NOT use any of the other URI forms for 969
EPCs defined in [TDS1.9]; see Section 8.1.1 for details. 970
8.4.2 Private or Industry-wide URN for Location identifiers 971
A CBV-Compliant document or CBV-Compatible document MAY use a private or industry-wide URN 972
as specified below to populate the
readPoint and businessLocation fields in all EPCIS event 973
types. However, both CBV-Compliant and CBV-Compatible documents SHOULD use the EPC URI 974
form (Section 8.4.1) unless there is a strong reason to do otherwise. See Section 8.1
for general 975
considerations regarding the use of Private or Industry-wide URI identifiers. 976
A Private or Industry-wide URI suitable for populating the readPoint and businessLocation 977
fields in all EPCIS event types SHALL have the following form: 978
urn:URNNamespace:**:loc:Locid 979
where the components of this template are as follows: 980
Template Component Description
urn:
URNNamespace
:**:
As specified in Section 8.1.2.
loc:
The characters
l
,
o
,
c
, and
:
(colon).
Locid
An identifier for the location that complies with the requirements of [RFC2141] and any
syntax rules defined for the registered URN namespace
URNNamespace, and which does
not contain a colon character. This identifier must be unique relative to all other identifiers
that begin with the same prefix.
Identifiers of this form must be assigned by the owner of the URN Namespace. The owner of the 981
URN Namespace may delegate the authority to assign new identifiers to End Users or other parties, 982
provided that appropriate rules are employed to ensure global uniqueness. 983
Non-Normative: Example (non-normative): An EPCIS document in XML format containing a 984
usage sample may be found in Section 11.2
. 985
8.4.3 HTTP URLs for Location identifiers 986
A CBV-Compliant document or CBV-Compatible document MAY use an HTTP URL as specified below 987
to populate the
readPoint and businessLocation fields in all EPCIS event types. However, both 988
CBV-Compliant and CBV-Compatible documents SHOULD use the EPC URI form (Section 8.4.1) 989
unless there is a strong reason to do otherwise. See Section
8.1 for general considerations 990
regarding the use of HTTP URL identifiers. 991
An HTTP URL suitable for populating the readPoint and businessLocation fields in all EPCIS 992
event types SHALL have the following form: 993
http://[Subdomain.]Domain/**/loc/Locid 994
where the components of this template are as follows: 995
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 39 of 62
Template Component Description
http://
[Subdomain.]Domain/
**/
As specified in Section 8.1.3.
loc/
The characters
l
,
o
,
c
, and
/
(slash).
Locid
An identifier for the location that matches the grammar rule segment-nz
defined in [RFC3986], Section 3.3 (among other things, this means Locid may
not contain a slash character), and which is unique relative to all other
identifiers that begin with the same prefix.
Identifiers of this form must be assigned by the owner of the Internet domain Domain. The owner of 996
the domain may delegate the authority to assign new identifiers to other parties, provided that 997
appropriate rules are employed to ensure global uniqueness. 998
Non-Normative: Example (non-normative): An EPCIS document in XML format containing a 999
usage sample may be found in Section 11.2
. 1000
8.4.4 Geographic Location URIs for Location identifiers 1001
A CBV-Compliant document or CBV-Compatible document MAY use a geographic location URI as 1002
specified in [RFC5870] to populate the
readPoint and businessLocation fields in all EPCIS 1003
event types. Such identifiers may be used in situations where it is not feasible to assign a unique 1004
location identifier; for example, to indicate the location of a ship on the open ocean. Both CBV-1005
Compliant and CBV-Compatible documents SHOULD use a location identifier as specified in 1006
Sections 8.4.1 through 8.4.3
(with preference given to the EPC URI form as specified in 1007
Section
8.4.1) unless a geographic location URI is the only feasible alternative. 1008
The syntax and meaning of geographic location URIs is specified in [RFC5870]. 1009
Non-Normative: Explanation (non-normative): The simplest form of RFC5870-compliant 1010
geographic location URI looks like this: geo:22.300,-118.44 1011
This example denotes the geographic location with latitude 22.300 degrees (north) and 1012
longitude 118.44 degrees (west). Other forms of the geo URI allow for the inclusion of 1013
altitude, uncertainty radius, and reference coordinate system. Please consult [RFC5870] for 1014
details of these and other considerations that apply to the use of the geographic location URI. 1015
8.5 Business transactions 1016
Identifiers for business transactions populate the “why” dimension of EPCIS events. This includes 1017
the
bizTrasactionList field in all EPCIS event types. 1018
The EPCIS standard provides for a business transaction to be identified by a pair of identifiers, the 1019
“business transaction identifier” (hereinafter “BTI”) that names a particular business transaction, 1020
and an optional “business transaction type” (hereinafter “BTT”) that says what kind of business 1021
transaction the identifier denotes (purchase order, invoice, etc.). Section 7.3
of this standard 1022
provides standardised values for BTTs. 1023
URI forms for BTIs are specified below. A CBV-Compliant document SHALL use one of the four URI 1024
forms specified in this section to populate the BTI field (text content of the
bizTransaction 1025
element) of EPCIS events, for every such field that is not null. A CBV-Compatible document MAY use 1026
one of the four URI forms specified in this section, or MAY use any other URI that meets the general 1027
requirements specified in [EPCIS1.2], Section 6.4, except for those URIs which in this standard are
1028
forbidden or designated for a different purpose. 1029
A bizTransaction element in an EPCIS event includes a BTI and an optional BTT in any of the 1030
following three combinations: 1031
■ If the goal is to communicate a business transaction identifier without indicating its type, a BTI 1032
is included and the BTT omitted. 1033
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 40 of 62
■ If the goal is to communicate a business transaction identifier and to indicate its type, and 1034
furthermore the type is one of the CBV standard types specified in Section 7.3
, a BTI is 1035
included, and one of the URIs specified in Section
7.3 is included as the BTT. 1036
■ If the goal is to communicate a business transaction identifier and to indicate its type, and 1037
furthermore the type is not one of the CBV standard types specified in Section 7.3
, the BTI is 1038
included, and some URI that does not begin with
urn:epcglobal:cbv:… is included as the 1039
BTT. (This is CBV-Compatible but not CBV-Compliant.) 1040
8.5.1 EPC URI for Business transaction identifiers 1041
A CBV-Compliant document or CBV-Compatible document MAY use an EPC Pure Identity URI as 1042
specified in Section 8.1.1
as a business transaction identifier in all EPCIS event types. 1043
Both CBV-Compliant and CBV-Compatible documents SHOULD NOT use EPC schemes other than 1044
GDTI EPCs
(urn:epc:id:gdti:…) or GSRN EPCs (urn:epc:id:gsrn:…) for business transaction 1045
identifiers, unless there is a strong reason to do so. GDTI EPCs SHOULD only be used as business 1046
transaction identifiers when they have been assigned to denote a business transaction, rather than 1047
a physical document not connected with any business transaction. 1048
Both CBV-Compliant and CBV-Compatible documents SHALL NOT use any of the other URI forms for 1049
EPCs defined in [TDS1.9]; see Section 8.1.1
for details. 1050
Non-Normative: Explanation (non-normative): One of the intended uses of the Global 1051
Document Type Identifier (GDTI) is to identify business transactions such as invoices, 1052
purchase orders, and so on. When a GDTI is used in this way, it is suitable for use as a 1053
business transaction identifier in EPCIS. However, many business information systems use 1054
other types of identifiers for business transactions, and so the use of GDTI is not as strongly 1055
recommended as SGLNs are for locations or other types of EPCs are for physical or digital 1056
objects. It is also for this reason that the form in Section 8.5.2
is provided. 1057
Non-Normative: Example (non-normative): An EPCIS document in XML format containing a 1058
usage sample may be found in Section 11.1. 1059
8.5.2 GLN-based identifier for legacy system business transaction identifiers 1060
A CBV-Compliant document or CBV-Compatible document MAY use a GLN-based identifier as 1061
specified below as a business transaction identifier in all EPCIS event types. 1062
A GLN-based URI suitable for use as a business transaction identifier in all EPCIS event types SHALL 1063
have the following form
: urn:epcglobal:cbv:bt:gln:transID where the components of this 1064
template are as follows: 1065
Template Component Description
urn:epcglobal:cbv:bt:
The 21 characters
u
,
r
,
n
, …,
b
,
t
, and
:
(colon).
gln:
A 13-digit Global Location Number (GLN) that identifies the business system within which
transID is defined, followed by a colon. This is typically a “party GLN” that identifies the
organisation responsible for the business transaction identifier, or a division of an
organisation that maintains a separate divisional business information system.
transID
An identifier for the business transaction that complies with the requirements of [RFC2141]
and which does not contain a colon character. This identifier must be unique relative to all
other identifiers that begin with the same prefix.
Identifiers of this form must be assigned by the owner of the GLN that is embedded in the identifier. 1066
The owner of the GLN may delegate the authority to assign new identifiers to other parties, provided 1067
that appropriate rules are employed to ensure global uniqueness. 1068
Non-Normative: Example (non-normative): An EPCIS document in XML format containing a 1069
usage sample may be found in Section 11.2
. 1070
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 41 of 62
8.5.3 Private or Industry-wide URN for business transaction identifiers 1071
A CBV-Compliant document or CBV-Compatible document MAY use a private or industry-wide URN 1072
as specified below as a business transaction identifier in all EPCIS event types. 1073
A private or industry-wide URN suitable for use as a business transaction identifier in all EPCIS 1074
event types SHALL have the following form: urn:URNNamespace:**:bt:transID where the 1075
components of this template are as follows: 1076
Template Component Description
urn:URNNamespace:**:
As specified in Section 8.1.2
.
bt:
The characters
b
,
t
, and
:
(colon).
transID
An identifier for the business transaction that complies with the requirements of [RFC2141]
and any syntax rules defined for the registered URN namespace URNNamespace, and which
does not contain a colon character. This identifier must be unique relative to all other
identifiers that begin with the same prefix.
Identifiers of this form must be assigned by the owner of the URN Namespace. The owner of the 1077
URN Namespace may delegate the authority to assign new identifiers to End Users or other parties, 1078
provided that appropriate rules are employed to ensure global uniqueness. 1079
Non-Normative: Example (non-normative): An EPCIS document in XML format containing a 1080
usage sample may be found in Section 11.2
1081
8.5.4 HTTP URLs for business transaction identifiers 1082
A CBV-Compliant document or CBV-Compatible document MAY use an HTTP URL as specified below 1083
as a business transaction identifier in all EPCIS event types. 1084
An HTTP URL suitable for use as a business transaction identifier in all EPCIS event types SHALL 1085
have the following form: http://[Subdomain.]Domain/**/bt/transID
where the components of this 1086
template are as follows: 1087
Template Component Description
http://[Subdomain.]Domain/**/
As specified in Section 8.1.3
.
bt/
The characters
b
,
t
, and
/
(slash).
transID
An identifier for the business transaction that matches the grammar rule
segment-nz defined in [RFC3986], Section 3.3 (among other things, this means
transID may not contain a slash character), and which is unique relative to all
other identifiers that begin with the same prefix.
Identifiers of this form must be assigned by the owner of the Internet domain Domain. The owner of 1088
the domain may delegate the authority to assign new identifiers to other parties, provided that 1089
appropriate rules are employed to ensure global uniqueness. 1090
Non-Normative: Example (non-normative): An EPCIS document in XML format containing a 1091
usage sample may be found in Section 11.2
. 1092
8.6 Source/Destination identifiers 1093
Identifiers for sources and destinations populate the source and destination elements 1094
(respectively) in the “why” dimension of EPCIS events. 1095
A CBV-Compliant document SHALL use one of the three URI forms specified in this section to 1096
populate the above fields of EPCIS events. A CBV-Compatible document MAY use one of the three 1097
URI forms specified in this section, or MAY use any other URI that meets the general requirements 1098
specified in [EPCIS1.2], Section 6.4, except for those URIs which in this standard are forbidden or 1099
designated for a different purpose. 1100
Both CBV-Compliant and CBV-Compatible documents SHOULD use the EPC URI form as specified in 1101
Section 8.6.1
unless there is a strong reason to do otherwise. 1102
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 42 of 62
8.6.1 EPC URI for Source/Destination identifiers 1103
A CBV-Compliant document or CBV-Compatible document MAY use an EPC Pure Identity URI as 1104
specified in Section 8.1.1 to populate the source and destination elements in all EPCIS event 1105
types. Both CBV-Compliant and CBV-Compatible documents SHOULD use this form unless there is a 1106
strong reason to do otherwise. 1107
Both CBV-Compliant and CBV-Compatible documents SHOULD NOT use EPC schemes other than 1108
SGLN EPCs (
urn:epc:id:sgln:…) for source and destination identifiers, unless there is a strong 1109
reason to do so. 1110
Both CBV-Compliant and CBV-Compatible documents SHALL NOT use any of the other URI forms for 1111
EPCs defined in [TDS1.9]; see Section 8.1.1
for details. 1112
8.6.2 Private or Industry-wide URN for Source/Destination identifiers 1113
A CBV-Compliant document or CBV-Compatible document MAY use a private or industry-wide URN 1114
as specified below, or a private or industry-wide URN as specified in Section 8.4.2, to populate the 1115
source and destination fields in all EPCIS event types. However, both CBV-Compliant and CBV-1116
Compatible documents SHOULD use the EPC URI form (Section 8.6.1
) unless there is a strong 1117
reason to do otherwise. See Section
8.1 for general considerations regarding the use of Private or 1118
Industry-wide URI identifiers. 1119
In addition to the private or industry-wide URN form as specified in Section 8.4.2, a Private or 1120
Industry-wide URI suitable for populating the source and destination fields in all EPCIS event 1121
types SHALL have the following form:
urn:URNNamespace:**:sd:Locid where the components 1122
of this template are as follows: 1123
Template Component Description
urn:URNNamespace:**: As specified in Section 8.1.2.
sd: The characters s, d, and : (colon).
Locid An identifier for the location that complies with the requirements of [RFC2141] and any syntax
rules defined for the registered URN namespace URNNamespace, and which does not contain a
colon character. This identifier must be unique relative to all other identifiers that begin with
the same prefix.
Identifiers of this form must be assigned by the owner of the URN Namespace. The owner of the 1124
URN Namespace may delegate the authority to assign new identifiers to End Users or other parties, 1125
provided that appropriate rules are employed to ensure global uniqueness. 1126
8.6.3 HTTP URLs for Source/Destination identifiers 1127
A CBV-Compliant document or CBV-Compatible document MAY use an HTTP URL as specified below, 1128
or an HTTP URL as specified in Section 8.4.3, to populate the
source and destination fields in all 1129
EPCIS event types. However, both CBV-Compliant and CBV-Compatible documents SHOULD use the 1130
EPC URI form (Section 8.6.1) unless there is a strong reason to do otherwise. See Section 8.1 for 1131
general considerations regarding the use of HTTP URL identifiers. 1132
In addition to the HTTP URL form as specified in Section 8.4.3, an HTTP URL suitable for populating 1133
the
source and destination fields in all EPCIS event types SHALL have the following form: 1134
http://[Subdomain.]Domain/**/sd/SourceOrDestId 1135
where the components of this template are as follows:
1136
Template Component Description
http://[Subdomain.]Domain/**/
As specified in Section 8.1.3.
sd/
The characters
s
,
d
, and
/
(slash).
SourceOrDestId
An identifier for the location that matches the grammar rule segment-nz defined in
[RFC3986], Section 3.3 (among other things, this means Locid may not contain a
slash character), and which is unique relative to all other identifiers that begin with
the same prefix.
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 43 of 62
Identifiers of this form must be assigned by the owner of the Internet domain Domain. The owner of 1137
the domain may delegate the authority to assign new identifiers to other parties, provided that 1138
appropriate rules are employed to ensure global uniqueness. 1139
8.7 Transformation identifiers 1140
Identifiers for transformations populate the transformationID field of EPCIS 1141
TransformationEvents. 1142
URI forms for transformation identifiers are specified below. A CBV-Compliant document SHALL use 1143
one of the four URI forms specified in this section to populate the
transformationID field of 1144
EPCIS
TransformationEvents, for every such field that is not null. A CBV-Compatible document 1145
MAY use one of the four URI forms specified in this section, or MAY use any other URI that meets 1146
the general requirements specified in [EPCIS1.2], Section 6.4, except for those URIs which in this 1147
standard are forbidden or designated for a different purpose. 1148
8.7.1 EPC URI for Transformation identifiers 1149
A CBV-Compliant document or CBV-Compatible document MAY use an EPC Pure Identity URI as 1150
specified in Section 8.1.1
to populate the transformationID field of EPCIS 1151
TransformationEvents. 1152
Both CBV-Compliant and CBV-Compatible documents SHOULD NOT use EPC schemes other than 1153
GDTI EPCs
(urn:epc:id:gdti:…) for transformation identifiers unless there is a strong reason to 1154
do so. GDTI EPCs SHOULD only be used as transformation identifiers when they have been assigned 1155
to denote a transformation, rather than a physical document not connected with any transformation. 1156
Both CBV-Compliant and CBV-Compatible documents SHALL NOT use any of the other URI forms for 1157
EPCs defined in [TDS1.9]; see Section 8.1.1 for details. 1158
Non-Normative: Explanation: One of the intended uses of the Global Document Type 1159
Identifier (GDTI) is to identify business transactions such as production orders which may be 1160
in one-to-one correspondence with transformations. When a GDTI is used in this way, it is 1161
suitable for use as a transformation identifier in EPCIS. However, many business information 1162
systems use other types of identifiers for transformations, and so the use of GDTI is not as 1163
strongly recommended as SGLNs are for locations or other types of EPCs are for physical or 1164
digital objects. It is also for this reason that the form in Section 8.7.2
is provided. 1165
8.7.2 GLN-based Identifier for Legacy System Transformation identifiers 1166
A CBV-Compliant document or CBV-Compatible document MAY use a GLN-based identifier as 1167
specified below 8.1.1 to populate the transformationID field of EPCIS TransformationEvents. 1168
A GLN-based URI SHALL have the following form: urn:epcglobal:cbv:xform:gln:xformID 1169
where the components of this template are as follows: 1170
Template Component Description
urn:epcglobal:cbv:xform:
The 24 characters
u
,
r
,
n
, …,
r
,
m
, and
:
(colon).
gln:
A 13-digit Global Location Number (GLN) that identifies the business system within which
xformID is defined, followed by a colon. This is typically a “party GLN” that identifies the
organisation responsible for the transformation identifier, or a division of an organisation
that maintains a separate divisional business information system.
xformID
An identifier for the transformation that complies with the requirements of [RFC2141] and
which does not contain a colon character. This identifier must be unique relative to all
other identifiers that begin with the same prefix.
Identifiers of this form must be assigned by the owner of the GLN that is embedded in the identifier. 1171
The owner of the GLN may delegate the authority to assign new identifiers to other parties, provided 1172
that appropriate rules are employed to ensure global uniqueness. 1173
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 44 of 62
8.7.3 Private or Industry-wide URN for Transformation identifiers 1174
A CBV-Compliant document or CBV-Compatible document MAY use a private or industry-wide URN 1175
as specified below to populate the transformationID field of EPCIS TransformationEvents. 1176
A private or industry-wide URN SHALL have the following form: 1177
urn:URNNamespace:**:xform:transID where the components of this template are as follows: 1178
Template Component Description
urn:URNNamespace:**:
As specified in Section 8.1.2
.
xform:
The characters
x
,
f
,
o
,
r
,
m
, and
:
(colon).
xformID
An identifier for the transformation that complies with the requirements of [RFC2141] and
any syntax rules defined for the registered URN namespace
URNNamespace, and which
does not contain a colon character. This identifier must be unique relative to all other
identifiers that begin with the same prefix.
Identifiers of this form must be assigned by the owner of the URN Namespace. The owner of the 1179
URN Namespace may delegate the authority to assign new identifiers to End Users or other parties, 1180
provided that appropriate rules are employed to ensure global uniqueness. 1181
8.7.4 HTTP URLs for Transformation identifiers 1182
A CBV-Compliant document or CBV-Compatible document MAY use an HTTP URL as specified below 1183
to populate the transformationID field of EPCIS TransformationEvents. 1184
An HTTP URL SHALL have the following form: 1185
http://[Subdomain.]Domain/**/xform/xformID 1186
where the components of this template are as follows: 1187
Template Component Description
http://[Subdomain.]Domain/**/
As specified in Section 8.1.3
.
xform/
The characters
x, f, o, r, m,
and / (slash).
xformID
An identifier for the transformation that matches the grammar rule segment-nz defined in
[RFC3986], Section 3.3 (among other things, this means xformID may not contain a slash
character), and which is unique relative to all other identifiers that begin with the same prefix.
Identifiers of this form must be assigned by the owner of the Internet domain Domain. The owner of 1188
the domain may delegate the authority to assign new identifiers to other parties, provided that 1189
appropriate rules are employed to ensure global uniqueness. 1190
Non-Normative: Example: An EPCIS document in XML format containing a usage sample 1191
may be found in Section 11.2. 1192
8.8 Event identifiers 1193
An event identifier may populate the
eventID field of an EPCIS event. When an EPCIS event 1194
includes an
eventID field, the identifier in that field must be globally unique (different from the 1195
event identifier in any other EPCIS event created by any party). Note that an EPCIS event is not 1196
required to include an event identifier. 1197
A CBV-Compliant document SHALL use the URI form specified in Section 8.8.1 to populate the 1198
eventID field of EPCIS events, for every such field that is not null. A CBV-Compatible document 1199
MAY use the URI form specified in Section 8.8.1, or MAY use any other URI that meets the general 1200
requirements specified in [EPCIS1.2], Section 6.4, except for those URIs which in this standard are
1201
forbidden or designated for a different purpose. 1202
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 45 of 62
8.8.1 Universally Unique Identifier (UUID) URIs for Event identifiers 1203
A CBV-Compliant document SHALL and a CBV-Compatible document MAY use a UUID Version 1 or 1204
Version 4 URI as specified in [RFC4122] to populate the
eventID fields in any EPCIS event where 1205
that field is not omitted. 1206
Non-Normative: Example: 1207
<eventID>urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6</eventID> 1208
9 Trade item master data 1209
This section specifies master data attributes that may be used to describe a trade item identifier 1210
that appears in the “what” dimension of an EPCIS event, including the EPC, Parent ID, and EPC 1211
Class fields. 1212
Different trade item identifiers are used at different levels of trade item identification. Each master 1213
data attribute defined in the CBV for trade item identifiers specifies one or more of the following 1214
three levels of identification to which it is applicable: 1215
Identification
Level
Description Typical Identifier Identifier
use in EPCIS
Event
Trade item-level A master data attribute that
applies to all instances of a
given trade item. As trade
items are usually identified
by a GTIN, this is often
called “GTIN-level”.
urn:epc:idpat:sgtin:0614141.112345.*
EPC Class
Lot-level A master data attribute that
applies to all instances of a
given trade item within a
specified batch or lot.
urn:epc:class:lgtin:0614141.112345.L123
EPC Class
Instance-level A master data attribute that
applies to a specific instance
of a trade item
urn:epc:id:sgtin:0614141.112345.400
EPC
Parent ID
1216
A CBV-Compliant or CBV-Compatible document MAY include any of the master data attributes 1217
specified in this section within the master data section of the EPCIS Header, subject to the 1218
constraints specified elsewhere in this section. The master data attributes specified in this section 1219
may also be used in an EPCIS Master Data Document or in the response to an EPCIS Master Data 1220
Query. A CBV-Compliant or CBV-Compatible document MAY include any of the lot-level or instance-1221
level master data attributes specified in this section in the ILMD section of an EPCIS event, but 1222
SHOULD NOT include trade item-level attributes in the ILMD section. 1223
When a master data attribute specified in this section is used in the master data section of the 1224
EPCIS Header, in an EPCIS Master Data Document, or in the response to an EPCIS Master Data 1225
Query, each such attribute applies to the specific identifier cited and also all matching identifiers at a 1226
lower level. For example, a master data attribute specified for the trade item-level identifier 1227
urn:epc:idpat:sgtin:0614141.112345.* would also apply to lot-level and instance-level 1228
identifiers that share the same GTIN. A master data attribute specified for the lot-level identifier 1229
urn:epc:class:lgtin:0614141.112345.L123 would also apply to instance-level identifiers 1230
that share the same GTIN and lot. 1231
When a master data attribute specified in this section is used in the ILMD section of an EPCIS event, 1232
it applies to all identifiers appearing in any
EPC or QuantityElement field within that event. 1233
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 46 of 62
9.1 Trade item master data attribute names 1234
In the master data section of an EPCIS header, in an EPCIS Master Data Document, and in the 1235
response to an EPCIS Master Data Query, a master data attribute is specified as a name/value pair. 1236
The name of every trade item master data attribute defined in this section consists of the following 1237
namespace identifier: 1238
urn:epcglobal:cbv:mda 1239
followed by a pound sign (#) character, followed by a local name as specified in Section 9.2. 1240
In the ILMD section of an EPCIS event, a master data attribute is specified as an XML element. The 1241
element name is an XML QName whose namespace is the same namespace identifier specified 1242
above and whose local name is the local name as specified in Section 9.2.
1243
Non-Normative: Example: Here is how the attribute sellByDate would appear in the 1244
EPCIS header, Master Data Document or Master Data Query response: 1245
<VocabularyElement id="urn:epc:class:lgtin:0614141.012345.L123"> 1246
<attribute id="urn:epcglobal:cbv:mda#sellByDate">2016-03-15</attribute> 1247
</VocabularyElement> 1248
Here is how the same attribute would appear in the ILMD section of an event: 1249
<epcis:EPCISDocument xmlns:cbvmda="urn:epcglobal:cbv:mda" …> 1250
... 1251
<ObjectEvent> 1252
... 1253
<QuantityElement> 1254
<epcClass>urn:epc:class:lgtin:0614141.012345.L123</epcClass> 1255
</QuantityElement> 1256
... 1257
<ilmd> 1258
<cbvmda:sellByDate>2016-03-15</cbvmda:sellByDate> 1259
</ilmd> 1260
... 1261
</ObjectEvent> 1262
... 1263
</epcis:EPCISDocument> 1264
9.2 Trade item master data attributes 1265
The tables below specify master data attributes that may be used to describe a trade item identifier. 1266
The meaning of the “Level” column is as follows: 1267
■ Trade Item: the master data attribute is a trade item-level attribute as specified in Section 9. 1268
■ Lot: the master data attribute is a lot-level attribute as specified in Section 9. 1269
■ Instance: the master data attribute is an instance-level attribute as specified in Section 9. 1270
■ Trade Item or Instance: the master data attribute is either a trade item-level attribute or an 1271
instance-level attribute as specified in Section 9, depending on the trade item. For example,
1272
netWeight is a trade item-level attribute for a fixed weight product but an instance-level 1273
attribute for a variable weight product. 1274
■ Trade Item or Lot or Instance: the master data attribute is either a trade item-level attribute 1275
or a lot-level attribute or an instance-level attribute as specified in Section 9, depending on the
1276
trade item. For example,
countryOfOrigin may be consistent across all instances of a trade 1277
item for a manufactured product, or consistent across all instances in a lot but varying across 1278
lots for fish species harvested in lots in varying territorial waters, or varying across all instances 1279
for fish species harvested individually in varying territorial waters. 1280
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 47 of 62
Master data attributes for each level are shown below in separate tables. Master data attributes that 1281
may be used at multiple levels are repeated in more than one table as appropriate. Within each 1282
table, attributes are listed alphabetically. 1283
9.2.1 Trade item master data attributes – trade item level 1284
The following attributes may be used to describe a trade item identifier at the trade item (GTIN) 1285
level. 1286
1287
Local Name Type Description Level
additionalTradeItem
Identification
String (1–80
characters)
A trade item identifier that is in addition to the GTIN.
Example:
12345111111
Trade
Item
additionalTradeItem
IdentificationTypeCode
Code A code that indicates what type of identifier is used
for
additionalTradeItemIdentification
The code list for this attribute is defined in GDSN; see
http://apps.gs1.org/GDD/Pages/clDetails.aspx?seman
ticURN=urn:gs1:gdd:cl:AdditionalTradeItemIdentifica
tionTypeCode&release=1
Example:
FDA_NDC_11
Trade
Item
countryOfOrigin
Code Country from which the goods are supplied.
The code list for this attribute is the ISO 3166-1
Alpha-2 list of 2-letter country codes; see
http://www.iso.org/iso/country_codes
Example:
UK
Trade
Item or
Lot or
Instance
descriptionShort
String (1–35
characters)
A free form short length description of the trade item
that can be used to identify the trade item at point of
sale.
Example:
Acme Red Widgets
Trade
Item
dosageFormType
String (1–35
characters)
A dosage form is the physical form of a medication
that identifies the form of the pharmaceutical item.
Example:
PILL
Trade
Item
drainedWeight
Measurement
(see
Section 9.2.4)
The weight of the trade item when drained of its
liquid. For example 225 "grm", Jar of pickles in
vinegar. Applies to defined bricks of GCI Global trade
item Classification - Mainly food trade item. Has to be
associated with a valid UoM.
Example: [see Section 9.2.4]
Trade
Item or
Instance
functionalName
String (1–35
characters)
Describes use of the product or service by the
consumer. Should help clarify the product
classification associated with the GTIN.
Example:
Widget
Trade
Item
grossWeight
Measurement
(see
Section 9.2.4)
Used to identify the gross weight of the trade item.
The gross weight includes all packaging materials of
the trade item. At pallet level the trade item-
GrossWeight includes the weight of the pallet itself.
For example, "200 grm", value - total pounds, total
grams, etc. Has to be associated with a valid UOM.
Example: [see Section 9.2.4]
Trade
Item or
Instance
manufacturerOfTradeItem
PartyName
String (1–200
characters)
Party name information for the manufacturer of the
trade item.
Example:
Acme Corporation
Trade
Item
netContentDescription
String (1–500
characters)
Free text describing the amount of the trade item
contained by a package, usually as claimed on the
label.
Example:
253 grams
Trade
Item
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 48 of 62
Local Name Type Description Level
netWeight
Measurement
(see
Section 9.2.4)
Used to identify the net weight of the trade item. Net
weight excludes any packaging materials and applies
to all levels but consumer unit level. For consumer
unit, Net Content replaces Net Weight (can then be
weight, size, volume). Has to be associated with a
valid UoM.
Example: [see Section 9.2.4]
Trade
Item or
Instance
labelDescription
String (1–500
characters)
A literal reproduction of the text featured on a
product's label in the same word-by-word order in
which it appears on the front of the product's
packaging. This may not necessarily match the GTIN
description as loaded by the supplier into the GTIN
description field in GDSN.
Example:
Acme Corporation Tiny Red Widgets
Trade
Item
regulatedProductName
String (1–500
characters)
The prescribed, regulated or generic product name or
denomination that describes the true nature of the
product and is sufficiently precise to distinguish it
from other products according to country specific
regulation.
Example:
Epcistra
Trade
Item
strengthDescription
String (1–500
characters)
Free text describing the strength of the active
ingredient(s) of the product
Example:
200mg/100mg
Trade
Item
tradeItemDescription
String (1–200
characters)
An understandable and useable description of a trade
item using brand and other descriptors. This attribute
is filled with as little abbreviation as possible while
keeping to a reasonable length. Free form text field,
this data element is repeatable for each language
used and must be associated with a valid ISO
language code. Field length is 178 characters. This
should be a meaningful description of the trade item
with full spelling to facilitate message processing.
Retailers can use this description as the base to fully
understand the brand, flavour, scent etc. of the
specific GTIN in order to accurately create a product
description as needed for their internal systems.
Example: GS1 Brand Base Invisible Solid
Deodorant AP Stick Spring Breeze
Trade
Item
9.2.2 Trade item master data attributes – lot level 1288
The following attributes may be used to describe a trade item identifier at the lot level. 1289
1290
Local Name Type Description Level
bestBeforeDate
Date The date before which the product is best used or
consumed. It is a statement about quality.
Example:
2017-03-15
Lot
countryOfOrigin
Code [see description in Section 9.2.1] Trade
Item or
Lot or
Instance
farmList
List of Farm List of structures describing farm information; see below Lot
firstFreezeDate
Date The date of initial freezing, if different from the date of
production.
Example:
2016-03-15
Lot
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 49 of 62
Local Name Type Description Level
growingMethodCode
Code The process through which fresh produce is grown and
cultivated.
The code list for this attribute is defined in GDSN; see
http://apps.gs1.org/GDD/Pages/clDetails.aspx?
semanticURN=urn:gs1:gdd:cl:GrowingMethod
Code&release=1
Example:
HYDROPONIC
Lot
harvestEndDate
Date The date when harvesting ended.
Example:
2016-03-15
Lot
harvestStartDate
Date The date when harvesting started.
Example:
2016-03-15
Lot
itemExpirationDate
Date The date after which the product should not be used or
consumed. Its meaning is determined based on the trade
item context (e.g., for food, the date will indicate the
possibility of a direct health risk resulting from use of the
product after the date, for pharmaceutical products, it will
indicate the possibility of an indirect health risk resulting
from the ineffectiveness of the product after the date). It is
often referred to as "use by date" or "maximum durability
date.”
Example:
2016-03-15
Lot
productionMethodFor
FishAndSeafoodCode
Code A code specifying how the fish had been grown / cultivated.
The code list for this attribute is defined in GS1 EDI; see
http://apps.gs1.org/GDD/Pages/clDetails.aspx?semanticUR
N=urn:gs1:gdd:cl:ProductionMethodForFishAndSeafood
Code&release=1
Example:
AQUACULTURE
Lot
sellByDate
Date The date before or on which, the product should be sold.
Example:
2017-03-15
Lot
storageStateCode
Code A code depicting that the referred product was previously
frozen or not.
The code list for this attribute is defined in GS1 EDI; see
http://apps.gs1.org/GDD/Pages/clDetails.aspx?semanticUR
N=urn:gs1:gdd:cl:StorageStateCode&release=1
Example:
Previously Frozen
Lot
unloadingPort
UN LOCODE Port where the goods were unloaded from a seagoing
vessel after having been transported by it.
The value of this attribute is a user vocabulary maintained
by UN/ECE; see
http://www.unece.org/cefact/locode/welcome.html
Example:
DE BRV
Lot
vesselCatch
InformationList
List of
VesselCatch
Information
List of structures describing vessel catch information; see
below
Lot
The value of vesselCatchInformationList consists of one or more elements named 1291
vesselCatchInformation, which contains the following subelements: 1292
Field Type Description
vesselID
String Identifier for the vessel
Example:
DE-X-1234
vesselName
String Name of the vessel
Example:
HMS Gena
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 50 of 62
Field Type Description
catchArea
Code A code specifying area where the product was caught.
The code list for this attribute is defined by the Food and
Agriculture Organization of the United Nations (FAO); see
http://www.fao.org/fishery/area/search/en
Example:
37.2
fishingGearTypeCode
Code A code specifying the type of gear used in capture of
fisheries.
The code list for this attribute is defined by the Food and
Agriculture Organization of the United Nations (FAO); see
ftp://ftp.fao.org/FI/DOCUMENT/cwp/handbook/
annex/AnnexM1fishinggear.pdf
Example:
TM
The value of farmList consists of one or elements named farm, which contains the following 1293
subelements: 1294
Field Type Description
farmIdentification
String Identifier for the farm
Example:
urn:epc:id:sgln:061414.00001.0
farmIdentificationTypeCode
Code Type of the farmIdentification
Example:
EPC-GLN
The code list for farmIdentificationTypeCode is as follows: 1295
Code Description
EPC-GLN
The identifier is a GS1 Global Location Number (GLN), expressed as a GLN EPC URI.
9.2.3 Trade item master data attributes – instance-level 1296
The following attributes may be used to describe a trade item identifier at the trade item (GTIN) 1297
level. 1298
Local Name Type Description Level
countryOfOrigin
Country Code [see description in Section 9.2.1] Trade
Item or
Lot or
Instance
drainedWeight
Measurement [see description in Section 9.2.1] Trade
Item or
Instance
grossWeight
Measurement [see description in Section 9.2.1] Trade
Item or
Instance
lotNumber
String (1–20
characters)
A distinctive combination of numbers and/or letters from which
the complete history of the manufacture, processing,
packaging, coding and distribution of a batch can be
determined.
Example:
ABC123
Instance
netWeight
Measurement [see description in Section 9.2.1] Trade
Item or
Instance
9.2.4 Values of type measurement 1299
Each value of type Measurement is a structure having the following subelements: 1300
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 51 of 62
Field Type Description
measurement
Decimal The numerical value of the measurement
measurementUnitCode
Code The unit of measure for the measurement.
The code list for this attribute is UN/ECE Recommendation 20; see
http://www.unece.org/cefact/recommendations/rec_index.html
When a value of type Measurement appears in ILMD, it takes the form illustrated below. In this 1301
example, the attribute is
netWeight with a value of 3.5 kilograms. 1302
<ilmd> 1303
<cbvmda:netWeight measurementUnitCode="KGM">3.5</cbvmda:netWeight> 1304
</ilmd> 1305
When a value of type Measurement appears in an EPCIS Master Data Document, the master data 1306
section of an EPCIS document header, or in a response to an EPCIS Simple Master Data Query, it 1307
takes the form illustrated below. 1308
<attribute id="urn:epc:cbv:mda:netWeight"><measurement 1309
measurementUnitCode="KGM">3.5</measurement></attribute> 1310
10 Location and party master data 1311
This section specifies master data attributes that may be used to describe a physical location 1312
identifier or party identifier. Physical location master data attributes may be used to describe a 1313
location identifier whether the location identifier is used as a EPCIS Read Point, Business Location, 1314
Source, or Destination. Party master data attributes may be used whether the party identifier is 1315
used as an EPCIS Source or Destination. 1316
Different physical location identifiers may denote locations at different levels of granularity. The 1317
master data attributes defined in the CBV for physical location identifiers are designed to be used for 1318
locations at two different levels of granularity: 1319
■ Site: A physical location where a structure or group of structures (and / or areas) is. Examples 1320
of a Site include a distribution centre, a retail store, a hospital, etc. 1321
■ Sub-site: A specific physical location contained within a site. Examples of a Sub-site include a 1322
back room within a retail store, the sales floor of a retail store, a storage area within a 1323
warehouse, and so on. 1324
A CBV-Compliant or CBV-Compatible document MAY include any of the master data attributes 1325
specified in this section within the master data section of the EPCIS Header, subject to the 1326
constraints specified elsewhere in this section. The master attributes specified in this section may 1327
also be used in an EPCIS Master Data Document or in the response to an EPCIS Master Data Query. 1328
A CBV-Compliant or CBV-Compatible document SHALL NOT include any of the master data 1329
attributes specified in this section in the ILMD section of an EPCIS event. 1330
10.1 Location and party master data attribute names 1331
In the master data section of an EPCIS header, in an EPCIS Master Data Document, and in the 1332
response to an EPCIS Master Data Query, a master data attribute is specified as a name/value pair. 1333
The name of every location/party master data attribute defined in this section consists of the 1334
following namespace identifier: 1335
urn:epcglobal:cbv:mda 1336
followed by a pound sign (
#) character, followed by a local name as specified in Section 10.2. As an 1337
exception, the master data attributes site, sst, ssa, and ssd use a colon (
:) character instead of 1338
a pound sign as the separator, for back-compatibility to CBV 1.1 and earlier. 1339
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 52 of 62
10.2 Location and party master data attributes 1340
The table below specifies master data attributes that may be used to describe a physical location or 1341
party identifier. 1342
If a master data attribute indicates “location” in the usage column of the table, then a CBV-1343
Compliant or CBV-Compatible document MAY use that attribute to describe an identifier that 1344
appears in any of the following fields in an EPCIS event: 1345
■ Read point 1346
■ Business location 1347
■ Source, if the source type is
location as specified in Section 7.4 1348
■ Destination, if the destination type is
location as specified in Section 7.4 1349
If a master data attribute indicates “party” in the usage column of the table, then a CBV-Compliant 1350
or CBV-Compatible document MAY use that attribute to describe an identifier that appears in any of 1351
the following fields in an EPCIS event: 1352
■ Source, if the source type is owning_party or possessing_party as specified in Section 7.4 1353
■ Destination, if the destination type is owning_party or possessing_party as specified in 1354
Section 7.4 1355
A CBV-Compliant or CBV-Compatible document SHALL NOT use master data attributes to describe 1356
an identifier except as permitted above. 1357
Local Name Type Description Usage
site (see note below)
String (1 –128
characters)
Identifies the site in which this location is contained.
For a Sub-site location, this is the identifier of the
parent location. For a Site location, this is the
identifier of the location itself.
When the identifier for the location to which this
master data attribute applies is an SGLN EPC, the
Site Location master data attribute is always the 13-
digit GLN implied by the company prefix and
location reference components of that SGLN
Location
sst (see note below)
Code List
(section 10.3.1)
Sub-Site Type: describes the primary business
function of the sub-site location. This master data
attribute is only applicable to a sub-site location.
This value is expressed as a single numerical code
(see code list below); for example, code 201
indicates that the sub-site type is a “back room” as
defined below
Location
ssa (see note below)
Code List
(section 10.3.2)
Sub-Site Attribute: further qualifies the business
function of the sub-site location. This master data
attribute is only applicable to a sub-site location.
Sub-site attributes are expressed as a comma-
separated list of zero or more numerical codes (see
code list below). For example, if the sub-site type is
203 (sales area), then sub-site attributes of
“404,412” further specifies that this location
identifier is a sales area for groceries (attribute 412)
that are frozen (attribute 404).
Location
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 53 of 62
Local Name Type Description Usage
ssd (see note below)
String (1 –128
characters)
Sub-Site Detail: provides additional proprietary
information. This master data attribute is only
applicable to a sub-site location.
For example, instead of sharing that a product is on
some shelf in the back room of store 123, a party
may wish to communicate the exact shelf in the
backroom of store 123, e.g. shelf #4567. The Sub-
Site Detail master data attribute provides the
identity of the specific shelf; e.g., 4567
Location
name
String The name of the location or party expressed in text. Location
or Party
streetAddressOne
String The first free form line of an address. This first part
is printed on paper as the first line below the name.
For example, the name of the street and the
number in the street or the name of a building.
Location
or Party
streetAddressTwo
String The second free form line of an address. This
second part is printed on paper as the second line
below the name. The second free form line
complements the first free form line to locate the
party or location.
Location
or Party
streetAddressThree
String The third free form line of an address. This third
part is printed on paper as the third line below the
name. The third free form line complements the
first and second free form lines where necessary.
Location
or Party
city
String Text specifying the name of the city. Location
or Party
state
String One of the constituent units of a nation having a
federal government.
Location
or Party
postalCode
String Text specifying the postal code for an address. Location
or Party
countryCode
String The ISO 3166-1 alpha-2 code specifying the country
for the address.
Location
or Party
latitude
Decimal Latitude of the location, in degrees. Positive
numbers are northern latitude; negative numbers
are southern latitude.
Location
longitude
Decimal Longitude of the location, in degrees. Positive
numbers are eastern longitude; negative numbers
are western longitude.
Location
Note: for back-compatibility with CBV 1.1 and earlier, the complete name of the attributes site, 1358
sst, ssa, and ssd are expressed differently; see Section 10.1. 1359
10.3 Location master data code list values 1360
The following section specifies code list values for sub-site type and sub-site attribute. 1361
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 54 of 62
10.3.1 Sub-Site Type 1362
The value of the Sub-Site Type master data attribute for a location identifier, if present, SHALL be 1363
one of the codes in the following table: 1364
Sub-Site Type Master Data Attribute Values
Code Short Description Definition
201
Backroom An area within a store (all formats - club, etc.) used to hold product until it is purchased or
can be moved to the sales floor
202
Storage Area An area where product is kept within a facility to fulfil future need.
Reserve rack or bulk stacking. A location where the product is stored until it is needed in
selection aisles making it accessible to the consumer. Reserve slots may contain one or
multiple pallet loads, as well as multiple items within them
For a retail store Secondary storage area associated with a store (may not be in the
physical location)
Potential to use this more broadly and add attributes to make distinction where necessary
(recalled area, quarantined area, controlled substance, lay-away)
203
Sales Floor An area within a store (all formats - club, etc.) where product is displayed for customer
purchase
207
Returns Area An area within a facility for holding or consolidating product to be sent back to the supplier,
shipper or designated location
208
Production Area An area within a facility where the conversion of materials and or assembly of components
to manufacture goods, products or services takes place.
209
Receiving Area An area within a facility where incoming merchandise is unloaded and checked for condition
and completeness
210
Shipping Area
An area within a facility where outgoing merchandise is checked for condition and
completeness and loaded onto a conveyance for transport
211
Sales Floor
Transition Area
An area within a store between two physical locations (e.g. Backroom and Sales Floor) -
used for a read point only
212
Customer Pick-Up
Area
An area designated at a store for customer to take possession of purchased product.
213
Yard An area outside of the main building used for holding product (e.g. Trailer or container)
214
Container Deck An area on board a shipping vessel where containers are loaded.
215
Cargo Terminal An area where cargo may get transferred between carriers.
Cargo terminals provide the interface between modes of transportation.
251
Packaging Area An area within a facility where product is packaged.
252
Picking Area An area within a facility in which product is picked to fulfil an order.
253
Pharmacy Area An area within a facility where prescription products are stored, dispensed and/or sold.
299
Undefined Any sub-site type not identified by any of the listed values
10.3.2 Sub-Site Attributes 1365
The value of the Sub-Site Attributes master data attribute for a location identifier SHALL be zero or 1366
more of the codes in the following table. 1367
When the value of the Sub-Site Attributes master data attribute is transmitted as a single string 1368
(including when the Sub-Site Attributes master data attribute is transmitted using the 1369
EPCISMasterDataDocument form specified in [EPCIS1.2]), the string SHALL consist of the codes 1370
separated by commas with no leading, trailing, or internal whitespace characters, and furthermore 1371
the codes SHALL appear in ascending numerical sequence reading from left-to-right. 1372
Non-Normative: Explanation (non-normative): The restriction on ascending numerical 1373
sequence guarantees that there is only one way to compose the string for a given set of 1374
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 55 of 62
attributes. This simplifies application processing of this data; e.g., when comparing whether 1375
two location identifiers have an identical set of Sub-Site Attributes. 1376
Sub-Site Attribute Master Data Attribute Values
Code Short Description Definition
401
Electronics A specific area within the store for holding electronic products such as
TV's, DVD players, etc.
402
Cold storage A specific area or room that maintains a temperature above freezing but
below ambient room temperature.
403
Shelf A specified internal location for holding product.
404
Frozen A specific area or room that maintains a temperature at or below freezing
405
Fresh A specific area or room that maintains a specified temperature and/or
humidity to preserve stored product
406
Promotion A specific area or room that is used to hold special purchased product.
407
End Cap A specific internal location on the sales floor, typically at the end of an
aisle, for displaying product.
408
Point of Sale An area in a retail location where sales transactions occur
409
Security A designated internal location for the purpose of minimising direct access
to the product
411
General Mdse An area where typically - non-food products other than perishable, dry
groceries and health and beauty care products that are displayed in stores
on standard shelving. Examples include household cleaning products,
paper napkins, laundry detergents, and insect repellents
412
Grocery An area where typically - food products that are displayed in stores on
standard shelving. Examples include canned goods, produce, meats.
413
Box Crusher A Baler used to compact recycled materials (e.g. corrugated boxes, slip
sheets and packaging material)
414
Dock / Door One or more doors where trucks or rail cars are loaded (shipping) or
unloaded (receiving). Used to load or unload trailers or vans.
415
Conveyor Belt A continuous moving strip or surface that is used for transporting single
cartons or a load of objects from one place to another
416
Pallet Wrapper An area where any automatic or manual method using bands of plastic film
applied to product used to encase palletised loads prior to shipment to
protect against product damage
417
Fixed Reader Any fixed read point configuration (reader and antennas) for the purpose
of capturing EPC data (e.g. Door way or conveyor read point)
418
Mobile Reader Any non-fixed (portable) reader configuration (reader and antennas) for
the purpose of capturing EPC data (e.g. Hand held or forklift reader)
419
Shelf/Storage Where the product is stored on the sales floor, not accessible to the
customer, until it can be moved, making it accessible to the consumer.
420
Returns An area within a store or retailer DC for holding or consolidating product to
be sent back to the supplier, shipper or designated location.
421
Staging An area within a DC or Manufacturing Facility which the receiving and
shipping docks use to gather and check inbound and outbound loads.
422
Assembly An area where components are put together into an end product,
appropriate to the process concerned.
423
Lay-Away An area within a store for holding or consolidating customer purchases for
final payment and pickup
424
Dispenser Tablet, caplet or capsule dispensing machine in which bulk product has
been placed to be dispensed on a prescription basis.
425
Quarantine An area at a Manufacturing, Distribution or Retail facility to hold product
that may not be suitable for consumption until further inspection
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 56 of 62
Sub-Site Attribute Master Data Attribute Values
426
Controlled Substance A caged and locked area in which regulated, controlled substance
pharmaceuticals are held while awaiting shipment.
427
Recalled Product An area in which recalled product is stored pending shipment back to the
manufacturer or the manufacturer’s designated returns centre for final
disposition
428
Quality Control An area in which any product not meeting quality standards is held
pending further evaluation.
429
Printing Room An area which provides printed labels/tags for the goods/cartons/pallets
within a DC or Manf Facility
Please note – this supports the process where an EPC tag is encoded off
the line and is later commissioned and associated with a particular
product.
430
Loading Dock A parking bay, partly enclosed by a raised platform, at which trucks are
loaded and unloaded, e.g. in a warehouse site.
431
Entrance Gate A point of transport access into a yard or other arriving area.
432
Exit Gate A point of transport exit from a yard or other departing area.
433
Gate A point of transport within a facility – not indicated specifically as an
entrance or an exit point.
434
Read Point Verification
Spot
A point at which a tagged object's location has been verified by an
associated read of a separate fixed location tag. Read Point Verification
Spot would be used when there is a business process to capture the
current location of an object at rest (typically with a mobile reader).
11 Example EPCIS Documents (non-normative) 1377
The following sections provide examples of usage of the Core Business Vocabulary. 1378
11.1 CBV-Compliant object event using standard vocabulary 1379
The following shows a CBV-Compliant EPCIS document in XML format containing a single object 1380
event, where CBV-Compliant identifiers are used for business step and disposition, and EPCs are 1381
used for all user vocabulary values. 1382
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> 1383
<epcis:EPCISDocument 1384
xmlns:epcis="urn:epcglobal:epcis:xsd:1" 1385
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 1386
creationDate="2005-07-11T11:30:47.0Z" 1387
schemaVersion="1"> 1388
<EPCISBody> 1389
<EventList> 1390
<ObjectEvent> 1391
<eventTime>2007-07-26T21:41:19Z</eventTime> 1392
<recordTime>2007-07-26T21:41:19Z</recordTime> 1393
<eventTimeZoneOffset>-05:00</eventTimeZoneOffset> 1394
<epcList> 1395
<!-- Section 8.2.1
– EPC Identifier --> 1396
<epc>urn:epc:id:sgtin:0614141.181335.234</epc> 1397
</epcList> 1398
<action>ADD</action> 1399
<!-- Section 7.2.1 – BizStep --> 1400
<bizStep>urn:epcglobal:cbv:bizstep:commissioning</bizStep> 1401
<!-- Section 7.2 – Disposition -->1402
<disposition>urn:epcglobal:cbv:disp:active</disposition> 1403
<!-- Section 8.4.1 – EPC URI for Locations --> 1404
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 57 of 62
<readPoint> 1405
<id>urn:epc:id:sgln:0614141.00300.1</id> 1406
</readPoint> 1407
<!-- Section 8.4.1 – EPC URI for Locations --> 1408
<bizLocation> 1409
<id>urn:epc:id:sgln:0614141.00300.0</id> 1410
</bizLocation> 1411
<bizTransactionList> 1412
<!-- Section 8.5.1
– EPC URI --> 1413
<!-- Section 8.5 – BTT --> 1414
<bizTransaction 1415
type="urn:epcglobal:cbv:btt:po">urn:epc:id:gdti:0614141.06012.1234</bizTrans1416
action> 1417
</bizTransactionList> 1418
</ObjectEvent> 1419
</EventList> 1420
</EPCISBody> 1421
</epcis:EPCISDocument> 1422
11.2 CBV-Compliant object event using HTTP URLs and Private or Industry-1423
wide URNs 1424
The following shows a CBV-Compliant EPCIS document in XML format containing a single object 1425
event, illustrating the use of HTTP URLs and Private or Industry-wide URNs for user vocabulary 1426
values. 1427
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> 1428
<epcis:EPCISDocument 1429
xmlns:epcis="urn:epcglobal:epcis:xsd:1" 1430
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 1431
creationDate="2005-07-11T11:30:47.0Z" 1432
schemaVersion="1"> 1433
<EPCISBody> 1434
<EventList> 1435
<ObjectEvent> 1436
<eventTime>2007-07-26T21:41:19Z</eventTime> 1437
<recordTime>2007-07-26T21:41:19Z</recordTime> 1438
<eventTimeZoneOffset>-05:00</eventTimeZoneOffset> 1439
<epcList> 1440
<!-- Section 8.2.2
--> 1441
<epc>urn:example:epcis:id:obj:Q12345.67890.001</epc> 1442
<!-- Section 8.2.3 --> 1443
<epc>http://epcis.example.com/user/vocab/obj/12345.67890</epc> 1444
</epcList> 1445
<action>ADD</action> 1446
<!-- Section 7.2.1 – BizStep --> 1447
<bizStep>urn:epcglobal:cbv:bizstep:commissioning</bizStep> 1448
<!—Section 7.2 – Disposition -->1449
<disposition>urn:epcglobal:cbv:disp:active</disposition> 1450
1451
<!-- Section 8.3.2 Location identifier --> 1452
<readPoint> 1453
<id>urn:example:epcis:id:loc:warehouse23</id> 1454
</readPoint> 1455
<!-- Section 8.3.3 Location identifier --> 1456
<bizLocation> 1457
<id>http://epcis.example.com/user/vocabularies/loc/abc.12345</id> 1458
</bizLocation> 1459
<bizTransactionList> 1460
<!-- Section 8.4.4 --> 1461
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 58 of 62
<bizTransaction 1462
type="urn:epcglobal:cbv:btt:po">http://transaction.example.com/prodution/ord1463
ers/bt/po12345</bizTransaction> 1464
<!-- Section 8.4.3 --> 1465
<bizTransaction 1466
type="urn:epcglobal:cbv:btt:inv">urn:example:epcis:bt:inv:12345</bizTransact1467
ion> 1468
<!-- Section 8.4.2 – Legacy System BT Identifier --> 1469
<bizTransaction 1470
type="urn:epcglobal:cbv:btt:desadv">urn:epcglobal:cbv:bt:0614141000029:asn121471
345</bizTransaction> 1472
</bizTransactionList> 1473
</ObjectEvent> 1474
</EventList> 1475
</EPCISBody> 1476
</epcis:EPCISDocument> 1477
11.3 CBV-Compatible event 1478
The following shows a CBV-Compatible EPCIS document in XML format containing a single object 1479
event. CBV-Compliant EPC identifiers are used for physical objects and locations, but because non-1480
standard identifiers are used for business step and disposition the document is CBV-Compatible and 1481
not CBV-Compliant. 1482
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> 1483
<epcis:EPCISDocument 1484
xmlns:epcis="urn:epcglobal:epcis:xsd:1" 1485
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 1486
creationDate="2005-07-11T11:30:47.0Z" 1487
schemaVersion="1"> 1488
<EPCISBody> 1489
<EventList> 1490
<ObjectEvent> 1491
<eventTime>2007-07-26T21:41:19Z</eventTime> 1492
<recordTime>2007-07-26T21:41:19Z</recordTime> 1493
<eventTimeZoneOffset>-05:00</eventTimeZoneOffset> 1494
<epcList> 1495
<!-- Section 8.2.1 – EPC Identifier --> 1496
<epc>urn:epc:id:sgtin:0614141.181335.234</epc> 1497
</epcList> 1498
<action>ADD</action> 1499
<bizStep>urn:example:uservocab:bizstep:quarantined</bizStep> 1500
<disposition>http://epcis.example.com/user/vocab/disp/contaminated</disposit1501
ion> 1502
<!-- Section 8.3.1 – Locations --> 1503
<readPoint> 1504
<id>urn:epc:id:sgln:0614141.00300.1</id> 1505
</readPoint> 1506
<!-- Section 8.3.1 – Locations --> 1507
<bizLocation> 1508
<id>urn:epc:id:sgln:0614141.00300.0</id> 1509
</bizLocation> 1510
</ObjectEvent> 1511
</EventList> 1512
</EPCISBody> 1513
</epcis:EPCISDocument> 1514
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 59 of 62
11.4 Location master data 1515
The following shows an EPCIS Master Data document illustrating the use of location master data 1516
attributes defined in Section 8.6. 1517
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> 1518
<epcismd:EPCISMasterDataDocument 1519
xmlns:epcismd="urn:epcglobal:epcis-masterdata:xsd:1" 1520
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 1521
schemaVersion="1" 1522
creationDate="2005-07-11T11:30:47.0Z"> 1523
<EPCISBody> 1524
<VocabularyList> 1525
<Vocabulary type="urn:epcglobal:epcis:vtype:ReadPoint"> 1526
<VocabularyElementList> 1527
<!-- Section 10.3 - Location Master Data Names --> 1528
<VocabularyElement id="urn:epc:id:sgln:0614141.00300.0"> 1529
<attribute 1530
id="urn:epcglobal:cbv:mda:site">0614141003006</attribute> 1531
</VocabularyElement> 1532
1533
<!-- Section 10.3 - Location Master Data Names --> 1534
<VocabularyElement id="urn:epc:id:sgln:0614141.00300.1"> 1535
<attribute 1536
id="urn:epcglobal:cbv:mda:site">0614141003006</attribute> 1537
<!-- Section 10.3.1 SST --> 1538
<attribute id="urn:epcglobal:cbv:mda:sst">208</attribute> 1539
<!-- Section 10.3.2 SSA --> 1540
<attribute id="urn:epcglobal:cbv:mda:ssa">422</attribute> 1541
<attribute id="urn:epcglobal:cbv:mda:ssd">Line #1 at Manufacturing 1542
Plant 1</attribute> 1543
</VocabularyElement> 1544
1545
<!-- Section 10.3 - Location Master Data Names --> 1546
<VocabularyElement id="urn:epc:id:sgln:0614141.00300.2"> 1547
<attribute 1548
id="urn:epcglobal:cbv:mda:site">0614141003006</attribute> 1549
<!-- Section 10.3.1 SST --> 1550
<attribute id="urn:epcglobal:cbv:mda:sst">251</attribute> 1551
<!-- Section 10.3.2 SSA --> 1552
<attribute id="urn:epcglobal:cbv:mda:ssa">416,417</attribute> 1553
</VocabularyElement> 1554
</VocabularyElementList> 1555
</Vocabulary> 1556
</VocabularyList> 1557
</EPCISBody> 1558
</epcismd:EPCISMasterDataDocument> 1559
12 References 1560
[EPCIS1.2] GS1, “EPC Information Services (EPCIS) Version 1.2 standard,” GS1 Working Draft, 1561
December 2015. 1562
[ISODir2] ISO, “Rules for the structure and drafting of International Standards (ISO/IEC 1563
Directives, Part 2, 2001, 4th edition),” July 2002. 1564
[RFC2141] R. Moats, “URN Syntax,” RFC 2141, May 1997, http://www.ietf.org/rfc/rfc2141
. 1565
[RFC3986] T. Berners-Lee, R. Fielding, L. Masinter, “Uniform Resource Identifier (URI): Generic 1566
Syntax,” RFC3986, January 2005, http://www.ietf.org/rfc/rfc3986
. 1567
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 60 of 62
[RFC4122] P. Leach, M. Mealling, R. Salz, “A Universally Unique IDentifier (UUID) URN 1568
Namespace,” RFC4122, http://www.ietf.org/rfc/rfc4122
. 1569
[RFC5870] A. Mayrhofer, C. Spanring, “A Uniform Resource Identifier for Geographic Locations 1570
('geo' URI),” RFC 5870, June 2010, http://www.ietf.org/rfc/rfc5870
. 1571
[TDS1.9] GS1, “GS1 EPCglobal Tag Data Standards Version 1.9,” GS1 standard, June 2014, 1572
http://www.gs1.org/epc/tag-data-standard
1573
13 Contributors to earlier versions 1574
Below is a list of active participants and contributors in the development of CBV 1.1. This list does 1575
not acknowledge those who only monitored the process or those who chose not to have their name 1576
listed here. The participants listed below generated emails, attended face-to-face meetings and 1577
conference calls that were associated with the development of this standard. 1578
Name Company
Andrew Kennedy FoodLogiQ (Working group co-chair)
Michele Southall GS1 US (Working group co-chair)
Gena Morgan GS1 (Working group facilitator)
Ken Traub Ken Traub Consulting LLC (Editor)
Craig Alan Repec GS1 Global Office
Jean-Pierre Allard Optel Vision
Romain Arnaud Courbon
Shirley Arsenault GS1 Global Office
Koji Asano GS1 Japan
Karla Biggs-Gregory Oracle
Havard Bjastad TraceTracker AS
Stephan Bourguignon Daimler AG
Bob Bunsey SPEDE Technologies
Birgit Burmeister Daimler AG
Jonas Buskenfried GS1 Sweden
Robert Celeste GS1 US
Chris Chandler GS1 US
Lucy Deus Tracetracker
Hussam El-Leithy GS1 US
Heinz Graf GS1 Switzerland
Anders Grangard GS1 Global
Emmanuel Hadzipetros TraceLink
Mark Harrison Auto-ID Labs
Dave Harty Systech International
Douglas Hill GS1 Denmark
Robert Hotaling Supply Insight
John Howells HDMA
Tany Hui GS1 Hong Kong
Yoshihiko Iwasaki GS1 Japan
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 61 of 62
Name Company
Art Kaufmann Frequentz LLC, IBM
John Keogh GS1 Global Office
Janice Kite GS1 Global Office
Steinar Kjærnsrød TraceTracker AS
Jay Kolli Abbott
Jens Kungl METRO Group
Sean Lockhead GS1 Global Office
Paul Lothian Tyson
Dale Moberg Axway
Reiko Moritani GS1 Japan
Mark Morris Abbott Laboratories Inc.
Marc-Antoine Mouilleron France Telecom Orange
Alice Mukaru GS1 Sweden
Falk Neider IBM Germany
Andrew Osbourne GS1 UK
Ted Osinski MET Laboratories
Nicolas Pauvre GS1 France
Cynthia Poetker Abbott Laboratories
Venkataramanan Rajaraman Abbott Laboratories
Craig Alan Repec GS1 Global Office
Chris Roberts GlaxoSmithKline
Ian Robertson Supply Chain RFID Consulting LLC
Dirk Rodgers Dirk Rodgers Consulting, LLC
Thomas Rumbach SAP AG
John Ryu GS1 Global Office
Aravindan Sankaramurthy Oracle
Michael Sarachman GS1 Global Office
Udo Scheffer METRO Group
Frank Schmid IBM (US)
Michael Smith Merck & Co., Inc.
Monika Solanki Aston University
Peter Spellman TraceLink
Steve Tadevich McKesson
Petter Thune-Larsen GS1 Norway
Peter Tomicki Zimmer, Inc.
Ralph Troeger GS1 Germany
Jens Vialkowitsch Robert Bosch GmbH
Geir Vevle HRAFN
Matthew Warren Zimmer, Inc.
David Weatherby GS1 UK
Joachim Wilkens C & A SCS
Core Business Vocabulary Standard
Release 1.2.1, Ratified, May 2017 © 2017 GS1 AISBL Page 62 of 62
1579
