This constraint is specified at
https://www.w3.org/TR/shacl/#property-path-sequence and was
intentionally designed like that. As you say it could theoretically have
the same effect as IRI properties, yet then the algorithms would need to
make an additional IF for the special case, and I assume we agree that
sequence paths with a length of one don't make sense.
Think about it this way: if we would map such lists to single values,
then arguably any API function that takes single values should also be
allowed to take array arguments with length of one. It would become
quite chaotic.
Holger
On 2021-02-20 6:19 am, Tomasz Pluskiewicz wrote:
Hi
I was surprised to find out today that a Property Path declared as an
RDF List with only a single element is not a valid construct and fails
validation with SHACL.js
I would expect [ sh:path ( ex:property ) ] be treated equally to [
sh:path ex:property ]
Why is sequence path defined to require *at least two members*?
Best,
Tom
--
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/eb72df9c-eee2-46f2-8872-49f860fcbcc1n%40googlegroups.com
<https://groups.google.com/d/msgid/topbraid-users/eb72df9c-eee2-46f2-8872-49f860fcbcc1n%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/06d9b66c-9df6-901d-2059-1e9dbd9921b6%40topquadrant.com.
