BS ISO/IEC 19987:2024
$215.11
Information technology. EPC Information Services (EPCIS)
Published By | Publication Date | Number of Pages |
BSI | 2024 | 202 |
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
11 | 1 Introduction |
12 | 2 Relationship to the GS1 System Architecture 2.1 Overview of GS1 standards |
13 | 2.2 EPCIS in relation to the “Capture” and “Share” layers |
14 | 2.3 EPCIS in Relation to trading partners |
15 | 2.4 EPCIS in relation to other GS1 System Architecture components |
18 | 3 EPCIS specification principles |
19 | 4 Terminology and typographical conventions |
20 | 5 EPCIS specification framework 5.1 Layers |
21 | 5.2 Extensibility 5.3 Modularity |
23 | 6 Abstract data model layer 6.1 Event data and master data |
25 | 6.1.1 Transmission of master data in EPCIS 6.2 Standard vocabulary and user vocabulary |
27 | 6.3 Extension mechanisms |
28 | 6.4 Identifier representation |
29 | 6.5 Hierarchical vocabularies |
30 | 7 Data definition layer 7.1 General rules for specifying data definition layer modules 7.1.1 Content |
31 | 7.1.2 Notation 7.1.3 Semantics |
33 | 7.2 Core event types module – overview |
34 | 7.2.1 UML Diagrams of EPCIS Event Types 7.2.1.1 UML with Ontology focus 7.2.1.2 UML with Syntax focus 7.2.1.3 UML for SBDH |
35 | 7.2.2 Overview of EPCIS event “dimensions” (non-normative) |
38 | 7.2.3 Table of vocabulary types |
39 | 7.3 Core event types module – building blocks 7.3.1 Primitive types |
40 | 7.3.2 Action type |
41 | 7.3.3 The “What” dimension 7.3.3.1 QuantityElement |
42 | 7.3.3.1.1 UOM 7.3.3.1.2 Class-level identifiers 7.3.3.2 Identifier types (Non-Normative) 7.3.4 The “When” dimension |
43 | 7.3.4.1 The “When” dimension in the EPCISEvent common base type 7.3.4.2 The “When” dimension in the Error Declaration 7.3.4.3 The “When” dimension in Sensor Metadata 7.3.5 The “Where” Dimension – read point and business location |
45 | 7.3.5.1 Example of the distinction between a read point and a business location (Non-Normative) |
46 | 7.3.6 The “Why” dimension 7.3.6.1 Business step 7.3.6.2 Disposition and Persistent Disposition 7.3.6.2.1 Disposition |
47 | 7.3.6.2.2 Persistent Disposition |
48 | 7.3.6.3 Business transaction 7.3.6.3.1 Business transaction type |
49 | 7.3.6.3.2 Business transaction ID 7.3.6.4 Source and destination |
50 | 7.3.6.4.1 Source/Destination type 7.3.6.4.2 Source/Destination ID 7.3.7 The “How” dimension 7.3.7.1 SensorElement |
51 | 7.3.7.1.1 SensorMetadata |
53 | 7.3.7.1.2 SensorReport |
56 | 7.3.7.1.3 Coordinate reference systems (CRS) 7.3.7.1.4 Sensor property type |
57 | 7.3.7.1.5 UOM 7.3.7.1.6 Microorganism ID 7.3.7.1.7 Chemical Substance ID 7.3.7.1.8 Resource ID 7.3.8 Instance/Lot master data (ILMD) |
58 | 7.4 Core event types module – events 7.4.1 EPCISEvent |
59 | 7.4.1.1 Explanation of eventTimeZoneOffset (Non-Normative) |
60 | 7.4.1.2 ErrorDeclaration 7.4.1.2.1 Use of error declarations (Non-Normative) |
62 | 7.4.1.2.2 Matching an error declaration to the original event (non-normative) 7.4.2 ObjectEvent (subclass of EPCISEvent) |
66 | 7.4.3 AggregationEvent (subclass of EPCISEvent) |
70 | 7.4.4 TransactionEvent (subclass of EPCISEvent) |
75 | 7.4.5 TransformationEvent (subclass of EPCISEvent) |
78 | 7.4.6 AssociationEvent (subclass of EPCISEvent) |
84 | 8 Service Layer |
86 | 8.1 Core capture operations module 8.1.1 Authentication and authorisation |
87 | 8.1.2 Capture service |
88 | 8.2 Core Query operations module 8.2.1 Authentication |
89 | 8.2.2 Authorisation and redaction 8.2.3 Queries for large amounts of data |
90 | 8.2.4 Overly complex queries 8.2.5 Query framework (EPCIS query control interface) |
92 | 8.2.5.1 Subscription controls |
93 | 8.2.5.2 Automatic limitation based on event record time |
94 | 8.2.5.3 Query schedule |
95 | 8.2.5.3.1 Query schedule examples (Non-Normative) |
96 | 8.2.5.4 QueryResults 8.2.6 Error conditions |
98 | 8.2.7 Predefined queries for EPCIS |
99 | 8.2.7.1 SimpleEventQuery |
131 | 8.2.7.1.1 Processing of MATCH query parameters 8.2.7.2 SimpleMasterDataQuery – REMOVED in EPCIS 2.0 8.2.8 Query callback interface |
132 | 9 XML bindings for data definition modules 9.1 Extensibility mechanism |
135 | 9.2 Standard business document header 9.3 EPCglobal Base schema |
136 | 9.4 Master data in the XML binding |
137 | 9.5 Schema for core event types |
138 | 9.6 Core event types – examples (Non-Normative) |
139 | 10 JSON/JSON-LD bindings for data definition 10.1 Brief introduction to JSON and JSON-LD in the context of EPCIS |
140 | 10.1.1 JavaScript Object Notation (JSON) |
141 | 10.1.2 JSON for Linked Data (JSON-LD) |
142 | 10.1.3 Features of the JSON-LD context resource |
143 | 10.1.4 Compact URI Expressions (CURIEs) |
144 | 10.2 Expression and validation of EPCIS data structures in JSON and JSON-LD 10.2.1 Expressing data fields expecting simple values |
146 | 10.2.2 Validating data fields expecting simple values |
148 | 10.2.3 Validation of fields (e.g. ‘action’) that expect a string value from an enumerated list |
149 | 10.2.4 Expressing simple lists of values |
150 | 10.2.5 Validating lists of values 10.2.6 Expressing lists of elements with inline attributes expressing type |
153 | 10.2.7 Modelling and validating subclasses of EPCIS event |
154 | 10.2.8 Comparison of how validation rules are expressed in XSD, JSON Schema and SHACL |
156 | 10.2.9 Mapping core SBDH fields to the JSON/JSON-LD data format for EPCIS 10.2.10 Online validation tools for JSON Schema and SHACL 10.2.11 Libraries and toolkits providing JSON-LD support 10.3 Validation schema (references to normative content) |
157 | 10.4 Non-normative examples in JSON and JSON-LD 11 Bindings for core capture operations module 11.1 Message queue binding |
158 | 11.2 HTTP binding |
159 | 12 REST Bindings 12.1 Code conventions 12.2 Introduction to REST |
161 | 12.3 Content negotiation, service discovery and custom headers for EPCIS |
163 | 12.4 Authentication and Authorization |
164 | 12.5 Pagination 12.6 Capturing EPCIS Events |
165 | 12.6.1 Capture Interface |
166 | 12.6.2 Capture Jobs Interface |
167 | 12.7 Events interface 12.7.1 EPCIS events collections 12.7.2 EPCIS events endpoints |
168 | 12.7.3 Event filtering with the EPCIS query language |
169 | 12.7.4 Top-level resources |
170 | 12.8 Query control interface |
172 | 12.8.1 Creating and using named queries 12.8.2 Deleting named queries 12.8.3 Subscribing to named queries |
174 | 12.8.3.1 Scheduled queries 12.8.3.2 Streaming queries |
175 | 12.8.3.3 Webhook (HTTP Callback) for query subscription |
176 | 12.8.3.4 WebSocket for query subscription |
177 | 12.8.4 EPCIS query language |
178 | 12.8.5 EPCIS query in the URL |
179 | 12.9 Backward Compatibility of REST bindings with EPCIS 1.2 12.10 EPCIS Error Conditions and HTTP Status Code Mapping |
182 | 13 Bindings for core query operations module 13.1 XML schema for core query operations module |
183 | 13.2 SOAP/HTTP binding for the query control interface |
184 | 13.3 AS2 Binding for the query control interface |
185 | 13.3.1 GS1 AS2 guidelines (Non-Normative) |
187 | 13.4 Bindings for query callback interface |
188 | 13.4.1 General Considerations for all XML-based bindings 13.4.2 HTTP binding of the query callback interface |
189 | 13.4.3 HTTPS binding of the query callback interface 13.4.4 AS2 Binding of the query callback interface |
190 | 14 Conformance 14.1 Conformance of EPCIS XML data 14.2 Conformance of EPCIS capture interface clients 14.3 Conformance of EPCIS capture interface servers |
191 | 14.4 Conformance of EPCIS query interface clients 14.5 Conformance of EPCIS query interface servers 14.6 Conformance of EPCIS query callback interface implementations 14.7 Conformance of JSON/JSON-LD bindings |
192 | 14.8 Conformance of REST Interface for EPCIS 2.0 Servers |
194 | 15 UML Diagrams for SBDH |
195 | 15.1 UML aligned with text of SBDH specification 15.2 UML aligned with XSD of SBDH specification 16 List of abbreviations (non-normative) |
197 | 17 References |