Skip to content

Add support for sh:TripleTerm to sh:nodeKind and allow lists #407

@bergos

Description

@bergos
Contributor

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.

Activity

HolgerKnublauch

HolgerKnublauch commented on Jun 16, 2025

@HolgerKnublauch
Contributor

Are there any real-world scenarios where a node can be either TripleTerm or something else?

ajnelson-nist

ajnelson-nist commented on Jun 16, 2025

@ajnelson-nist
Contributor

Are there any real-world scenarios where a node can be either TripleTerm or something else?

What about a TripleTerm or the IRI or BNode that identifies a TripleTerm? I.e., just not a Literal.

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
bergos

bergos commented on Jun 22, 2025

@bergos
ContributorAuthor

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.

self-assigned this
on Jun 22, 2025
added a commit that references this issue on Jun 22, 2025
added a commit that references this issue on Aug 13, 2025
1d4d240
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

CoreFor SHACL 1.2 Core spec

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Participants

    @bergos@HolgerKnublauch@ajnelson-nist

    Issue actions

      Add support for `sh:TripleTerm` to `sh:nodeKind` and allow lists · Issue #407 · w3c/data-shapes