ISO/IEC 19988:2015

INTERNATIONAL ISO/IEC
STANDARD 19988
First edition
2015-09-15
Information technology — GS1 Core
business vocabulary (CBV)
Technologies de l’information — Vocabulaire relatif aux activités de
base GS1
Reference number
©
ISO/IEC 2015
© ISO/IEC 2015, Published in Switzerland
All rights reserved. Unless otherwise speci�ied, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be re�uested from either ISO at the address below or ISO�s member body in the country of
the requester.
ISO copyright of�ice
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright�iso.org
www.iso.org
ii © ISO/IEC 2015 – All rights reserved

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non‐governmental, in liaison with ISO and IEC, also
take part in the work. In the field of information technology, ISO and IEC have established a joint
technical committee, ISO/IEC JTC 1.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for
the different types of document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does
not constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO's adherence to the WTO principles in the Technical
Barriers to Trade (TBT), see the following URL: Foreword — Supplementary information.

The committee responsible for this document is ISO/IEC JTC 1, Information technology.
© ISO/IEC 2015 – All rights reserved iii

Core Business Vocabulary
GDSN Package Measurement Rules
Core Business Vocabulary (CBV)

GS1 Standards Document
GS1 Standard
Version 1.1, May 2014
Version 1 13 2 Dec 2013
Version 1.1, May-2014 All contents © 2010–2014 GS1         Page 1 of 62

Core Business Vocabulary
© 2010–2014 GS1 AISBL
All rights reserved.
GS1 Global Office
Avenue Louise 326, bte 10
B-1050 Brussels, Belgium
Disclaimer
GS1 AISBL (GS1) is providing this document as a free service to interested industries.
This document was developed through a consensus process of interested parties in developing
the Standard. Although efforts have been made to assure that the document is correct, reliable, and technically
accurate, GS1 makes NO WARRANTY, EXPRESS OR IMPLIED, THAT THIS DOCUMENT IS CORRECT,
WILL NOT REQUIRE MODIFICATION AS EXPERIENCE AND TECHNOLOGY DICTATE,
OR WILL BE SUITABLE FOR ANY PURPOSE OR WORKABLE IN ANY APPLICATION,
OR OTHERWISE. Use of this document is with the understanding that GS1 DISCLAIMS ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
IMPLIED WARRANTY OF NON-INFRINGEMENT OF PATENTS OR COPYRIGHTS,
MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE,
THAT THE INFORMATION IS ERROR FREE, NOR SHALL GS1 BE LIABLE
FOR DAMAGES OF ANY KIND, INCLUDING DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
CONSEQUENTIAL OR EXEMPLARY DAMAGES, ARISING OUT OF USE OR THE INABILITY
TO USE INFORMATION CONTAINED HEREIN OR FROM ERRORS CONTAINED HEREIN.
Version 1.1, May-2014 All contents © 2010–2014 GS1        Page 2 of 62
© ISO/IEC 2015 – All rights reserved

Core Business Vocabulary
2 Abstract
3 This GS1 Standard defines Version 1.1 of the Core Business Vocabulary (CBV). The goal of
4 this standard is to specify the structure of vocabularies and specific values for the vocabulary
5 elements to be utilized in conjunction with the GS1 Electronic Product Code Information
6 Services (EPCIS) standard for data sharing both within and across enterprises. The aim is to
7 standardize these elements across users of EPCIS to improve the understanding of data contained
8 in EPCIS events.
9 Audience for this document
10 The target audience for this standard includes:
11 • Users implementing the EPCIS standard for the purposes of capturing and sharing event data
12 in the supply chain.
13 • Parties interested in implementing EPCIS Accessing applications.
14 • Parties interested in implementing EPCIS Capture applications.
15 Status of this document
16 This section describes the status of this document at the time of its publication. Other
17 documents may supersede this document. The latest status of this document series is
18 maintained at GS1. See www.gs1.org/gsmp for more information.
19 This version of the GS1 CBV 1.1 Standard is the ratified version and has completed all GSMP
20 steps.
21 Comments on this document should be sent to gsmp@gs1.org.
22 Differences from CBV 1.0
23 CBV 1.1 is fully backward compatible with CBV 1.0 except as noted below.
24 CBV 1.1 includes these new or enhanced features:
25 • A new standard vocabulary for EPCIS source/destination type is added.
26 • Templates for new user vocabularies for EPCIS source/destination identifier, EPCIS
27 transformation identifier, and object classes are added.
28 • New business step, disposition, and business transaction type values are added. The
29 definitions of existing values are also clarified.
30 • Disposition values non_sellable_expired, non_sellable_damaged,
31 non_sellable_disposed, non_sellable_no_pedigree_match, and
32 non_sellable_recalled defined in CBV 1.0 are deprecated in favor of new

