W3C home > Mailing lists > Public > public-data-shapes-wg@w3.org > October 2016

shapes-ISSUE-191 (Parameter value types): Should the value types of parameters be constraints [SHACL Spec]

From: RDF Data Shapes Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 18 Oct 2016 04:07:43 +0000
To: public-data-shapes-wg@w3.org
Message-Id: <E1bwLgl-0004mb-3l@maia.w3.org>
shapes-ISSUE-191 (Parameter value types): Should the value types of parameters be constraints [SHACL Spec]

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

Raised by: Holger Knublauch
On product: SHACL Spec

In the currently published draft of the spec, each parameter of the core vocabulary is annotated with a column "Value type" that carries no meaning. Peter also stated that some of these value types are rather unhelpful:

https://lists.w3.org/Archives/Public/public-rdf-shapes/2016Oct/0059.html

I think we should do a proper job here and make the value types more useful, making SHACL more predictable. The Value types column should be deleted and instead the TEXTUAL DEFINITION of each component should enumerate constraints on these values. Shapes graphs that violate these constraints are invalid.

I have made these changes to the draft and would like the WG to review them:

https://github.com/w3c/data-shapes/commit/292f12936181ca2d3fd5c096a7880f2de6054f02

My proposal is to approve these changes.
Received on Tuesday, 18 October 2016 04:07:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:30:37 UTC