Skip to content
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

Issue 139 (partial): Fix DASH shape-component usage by copying original shape #162

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

ajnelson-nist
Copy link

The patch(es) in this PR include documentation for their changes.

This PR fixes some, but not all, of the SHACL-SHACL validation issues in #139 . It includes a suggestion for how to fix some of the other issues pertaining to the sh:or-linked rdf:Lists. I'm happy to add follow-on patches to fix other rdf:List issues, but I wanted to pause for input from the maintainers before doing so.

I believe this PR can be merged without negative impact.

The shape-component transcribed from DASH was transcribed incorrectly.
The RDF List was constructed incorrectly, needing both a `rdf:first` and
`rdf:rest` predicate.  Also, from DASH-prescribed usage with `sh:or`,
the RDF List members must be `sh:Shape`s, each housing a `sh:datatype`
constraint predicate.

To avoid other transcription or reformatting errors, this patch copies
the original shape from DASH, adding an `rdfs:isDefinedBy` to cite the
source.  Because DASH does not provide a `owl:versionIRI`, an extra
comment noting the copy date and destination file is also added.

This patch addresses 37 of the 70 reported SHACL-SHACL validation errors
noted in Issue 139.

References:
* https://datashapes.org/dash.html#StringOrLangString
* DOI-DO#139

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This merge aligns some whitespace styling by hand.
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.

None yet

1 participant