You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sh:nodeKind should be extended to support sh:TripleTerm. List values should be accepted, like in the recent change for sh:datatype and sh:class in PR #395, to avoid extending the list of possible values with all combinations.
changed the title [-]Add support for TripleTerm to sh:nodeKind and allow lists[/-][+]Add support for `sh:TripleTerm` to `sh:nodeKind` and allow lists[/+]on Jun 18, 2025
Are there any real-world scenarios where a node can be either TripleTerm or something else?
There should be only one use case: checking if a triple term is used with the intended property rdf:reifies. But the specification defines it only with SHOULD and allows other use cases.
Activity
HolgerKnublauch commentedon Jun 16, 2025
Are there any real-world scenarios where a node can be either TripleTerm or something else?
ajnelson-nist commentedon Jun 16, 2025
What about a TripleTerm or the IRI or BNode that identifies a TripleTerm? I.e., just not a Literal.
[-]Add support for TripleTerm to sh:nodeKind and allow lists[/-][+]Add support for `sh:TripleTerm` to `sh:nodeKind` and allow lists[/+]bergos commentedon Jun 22, 2025
There should be only one use case: checking if a triple term is used with the intended property
rdf:reifies
. But the specification defines it only with SHOULD and allows other use cases.feat: #407 add support for sh:TripleTerm to sh:nodeKind and allow lists
Merge pull request #410 from w3c/issue-407-nodekind