1. GlencoIS – Interoperability through Reference Data ISO15926 Reference Data Some Template Ref Data Issues (Relevant to coordinating JORD take-up) PCA / FIATECH Modelling SIG 16 th Dec 2010 Ian Glendinning ian@glencois.com GlencoIS (Information Services) Ltdian@glencois.com Realizing Open Information Interoperability – ROI 2

2. GlencoIS – Interoperability through Reference Data Some JORD Technical Issues JORD aims to support, coordinate & validate that (as a minimum) ; All compliant use of ISO15926 actually uses valid Ref Data. All compliant use of ISO15926 actually uses valid Template Signatures. So enhanced RDS created by JORD needs to fix; A number of publishing and uploading technology issues with people actually using RDS (triple-stores, URI’s, namespaces, ID-Generation, Sandboxes, Part6 Meta-data implementation, XML, OWL … others ?) A number of implementation-technology-neutral content modelling issues inconsistent with usage procedures being coordinated and business uses that need to be supported (for current projects). Today – examples of the latter modelling issues. Later – the processes by which similar issues will be handled in JORD and – the technical resources to implement technology fixes

3. GlencoIS – Interoperability through Reference Data Example Template Signature Issues Compound Templates – templates whose roles are templates. (So that we can use templates as intended to assemble, classify, specialize, organize, arrange other templates.) Example – information sets comprising multiple property attribute templates. Eg “Process Data” subset in a datasheet / or even an OIM, comprising several properties / indirect properties, but with common identity for engineering business information management purposes. Example – core application or engineering geometric object comprising assemblies and specializations of base / abstract Part 3 geometric objects. Issue – Needed, but not supported directly by Part 7 FOL Identification / Naming – context for uniqueness and language. Clearly needed, but no agreed templates / signatures yet. Multiple Issues … unique library naming convention …. name strings organized according to language, BUT it is the naming relation that declares the use in a language context (strings are not unique to any one language). Others from previous Modelling SIG’s (eg Frederick) / iRING / IDS-ADI Projects / Proteus / Inst-SIG / Geom-SIG / IOHN / EqHub / Onno … ?

4. GlencoIS – Interoperability through Reference Data Aside – NB «Core» Reference Data Core Classes & Templates Standard Classes & Templates Data Model (Base Classes & Templates) Manufactured & Application- Specific Classes & Templates Data Model (Base Classes & Templates) Application-Specific Classes inc Templates > Simple technical compliance of any valid RDL Items. Bottom-Up Content Development >>> ( Any new industry / business areas / uses ) Compliance of valid RDL Items constrained by needs of industrial standardization. (Content management hierarchies, SIG’s, etc.) P4 (initial) / WIP Content Implemented in P9 (SPARQL Facade) Represented in P8 (RDF/OWL)

5. GlencoIS – Interoperability through Reference Data ID’s & Triples / Relationships & Mappings ID’s (URI’s) are fundamental to the Reference Data architecture and Fundamentally all mappings and all relationships are Triples. ID#1 (URI)Relationship ID (URI)ID#2 (URI) (URI) ”MyPump101” (Classification relationship URI) (RDL Class URI) Centrifugal Pump (URI) ” Центробежный насос” (?) (Identification relationship URI) (RDL Class URI) Centrifugal Pump (URI) ”MyCatalogueXYZPumpType” (Specialization relationship URI) (RDL Class URI) Centrifugal Pump These are indicative only. In practice these are ”proto-templates” in Part 7 terms (one for each Part 2 relationship entity). Everything else is built from these.

6. GlencoIS – Interoperability through Reference Data Language – Victor’s Proposal Thing Named Thing ES “Именованный объект” CoIdent representedpattern CoCoIdent Russian Thing Name Representation Class ISO 15926-4 CLASS http://rdl.rdlfacade.org/data#R70635856 237 class_of_represented Language Russian Name for Thing Class class_of_pattern Language Russian Language Language NATURAL LANGUAGE http://rdl.rdlfacade.org/data#R8453962037 7 CoCoIdent NAME REFERENCE http://rdl.rdlfacade.org/ data#R39627084634 http://rdl.rdlfacade.org/ data#R39627084634

7. GlencoIS – Interoperability through Reference Data Ian’s Response Thing Named Thing ES “Именованный объект” CoIdent representedpattern CoCoIdent Russian Thing Name Representation Class ISO 15926-4 CLASS http://rdl.rdlfacade.org/data#R70635856 237 class_of_represented Language Russian Name for Thing Class class_of_pattern Language Russian Language Language NATURAL LANGUAGE http://rdl.rdlfacade.org/data#R8453962037 7 CoCoIdent NAME REFERENCE http://rdl.rdlfacade.org/ data#R39627084634 http://rdl.rdlfacade.org/ data#R39627084634 This relation IS the Russian Language Naming relation These are about organization of natural language strings in the library. NB identical strings can be homonyms in one or more language It is this relation that says “I am using the X language to name this thing” NOT the classification of the string itself.

8. GlencoIS – Interoperability through Reference Data The “Language Naming” Signature (Actually two templates & signatures, depending whether it is the class or the member you are naming) Thing Named Thing ES “Именованный объект” CoIdent representedpattern CoCoIdent Russian Thing Name Representation Class ISO 15926-4 CLASS http://rdl.rdlfacade.org/data#R70635856 237 class_of_represented Name String Russian Name for Thing Class class_of_pattern Language Russian Language Language NATURAL LANGUAGE http://rdl.rdlfacade.org/data#R8453962037 7 CoCoIdent NAME REFERENCE http://rdl.rdlfacade.org/ data#R39627084634 http://rdl.rdlfacade.org/ data#R39627084634 This relation IS the Russian Language Name-Assignment relation

9. GlencoIS – Interoperability through Reference Data