W3C home > Mailing lists > Public > public-data-shapes-wg@w3.org > January 2017

Re: ISSUE-92: Should repeated properties be interpreted as additive or conjunctive?

From: Eric Prud'hommeaux <eric@w3.org>
Date: Thu, 12 Jan 2017 12:14:37 -0500
To: Irene Polikoff <irene@topquadrant.com>
Cc: "public-data-shapes-wg@w3.org" <public-data-shapes-wg@w3.org>
Message-ID: <20170112171436.GY6394@w3.org>
* Irene Polikoff <irene@topquadrant.com> [2017-01-12 12:05-0500]
> Hi Eric,
> 
> I hope your proposal could be restored.
> 
> Since partitioning was not a goal, but a way to address these use cases and SHACL has QualifiedValueShape for the first use case and an OR for the second use case, do you think the use cases are addressed or is there still something missing?

Partitioning was not a goal but was the only way we found of providing
a satisfactory user experience. While qualified cardinality
restrictions can capture top-level repeated properties, they become
quite a burden to author and maintain. Likewise, exploding every OR
with a negation of the DNF of the other disjuncts requires diligence
and is tedious and error prone if the disjuncts have any complexity to
them.


> Irene
> 
> > On Jan 12, 2017, at 6:00 AM, Eric Prud'hommeaux <eric@w3.org> wrote:
> > 
> > Originally, ShEx (a surface syntax for ResourceShape plus OR) didn't have partitions. It was added to:
> > 
> >  1 address the frequent (and encouraged) reuse of generic properties. These are extremely common in clinical data, for instance a BP observation has two components, one of which has a code for systolic and the other a code for diastolic.
> > 
> >  2 provide an OR that was closer to user expectations and reduced the need for defensive programming, e.g a shape expecting either a name or a given and family name should reject a mixture like { <s> foaf:name "X"; foaf:givenName "Y" }.
> > 
> > Partitioning was never a goal; it was a means of satisfying these needs.
> 

-- 
-ericP

office: +1.617.599.3509
mobile: +33.6.80.80.35.59

(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.

There are subtle nuances encoded in font variation and clever layout
which can only be seen by printing this message on high-clay paper.
Received on Thursday, 12 January 2017 17:14:46 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 12 January 2017 17:14:47 UTC