Version 1.1, May-2014 All contents © 2010–2014 GS1         Page 3 of 62
© ISO/IEC 2015 – All rights reserved

Core Business Vocabulary
33 disposition values expired, damaged, disposed, no_pedigree_match, and
34 recalled introduced in CBV 1.1.
35 • RFC5870-compliant geocoordinate URIs are now permitted as location identifiers.
36 • The introductory material is revised to align with the GS1 System Architecture.
Version 1.1, May-2014 All contents © 2010–2014 GS1         Page 4 of 62
© ISO/IEC 2015 – All rights reserved

Core Business Vocabulary
65 Table of Contents
66 1 Introduction – Core Business Vocabulary . 7
67 2 Relationship to the GS1 System Architecture . 8
68 3 Relationship to EPCIS . 8
69 3.1 EPCIS Event Structure . 8
70 3.2 Vocabulary Kinds . 9
71 3.2.1 Standard Vocabulary. 10
72 3.2.2 User Vocabulary . 11
73 4 Terminology and Typographical Conventions . 11
74 5 Compliance and Compatibility . 12
75 5.1 CBV Compliant . 12
76 5.2 CBV Compatible . 14
77 6 Use of Uniform Resource Identifiers (URIs) . 16
78 6.1 URI Prefix for Standard Vocabularies in the CBV . 16
79 6.2 Limitation on Use of the URI Prefix . 16
80 7 Standard Vocabularies . 17
81 7.1 Business Steps . 17
82 7.1.1 URI Structure . 17
83 7.1.2 Element Values and Definitions – Business Step . 17
84 7.2 Dispositions . 24
85 7.2.1 URI Structure . 24
86 7.2.2 Element Values and Definitions – Dispositions . 25
87 7.3 Business Transaction Types . 29
88 7.3.1 URI Structure . 29
89 7.3.2 Element Values and Definitions – Business Transaction Types . 29
90 7.4 Source/Destination Types . 30
91 7.4.1 URI Structure . 30
92 7.4.2 Element Values and Definitions – Source/Destination Types . 30
93 8 User Vocabularies . 31
94 8.1 General Considerations . 31
95 8.1.1 General Considerations for EPC URIs as User Vocabulary Elements . 33
96 8.1.2 General Considerations for Private or Industry-wide URN as User Vocabulary Elements33
97 8.1.3 General Considerations for HTTP URLs as User Vocabulary Elements . 34
98 8.2 Physical or Digital Objects (Instance-Level Identification) . 35
99 8.2.1 EPC URI for Instance-level Identification of Objects . 35
100 8.2.2 Private or Industry-wide URN for Instance-level Identification of Objects . 35
101 8.2.3 HTTP URLs for Instance-level Identification of Objects . 36
102 8.3 Physical or Digital Objects (Class-Level Identification) . 37
103 8.3.1 EPC URI for Class-level Identification of Objects . 37
104 8.3.2 Private or Industry-wide URN for Class-level Identification of Objects . 39
105 8.3.3 HTTP URLs for Class-level Identification of Objects . 39
106 8.4 Locations . 40
107 8.4.1 EPC URI for Location Identifiers . 40

Version 1.1, May-2014 All contents © 2010–2014 GS1         Page 5 of 62
© ISO/IEC 2015 – All rights reserved

