glencois – interoperability through reference data iso15926 reference data some template ref data...

GlencoIS – Interoperability through Reference Data

ISO15926 Reference DataSome Template Ref Data Issues

(Relevant to coordinating JORD take-up)

PCA / FIATECH Modelling SIG 16th Dec 2010

Ian Glendinning [email protected]

GlencoIS (Information Services) Ltd

Realizing Open Information Interoperability – ROI2

mailto:[email protected]


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 JORDand – the technical resources to implement technology fixes


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 … ?


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-SpecificClasses inc Templates

<< P 2, 3 & 7 Only >>

Simpletechnicalcomplianceof any validRDL Items.

Bottom-Up Content Development Bottom-Up Content Development

<<<< Unconstrained Evolution >>>>(Any new industry / business areas / uses)

Complianceof valid RDL Items constrained by needs of industrial standardization.(Content management hierarchies, SIG’s, etc.)

P4 (initial) / WIP Content

Implem

ented in P9 (SPA

RQ

L F

acade)

Represented in P

8 (RD

F/O

WL

)


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)

<MyObject> (URI)

”MyPump101”

<is a> (Classification relationship URI)

<RDL Class>(RDL Class URI)Centrifugal Pump

<My String or Symbol> (URI)

” Центробежный насос” (?)

<is a name for> (Identification relationship URI)


<MyClass> (URI)

”MyCatalogueXYZPumpType”

<is a subClass of> (Specialization relationship URI)


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.


Language – Victor’s Proposal

Thing

Named Thing

ES

“Именованный объект”

CoIdent

represented pattern

CoCoIdent

Russian Thing Name Representation

Class

ISO 15926-4 CLASShttp://rdl.rdlfacade.org/data#R70635856237

class_of_represented

Language

Russian Name for Thing Class

class_of_pattern

Language

Russian Language

Language

NATURAL LANGUAGEhttp://rdl.rdlfacade.org/data#R84539620377

CoCoIdent

NAME REFERENCE

http://rdl.rdlfacade.org/data#R39627084634

http://rdl.rdlfacade.org/%0Bdata#R39627084634



Ian’s Response

Thing

Named Thing

ES


CoIdent

represented pattern

CoCoIdent


Class



Language


class_of_pattern

Language

Russian Language

Language


CoCoIdent

NAME REFERENCE


This relationIS 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.



GlencoIS – Interoperability through Reference DataThe “Language Naming” Signature(Actually two templates & signatures, depending whether it is the class or the member you are naming)

Thing

Named Thing

ES


CoIdent

represented pattern

CoCoIdent


Class



Name String


class_of_pattern

Language

Russian Language

Language


CoCoIdent

NAME REFERENCE


This relationIS the Russian LanguageName-Assignment relation



glencois – interoperability through reference data iso15926 reference data some template ref data...

Documents