shapes-ISSUE-111 (charter issues): How should the working group address the issues called out in the WG charter?

shapes-ISSUE-111 (charter issues): How should the working group address the issues called out in the WG charter?

http://www.w3.org/2014/data-shapes/track/issues/111

Raised by: Peter Patel-Schneider
On product: 

Our charter says:

This working group will address the need for RDF data validation/interface definition on the Semantic Web. It will address issues like:

Defining and publishing a description of the intended topology and value constraints of nodes in an RDF graph, henceforth a "shape".

Verification of data integrity with respect to a shape.

Human and machine interpretation of shapes to develop or optimize SPARQL queries and develop user interfaces.


The working group has not yet described how what it is producing addresses these issues.


PROPOSAL:  The Shapes Constraint Language (SHACL), as "a language for describing and constraining the contents of RDF graphs", meets all three of the issues listed in the working group charter.  The high-level (or core) language described in Sections 2 and 3 of "Shapes Constraint Language (SHACL)" (http://w3c.github.io/data-shapes/shacl/) defines a declarative shape language that can be used to describe "the intended topology and value constraints of nodes in an RDF graph".  Later parts of "Shapes Constraint Language (SHACL)" provides extensions to that language for less-common constraints.  The validation process described throughout "Shapes Constraint Language (SHACL)" defines "[v]erification of data integrity with respect to a shape".  The high-level language can be used to "develop or optimize SPARQL queries" for checking shape verification.  The high-level language can also be used for structuring some of the information needed for developing user interfaces by adding UI-specific information to shapes nd constraints, particularly property constraints.

PROPOSAL:  Remove sh:defaultValue, so that user interfaces can fully experiment with adding UI information to SHACL shapes and constraints.  When there is some consensus on how UI information can be added to SHACL constructs, this consensus can be standardized by W3C.

Received on Thursday, 5 November 2015 21:47:38 UTC