Core Business Vocabulary
108 8.4.2 Private or Industry-wide URN for Location Identifiers . 40
109 8.4.3 HTTP URLs for Location Identifiers . 41
110 8.4.4 Geographic Location URIs for Location Identifiers . 42
111 8.5 Business Transactions . 42
112 8.5.1 EPC URI for Business Transaction Identifiers . 43
113 8.5.2 GLN-based Identifier for Legacy System Business Transaction Identifiers. 43
114 8.5.3 Private or Industry-wide URN for Business Transaction Identifiers . 44
115 8.5.4 HTTP URLs for Business Transaction Identifiers . 44
116 8.6 Source/Destination Identifiers . 45
117 8.6.1 EPC URI for Source/Destination Identifiers . 45
118 8.6.2 Private or Industry-wide URN for Source/Destination Identifiers . 46
119 8.6.3 HTTP URLs for Source/Destination Identifiers . 46
120 8.7 Transformation Identifiers . 47
121 8.7.1 EPC URI for Transformation Identifiers . 47
122 8.7.2 GLN-based Identifier for Legacy System Transformation Identifiers . 48
123 8.7.3 Private or Industry-wide URN for Transformation Identifiers . 48
124 8.7.4 HTTP URLs for Transformation Identifiers . 49
125 9 Location Master Data . 49
126 9.1 Location Master Data Constraints . 50
127 9.2 Location Master Data Names . 51
128 9.3 Location Master Data Values . 51
129 9.3.1 Site Location . 51
130 9.3.2 Sub-Site Type . 51
131 9.3.3 Sub-Site Attributes . 52
132 9.3.4 Sub-Site Detail . 55
133 10 Example EPCIS Documents (non-normative) . 55
134 10.1 CBV-Compliant Object Event using standard vocabulary . 55
135 10.2 CBV-Compliant Object Event using HTTP URLs and Private or Industry-wide URNs . 56
136 10.3 CBV-Compatible Event . 57
137 10.4 Location Master Data . 57
138 11 References . 58
139 12 Acknowledgement of Contributors and Companies Opt’d-in during the Creation of
140 this Standard (non-normative) . 59
Version 1.1, May-2014 All contents © 2010–2014 GS1         Page 6 of 62
© ISO/IEC 2015 – All rights reserved

Core Business Vocabulary
147 1 Introduction – Core Business Vocabulary
148 This GS1 Standard defines the Core Business Vocabulary (CBV). The goal of this standard is to
149 specify various vocabulary elements and their values for use in conjunction with the EPCIS
150 standard [EPCIS1.1], which defines mechanisms to exchange information both within and across
151 organization boundaries. The vocabulary identifiers and definitions in this standard will ensure
152 that all parties who exchange EPCIS data using the Core Business Vocabulary will have a
153 common understanding of the semantic meaning of that data.
154 This standard is intended to provide a basic capability that meets the above goal. In particular,
155 this standard is designed to define vocabularies that are core to the EPCIS abstract data model
156 and are applicable to a broad set of business scenarios common to many industries that have a
157 desire or requirement to share data. This standard intends to provide a useful set of values and
158 definitions that can be consistently understood by each party in the supply chain.
159 Additional end user requirements may be addressed by augmenting the vocabulary elements
160 herein with additional vocabulary elements defined for a particular industry or a set of users or a
161 single user. Additional values for the standard vocabulary types defined in this standard may be
162 included in follow-on versions of this standard.
163 This standard includes identifier syntax and specific vocabulary element values with their
164 definitions for these Standard Vocabularies:
165 • Business step identifiers
166 • Disposition identifiers
167 • Business transaction types
168 • Source/Destination types
169 This standard provides identifier syntax options for these User Vocabularies:
170 • Objects
171 • Locations
172 • Business transactions
173 • Source/Destination identifiers
174 • Transformation identifiers
175 This standard provides Master Data Attributes and Values for describing Physical Locations
176 including:
177 • Site Location
178 • Sub-Site Type
179 • Sub-Site Attributes
180 • Sub-Site Detail
181 Additional detailed master data regarding locations (addresses, etc) are not defined in this
182 standard.
Version 1.1, May-2014 All contents © 2010–2014 GS1         Page 7 of 62
© ISO/IEC 2015 – All rights reserved

