[FYI] Validation rules for SKOS mapping

Dear All,

I am using SKOS for terminology mapping, as well as mapping validation. In 
the project I worked on, SKOS mappings between a few clinical 
terminologies are developed, however, we discovered there are many errors 
in the mappings.

By analyzing the errors, we discovered that as most of the SKOS mappings 
can be considered as transitive and bidirectional after certain inference, 
the mappings therefore may bring assertions that a mapping creator may not 
be aware of. Furthermore, those assertions may also conflict with existing 
semantic or mapping relations. We therefore developed a set of rules to 
detect problematic patterns in SKOS mapping, so that a mapping creator 
could validate these problematic patterns, and eventually improve the 
quality their mappings.

We would like to share these rules with SKOS community. Those who are 
interested in could use these rules to check your SKOS mappings, and we 
are willing to hear your feedback. 

Our SKOS mapping validation rules are expressed in N3 format and published 
at [1]. It can be executed by N3 reasoning engine EYE [2]. An explanation 
document for the validation rules is uploaded to [3].

An example of using the validation rules to check sample SNOMED to ICD-10 
mappings are created:
Sample mappings as well as the related concepts are put together in [4]. 
Validation results can be found in [5]. 
Detailed explanation can be found in [3] in Section 4.6 and Section 5.


[1] 
http://eulersharp.sourceforge.net/2003/03swap/skos-mapping-validation-rules.n3
[2] http://eulersharp.sourceforge.net
[3] http://arxiv.org/ftp/arxiv/papers/1310/1310.4156.pdf
[4] 
http://eulersharp.sourceforge.net/2007/07test/skos-mapping-sample-snomed-icd10.n3
[5] http://eulersharp.sourceforge.net/2007/07test/skos_mv_answer.n3

Kind Regards,

Hong Sun | Agfa HealthCare
Researcher | HE/Advanced Clinical Applications Research