From OntologPSMW

Jump to: navigation, search
[ ]

This is one of the "OntologySummit2013_Hackathon_Clinics" Projects ...     (1)

Contents

Project (HC-06): ISO 15926 Reference Data Validation     (2)

Project Co-champions: Victor Agroskin     (2A)

Event Date / Time: (Day-1) Sat 2013.03.30 (possibly also Sun 2013.03.31) ... see: [ details]     (2B)

Archived work output can be found here     (2C)

Participant Volunteers:     (2D)

Add your name below, along with any time constraints or other participation-related comments. Thank you!     (2E)

see: Work Plans     (2G)

Abstract     (2H)

This ontology clinic is aimed at the evaluation of publicly available ISO 15926 reference data, viewing it as an ontology for the engineering domain. We will look for compliance to upper ontology constraints, diagnose problems in reference data, evaluate ease of understanding and use of existing data, and make suggestions for ontology improvement. Another goal is to apply formal ontology quality metrics for data in question.     (2H1)

The effort will develop rules and algorithms to support generic verification tests, and also attempt to invent and implement specialized checks and quality metrics for ISO 15926 reference data.     (2H2)

see: [ [ Project document] ]     (2H3)

Ontology involved     (2I)

The ISO 15926 is a standard for engineering data integration, sharing, exchange, and hand-over. The standard defines a generic data model as an upper ontology for an engineering domain. Extensive Reference Data Libraries (ontology data) for process plants are developed by community of users, which includes equipment manufacturers, engineering companies and owner/operator companies in oil and gas, nuclear power, petrochemical industries, and others. Standard development and application is jointly managed as JORD project by two industry associations: POSC Caesar Association and FIATECH.     (2I1)

Upper ontology of the ISO 15926 is publicly available as an OWL representation of ISO 15926-2 at:     (2I2)

JORD Reference Data Library is available as a reference data service:     (2I4)

A snapshot file with full content of an endpoint is available for download at:     (2I7)

Various resources for study of ISO 15926 are available from     (2I9)

Evaluate publicly available ISO 15926 reference data:     (2J1)

  • compliance to the best practices of ontology engineering;     (2J2)
  • compliance to logical model and upper ontology constraints;     (2J3)
  • diagnose problems in reference data;     (2J4)
  • make suggestions for data improvement;     (2J5)
  • evaluate ease of access, understanding and use of existing ontology data.     (2J6)

We'd also like to attempt calculation of ontology quality metrics for ISO 15926 upper ontology and Reference Data Library in various software environments or by standalone tools. We can use existing methodologies (like OntoClean, OQuaRE or OntoQA) or brainstorm for new metrics.     (2J7)

Deliverables     (2K)

We are panning to get:     (2K1)

  • the list of "hard" problems (errors, inconsistencies, missing data, etc.) in existing JORD Reference Data Library;     (2K2)
  • characterization of any "soft" problems with data identification, availability, understandability, etc.;     (2K3)
  • adopted or new ontology quality metric methodologies for ISO 15926 ontology;     (2K4)
  • ontology quality metrics calculated for JORD Reference Data Library;     (2K5)
  • suggestions for improvement of data consistency and quality in JORD Reference Data Library;     (2K6)
  • algorithms, scripts, software tools proven to be useful for verification and quality assessment of ISO 15926 data, made available to ISO 15926 community.     (2K7)

Project results will be presented 11-14 of April at ISO 15926 round table during 4th annual Systems Engineering Challenges workshop of INCOSE Russian chapter.     (2K8)