Core Business Vocabulary
183 2 Relationship to the GS1 System Architecture
184 The Core Business Vocabulary is a companion standard to the EPCIS standard. EPCIS is the
185 standard that defines the technical interfaces for capturing and sharing event data. EPCIS defines
186 a framework data model for event data. The Core Business Vocabulary is a GS1 data standard
187 that supplements that framework by defining specific data values that may populate the EPCIS
188 data model. As such, the CBV exists in the “Share” group of GS1 standards.
189 3 Relationship to EPCIS
190 This section specifies how the Core Business Vocabulary standard relates to the EPC
191 Information Services (EPCIS) standard.
192 3.1 EPCIS Event Structure
193 The EPCIS 1.1 standard [EPCIS1.1] specifies the data elements in an EPCIS event. The
194 following lists these data elements, and indicates where the Core Business Vocabulary provides
195 identifiers that may be used as values for those data elements.
196 • The “what” dimension  The what dimension for most event types contains one or more
197 unique identifiers for physical or digital objects or classes of physical or digital objects.
198 Identifiers for physical or digital objects in the Core Business Vocabulary are specified in
199 Section 8.2 (instance-level) and Section 8.3 (class-level). In the case of an EPCIS
200 TransformationEvent, an optional TransformationID may be used to link together multiple
201 events that describe the same transformation. The Core Business Vocabulary includes
202 TransformationIDs in Section 8.7.
203 • The “when” dimension  The moment in time at which an EPCIS event occurred. Event
204 time is fully specified in the EPCIS standard.
205 • The “where” dimension  The “where” dimension consists of two identifiers that describe
206 different aspects of where an event occurred:
207 • Read Point  The location where the EPCIS event took place. In the case of an EPCIS
208 event arising from reading a bar code or RFID tag, the Read Point is often the location
209 where the bar code or RFID tag was read.  Identifiers for read points in the Core
210 Business Vocabulary are specified in Section 8.3.
211 Example: A reader is placed at dock door #3 at the London Distribution Center (DC).
212 Product passed through the dock door. Read point = 213 London DC Dock Door #3>
214 • Business Location  The location where the subject of the event is assumed to be
215 following an EPCIS event, until a new event takes place that indicates otherwise.
216 Identifiers for business locations in the Core Business Vocabulary are specified in
217 Section 8.3.
218 Example: A product is read through the sales floor transition door at store #123. The
219 product is now sitting on the sales floor. Business location = 220 for store #123 Sales Floor>

Version 1.1, May-2014 All contents © 2010–2014 GS1         Page 8 of 62
© ISO/IEC 2015 – All rights reserved

Core Business Vocabulary
221 • The “why” dimension  The “why” dimension consists of two identifiers and a list of
222 business transaction identifiers, which collectively provide the business context or “why” the
223 event occurred:
224 • Business Step   Denotes a specific activity within a business process. The business step
225 field of an event specifies what business process step was taking place that caused the
226 event to be captured. Identifiers for business steps in the Core Business Vocabulary are
227 specified in Section 7.1.
228 Example: an EPCIS event is generated as a product departs the location identified by
229 the Read Point. Business Step =
230 • Disposition   Denotes the business state of an object. The disposition field of an event
231 specifies the business condition of the subject of the event (the things specified in the
232 “what” dimension), subsequent to the event. The disposition is assumed to hold true until
233 another event indicates a change of disposition. Identifiers for dispositions in the Core
234 Business Vocabulary are specified in Section 7.2.
235 Example: an EPCIS event is generated and afterward the products can be sold as-is and
236 customers can access product for purchase. Disposition = 237 “sellable and accessible”>
238 • Business Transaction References  An EPCIS event may refer to one or more business
239 transaction documents. Each such reference consists of two identifiers:
240 • Business Transaction Type   Denotes a particular kind of business transaction.
241 Example: the identifier that denotes “purchase order”.  Identifiers for business
242 transaction types in the Core Business Vocabulary are specified in Section 7.3.
243 • Business Transaction Identifier  Denotes a specific business transaction document of
244 the type indicated by the Business Transaction Type. Example:  245 denotes Example Corp purchase order #123456> Identifiers for business
246 transactions in the Core Business Vocabulary are specified in Section 8.5.
247 • Source and Destination References  An EPCIS event may refer to one or more sources
248 and/or destinations that describe the endpoints of a business transfer of which the event is
249 a part. Each source or destination reference consists of two identifiers:
250 • Source or Destination Type   Denotes a particular kind of source or destination.
251 Example: the identifier that denotes “owning party”.  Identifiers for source and
252 destination types in the Core Business Vocabulary are specified in Section 7.4.
253 • Source or Destination Identifier  Denotes a source or destination of the type
254 indicated by the Business Transaction Type. Example:  255 Example Corp as an owning party> Identifiers for sources and destinations in the
256 Core Business Vocabulary are specified in Section 8.6.
257 3.2 Vocabulary Kinds
258 (The material in this section is adapted directly from [EPCIS1.1], Section 6.2.)

