OIDDI Open Interoperable Domain Dictionary Initiative

Transcription

1 OIDDI Open Interoperable Domain Dictionary Initiative Addie Dijkstra, Donald Radley Based on a presentation held at the OIDDI meeting in Bath (UK) July 2004 by Wolfgang Wilkes, Guy Pierra ISO TC184 SC4 WG2 3(Eindhoven/Radley)7

2 Outline 1. Introduction 2. OIDDI goals 3. OIDDI approach 4. Next steps 3(Eindhoven/Radely)7 page 2

3 B2B Commerce / engineering Buying, ordering, inquiring about something need to specify the what : Kind of product? Characteristic properties? + to agree on terms I need a can of hexagonal machine screw: total length? 20 threaded length? 10 diameter? 5 coating? teflon 3(Eindhoven/Radely)7 page 3

4 Switching to e-commerce / e-engineering Computer are used on one or both sides: To formally define the what kind of product characteristic properties product Data Element Type dictionary To specify computer-sensible identifiers and exchange formats information models & publication formats To specify business processes business protocols e-commerce requires three huge pieces of work: (1) Product DET dictionaries (2) Structure & Formats (3) Business protocols Product experts Information modelers Business experts 3(Eindhoven/Radely)7 page 4

5 Definitions Dictionary IEC Component Data Dictionary A hierarchical classification of components in a classification tree A set of characteristic properties (DETs) associated with each class that fully describe components belonging to a class. Within the classification hierarchy, sub-classes inherit properties from those classes above them in the tree Where relevant, conditions for which the property values are valid Or: a set of characteristic properties (DETs) associated with a set of classes that fully describe items belonging to a class 3(Eindhoven/Radely)7 page 5

6 Definitions Library A set of items including associated specifying data according to the applicable DETs as specified in the dictionary of DETs Synonym: catalogue DET: Data Element Type 3(Eindhoven/Radely)7 page 6

7 Many Dictionaries Existing epdc has identified at least 37 different dictionaries (08/2003) - UNSPSC (H) - ecl@ss (H) - HS (Harmonized System - H) - CPV (European Procurement - H) - CPC (UN Classif. H) - NATO (Military Procurement H) - NAICS (North American H) - NACE (Economic Activities in the EU H) - BEC (Broad Econ. Cat. H) - eotd (ECCMA H) - CCIO (Commodities by Ind. Orig. - H) - COICOP (Ind. Consumption H) - CN (Combined Nomenclature H) - ISIC (Econom. Act. H) - PRODCOM (Products of the EC H) - CPA (Class. Prod. by Activity H) - NIGP (Periscope H) - RUS (Requisite H) - GCI (Retail V) - PIDX (Oil V) - RNTD (Electronic comp. V) - IEC (Electrical, Electronic V) - GHS (Hazardeous Chem. V) - Sanitary + Heating (V) - RAPID (Agrochemicals V) - SEMI (Electronics V) - CAMPUS (Plastics V) - ICD-10 (Medical V) - ATC (Anatomical Therapeutic V) - PHC (Pharmaceutical V) - Proficlass (Construction - V) - SNITEM (Medical Technology V) - etc and they are sure there are many others 3(Eindhoven/Radely)7 page 7

8 What? Goals of OIDDI Separation of concerns: ensure that any dictionary can be used in any business process Interoperability of product / property dictionaries: How? ensure that several dictionaries can be used together Reaching consensus on the same information model: ISO/IEC dictionary interoperability: same software tools, easy mapping (some overlap acceptable!), joint use of several dictionaries Ensuring that interoperable dictionaries are open (freely downloadable) no more economic interest to duplicate the work! Defining rules and mechanism for inter-dictionary importation reusing is easier than defining again 3(Eindhoven/Radely)7 page 8

9 OIDDI Assumptions No organization can develop a universal dictionary Different dictionaries for different domains No company belongs to one predefined particular domain Need to use (uniformly) several domain dictionaries Usage of dictionaries similar/identical across industrial sectors Software tools should be usable across all sectors 3(Eindhoven/Radely)7 page 9

10 Vision component part number One (a few) high level classification hierarchy Without properties electric comp. input voltage... Mechanical comp. Hardness... Software comp. language One (a few) generic dictionary With generic properties 3 - A number of interoperable domain dictionaries 4 - Inter-dictionary references to avoid duplication Usage: uniform reference => same identification mechanism uniform display => similar model architecture uniform recording => common exchange format for exchange of dictionary content (meta-data) 3(Eindhoven/Radely)7 page 10

11 Approach 1. Build association 2. Membership includes commitment to OIDDI prescriptions 3. Make all important dictionary providers to members 4. Provide tools & conformance tests 5. Encourage interoperability and harmonisation projects 3(Eindhoven/Radely)7 page 11

12 Initial Plans for Association Build steering committee Committee members are elected by OIDDI members Task: Support and supervise the activities of OIDDI Chairmanship Initial phase: Chairman of IEC SC3D and convener of ISO TC184 SC4 WG2 Afterwards: consensual designation by members Membership is free of charge Financial support Volunteering work by members Seek for public funding (e.g. from CEN / EU) 3(Eindhoven/Radely)7 page 12

