Update User property order to force correct grouping in a shacl-vue form #65

Open
jsheunis wants to merge 1 commit from reorder into main

1 commit

Author SHA1 Message Date
a962056358 Update User property order to force correct grouping in a shacl-vue form
All checks were successful
Codespell / Check for spelling errors (pull_request) Successful in 26s
Model checks / lint (pull_request) Successful in 1m34s
Validate examples and verify unmodified conversion / lint (pull_request) Successful in 2m46s
This is in response to inm7/annotate.inm7.de-users#18

A recent update to shacl-vue stated that, for a rendered form, a property should be divided
into the class group that either made the latest change to it if it was inherited,
or into the class that introduced the property. But it seems this update did not foresee
the situation where both an original and inheriting class have properties annotated with
the exact same sh:order. This causes a given property to be placed, incorrectly, in what
is determined, correctly, to be the originating class.

This stems from the fact that there is no machine-actionable knowledge about annotation
inheritance in the shacl that is exported from a linkml schema. The only way of knowing
this, in the current approach, is if the property changes. This is what we are doing with
this commit, by changing the annotation. This is done because of the absence of a better
solution at the current time.
2025-05-18 22:57:03 +02:00