Version 1.1, May-2014 All contents © 2010–2014 GS1         Page 9 of 62
© ISO/IEC 2015 – All rights reserved

Core Business Vocabulary
259 Vocabularies are used extensively within EPCIS to model conceptual, physical, and digital
260 entities that exist in the real world.
261 Examples of vocabularies defined in the EPCIS standard are business steps, dispositions,
262 location identifiers, physical or digital object identifiers, business transaction type names, and
263 business transaction identifiers. In each case, a vocabulary represents a finite (though open-
264 ended) set of alternatives that may appear in specific fields of events.
265 It is useful to distinguish two kinds of vocabularies, which follow different patterns in the way
266 they are defined and extended over time:
267 • Standard Vocabulary  A Standard Vocabulary is a set of Vocabulary Elements whose
268 definition and meaning must be agreed to in advance by trading partners who will exchange
269 events using the vocabulary.
270 • User Vocabulary  A User Vocabulary is a set of Vocabulary Elements whose definition and
271 meaning are under the control of a single organization.
272 These concepts are explained in more detail below.
273 3.2.1 Standard Vocabulary
274 A Standard Vocabulary is a set of Vocabulary Elements whose definition and meaning must be
275 agreed to in advance by trading partners who will exchange events using the vocabulary. For
276 example, the EPCIS standard defines a vocabulary called “business step,” whose elements are
277 identifiers denoting such things as “shipping,” “receiving,” and so on. One trading partner may
278 generate an event having a business step of “shipping,” and another partner receiving that event
279 through a query can interpret it because of a prior agreement as to what “shipping” means.
280 Standard Vocabulary elements tend to be defined by organizations of multiple end users, such as
281 GS1, industry consortia outside GS1, private trading partner groups, and so on. The master data
282 associated with Standard Vocabulary elements, if any master data is defined at all, are defined by
283 those same organizations, and tend to be distributed to users as part of a standard or by some
284 similar means. New vocabulary elements within a given Standard Vocabulary tend to be
285 introduced through a very deliberate and occasional process, such as the ratification of a new
286 version of a standard or through a vote of an industry group.
287 The Standard Vocabularies specified in the Core Business Vocabulary standard are: business
288 steps (Section 7.1), dispositions (Section 7.2), business transaction types (Section 7.3), and
289 source and destination types (Section 7.4). The elements and definitions are agreed to by parties
290 prior to exchanging data, and there is general agreement on their meaning.
291 Example: the following is a business step identifier defined in Section 7.1 herein:
292 urn:epcglobal:cbv:bizstep:receiving
293 This identifier is defined by the GS1 Core Business Vocabulary standard, and its meaning is
294 known and accepted by those who implement the standard.
295 While an individual end user organization acting alone may introduce a new Standard
296 Vocabulary element, such an element would have limited use in a data exchange setting, and
297 would probably only be used within an organization’s four walls. On the other hand, an industry
298 consortium or other group of trading partners may define and agree on standard vocabulary

Version 1.1, May-2014 All contents © 2010–2014 GS1         Page 10 of 62
© ISO/IEC 2015 – All rights reserved

