Re: SHACL syntax and metamodel complexity

This wording is extremely confused.   It is possible to have multiple
constraint components on the same property in one component, such as a
minCount and a class.  The confusion comes from using "property" for two
different things.


On 03/03/2016 03:22 PM, Arnaud Le Hors wrote:
> Ah ok, I found where the restriction comes from in the spec:
> Section 3.1 Property Constraints (sh:property)
> "None of these properties can be repeated within the same
> sh:PropertyConstraint. In order to define multiple constraints using the same
> property, such as multiple sh:hasValue constraints, the shape must use
> multiple sh:property definitions."
> Thanks.
> --
> Arnaud  Le Hors - Senior Technical Staff Member, Open Web Technologies - IBM
> Software Group

Received on Thursday, 3 March 2016 23:29:43 UTC