[data-shapes] Pull Request: #429: Have SHACL-SHACL warn about unsatisfiable usage of `sh:in` and `sh:xone`

ajnelson-nist has just submitted a new pull request for https://github.com/w3c/data-shapes:

== #429: Have SHACL-SHACL warn about unsatisfiable usage of `sh:in` and `sh:xone` ==
Closes #429 .

* [See this document rendered online here](https://raw.githack.com/w3c/data-shapes/{issue-429-list-lengths-xone-in}/shacl12-core/index.html)

This patch revises part of the implementation in PR 417.

* `in-minListLength` was not added to the Core document, but it was referenced in SHACL-SHACL.  Verbiage is added to Core in line with the text drafted for Issue 429.
* `xone-memberShape` was added as a reference in SHACL-SHACL, but doesn't exist in the Core document.  `xone-members-node` is the anchor in the Core document.  `xone-members-node` is now used.
* The `PropertyShape` for `sh:in` set a minimum required length of 1, which after discussion in Issue 429 appears to be a backward- incompatible change.  A shape paralleling the original suggestion for `sh:xone` is added to house that new restriction at the same warning- level severity.

An implementation style point: The property shapes housing `sh:minListLength` are given IRIs after sketching a test (`.../in-003.ttl`) and assuming it would be more desirable to have an IRI-identified shape in the results graph, rather than a blank node.

A testing style point: Rather than running SHACL-SHACL over the whole of a test, shapes from SHACL-SHACL are copied into some focused tests (`.../{in,xone}-003.ttl`).

See https://github.com/w3c/data-shapes/pull/451


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 29 July 2025 14:31:57 UTC