- From: Irene Polikoff <irene@topquadrant.com>
- Date: Mon, 13 Jun 2016 10:43:21 -0400
- To: kcoyle@kcoyle.net
- Cc: public-data-shapes-wg@w3.org
No more than n instances of Creator would work using this new constraint. The second example is different. With it, I think, we are back to minCount/maxCount and a shape with the scopeClass bf:Instance and minCount/maxCount constraint on whatever property connects instances of be:Instance and be:Work. Sent from my iPhone > On Jun 13, 2016, at 9:53 AM, Karen Coyle <kcoyle@kcoyle.net> wrote: > > Holger, you give the 1/1 example, but would this also support other numbers? I assume so, but the description of the schema.org case and the example are only 1/1. > > Other possible use cases are: > > - no more than n instances of ex:Creator > - only one instance of bf:Work for each bf:Instance > etc. > > kc > > >> On 6/13/16 5:04 AM, RDF Data Shapes Working Group Issue Tracker wrote: >> shapes-ISSUE-168 (instance count): How to constrain number of instances of a class in a graph [SHACL - Core] >> >> http://www.w3.org/2014/data-shapes/track/issues/168 >> >> Raised by: Holger Knublauch >> On product: SHACL - Core >> >> There was recent discussion about how to specify min/max numbers of instances in a graph. Off-list I had also received a question from schema.org people about how to state that a graph/message must have exactly one instance of schema:FlightReservation, possibly to ensure that a graph has a starting point/root for validation. >> >> A possible syntax that would easily work with the current architecture could be >> >> ex:MyShape >> a sh:Shape ; >> sh:scopeNode schema:FlightReservation ; >> sh:constraint [ >> sh:minInstanceCount 1 ; >> sh:maxInstanceCount 1 ; >> ] . >> >> >> >> > > -- > Karen Coyle > kcoyle@kcoyle.net http://kcoyle.net > m: 1-510-435-8234 > skype: kcoylenet/+1-510-984-3600 >
Received on Monday, 13 June 2016 14:44:01 UTC