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

Re: shapes-ISSUE-157 (constraint component support): the support for constraint components is incorrectly stated [SHACL Spec]

From: Peter F. Patel-Schneider <pfpschneider@gmail.com>
Date: Thu, 28 Apr 2016 23:55:48 -0700
To: Holger Knublauch <holger@topquadrant.com>, public-data-shapes-wg@w3.org
Message-ID: <57230574.5050605@gmail.com>
It's not a matter of precision.  The definition with properties is incorrect.

peter


On 04/28/2016 04:09 PM, Holger Knublauch wrote:
> Ok, I have rolled back to the previous policy of listing the constraint classes:
> 
> https://github.com/w3c/data-shapes/commit/19ef548ffe19371d17c4fffb14086ef3064e2028
> 
> 
> I had thought it would be more readable with the properties only, but this was
> indeed less precise.
> 
> Please confirm we can close this.
> 
> Holger
> 
> 
> On 28/04/2016 22:44, RDF Data Shapes Working Group Issue Tracker wrote:
>> shapes-ISSUE-157 (constraint component support): the support for constraint
>> components is incorrectly stated [SHACL Spec]
>>
>> http://www.w3.org/2014/data-shapes/track/issues/157
>>
>> Raised by: Peter Patel-Schneider
>> On product: SHACL Spec
>>
>> The "support" for constraint components is stated in terms of sh:constraint,
>> sh:property, and sh:inverseProperty.  This does not work, because any
>> constraint can be used as the object of a sh:constraint triple.
>>
>> For example, the intent in the spec is that sh:datatype should not be used
>> in inverse property constraints, but the spec allows sh:datatype constraint
>> component properties to appear in inverse property constraints.
>>
>>
>> 3.1.3 sh:datatype
>>
>> The property sh:datatype can be used to restrict the datatype of all value
>> nodes. The values of sh:datatype must be resources representing datatypes,
>> such as xsd:string.
>>
>> Constraint Component: sh:DatatypeConstraintComponent
>>
>> Supported Context Properties: sh:constraint, sh:property
>>
>>
>>
> 
> 
Received on Friday, 29 April 2016 06:56:32 UTC

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