Core Business Vocabulary
299 elements beyond those defined by the Core Business Vocabulary, and these may be usefully used
300 within that trading group.
301 3.2.2 User Vocabulary
302 A User Vocabulary is a set of Vocabulary Elements whose definition and meaning are under the
303 control of a single organization. For example, the EPCIS standard defines a vocabulary called
304 “business location,” whose elements are identifiers denoting such things as “Acme Corp.
305 Distribution Center #3.” The location identifier and any associated master data is assigned by
306 the user. Acme Corp may generate an event whose business location field contains the identifier
307 that denotes “Acme Corp. Distribution Center #3,” and another partner receiving that event
308 through a query can interpret it either because the partner recognizes the identifier as being
309 identical to the identifier received in other events that took place in the same location, or because
310 the partner consults master data attributes associated with the location identifier, or both.
311 Example:
312 urn:epc:id:sgln:0614141.12345.400
313 This identifier is assigned by the End User who owns the GS1 Company Prefix 0614141, and the
314 meaning of the identifier (that is, what location it denotes) is determined exclusively by that end
315 user. Another End User can understand the meaning of this identifier by consulting associated
316 master data.
317 User Vocabulary elements are primarily defined by individual end user organizations acting
318 independently. The master data associated with User Vocabulary elements are typically defined
319 by those same organizations, and are usually distributed to trading partners through the EPCIS
320 Query Interface or other data exchange / data synchronization mechanisms. New vocabulary
321 elements within a given User Vocabulary are introduced at the sole discretion of an end user, and
322 trading partners must be prepared to respond accordingly.
323 While the Core Business Vocabulary standard does not (and as the discussion above makes clear,
324 cannot) specify particular user vocabulary elements, the Core Business Vocabulary does provide
325 syntax templates that are recommended for use by End Users in constructing their own user
326 vocabulary elements. See Section 8.1. The user vocabularies for which templates are specified
327 in this standard are: physical or digital objects (Sections 8.2 and 8.3), locations which include
328 both read points and business locations (Section 8.4), business transaction identifiers
329 (Section 8.5), source/destination identifiers (Section 8.6), and transformation identifiers
330 (Section 8.7).
331 4 Terminology and Typographical Conventions
332 Within this standard, the terms SHALL, SHALL NOT, SHOULD, SHOULD NOT, MAY,
333 NEED NOT, CAN, and CANNOT are to be interpreted as specified in Annex G of the ISO/IEC
334 Directives, Part 2, 2001, 4th edition [ISODir2]. When used in this way, these terms will always
335 be shown in ALL CAPS; when these words appear in ordinary typeface they are intended to have
336 their ordinary English meaning.
337 All sections of this document, with the exception of Sections 1, 2, and 3, are normative, except
338 where explicitly noted as non-normative.

Version 1.1, May-2014 All contents © 2010–2014 GS1         Page 11 of 62
© ISO/IEC 2015 – All rights reserved

Core Business Vocabulary
339 The following typographical conventions are used throughout the document:
340 • ALL CAPS type is used for the special terms from [ISODir2] enumerated above.
341 • Monospace type is used to denote programming language, UML, and XML identifiers, as
342 well as for the text of XML documents.
343  Placeholders for changes that need to be made to this document prior to its reaching the final
344 stage of approved GS1 standard are prefixed by a rightward-facing arrowhead, as this
345 paragraph is.
346 5 Compliance and Compatibility
347 The GS1 Core Business Vocabulary is designed to facilitate interoperability in EPCIS data
348 exchange by providing standard values for vocabulary elements to be included in EPCIS data.
349 The standard recognizes that the greatest interoperability is achieved when all data conforms to
350 the standard, and also recognizes that individual End Users or groups of trading partners may
351 need to extend the standard in certain situations.
352 To that end, this standard defines two levels of conformance for EPCIS documents:
353 • CBV-Compliant  An EPCIS document that only uses vocabulary identifiers specified in the
354 Core Business Vocabulary standard in the standard fields of EPCIS events.
355 • CBV-Compatible  An EPCIS document that uses a combination of vocabulary identifiers
356 specified in the Core Business Vocabulary standard and other identifiers that are outside the
357 standard.
358 An EPCIS document is neither CBV-Compliant nor CBV-Compatible if it wrongly uses
359 identifiers defined in the Core Business Vocabulary standard or if it violates any other rules
360 specified herein.
361 The formal definition of these terms is specified below.
362 5.1 CBV Compliant
363 A “CBV-Compliant Document” is a document that conforms to the schema and other constraints
364 specified in [EPCIS1.1], and which furthermore conforms to all the normative language in this
365 standard that pertains to a “CBV-Compliant Document.”
366 A “CBV-Compliant Application” is any application for which both of the following are true:
367 • If it operates in a mode where it claims to accept a CBV-Compliant Document as an input,
368 the application SHALL accept any document that is a CBV-Compliant Document according
369 to this standard, and furthermore in processing that input SHALL interpret each CBV
370 identifier according to the meaning specified herein.
371 • If it operates in a mode where it claims to produce a CBV-Compliant Document as an output,
372 the application SHALL only produce a document that is a CBV-Compliant Document
373 according to this standard, and furthermore in generating that output SHALL only use CBV
374 identifiers to denote their meaning as specified herein.