13 Approach 1. Build association 2. Membership includes commitment to OIDDI prescriptions 3. Make all important dictionary providers to members 4. Provide tools & conformance tests 5. Encourage interoperability and harmonisation projects 3(Eindhoven/Radely)7 page 13

14 OIDDI Prescriptions Identification of dictionary providers Identification of dictionary elements by using the provider identification Common data model for all dictionaries Common ISO/IEC : PLIB ISO13584 / IEC Common exchange formats for exchange of dictionaries (meta-data) (e.g. ISO , XML schema) Free availability of dictionaries 3(Eindhoven/Radely)7 page 14

15 OIDDI referencing mechanism 1. source identification Organization identification according to ISO/IEC :1998 => generic mechanism for information source identification: ISO/IEC :1998 Data element name Description Obligation Data type Maximum length International Code Designator (ICD) Identification of an organization identification scheme Mandatory Integer 4 Organization Identifier (OI) Identification of an organization within an identification scheme Mandatory String 35 3(Eindhoven/Radely)7 page 15

16 Source identification examples ICD Code 0060 Name of code Data Universal Numbering System (DUNS Number) Registration authority Dun & Bradstreet 0112 Registration of Standardization Organization ISO The source identification for the IEC dictionary: ICD / OI / / / Dictionary Identifier = 0112/2///61360_4_1 The dictionary identifier is an extension to ISO/IEC (Eindhoven/Radely)7 page 16

17 OIDDI referencing mechanism 2. Class & property identification Identification Class 0112/2///61630_4_1 AAA IEC root class Data element type (Property) 0112/2///61630_4_1 AAA AAF factor of permeability of magnetic material at specified frequency... Data element types from different sources may be merged 3(Eindhoven/Radely)7 page 17

18 Example of Common Information Model support_resource_schema.identifier (DER) dic_identifier dictionary_definition (INV) referenced_by S[0:1] 1, 2 (2) (ABS) basic_semantic_unit code version support_resource_schema.identifier (INV) definition S[0,1] *code_type *version_type 1, 10 (6) 1, 4 (1) 2, 6 (ABS) dictionary_element (ABS) content_item (ABS) supplier_related_bsu (DER) *absolute_id 1 1, 4 version_type (DER) (RT) version name_scope 1, 15 (2, 2, 2, 3, 3, 6) 2, 12 (ABS) class 1, 18 (6) supplier_bsu 1, 3 (2) (RT) code property_bsu (INV) describes_classes S[0:?] (DER) *absolute_id (ABS) class_related_bsu *supplier_code_ type (INV) added_visible_properties S[0:?] (DER) known_visible_ properties S[0:?] defined_by class_bsu (RT) code (DER) *absolute_id *class_code_type support_resource_schema. identifier (INV) subclasses S[0:?] 2, 12, (ABS) class 1, 13 (2, 2, 4) 1, 16 (2, 4) (RT) code *data_type_code_type name_scope (INV) added_visible_ data_types S[0:?] (DER) known_visible_data_types S[0:?] data_type_bsu (DER) *absolute_id (INV) defining_classes S[0:1] support_resource_schema. identifier 2, 12, (ABS) class 3(Eindhoven/Radely)7 page 18

19 Approach 1. Build association 2. Membership includes commitment to OIDDI prescriptions 3. Make all important dictionary providers members 4. Provide tools & conformance tests 5. Encourage interoperability and harmonisation projects 3(Eindhoven/Radely)7 page 19

20 Current supporters ISO TC184 SC4 IEC SC3D RosettaNet eclass UCC (UNSPSC) ECALS / JEITA JEMIMA ECCMA / NATO USPI/NL epdc joint CEN Workshop under discussion 3(Eindhoven/Radely)7 page 20

21 Approach 1. Build association 2. Membership includes commitment to OIDDI prescriptions 3. Make all important dictionary providers to members 4. Provide tools & conformance tests 5. Encourage interoperability and harmonisation projects 3(Eindhoven/Radely)7 page 21

22 Provide tools & conformance tests Tools Dictionary browsers and editors Exchange tools for different formats XML Tabular form Step File Format (ISO10303/21) Compliance Certification Service to be set up Definition of compliance levels Development of tool support 3(Eindhoven/Radely)7 page 22

23 Approach 1. Build association 2. Membership includes signature to OIDDI prescriptions 3. Make all important dictionary providers to members 4. Provide tools & conformance tests 5. Encourage interoperability and harmonisation projects 3(Eindhoven/Radely)7 page 23

24 Interoperability and Harmonisation Projects Goals: Encourage the harmonisation of dictionaries Support the definition of mappings Support the introduction of inter-dictionary references Example: IEC TC93 WG6: Joint project between RosettaNet, ECALS, IEC61360 This project has demonstrated the difficulty of interoperability when dictionaries are not aligned classification structures differ essential data element types cannot be mapped due to omissions 3(Eindhoven/Radely)7 page 24

25 Next steps Consolidation of the expectations and production of a vision paper Licence policy: Collect information from dictionary providers on their views on the usage scenarios for dictionaries. Creation of a document which outlines the goals and the requirements of OIDDI in a form that can be signed by dictionary providers (without getting legal problems). Installation of OIDDI as a legal organisation and acquiring initial funding. 3(Eindhoven/Radely)7 page 25