We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
shacl
shex
When a shacl constraint has an inspecified maxCount, there is no maximum bound. This means that if I have the following shape
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix sh: <http://www.w3.org/ns/shacl#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . @prefix ex: <http://example.org/test#> . ex:TestShape a sh:NodeShape ; sh:targetClass ex:AccessRequest ; sh:property [ sh:path ex:requestedGraphs ; sh:minCount 1 ; sh:datatype xsd:string ] .
Then the following should be generated
prefix xsd: <http://www.w3.org/2001/XMLSchema#> prefix ex: <http://example.org/test#> prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> prefix sh: <http://www.w3.org/ns/shacl#> ex:TestShape { ex:requestedGraphs xsd:string{1,} }
instead of
prefix xsd: <http://www.w3.org/2001/XMLSchema#> prefix ex: <http://example.org/test#> prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> prefix sh: <http://www.w3.org/ns/shacl#> ex:TestShape { ex:requestedGraphs xsd:string{1,1} }
Similarly the default for minCount is 0 wheras the converter here uses a default of 1.
minCount
The text was updated successfully, but these errors were encountered:
fix: patching weso/shaclex#637
3e370d8
Successfully merging a pull request may close this issue.
When a shacl constraint has an inspecified maxCount, there is no maximum bound. This means that if I have the following shape
Then the following should be generated
instead of
Similarly the default for
minCount
is 0 wheras the converter here uses a default of 1.The text was updated successfully, but these errors were encountered: