BS EN IEC 62656-8:2020
$215.11
Standardized product ontology register and transfer by data parcels – Part 8: Web service interface for data parcels
| Published By | Publication Date | Number of Pages |
| BSI | 2020 | 82 |
IEC 62656-8:2020 specifies a web service interface to exchange data parcel(s) conformant to IEC 62656-1, between a parcel server and a parcel client or between parcel servers. This interface comprises three basic services: a registration service, resolution service and subscription service. This document includes the following: – holistic use scenario; – detailed specification of the three basic services; – JSON and XML notation schemas for data parcel(s). The following items are outside the scope of this document: – user identification and authorization; – query language for a data parcel; – transportation protocol; – data and communication security techniques.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | undefined |
| 5 | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications |
| 7 | English CONTENTS |
| 11 | FOREWORD |
| 13 | INTRODUCTION |
| 15 | 1 Scope 2 Normative references |
| 16 | 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions |
| 18 | 3.2 Abbreviated terms 4 Use scenarios 4.1 Holistic use scenario |
| 19 | 4.2 Use scenario between server and client Figures Figure 1 – Holistic use scenario of parcel web services |
| 20 | 4.3 Use scenario between servers Figure 2 – Parcel resolution and registration services between a server and a client |
| 21 | 5 Parcel web service specification 5.1 General 5.2 Exception 5.2.1 General Figure 3 – Parcel subscription service between registries |
| 22 | 5.2.2 Naming convention for an exception 5.2.3 Standard-defined exceptions Figure 4 – Tree structure of exceptions |
| 23 | 5.3 Search scope Tables Table 1 – Standard-defined exceptions for parcel web services |
| 24 | Figure 5 – Example of structural view of the use of search scope modifiers Table 2 – Specification of search scope modifiers |
| 25 | 5.4 Parcel registration service 5.4.1 General 5.4.2 Request message Figure 6 – Example of a parcel sheet view of the use of search scope modifiers Table 3 – Structure of a request message of the parcel registration service |
| 27 | 5.4.3 Response message Table 4 – Structure of a response message of the parcel registration service |
| 28 | 5.4.4 Exception 5.5 Parcel resolution service 5.5.1 General |
| 29 | 5.5.2 Request message Figure 7 – Overview of parcel resolution service |
| 30 | Table 5 – Structure of a request message of the parcel resolution service |
| 32 | 5.5.3 Response message 5.5.4 Exception Table 6 – Structure of a response message of the parcel resolution service |
| 33 | 5.6 Parcel subscription service 5.6.1 General 5.6.2 Request message Table 7 – Structure of a request message of the parcel subscription service |
| 34 | 5.6.3 Response message 5.6.4 Exception 5.6.5 Specification of change notification Table 8 – Structure of a response message of the parcel subscription service |
| 35 | 6 Specification of parcel data representation in a web service message 6.1 General 6.2 Basic data representation Table 9 – Specification of a notification |
| 36 | 6.3 Reserved keywords 6.3.1 Keyword indicating conjunctive parcels 6.3.2 Keyword indicating parcel ontology layer of a set of data parcels 6.3.3 Keyword indicating header section 6.3.4 Keyword indicating class header section Figure 8 – Basic structure of a data representation for a conjunctive set of data parcels |
| 37 | 6.3.5 Keyword indicating schema header section 6.3.6 Keyword indicating data section 6.3.7 Keyword indicating default supplier in data section 6.3.8 Keyword indicating default version in data section 6.4 Additional instructions to data parcels for parcel web services 6.4.1 Codification mode |
| 38 | 6.4.2 Intended language 6.4.3 Default value |
| 39 | 6.5 Description of instructions Figure 9 – Example of the use of default values |
| 40 | 7 Data representation in JSON 7.1 Basic structure of data representation in JSON Table 10 – Description of the instructions specified in IEC 62656-1 Table 11 – Description of the instructions specified in this document |
| 41 | Figure 10 – Basic structure of data representation in JSON |
| 42 | 7.2 Reserved JSON name indicating an array of data parcels 7.3 JSON names for class header section 7.3.1 JSON name indicating the instruction “#CLASS_ID” 7.3.2 JSON name indicating the instruction “#PARCEL_MODE” 7.3.3 JSON name indicating the instruction “#PARCEL_ID” 7.3.4 JSON name indicating the instruction “#DEFAULT_SUPPLIER” |
| 43 | 7.3.5 JSON name indicating the instruction “#DEFAULT_VERSION” 7.3.6 JSON name indicating the instruction “#OBJECT_ID_NAME” 7.3.7 JSON name indicating the instruction “#ID_ENCODE” 7.3.8 JSON name indicating the instruction “#PWS_CODIFICATION_MODE” 7.3.9 JSON name indicating the instruction “#INTENDED_LANGUAGE” 7.4 JSON names for schema header section 7.4.1 Basic structure of data representation for schema header section in JSON |
| 44 | 7.4.2 JSON names for the schema header section Figure 11 – Basic structure of data representation for schema header section in JSON |
| 45 | 7.5 Data representation for data section in JSON 7.5.1 Vertical JSON notation for data section 7.5.2 Lateral JSON notation for data section 7.6 Character encode |
| 46 | 8 Data representation in XML 8.1 Basic structure of data representation in XML Figure 12 – Basic structure of data representation in XML |
| 47 | 8.2 Reserved keyword indicating data parcel 8.3 XML elements for class header section 8.3.1 XML element indicating the instruction “#CLASS_ID” 8.3.2 XML element indicating the instruction “#PARCEL_MODE” 8.3.3 XML element indicating the instruction “#PARCEL_ID” 8.3.4 XML element indicating the instruction “#DEFAULT_SUPPLIER” 8.3.5 XML element indicating the instruction “#DEFAULT_VERSION” |
| 48 | 8.3.6 XML element indicating the instruction “#OBJECT_ID_NAME” 8.3.7 XML element indicating the instruction “#ID_ENCODE” 8.3.8 XML element indicating the instruction “#PWS_CODIFICATION_MODE” 8.3.9 XML element indicating the instruction “#INTENDED_LANGUAGE” 8.4 XML elements for schema header section 8.4.1 Basic structure of data representation for schema header section in XML |
| 49 | 8.4.2 XML elements of schema header section Figure 13 – Basic structure of data representation for schema header section in XML |
| 50 | 8.5 XML elements and attributes for data section 8.5.1 Vertical XML notation of data section Figure 14 – Structure of data representation for data sectionin the vertical XML notation |
| 51 | 8.5.2 Lateral XML notation of data section |
| 52 | Figure 15 – Structure of data representation for data section in lateral XML notation |
| 53 | 8.6 Character encode |
| 54 | Annex A (normative)Schema A.1 JSON schema A.1.1 Vertical JSON schema Figure A.1 – Vertical JSON schema (1 of 2) |
| 56 | A.1.2 Lateral JSON schema Figure A.2 – Lateral JSON schema (1 of 2) |
| 58 | A.1.3 Exception JSON schema Figure A.3 – Exception JSON schema |
| 59 | A.2 XML schema A.2.1 Vertical XML schema Figure A.4 – Vertical XML schema (1 of 3) |
| 62 | A.2.2 Lateral XML schema Figure A.5 – Lateral XML schema (1 of 3) |
| 64 | A.2.3 Exception XML schema Figure A.6 – Exception XML schema |
| 65 | Annex B (normative) Web service representation B.1 Web service representation in WADL Figure B.1 – Web service representation in WADL (1 of 4) |
| 69 | B.2 Web service representation in WSDL Figure B.2 – Web service representation in WSDL (1 of 4) |
| 73 | Annex C (informative)Examples of data representation C.1 Example data parcel Table C.1 – Example data parcel |
| 74 | C.2 Example of data representation in JSON notation C.2.1 Example of data representation in vertical JSON notation Figure C.1 – Example of data representation in vertical JSON notation |
| 75 | C.2.2 Example of data representation in lateral JSON notation Figure C.2 – Example of data representation in lateral JSON notation |
| 76 | C.3 Example of data representation in XML notation C.3.1 Example of data representation in vertical XML notation Figure C.3 – Example of data representation in vertical XML notation (1 of 2) |
| 78 | C.3.2 Example of data representation in lateral XML notation Figure C.4 – Example of data representation in lateral XML notation (1 of 2) |
| 80 | Annex D (informative)Descriptions of the instructions of “optional – informative” Table D.1 – Descriptions of the instructions of “optional – informative” |
| 81 | Bibliography |
Related products
-
IEC 62656-8:2020
Standardized product ontology register and transfer by data parcels – Part 8: Web service interface…
