[spec] Should `completeTyping()` include ancestors? (#62)

ericprud has just created a new issue for https://github.com/shexSpec/spec:

== Should `completeTyping()` include ancestors? ==
[1.5.2 Validation Definition](https://shex.io/shex-next/#validation) says:

`n@sl EXACTLY ::- satisfies(n, def(s.label), G, Sch, completeTyping(G, Sch), neigh(n))`

`n@sl ::- satisfiesDescendant(n, def(s.label), G, Sch, completeTyping(G, Sch), neigh(n))`

where I understand `completeTyping()` to be making sure that the same total truth is maintained regardless of which pieces of it you interrogate with isValid queries.
The same section then defines a correct typing:

> A correct typing is a typing such that for every RDF node/shape pair (n,l), `satisfies(…)` holds or `satisfiesDescendant(…)` holds.

Should the correct typing be ONLY `satisfies(…)`? This would allow it to answer shapemaps where EXACTLY is true.

I'm guessing that the current text (post-review by Iovka and Labra) is fine because we're counting on the first two lines of this issue text to differentiate EXACTLY from, um, not EXACTLY. Just wanted your eyes to verify this.

Please view or discuss this issue at https://github.com/shexSpec/spec/issues/62 using your GitHub account


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

Received on Wednesday, 29 May 2024 15:44:46 UTC