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

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?

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.