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

Add inversion rules for SEMAPV cross-species predicates. #261

Merged
merged 1 commit into from
Feb 22, 2023
Merged

Add inversion rules for SEMAPV cross-species predicates. #261

merged 1 commit into from
Feb 22, 2023

Conversation

gouttegd
Copy link
Contributor

This PR updates the documentation to propose new inversion (“flipping”) rules for the cross-species predicates defined in the “semantic mapping vocabulary” (SEMAPV).

Specifically, it proposes that semapv:crossSpeciesExactMatch can be directly inverted, and that semapv:crossSpeciesNarrowMatch and semapv:crossSpeciesBroadMatch are mutually inverse. This follows the logic of the skos:{exact,narrow,broad}Match predicates upon which those cross-species variants are based.

semapv:crossSpeciesCloseMatch is not listed on purpose; the predicate is to be implicitly considered as “non-invertible”.

  • docs/ have been added/updated
  • make test has been run locally (not applicable, documentation change only)
  • tests have been added/updated (likewise)
  • CHANGELOG.md has been updated (deemed not necessary)

This commits add new inversion rules for the cross-species predicates
defined in the "semantic mapping vocabulary" (SEMAPV).
Copy link
Collaborator

@matentzn matentzn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! Thanks!

@matentzn matentzn merged commit 6543c3a into mapping-commons:master Feb 22, 2023
@gouttegd gouttegd deleted the inversion-rules-for-semapv branch February 22, 2023 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants