.15926 Editor v1.0 released

October 1, 2012

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/


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: