Extend mapping metdata and align with SSSOM
Opened this issue · 0 comments
At BioHackathon 2015 a list of fields for ontology metadata mapping were collected (see https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7141167/). This work later resulted in the Simple Standard for Sharing Ontological Mappings (SSSOM) (see https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9216545/, the section on related works and https://w3id.org/sssom/). SSSOM and JSKOS have evolved independently with simlar goals and should be aligned. I started discussion to get to know each other at mapping-commons/sssom#250 and alignment at
mapping-commons/sssom#249.
Basically SSSO Mapping corresponds to JSKOS Concept Mapping and SSSO MappingSet corresponds to JSKOS Concordance (although SSSO MappingSet may be broader as it can contain mappings between more then two vocabularies). SSSO properties/fields/slots of both Mapping and MappingSet respectively should have correspondence in JSKOS.
Mapping
- subject_id:
from.memberSet[].uri
- subject_label:
from.memberSet[].prefLabel
- subject_category:
from.memberSet[].type
?? - predicate_id:
type
- predicate_label: -
- predicate_modifier: TODO
- object_id:
to.memberSet[].uri
- object_label:
to.memberSet[].prefLabel
- object_category:
to.memberSet[].type
?? - mapping_justification: TODO
- author_id:
creator[].uri
- author_label:
creator[].prefLabel
- reviewer_id: done with annotations (TODO)
- reviewer_label: dito
- creator_id:
contributor[].uri
- creator_label:
contributor[].prefLabel
- license:
license
of the Concordance - subject_type:
from.memberSet[].type
?? - subject_source:
from.memberSet[].inScheme
? - subject_source_version: ?
- object_type:
from.memberSet[].type
?? - object_source:
to.memberSet[].inScheme
? - object_source_version: ?
- mapping_provider: TODO
- mapping_source: TODO
- mapping_cardinality: TODO (can be derived automatically)
- mapping_tool: TODO
- mapping_tool_version: TODO
- mapping_date:
created
- confidence:
mappingRelevance
(experimental) - subject_match_field: -
- object_match_field: -
- match_string: -
- subject_preprocessing: -
- object_preprocessing: -
- semantic_similarity_score: ?
- semantic_similarity_measure: ?
- see_also: ?
- other: -
- comment: ? maybe
note
or doable with annotations
Most relevant open issues:
- support
mapping_justification
as new JSKOS fieldjustification
. - support
mapping_tool
- rename
mappingRelevance
toconfidence
or keep it and adjust definition? - can
predicate_modifier
be mapped to a null-mapping or are there other cases as well? - find out about SSSOM
subject_type
/object_type
vs.subject_category
/object_category
MappingSet
to be done