The suggestion in this ticket ISSUE-139 is to basically remove the
notion of context from SHACL, making all constraint parameters
applicable everywhere. I would like to showcase my recent work on SHACL
editing for the next release of TopBraid web products, to clarify some
of "my" requirements.
Please look at the two attached screenshots. The first is an excerpt of
an edit form for sh:PropertyConstraints, the second is for
sh:InversePropertyConstraint. Both have different input fields, e.g.
inverse property constraints cannot have a minExclusive or datatype.
The algorithm that populates these forms is the same as the algorithm I
use for generating more general instance forms. While I could hard-code
this for the core vocabulary, support for the extension mechanism is
crucial for us and our customers. The system would automatically insert
widgets for constraint parameters that it has imported from 3rd-party
shapes files. For example, a widget for "this property is a primary key"
would show up only for property constraints, not inverse properties. It
uses sh:context to figure that out.
Holger