Version 1.1, May-2014 All contents © 2010–2014 GS1         Page 12 of 62
© ISO/IEC 2015 – All rights reserved

Core Business Vocabulary
375 The following list summarizes the requirements for an EPCIS document to be a “CBV-
376 Compliant Document,” as specified elsewhere in this standard:
377 • A CBV-Compliant Document SHALL conform to the schema and other constraints specified
378 in [EPCIS1.1].
379 • A CBV-Compliant Document SHALL NOT use any URI beginning with
380 urn:epcglobal:cbv: except as specified in this standard.
381 • Each EPCIS event in a CBV-Compliant Document SHALL include a bizStep field, and
382 the value of the bizStep field SHALL be a URI consisting of the prefix
383 urn:epcglobal:cbv:bizstep: followed by the string specified in the first column of
384 some row of the table in Section 7.1.2.
385 • A CBV-Compliant Document MAY include a disposition field. If the disposition
386 field is present, the value of the disposition field SHALL be a URI consisting of the
387 prefix urn:epcglobal:cbv:disp: followed by the string specified in the first column
388 of some row of the table in Section 7.2.2.
389 • Each EPCIS event in a CBV-Compliant Document MAY include one or more
390 bizTransaction elements. If bizTransaction elements are present, each such
391 element MAY include a type attribute. If a given bizTransaction element includes a
392 type attribute, the value of the type attribute SHALL be a URI consisting of the prefix
393 urn:epcglobal:cbv:btt: followed by the string specified in the first column of some
394 row of the table in Section 7.3.2.
395 • Each EPCIS event in a CBV-Compliant Document MAY include one or more source or
396 destination elements. The value of the type attribute of each such element SHALL be
397 a URI consisting of the prefix urn:epcglobal:cbv:sdt: followed by the string
398 specified in the first column of some row of the table in Section 7.4.2.
399 • URIs defined in the EPC Tag Data Standard SHALL only be used in a CBV-Compliant
400 Document as specified in Section 8.1.1.
401 • A CBV-Compliant document SHALL use one of the three URI forms specified in
402 Section 8.2 to populate instance-level identifiers in the “what” dimension of EPCIS events
403 (that is, the epcList, parentID, childEPCs, inputEPCList, and
404 outputEPCList fields in EPCIS ObjectEvents, AggregationEvents,
405 TransacationEvents, and TransformationEvents), for every such field that is
406 not null. A CBV-Compliant document SHOULD use the EPC URI form as specified in
407 Section 8.2.1 unless there is a strong reason to do otherwise.
408 • A CBV-Compliant document SHALL NOT use an SGLN EPC (urn:epc:id:sgln:…) as
409 an object identifier.
410 • A CBV-Compliant document SHALL use one of the three URI forms specified in
411 Section 8.3 to populate class-level identifiers in the “what” dimension of EPCIS events (that
412 is, the epcClass fields in all EPCIS event types), for every such field that is not null. A
413 CBV-Compliant document SHOULD use the EPC URI form as specified in Section 8.3.1
414 unless there is a strong reason to do otherwise.

