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

How strict should a KGCL applicator be? #38

Open
gouttegd opened this issue May 14, 2023 · 0 comments
Open

How strict should a KGCL applicator be? #38

gouttegd opened this issue May 14, 2023 · 0 comments

Comments

@gouttegd
Copy link

Had there been any discussion as to what behaviour one should expect when trying to apply a KGCL change that does not fully match the existing ontology?

For example, considering the following changeset:

rename EX:1234 from 'alice' to 'bob'
create exact synonym 'robert' for EX:1234
remove definition for EX:5678

What is the expected behaviour if the rdfs:label of EX:1234 is not “alice”?

I can imagine 4 different options:

  • Relaxed: Apply changes where possible even where there is a mismatch. In this example, EX:1234 should get the new label “alice” regardless of what its existing label is.
  • Change-level strict: Reject any change where there is a mismatch, apply all other changes normally. In this example, reject the first change, apply the others two.
  • Node-level strict: If there is a mismatch in one change, reject all changes that are related to the same node. In this example, reject the first two changes (since both are about EX:1234), apply the last one.
  • Changeset-level strict: Only apply the changes in a changeset if they all can be applied cleanly, reject the entire changeset for any mismatch in any change. In this example, all three changes would be rejected.
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

No branches or pull requests

1 participant