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.
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:
What is the expected behaviour if the
rdfs:labelofEX:1234is not “alice”?I can imagine 4 different options:
EX:1234should get the new label “alice” regardless of what its existing label is.EX:1234), apply the last one.