Version 1.1, May-2014 All contents © 2010–2014 GS1         Page 13 of 62
© ISO/IEC 2015 – All rights reserved

Core Business Vocabulary
415 • A CBV-Compliant document SHALL use one of the four URI forms specified in Section 8.4
416 to populate the “where” dimension of EPCIS events (that is, the readPoint and
417 businessLocation fields in all EPCIS event types), for every such field that is not null.
418 A CBV-Compliant document SHOULD use the EPC URI form as specified in Section 8.4.1
419 unless there is a strong reason to do otherwise.
420 • When using an EPC URI as a location identifier (Section 8.4.1), a CBV-Compliant document
421 SHOULD NOT use EPC schemes other than SGLN (urn:epc:id:sgln:…), unless there
422 is a strong reason to do so.
423 • A CBV-Compliant document SHALL use one of the four URI forms specified in Section 8.5
424 to populate the business transaction identifier field (that is, the text content of the
425 bizTransaction element) of EPCIS events, for every such field that is not null.
426 • When using an EPC URI as a business transaction identifier, a CBV-Compliant Documents
427 SHOULD NOT use EPC schemes other than GDTI EPCs (urn:epc:id:gdti:…) or
428 GSRN EPCs (urn:epc:id:gsrn:…), unless there is a strong reason to do so. GDTI
429 EPCs SHOULD only be used as business transaction identifiers when they have been
430 assigned to denote a business transaction, rather than a physical document not connected with
431 any business transaction.
432 • A CBV-Compliant document SHALL use one of the three URI forms specified in
433 Section 8.6 to populate a source or destination identifier field (that is, the text content of a
434 source or destination element), for every such field that is not null. A CBV-
435 Compliant document SHOULD use the EPC URI form as specified in Section 8.6.1 unless
436 there is a strong reason to do otherwise.
437 • When using an EPC URI as a location identifier (Section 8.6.1), a CBV-Compliant document
438 SHOULD NOT use EPC schemes other than SGLN (urn:epc:id:sgln:…), unless there
439 is a strong reason to do so.
440 • A CBV-Compliant document SHALL use one of the four URI forms specified in Section 8.7
441 to populate the transaction identifier field (that is, the text content of the
442 transformationID element) of EPCIS TransformationEvents, for every such
443 field that is not null.
444 • When using an EPC URI as a transformation identifier, a CBV-Compliant Document
445 SHOULD NOT use EPC schemes other than GDTI EPCs (urn:epc:id:gdti:…) unless
446 there is a strong reason to do so. GDTI EPCs SHOULD only be used as transformation
447 identifiers when they have been assigned to denote a transformation, rather than a physical
448 document not connected with any transformation.
449 5.2 CBV Compatible
450 A “CBV-Compatible Document” is a document that conforms to the schema and other
451 constraints specified in [EPCIS1.1], and which furthermore conforms to all the normative
452 language in this standard that pertains to a “CBV-Compatible Document.”
453 A “CBV-Compatible Application” is any application for which both of the following are true:

Version 1.1, May-2014 All contents © 2010–2014 GS1         Page 14 of 62
© ISO/IEC 2015 – All rights reserved

Core Business Vocabulary
454 • If it operates in a mode where it claims to accept a CBV-Compatible Document as an input,
455 the application SHALL accept any document that is a CBV-Compatible Document according
456 to this standard, and furthermore in processing that input SHALL interpret each CBV
457 identifier according to the meaning specified herein.
458 • If it operates in a mode where it claims to produce a CBV-Compatible Document as an
459 output, the application SHALL only produce a document that is a CBV-Compatible
460 Document according to this standard, and furthermore in generating that output SHALL only
461 use CBV identifiers to denote their meaning as specified herein.
462 The following list summarizes the requirements for an EPCIS document to be a “CBV-
463 Compatible Document,” as specified elsewhere in this standard.
464 • A CBV-Compatible Document SHALL conform to the schema and other constraints
465 specified in [EPCIS1.1].
466 • A CBV-Compatible Document SHALL NOT use any URI beginning with
467 urn:epcglobal:cbv: except as specified in this stand
...