Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposing changing attribute names for mapping precision/equivalence #156

Open
aostropolets opened this issue Aug 7, 2023 · 2 comments · Fixed by #160
Open

Proposing changing attribute names for mapping precision/equivalence #156

aostropolets opened this issue Aug 7, 2023 · 2 comments · Fixed by #160

Comments

@aostropolets
Copy link

As we (Vocab WG) started implementing community contribution for OHDSI Vocabularies, we thought of aligning the names for meta-data (specifically, mapping precision aka equivalence).

What we've been using so far is SSSOM (more specifically, Semantic Mapping Vocabulary [SEMAPV]) to capture our mapping predicates, link 1 and link 2.

These mappings correspond to the Usagi names as follows:

Equal = exactMatch
Equivalent = closeMatch
Wider = broadMatch
Narrower = narrowMatch
Inexact = relatedMatch

We would like to gather opinions on renaming equivalence attributes in USAGI to the names above so that meta-data attributes for mapping equivalence/precision are interoperable between USAGI and OHDSI Vocabularies.

As usually, many thanks :)

@aostropolets aostropolets changed the title Proposing changing attribute names for mapping precision Proposing changing attribute names for mapping precision/equivalence Aug 7, 2023
@AEW0330
Copy link

AEW0330 commented Nov 9, 2023

Links to supporting SSSOM documentation, publication, and code:
SSSOM paper: https://academic.oup.com/database/article/doi/10.1093/database/baac035/6591806
SSSOM GitHub repo: https://github.com/mapping-commons/SSSOM
SSSOM documentation: https://mapping-commons.github.io/sssom/
SKOS (a preferred predicate ontology where exactMatch etc. come from): https://www.w3.org/2004/02/skos/

@MaximMoinat
Copy link
Collaborator

Agree with making the naming consistent across tools, happy to see SKOS adopted in Usagi. Will make a start for implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants