Re: shapes-ISSUE-91 (hsolbrig): Default Cardinality [SHACL Spec] from Holger Knublauch on 2015-09-24 (public-data-shapes-wg@w3.org from September 2015)

From: Holger Knublauch <holger@topquadrant.com>
Date: Fri, 25 Sep 2015 09:02:19 +1000
To: public-data-shapes-wg@w3.org
Message-ID: <560480FB.4010609@topquadrant.com>

I believe if something is left unspecified then it should count as 
unconstrained. So if no sh:minCount or sh:maxCount is given then it 
should count as 0..* by default.

PROPOSAL: Close ISSUE-91 stating that the default interpretations of 
sh:minCount and sh:maxCount (and their qualified counterparts) should 
remain as currently specified.

Holger

PS: A compact syntax may of course use different conventions and 
automatically generate the corresponding min/max triples.

On 9/25/2015 0:46, RDF Data Shapes Working Group Issue Tracker wrote:
> shapes-ISSUE-91 (hsolbrig): Default Cardinality [SHACL Spec]
>
> http://www.w3.org/2014/data-shapes/track/issues/91
>
> Raised by: Harold Solbrig
> On product: SHACL Spec
>
> The defaults for cardinality in UML are [1..1]  (see: MultiplicityElement.lowerBound() and MultiplicityElement.upperBound() on page 41 of OMG specification ptc/2013-09-05).  Should these be the defaults for mincount and maxcount in Section 3.1.5 of the SHACL specification as well?  Currently they are [0..*].
>
>
>

Received on Thursday, 24 September 2015 23:02:56 UTC