We at TechInvestLab have experience of introducing of ISO 15926 to general public (not professional ontologists) in self-education mode. It required very special reading sequence (in Russian this is in more details at http://dot15926.livejournal.com/27293.html):   

 I. Theory for general understanding.   

 1. Read a book of Chris Partridge “Business Objects: Re-Engineering for Re-Use” http://www.borosolutions.co.uk/research/content/files/books/BusObj-Printed-20050531-with-watermark.pdf/at_download/file (while this book has no references to ISO 15926 or any other language or software or standard). This is mandatory reading for all beginners. In Russian we have video about 4D vs 3D ontology that we recommend as addition for 7th Chapter of this book. Try to find something equal to support 4D understanding (it is very tricky).   

 2. Only then you should read “An Introduction to ISO 15926” issued by FIATECH consortium — http://fiatech.org/images/stories/techprojects/project_deliverables/iso-intro-ver1.pdf

3. Then you should read first part of book of Matthew West “Developing High Quality Data Models”: http://www.amazon.com/Developing-High-Quality-Data-Models/dp/0123751063 (second part of this book is HQDM specific data model, you need not to read it. First part is mandatory).  

4. Read thesis of Andries van Renssen “Gellish. A Generic Extensible Ontological Language”: http://repository.tudelft.nl/assets/uuid:de26132b-6f03-41b9-b882-c74b7e34a07d/its_renssen_20050914.pdf This is also not about ISO 15926 and not even 4D but there are many interesting things about relations and table format. Take ideas about table data representation and usage of ontology in engineering.  Take no ontology from this book (except very good set of relations).   

This is about 1200 pages (about 4 month for 4 hours/day or reading).   

Many people stops here. This is general education in engineering approach to ontology.   

II. Now you are ready to mastering knowledge of ISO 15926 as a standard.   

1. Read ISO 15926 Part 2 (this is upper ontology, 201 type of entities). 241 pages.   

2. Read 47 pages of draft of ISO 15926 Part 6 (RDL management).

3. Take  .15926 Editor (freeware, http://techinvestlab.ru/dot15926Editor) . Have fun browsing PCA RDL (about 2.7mln triples for near 50000 concepts like “centrifugal pump” — you can prefer do it online from SPARQL endpoint or load from OWL file that take about 1 minute 20 second on a notebook with our Editor). Spend not too much time for this. This is like reading Encyclopedia, only to get understanding.    

4. Read ISO 15926 Part 7 (templates in logic language Plan 9), 126 pages and Part 8 (templates in OWL). 

5. Now try to see examples from http://15926.info/ — now you have a chance to understand it. We have several examples of engineering data in .15926 Editor samples directory. See also sample diagrams on http://techinvestlab.ru/iso15926_sample_diagrams. Up to this moment you will find multiple examples from different sources.

6. Read “ISO 15926 outside” methodology for reference data engineering: http://techinvestlab.ru/files/RefDataEng/RefDataEngr_ver_2_25feb11.doc — 18 pages.    

7. Subscribe for community “ISO 15926” in LinkedIn and read discussions. Read http://iringug.org (implementations hub) and news at http://iringtoday.com.   

This is about 500 pages and many diagrams to understand. 2 month.

Most of people stops here. If you are not scared, proceed to real thing.   

III. Now you are ready to do you first ISO 15926 systems federation project.

Join somebody with ISO 15926 experience to supervise you modeling activity and tool chain mastering (e.g. TechInvestLab with .15926 Platform tool chain).

Welcome to the ontology-based systems federation community of practice! You have “yellow belt” qualification at this point.

After 3 year you will have “black belt” master level and can participate at Modeling Meeting of POCSCaesar Association.

This is valid for general public while for more experienced developers this self-education sequence can be passed really fast!

TechInvestLab.ru made release of .15926 Editor v1.0 as a freeware. The Editor is intended to become for ISO 15926 data what Protégé became for OWL data – a primary free tool for data exploration and creation. It can be downloaded here: http://techinvestlab.ru/dot15926Editor

.15926 Editor is one of realizations of iRING architecture (http://iringtoday.com/). This is first ISO 15926 software that  included voluntary JORD requirements Compliance Report in its documentation.

With .15926 Editor v1.0 you can
•    Browse ISO 15926-2 upper ontology and use it in three different namespaces:  JORD/PCA RDL, legacy RDS/WIP or ISO 15926-8.
•    Search and navigate all public ISO 15926 SPARQL-endpoints,
… or any other ISO 15926 endpoint you like, with authorization capabilities,
… including search for legacy RDS/WIP identifiers.
•    Search, navigate and edit reference data files distributed publicly, including ISO 15926-4, JORD/PCA RDL and ISO 15926-8 templates,
… or any other ISO 15926 files you like.
•    Create from scratch your own reference classes and templates (or project data including template instances),
… in forms ready for file exchange or upload to triple store,
… generating URI in your namespaces using UUID compliant with RFC 4122 / ITU-T X.667 / ISO/IEC 9834-8,
•    Build complex data project from local files and endpoints, bringing reference data, template definitions and project data together for integrated navigation and verification, customizing namespaces and meta-data attributes.
•    Design and run intricate semantic queries or whole data mining and data verification algorithms for ISO 15926 data,
… using the power of Python general purpose programming language through full-featured REPL environment,
… and accessing APIs of various .15926 Platform components to read, analyze and change reference and project data.
•    Visualize broad set of predefined data patterns and search for patterns in your data.
•    Make conversion of reference and project data from TabLan.15926 data description tables (.xlsx) to ISO 15926.
•    Import reference data from JSON files created by engineering catalog application (third party).
•    Explore (with somewhat limited capabilities) large datasets of non ISO 15926 data,
… OpenCYC knowledge base, for example.

This is how .15926 Editor recognize and show ontology patterns in JORD reference data library:

Most of the contemporary ontology-related applications suppose point-and-click interface, but .15926 Editor combine easy multi-window mouse clicking with the power of interactive text-based Python query exploration and creation of ISO 15926 data. Assume you have a need to send an email to a colleague with designations of all reference data entities on JORD RDL which are instances of Scale and have “celsius” in their labels. It can be done with this script in Python console of .15926 Editor:

outfile = file(‘scales_celsius.txt’, ‘w’)

scales=find(type=part2.Scale, label=icontains(‘celsius’))

for entity in scales:

    designations=find(id=entity, hasDesignation=out)

    for property in designations:

       outfile.write(entity+’ : ‘+property+’\n’)


Results will be in scales_celsius.txt file in the main program folder.

Or let’s analyze patterns of data in RDL to identify all possible instances of the p7tpl template ClassOfCauseOfBeginningOfClassOfIndividual and form list of possible signatures in a separate file. Run the following script:

outfile = file(‘COCOBOCOI_sign.txt’, ‘w’)

begun=find(type=part2.ClassOfCauseOfBeginningOfClassOfIndividual, hasClassOfBegun=out)

for elem1 in begun:

    causer=find(hasClassOfBegun=elem1, hasClassOfCauser=out)

    for elem2 in causer:



and look for COCOBOCOI_sign.txt  file in the main program folder.

The Editor as an example of .15926 Platform application is not designed to support any particular data integration workflow for specific engineering life cycle processes. Specific applications that take care of diversity of specific CAD/CAM/PLM/ERP/EAM/CRM/etc. data format and support needed format-specific Readers and Writers should be built on .15926 Platform with usage of it semantic graph Builder API (for Readers) and semantic graph Scanner API (for Scanners) that supported by the Platform. Mapping components are integrated in .15926 Platform environment as Python modules, with possibility to access external or internal pattern mapping descriptions and direct access to APIs of source/target data bases.

Russian and English language community for .15926 discussions now have more than 100 subscribers: http://dot15926.livejournal.com/

Slides of my presentation on Ontology Summit 2012 session on System Integration and Federation (http://ontolog.cim3.net/cgi-bin/wiki.pl?ConferenceCall_2012_03_01):

Actually I was co-chaired the session, along with Cory Casanave. Me and Cory also champions of the Summit System Integration and Federation Track. This was very interesting experience.

Ontology Summit is an organized thinking machine that work from January to April every year to brain-storm one of a topic of interest for ontology engineering community. Ontology Summit producing a special artifact: Communique with results of the brain-storming and discussion. One more outcome is synchronization of understanding of the topic of interest by ontology engineering community, but this outcome is intangible.

Summit Communique will be endorsed by Summit participants and broader community and then will be open published on a website (past Communiques: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit) and in “Applied Ontology” journal, the premier journal in the field of Formal Ontology for information systems. Communique has co-lead Editors and track champions as editors. Producing of Communique as a final stage of year’s Summit is a main task of Summit participants meeting in person for 2 days long “Workshop and Symposium” in USA (at a NIST place). Workshop and Symposium at NIST place has possibility of virtual presence (it is “virtureal”) of those participants that cannot be present in person. This symposium has co-chairs. Ontology Summit has general co-chairs.

Year’s topic is decomposed to 3-7 facets/aspects that intensively discussed separately. Such a facet is called “track”. Summit tracks discussion is facilitated by Track Champions and have wiki page “Track Synthesis” as a main outcome artifact. Track Synthesis page (for our Track this is http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012_SystemsFederationIntegration_Synthesis)  is edited by track champions on a basis of:

Track champions also serve as co-editors for Communique that will comprise of major ideas of Track Synthesis pages of all Tracks.

General Summit co-chairs is responsible for thematic integrity of all Tracks and Workshop and Symposia to provide needed scrutiny to Summit topic.

Every track have one or more online 2-hours Sessions that is comprised of 3-6 short slide presentations on track topics, group chat and Q&A session with a panel of presenters. Audio, slides, chat transcripts and survey results will be published and used by track champions to prepare Track Synthesis. Every separate Session usually have two co-chairs. Session co-chairs are responsible for inviting leading experts on relevant areas relevant to the session topic as speakers, and facilitation of chat and moderate discussion among the panelists and other session participants.

Overall process leads by Organizing Committee that comprised of track champions, workshop and symposium co-chairs, lead co-editors, general Summit co-chairs. Also Organizing Committee has representatives of current six Ontology Summit organizers (Ontolog, NIST, NCOR, NCBO, IAOA, NCO_NITRD) and PR champion.

All the logistics and overall organizing work in “virtual” part of Summit (i.e. tracks and virtual part of Workshop and Symposium) is coordinated by a designate from the Ontolog Forum that acting on behalf and for Organizing Committee. The same organization/logistics function for real part of Workshop and Symposium is similarly provided by a coordinator designated by NIST.

Thus ideas on current Summit topic flow from

  • Ontology Summit discussion list to
  • Track Sessions presentations, panel discussion and chat; surveys and polls, Delphi study to
  • Track Input pages (for all Sessions and surveys) to
  • Track Synthesis pages to
  • Workshop and Symposia final discussions to
  • publishable Communique of a Summit.

My slides for second session of systems engineering track of Ontology Summit 2012 (it was published as additional slides here — http://ontolog.cim3.net/cgi-bin/wiki.pl?ConferenceCall_2012_02_02 ):

My remark in this session was necessity to add methodologists (situational method engieers) to systems engineers and ontologists. Ontologists are not methodologists and thus need professional help to understand what is systems engieering method. We heavily use situational method engineering standards (e.g. ISO 24744) to understand what is systems engineering as a method of work. And after that we can start ontology work with systems engineering.

Today I deliver a talk “Ontology Engineering for Systems Engineering” at one of the session of Ontology Summit — http://ontolog.cim3.net/cgi-bin/wiki.pl?ConferenceCall_2012_01_26

My slides:

This talk was about 20 minutes in English, but yesterday I presented the same topic at INCOSE Russian Chapter meeting about 3 hours (in Russian, with video: http://incose-ru.livejournal.com/32094.html).

The feature and usability release 0.87 at http://techinvestlab.ru/files/dot15926Editor/dot15926Editor087.rar Some features are really nice, please update!

New in version 0.87:
* Capability to add and edit template instances in preset Tablan.
* Correct visualization of Same As data attribute.
* Data source indication for data items viewed.
* Reload of entities for interrupted SPARQL request.
* Process interruption with window closure (mistake correction capability).
* Capability to access password protected SPARQL endpoints.
* URI dereferencing and web access for data model items and all data items.
* Some usability tips and tricks in documentation.

Next we plan feature release with template-based search to have possibility extract sub-graph from stored semantic network (we call it “scanner” because search engine will scan overall semantic network with template-based pattern matching).

Then we will add support of reporting (rendering, writing) this searched sub-graph in different formats (ISO 15926 part 8, .xls table, HTML, diagrams in GraphViz, etc.).

Next we will support OIMs and reference data library maintenance.

Then we open source code (we hope that to up to that moment architecture of .15926 programming platform for different plug-ins will be stable). This will be final release of .15926 version 1.0

Next really big thing will be support of DSLs with language workbench (projectional technology). This ISO 15926 ontology-based language workbench will be .15926 version 2.0.

The bugfix and usability release of .15926 Editor (version 0.83) can be downloaded from http://techinvestlab.ru/dot15926Editor

Some bugs were quite severe, including incorrect namespace identification. Please update!

New features: Part 2 membership rules and URI resolvability check.

Thank you all for valuable feedback! We expect more usability features in January 2012. Then we will move to development of template-based search and OIM support.