Extend mapping metdata and align with SSSOM

[nichtich]

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

SSSOM field	SKOS field
subject_id	from.memberSet[].uri
subject_label	from.memberSet[].prefLabel
subject_category	from.memberSet[].type (URI)
predicate_id	type (URI)
predicate_label	- (implied by type)
predicate_modifier	Negative mappings are not supported but empty mappings are
object_id	to.memberSet[].uri
object_label	to.memberSet[].prefLabel
object_category	to.memberSet[].type (URI)
mapping_justification	justification (0.7.0)
author_id	creator[].uri (URI)
author_label	creator[].prefLabel
reviewer_id	annotations[].creator.id (URI)
reviewer_label	annotations[].creator.name (URI)
creator_id	contributor[].uri (URI)
creator_label	contributor[].prefLabel
license	license of the Concordance (individual mappings have no license)
subject_type	from.memberSet[].type (URI, limited list)
subject_source	from.memberSet[].inScheme
subject_source_version	from.memberSet[].inScheme or its versionId (0.7.0)
object_type	from.memberSet[].type (URI, limited list)
object_source	to.memberSet[].inScheme
object_source_version	to.memberSet[].inScheme or its versionId (0.7.0)
mapping_provider	publisher
mapping_source	source
mapping_cardinality	TODO (can be derived automatically)
mapping_tool	tool (0.7.0)
mapping_tool_version	tool[].versionId (0.7.0)
mapping_date	created
publication_date	published
confidence	mappingRelevance
curation_rule	guidelines (0.7.0)
curation_rule_text	guidelines[].prefLabel (0.7.0)
subject_match_field	- (see #152)
object_match_field	- (see #152)
match_string	- (see #152)
subject_preprocessing	- (see #152)
object_preprocessing	- (see #152)
similarity_score	- (see #152)
similarity_measure	- (see #152)
see_also	TODO
issue_tracker_item	issue (0.7.0)
other	-
comment	note

Most relevant open issues:

• support mapping_justification as new JSKOS field justification.
• support mapping_tool
• rename mappingRelevance to confidence 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
• find out meaning of mapping_provider and mapping_source (Clarify the description of mapping_provider mapping-commons/sssom#400)
• allow to add information about automatic mappings (match_field, preprocessing...): Express information about automatic mappings #152
• Document how to reference curation_rule (probably a property of concordance)

MappingSet

A SSSOM MappingSet is a JSKOS Concordance or Registry.

Most fields (comment, creator_id...) are already listed above. In addition there is:

SSSOM field	SKOS field
curie_map	- (syntax level)
mappings	mappings (of a registry or concordance)
mapping_set_id	uri
mapping_set_version	versionId
mapping_set_source	source
mapping_set_title	prefLabel
mapping_set_description	?
predicate_type	?
issue_tracker	issueTracker (0.7.0)
extension_definitions	-