Availability of data in OWL, RDF/XML and at a SPARQL endpoint allows the use of both public and proprietary tools in this clinic project. General purpose ontology management and Semantic Web tools can be used along with special purpose tools developed for work with ISO 15926 data (like iRING Tools http://iringug.org/wiki/index.php?title=IRINGTools or .15926 Editor http://techinvestlab.ru/dot15926Editor)     (2L1)

Collaborators     (2M)

Project initiators are TechInvestLab.ru, a Moscow (Russia) based company, developer of the .15926 software environment. Another team of tool developers from Moscow (http://agentlab.blogspot.ru) has also expressed interest in participating.     (2M1)

We are looking for collaborators �� ontology evaluation experts commanding any generic or specialized software tools to work on proposed ISO 15926 datasets. We will welcome software tool developers willing to show use of their instruments for project tasks.     (2M2)

Resources and facility     (2N)

Our own tool .15926 Editor is freely available (http://techinvestlab.ru/dot15926Editor), well documented, is designed for exploratory programming and includes examples of use for data verification. Basic knowledge of the Python programming language will be enough to join us in the project with this tool.     (2N1)

We will be happy to provide office space for real world collaboration in Moscow, well connected to the virtual environment of the Hackathon.     (2N2)


Work Plans     (2O)

from: (email to participants) Victor Agroskin / 2013.03.26     (2O1)

A. Project schedule:     (2O2)

We propose to start on Sat 2013.03.30 at 2:00pm Moscow / 11:00am CET / 10:00 UTC. At this time we'll open communication infrastructure of the project from our Moscow office (we propose Skype for voice and Mikogo http://www.mikogo.com/ for screen sharing). We'll work for some 5-6 hours, after that we can make a break for 1 hour and will be ready to continue work from our homes if team members wish so, or new people from other time zones join us.     (2O3)

Project continuation on Sat 2013.04.06 will be discussed later.     (2O4)

B. General framework:     (2O5)

Our proposal is to do work in short iterations within the loop:     (2O6)

1. Selection of a Test or a Metric (we've to prepare the list before the start of the meeting).     (2O7)

2. Short presentation of a Test or a Metrics from the most competent participant (should be prepared in advance, I think?).     (2O8)

3. Discussion of its application to ISO 15926 upper ontology or reference data, suitable algorithm and tools (software environments) selection. We'll always try to do each Test or Metric in at least two environments - to compare results and get better understanding of tool applicability.     (2O9)

4. Implementation (performed concurrently if several tools/software environments selected).     (2O10)

5. Test on real data, discussion of results.     (2O11)

6. Preliminary documenting of results (errors, inconsistencies, metric values, etc).     (2O12)

7. Go to (1) .     (2O13)

If only one team team takes implementation of some Test or Metric, steps 1-3 can be performed in a loop until all people/teams capable to do implementation have some task assigned.     (2O14)

Final documentation and packaging of results, suggestions and useful code snippets for presentation to ISO 15926 community and to JORD project will be done after the main event. We (TechInvestLab.ru) are ready to do the job.     (2O15)

C. Ontology data sources:     (2O16)

Upper ontology of the ISO 15926 is publicly available as several OWL representations of various aspects of ISO 15926-2 at:     (2O17)

JORD Reference Data Library is available as a reference data service:     (2O25)

the human browser access & query page is http://posccaesar.org/endpoint/     (2O26)

A snapshot file with full content of an endpoint is available for download at:     (2O28)

D. Initial list of problems:     (2O30)

We (TechInvestLab.ru) can suggest several Tests to perform on ISO 15926 upper ontology and/or reference data:     (2O31)

a) Verification of upper ontology (currently distributed between 6 OWL files). This representation is heavily criticised and a new effort to do a standard representation in OWL 2 is currently suggested to ISO. The list of problems detections and suggestions for improvement will be of great value to the community.     (2O32)

b) Reference data compliance to upper ontology. There are many requirements to reference data library content coming from ontology restrictions: abstract classes and disjoint classes, mandatory relationships (properties), membership relations between classes of classes and classes, etc. Simple scripts to find most common mistakes can be found in the documentation to .15926 Editor (section 6.4).     (2O33)

c) Filling gaps in entities and relations. This effort can be based on methods outlined in http://ontolog.cim3.net/file/work/OntologySummit2013/2013-03-07_OntologySummit2013_OntologyEvaluation-IntrinsicAspects-2/OntologySummit2013_debugging_is-a_structure--PatrickLambrix_20130307.pdf and it'll be great if this team will be convinced to join our project. In ISO 15926 reference data libraries classes of individuals, classes of classes and classes of relationships can be viewed as corresponding taxonomy systems, thus suggestions for missing members in these taxonomies can be deduced from the existing correspondence relations.     (2O34)

E. Questions to participants:     (2O35)

1. Please suggest more Tests and especially Metrics - our knowledge of these comes only from the Summit materials.     (2O36)

2. Please indicate your readiness to apply your tools to the tasks identified in the project (or suggested by you). If some initial introduction to data or its transformation are required - notify us in advance, we can discuss it together, by email or by arranging a preparation call.     (2O37)

3. If you are interested to work in Python data exploration environment of .15926 Editor - please take a look (download from http://techinvestlab.ru/dot15926Editor ) and ask questions before the event.     (2O38)



This page has been migrated from the OntologWiki - Click here for original page     (2O41)