The spec only states that the list members of sh:or must be (any)
*shapes*. This means they may be node shapes OR property shapes, as in
the example of the spec. Both syntaxes here would/should have the same
semantics unless I am missing something. To reiterate, property shapes
have the same status as node shapes in SHACL, and may also appear
stand-alone.
Holger
On 28/03/2021 11:23 pm, Tomasz Pluskiewicz wrote:
I'm a little confused by the example of sh:or presented in the spec.
Why are the sh:path and sh:minCount directly attached to the shape in
the list? Wouldn't sh:property be necessary?
ex:OrConstraintExampleShape
a sh:NodeShape ;
sh:or (
[ sh:property [ sh:path ex:firstName ; sh:minCount 1 ; ]
[ sh:property [ sh:path ex:givenName ; sh:minCount 1 ; ]
)
.
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/bedd1acd-4fd9-4a78-8465-dd37ca02bef2n%40googlegroups.com
<https://groups.google.com/d/msgid/topbraid-users/bedd1acd-4fd9-4a78-8465-dd37ca02bef2n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "TopBraid
Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/93c43a50-b213-ee75-a795-931a3052803c%40topquadrant.com.
