ISSUE-83: How should multiple definitions of sh:qualifiedValueShape of a property constraint be treated?
multiple sh:qualifiedValueShapes
How should multiple definitions of sh:qualifiedValueShape of a property constraint be treated?
- State:
- CLOSED
- Product:
- SHACL Spec
- Raised by:
- Simon Steyskal
- Opened on:
- 2015-08-21
- Description:
- Hi!
 
 The current specification does not specify how multiple sh:qualifiedValueShapes should be treated when they are used within a single property constraint.
 
 For example, if I want to specify that there must exist exactly 3 values for ex:parent where at least 1 of them must be ex:female (and ex:male respectively), the current specification does not prohibit me from writing something like this:
 
 ex:QualifiedValueShapeExampleShape
 a sh:Shape ;
 sh:property [
 sh:predicate ex:parent ;
 sh:minCount 3 ;
 sh:maxCount 3 ;
 sh:qualifiedValueShape [
 sh:property [
 sh:predicate ex:gender ;
 sh:hasValue ex:female ;
 ]
 ] ;
 sh:qualifiedMinCount 1 ;
 sh:qualifiedValueShape [
 sh:property [
 sh:predicate ex:gender ;
 sh:hasValue ex:male;
 ]
 ] ;
 sh:qualifiedMinCount 1 ;
 ] .
 
 Of course, one way to approach that would be to use sh:AndConstraint for >1 qualifiedValueShapes, but that's not explicitly mentioned in the draft.
 
 btw. there is a typo in the code example of the draft ->
 
 sh:predicate [
 sh:predicate ex:gender ;
- Related Actions Items:
- No related actions
- Related emails:
- Re: review of SHACL document (First pass of responses) (from holger@topquadrant.com on 2015-09-02)
- Re: shapes-ISSUE-83 (multiple sh:qualifiedValueShapes): How should multiple definitions of sh:qualifiedValueShape of a property constraint be treated? [SHACL Spec] (from holger@topquadrant.com on 2015-08-24)
- AW: Re: shapes-ISSUE-83 (multiple sh:qualifiedValueShapes): How should multiple definitions of sh:qualifiedValueShape of a property constraint be treated? [SHACL Spec] (from simon.steyskal@wu.ac.at on 2015-08-21)
- Re: shapes-ISSUE-83 (multiple sh:qualifiedValueShapes): How should multiple definitions of sh:qualifiedValueShape of a property constraint be treated? [SHACL Spec] (from axel.polleres@wu.ac.at on 2015-08-21)
- Re: shapes-ISSUE-83 (multiple sh:qualifiedValueShapes): How should multiple definitions of sh:qualifiedValueShape of a property constraint be treated? [SHACL Spec] (from simon.steyskal@wu.ac.at on 2015-08-21)
- Re: shapes-ISSUE-83 (multiple sh:qualifiedValueShapes): How should multiple definitions of sh:qualifiedValueShape of a property constraint be treated? [SHACL Spec] (from holger@topquadrant.com on 2015-08-21)
- shapes-ISSUE-83 (multiple sh:qualifiedValueShapes): How should multiple definitions of sh:qualifiedValueShape of a property constraint be treated? [SHACL Spec] (from sysbot+tracker@w3.org on 2015-08-21)
 
Related notes:
Resolution: Close ISSUE-83, the specification says this is actually invalid syntax in section 3.1 https://w3c.github.io/data-shapes/shacl/#constraints-property (note that the same result can however be achieved using multiple property constraints)
See: http://www.w3.org/2015/09/17-shapes-minutes.html#resolution06
Display change log