sssom
sssom copied to clipboard
mapping-commons
Simple Standard for Sharing Ontology Mappings
Suggestion from @AlasdairGray Thanks!
We have one action to build products #95. We should also have one that runs unit tests, should just be `make test` Example https://github.com/linkml/linkml-model/blob/main/.github/workflows/pr-test.yaml Also consider: https://github.com/linkml/linkml-model/blob/main/.github/workflows/pypi-publish.yaml EDIT (by @matentzn):...
From @kec Regarding the mapping has fields for author_id, reviewer_id, and creator_id. It may be that there is a need for more than one workflow, particularly for things that might...
Point from @hsolbrig, establish overlap, difference with SNOMEDs complex map system.
When - creating reference mappings based on multiple sets of candidate mappings or - creating new mappings based on walks of other mappings we currently have no way to capture...
After discussions with @NuriaQueralt, its clear we need to distinction a few more roles than just "creator". - creator: first agent to assert the mapping - publisher: the group/individual that...
This goes to our best practice guide. @sbello from MGI asked in slack: > How broad is too broad? To put that another way where is the line where you...
When compared to OMOP2OBO, SSSOM lacks expressivity at first glance. Here is an example: ``` Example: Hip pain (OMOP_4170554) Ontology Concepts: Hip pain (HP_0030838) Arthralgia of the hip (HP_0003365) Mapping...
Not for the first version, but it would be interesting to think about how SSSOM relates to PROV-O. e.g. would mappings have prov:wasGeneratedBy properties? could ontology alignment be a prov:Activity?
The goal of SSSOM is to define a fully community-managed extensible standard for the representation of mappings. It is deliberately not as rigid as ISO or W3C standards, and welcomes...
Metadata
Owner
Metadata
Simple Standard for Sharing Ontology Mappings