ISSUE-100: Specifying the order of property constraints (e.g. with sh:index)

sh:index

Specifying the order of property constraints (e.g. with sh:index)

State:

CLOSED

Product:

SHACL - UI

Raised by:

Holger Knublauch

Opened on:

2015-10-07

Description:

As a little non-validation "annotation" feature similar to default values, I suggest that all property constraints may have an xsd:integer-valued property called sh:index that can be used to give hints about the relative ordering of properties. This information may be used to arrange widgets in a user interface, to pretty-print properties in Turtle or JSON-LD files etc.

Example:

ex:MyShape
sh:property [
sh:predicate ex:givenName ;
sh:index 0 ;
rdfs:label "given name" ;
] ;
sh:property [
sh:predicate ex:familyName ;
sh:index 1 ;
rdfs:label "family name" ;
] .

to hint that given name should appear before family name.

I believe this is easy to specify, easy to ignore by those who don't need it, yet may find widespread use - TopBraid would certainly support this in various places. We already have sh:index in sh:Function definitions, to specify the ordering of arguments, and I am simply suggesting to pull this one level up, to sh:AbstractPropertyConstraint.

Related Actions Items:

No related actions

Related emails:

1. Re: Can we freeze the Tracker for while? (from lehors@us.ibm.com on 2015-11-09)
2. Re: Can we freeze the Tracker for while? (from kcoyle@kcoyle.net on 2015-11-09)
3. Re: Can we freeze the Tracker for while? (from holger@topquadrant.com on 2015-11-09)
4. shapes-ISSUE-100 (sh:index): Proposal to allow (optional) sh:index for property constraints [SHACL Spec] (from sysbot+tracker@w3.org on 2015-10-07)

Related notes:

Display change log