Requirement 2.11.7, Separation of Structural from Complex Constraints from Richard Cyganiak on 2015-03-05 (public-data-shapes-wg@w3.org from March 2015)

From: Richard Cyganiak <richard@cyganiak.de>
Date: Thu, 5 Mar 2015 12:52:40 +0000
To: public-data-shapes-wg@w3.org
Message-Id: <F6F58C93-BC16-4B88-B3B7-E2C91365162A@cyganiak.de>

I took an action to propose a rephrasing of Requirement 2.11.7, “Separation of Structural from Complex Constraints”

Link:
https://www.w3.org/2014/data-shapes/wiki/Requirements#Separation_of_structural_from_complex_constraints

I encourage in particular those who have voted on the original constraint (HK, KC:+1, SSt:+1, labra: +1, pfps: -1) to consider whether this changes their vote, and if so, update the wiki.

The original requirement reads:

[[[
The language should separate structural constraints from more complex constraints (like arbitrary SPARQL or nested constraint expressions) so that certain light-weight applications can validate the constraints without a full SPARQL processor.
]]]

My proposed rephrasing:

[[[
There shall be a SHACL profile that excludes any support for constraints defined via embedded SPARQL queries or other complex lower-level expressions. This is so that lightweight applications can validate constraints without requiring a SPARQL processor or similar subsystem.
]]]

This completes ACTION-15.

Richard

Received on Thursday, 5 March 2015 12:53:09 UTC