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

Re: shapes-ISSUE-156 (property pair constraints): problems in the description of property pair constraints [SHACL Spec]

From: Arnaud Le Hors <lehors@us.ibm.com>
Date: Thu, 28 Apr 2016 09:10:15 -0700
Message-Id: <201604281610.u3SGAcTu026524@d03av04.boulder.ibm.com>
To: Holger Knublauch <holger@topquadrant.com>
Cc: public-data-shapes-wg@w3.org
Holger Knublauch <holger@topquadrant.com> wrote on 04/28/2016 12:24:10 AM:

> From: Holger Knublauch <holger@topquadrant.com>
> To: public-data-shapes-wg@w3.org
> Date: 04/28/2016 12:24 AM
> Subject: Re: shapes-ISSUE-156 (property pair constraints): problems 
> in the  description of property pair constraints [SHACL Spec]
> 
> This duplicate should be closed.
> 

Done.
--
Arnaud  Le Hors - Senior Technical Staff Member, Open Web Technologies - 
IBM Cloud


> Holger
> 
> 
> On 28/04/2016 17:11, RDF Data Shapes Working Group Issue Tracker wrote:
> > shapes-ISSUE-156 (property pair constraints): problems in the 
> description of property pair constraints [SHACL Spec]
> >
> > http://www.w3.org/2014/data-shapes/track/issues/156
> >
> > Raised by: Peter Patel-Schneider
> > On product: SHACL Spec
> >
> > The descriptions of the property pair constraints have multiple 
problems.
> >
> > They do not match the definition of property constraints because 
> they are not about the singular object of triples.
> >
> > The are not allowed for inverse property constraints although they
> work just as well for inverse property constraints as they do for 
> property constraints.
> >
> > They refer to property values, which are not defined in the spec.
> >
> > They talk about an (ordered) pair of properties but do not take an
> (ordered) pair of properties as arguments.
> >
> >
> >
> 
> 
Received on Thursday, 28 April 2016 16:11:14 UTC

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