Shopping Cart

No products in the cart.

BSI PD IEC/TS 62656-2:2013

$198.66

Standardized product ontology register and transfer by spreadsheets – Application guide for use with the IEC common data dictionary (CDD)

Published By Publication Date Number of Pages
BSI 2013 58
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

This part of IEC 62656 provides an application guide for the data parcels specified in IEC 62656-1 and used for the definition of a domain data dictionary that may be imported from and exported to the IEC common data dictionary, or IEC CDD for short, maintained as the IEC 61360-4 database [1]3. This part of IEC 62656 provides instructions for the interpretation and use of the technical specification defined in IEC 62656-1 within a software application, to avoid misuse of the data constructs available in IEC 62656-1.

This application guide contains the following items:

  • principal information for implementing data parcels for data dictionaries from/to the IEC CDD,

  • typical examples of how to implement typical features on data parcels,

  • extension of conformance classes for implementation of parcel-based systems to import/export data parcels from/to the IEC CDD.

The following items are outside the scope of this part of IEC 62656:

  • procedures for building IEC 61360 compliant domain data dictionaries,

  • semantics of a standard data dictionary itself,

  • theoretical explanation of the logical structure of data parcels, which is considered in IEC 62656-1,

  • interface for the common information model (IEC 61970-301 [2]), which is considered in IEC 62656-3 [3].

PDF Catalog

PDF Pages PDF Title
4 English
CONTENTS
6 FOREWORD
8 INTRODUCTION
9 1 Scope
2 Normative references
10 3 Terms and definitions
11 4 Overview
4.1 General
4.2 Data dictionary
Figures
Figure 1 – Typical use scenario
12 Figure 2 – Data dictionary
13 4.3 Data parcel
Figure 3 – Spreadsheet implementation
14 4.4 Blank parcel sheets
Figure 4 – Parcel sheet
15 5 Common cases for defining ontological elements
5.1 Semantics
16 5.2 Assigning an identifier
Figure 5 – Semantic definitions of ontological elements
17 5.3 Assigning a definition class
Figure 6 – Identification of ontological elements
18 5.4 Attributes to be considered
6 Specifying structures for data dictionaries
6.1 General
6.2 Classification tree
19 6.3 Reuse of properties, data types and documents in other branches
Figure 7 – Example of a simple classification tree
Figure 8 – Parcel implementation for simple classification trees
20 6.4 Composition tree
Figure 9 – Example of import mechanism
Figure 10 – Parcel implementation for case of relationships
21 Figure 11 – Composition relationship between two branches
Figure 12 – Example of a composition tree
22 7 Defining ontological elements by optional parcels
7.1 Defining enumerations
Figure 13 – Parcel implementation for composition trees
23 Figure 14 – Example of a use case of enumeration
24 7.2 Defining named data types
Figure 15 – Parcel implementation for enumerations
26 7.3 Defining information of external resources
Figure 16 – Parcel implementation for named data types
27 7.4 Defining units of measurement
Figure 17 – Parcel implementation for document references
29 7.5 Defining relationships between ontological elements
Figure 18 – Parcel implementation for unit of measurement
30 Figure 19 – UML package diagram by relations
31 Figure 20 – Parcel implementation of UML packages by predicate relations
Figure 21 – UML package diagram by functions
32 8 Advanced concepts
8.1 Implementation of condition
Figure 22 – Parcel implementation of UML packages by functions
33 8.2 Implementation of cardinality
Figure 23 – Example of condition
Figure 24 – Parcel implementation for condition
Tables
Table 1 – Property data element type for condition
34 8.3 Implementation of blocks and lists of properties (LOPs)
Figure 25 – Example of cardinality
Figure 26 – Parcel implementation for cardinality
35 Figure 27 – View example of a LOP and nested blocks
36 Figure 28 – Example of use case of blocks
Figure 29 – Example of a composition view of an LOP
37 8.4 Implementation of polymorphism
Figure 30 – Parcel implementation for blocks
38 Figure 31 – Example of a use case of polymorphism
Figure 32 – Example of composition view for polymorphism
39 Figure 33 – Parcel implementation for polymorphism
40 Figure 34 – Example of a use case of polymorphism with multiple choices
Figure 35 – Example of composition view for polymorphism with multiple choices
41 8.5 Alternate IDs
Figure 36 – Parcel implementation for polymorphism with multiple choices
42 9 Data file representation for storage and exchange
9.1 CSV format for representation of data parcels
9.2 Cell delimiter
9.3 Line feed character
43 9.4 Space character
9.5 Character encoding
10 Conformance to implementation for the IEC CDD
Figure 38 – Example of how to escape the line feed characters
44 Table 2 – POM conformance classes
45 Annex A (normative) Information object registration – Document identification
46 Annex B (informative) Examples of pattern constraints for attributes
Table B.1 – Examples of pattern constraints for attributes (1 of 3)
49 Annex C (informative) Examples for attribute values
50 Table C.1 – Examples of attribute values (1 of 3)
53 Annex D (informative) Sample data
54 Annex E (informative) Parcelling tools
55 Bibliography
BSI PD IEC/TS 62656-2:2013
$198.66