.15926 Editor v.1.2 released!

February 22, 2013

Yesterday we (TechInvestLab) released .15926 Editor version 1.2. We position it as software environment for ISO 15926 that is like Protege for ordinary OWL ontologies. You may download it here (it is freeware): http://techinvestlab.ru/dot15926Editor

Main feature of this version is user-defined patterns. You can define your own patterns which are now multi-role and may have several options, and use them in search queries. Our test “dictionary” implementation supports patterns for many possible areas of use: template expansion/contraction, pattern modelling, pattern mapping, etc. Predefined pattern set and documentation contain examples of patterns from JORD mapping methodology and from IIP project of iRING User Group. This is how you can define e.g. “classification” pattern:

patterns.append({
'name': 'Classification',
'signature': {'classifier': 'is classified by', 'classified': 'is classifier of',
'classofclassifier': 'is class of member', 'classofmember': 'is class of classifier'},
'options': [ 
    {'type': p7tpl.ClassificationOfIndividual,          'classifier': 'hasClass',           'classified': 'hasIndividual'},
    {'type': p7tpl.ClassificationOfClass,               'classifier': 'hasClassClassifier', 'classified': 'hasClass'},
    {'type': p7tpl.ClassificationOfRelationship,        'classifier': 'hasRelation',        'classified': 'hasPair'},
    {'type': p7tpl.ClassificationOfClassOfIndividual,   'classifier': 'hasClassClassifier', 'classified': 'hasClass'},
    {'type': p7tpl.ClassificationOfClassOfRelationship, 'classifier': 'hasClassClassifier', 'classified': 'hasClass'},
    {'type': part2.ClassOfClassification, 'classofmember': 'hasClassOfClassified', 'classofclassifier': 'hasClassOfClassifier'},
    {'type': p7tpl.ClassOfClassification, 'classofmember': 'hasClassOfClassified', 'classofclassifier': 'hasClassOfClassifier'},

    {'name':       'ClassificationTemplate',    
    'type':        p7tpl.Classification,
                        'classifier':  'hasClassifier',
                        'classified':  'hasClassified',
                        'expansion':       'ClassificationTemplAxiom'},

                        {'name'  : 'ClassificationTemplAxiom',
        'type' : part2.Classification, 
        'classifier' : 'hasClassifier', 
        'classified' : 'hasClassified',}
        ]
})

Here is a screenshot of “out of the box” example patterns visualisation for pump from JORD RDL:

patternexample

We now have new level of compliance to ISO 15926-8 requirements for RDF/OWL template format. But we still can read multiple non-compiant data, and this reading not constrained only to OWL files. Open-source extension for import of template definitions from Excel table used to populate iRING Tools software is included. And you can add extensions for you favorite data formats, this is only easier since previous version (we have more in our API for extensions development).

Also registration and creation of custom object properties for non-standard representation of relationships is allowed and their visualization is improved (the Editor can now be used as a
general-purpose RDF/XML editing software if need arises, with allowing search and editing by all object and data properties at RDF level). Find you “ordinary OWL ontology” in  http://swoogle.umbc.edu/ and open it with .15926 Editor! Or open biology ontology from http://obofoundry.org in next pane to JORD RDL to work on something like “heart properties of a pump” or vice versa 🙂

We plan to use this version in ontology hackaton/clinic during Ontology Summit 2013. We are registered for participation (http://ontolog.cim3.net/file/work/OntologySummit2013/2013-02-21_OntologySummit2013_Synthesis-I/OntologySummit2013_hackathon-clinics-approach–MikeDean-PeterYim_20130221.pdf) with our russian-speaking community (announce in Russian: http://dot15926.livejournal.com/40280.html).

In the release version 1.2 we closed 53 issues and there was not so many bugs among them. We implemented many new features that not mentioned in this post.

We actively used GitHub.com for software development, not only for configuration management with Git but also for issue tracking with web-based issue tracker of GitHub. We have distributed software development team that resides in Moscow and Saint-Petersburg. Now we want to add in next version 1.3 of our .15926 Editor a set of GitHub-enabled collaborative ontology engineering features (commit to Git, version control with diff function for ontology, issue tracking).

Advertisement

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 )

Connecting to %s

%d bloggers like this: