Skip to content

#160: Allow lists at sh:class and sh:datatype #395

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: gh-pages
Choose a base branch
from

Conversation

HolgerKnublauch
Copy link
Contributor

I have not yet added the JSON-LD to the samples - is my understanding correct that the generation of that will be automated?

Closes #160

For each value node
that is either a literal, or a non-literal that is not a SHACL instance of $class in the data graph,
that is either a literal, or a non-literal that is not a SHACL instance of any of the classes in the data graph,
there is a validation result with the value node as sh:value.

The remainder of this section is informative.

Note that multiple values for sh:class are interpreted as a conjunction,
i.e. the values need to be SHACL instances of all of them.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
i.e. the values need to be SHACL instances of all of them.
i.e., the values need to be SHACL instances of all of them.

Co-authored-by: Ted Thibodeau Jr 
Comment on lines +3150 to +3151
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think #160 should not be closed until this box is populated. I also recall there's supposed to be an automatic generation process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Multivalued or union sh:dataType
4 participants