BS EN 62361-100:2016
$198.66
Power systems management and associated information exchange. Interoperability in the long term – CIM profiles to XML schema mapping
| Published By | Publication Date | Number of Pages |
| BSI | 2016 | 56 |
IEC 62361-100:2016 describes a mapping from CIM profiles to W3C XML Schemas, intended to facilitate the exchange of information in the form of XML documents whose semantics are defined by the IEC CIM and whose syntax is defined by a W3C XML schema.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 4 | European foreword Endorsement notice |
| 5 | Annex ZA (normative) Normative references to international publications with their corresponding European publications |
| 6 | English CONTENTS |
| 9 | FOREWORD |
| 11 | INTRODUCTION |
| 12 | 1 Scope 2 Normative references 3 Terms and definitions |
| 14 | 4 System context 4.1 Profiling process |
| 15 | 4.2 CIM 4.3 Contextual model 4.4 Contextual model artefacts 4.4.1 Contextual model artefacts and CIM subset 4.4.2 Contextual model artefacts definition |
| 16 | Tables Table 1 – Contextual model artefacts |
| 18 | 4.5 Mapping contextual model to XML schema 4.5.1 General 4.5.2 Traceability 4.6 XML Schema Representation |
| 19 | 4.7 Namespaces 5 Mapping specifications 5.1 General 5.1.1 Example |
| 20 | 5.1.2 Mapped name 5.2 Profile mapping 5.2.1 General Figures Figure 1 – Example XML Schema CIM-based profile |
| 21 | 5.2.2 Namespace and version 5.2.3 Schema top level element |
| 22 | 5.2.4 Types 5.2.5 Semantic annotation |
| 23 | 5.3 Structured classes |
| 24 | 5.4 Compound classes |
| 25 | 5.5 Basic types 5.6 Simple types 5.6.1 Mapping rules Table 2 – Basic Types |
| 26 | 5.6.2 Possible facets |
| 27 | 5.7 Data Types mapping Table 3 – Facets |
| 29 | 5.8 Enumeration classes mapping |
| 30 | 5.9 CodeList classes mapping |
| 31 | 5.10 Simple properties mapping |
| 32 | 5.11 Compound properties mapping |
| 33 | 5.12 Object properties 5.12.1 Mapping rules overview 5.12.2 Typed object properties mapping 5.12.3 By reference object properties mapping |
| 34 | 5.12.4 Union object properties mapping |
| 36 | 5.13 Exclusive property group mapping |
| 37 | 5.14 Documentation and categorized documentation 5.14.1 General mapping 5.14.2 Documentation mapping 5.14.3 Categorized documentation mapping 5.14.4 Stereotype mapping |
| 38 | 5.15 Names 5.16 Mapping order 5.16.1 General mapping order basis Figure 2 – Example of alphabetical order Figure 3 – Example of business order |
| 39 | 5.16.2 Alphabetical based mapping order |
| 40 | 5.16.3 Business context based mapping order 5.17 Changing name rules Figure 4 – Example business context order of a schema |
| 42 | Annex A (normative) Use of dedicated XML schemas for datatypes, enumerations and codelists A.1 Context: A.2 Modular schema design and mapping: |
| 43 | A.3 Artefact mapping A.3.1 General rule A.3.2 Datatype, enumeration or codelist mapping: |
| 44 | A.3.3 Simple property mapping |
| 45 | Annex B (informative) Contextual model representations Table B.1 – Contextual model representation |
| 46 | Annex C (informative) Changing name rules examples C.1 Changing name rule context C.2 Changing name rules when using “union” super class C.2.1 General C.2.2 Changing name rule when CIM association end role name and CIM super class name are the same Figure C.1 – Example of end role name matching super class name |
| 47 | C.2.3 Changing name rule when CIM association end role name is the CIM super class name prefixed by a qualifier followed by an underscore Figure C.2 – Contextual model end role name matching super class name Figure C.3 – Example of end role name with a qualifier |
| 48 | C.2.4 Changing name rule when CIM association end role name and the CIM super class name are completely different Figure C.4 – Contextual model end role name with a qualifier Figure C.5 – End role name and super class name different |
| 49 | C.3 Changing name rules when using complex properties with the same name C.3.1 General C.3.2 Changing name rule when CIM association end role name and CIM super class name are the same Figure C.6 – Contextual model with end role name different from super class name |
| 50 | C.3.3 Changing name rule when CIM association end role name is the CIM super class name prefixed by a qualifier followed by an underscore Figure C.7 – Example of end role name matching super class name Figure C.8 – Contextual model end role name matching super class name |
| 51 | Figure C.9 – Example of end role name with a qualifier Figure C.10 – Contextual model end role name with a qualifier |
| 52 | C.3.4 Changing name rule when CIM association end role name and the CIM super class name are completely different Figure C.11 – End role name and super class name different Figure C.12 – Contextual model with end role name different from super class name |
| 54 | Bibliography |
