Shaclc: add features and implementations #70
Conversation
|
@jeswr and @HolgerKnublauch can you review? |
|
Hi Vladimir, I am generally supportive of the SHACL-C work and believe it should become a deliverable of the upcoming 1.2 WG. I personally do not have bandwidth to work on it though, as I would like to focus on the other deliverables. So please don't wait for reviews from me. |
shacl-compact-syntax/scope.md
Outdated
| - [Support `xone` and more `or` cases](https://github.com/w3c/shacl/issues/12) | ||
| - Opt out of the production of the triple `?baseUri rdf:type owl:Ontology` | ||
| - Non-validating characteristics (e.g., generating `sh:order` triples by declaring `@order` at the top of a file/shape, allow grouping by `@group` at the top of a set of properties, and allowing a `@description` above properties). | ||
| - Target shapes, see [rsx:targetShape](https://rdf4j.org/shacl/extensions.html) |
There was a problem hiding this comment.
I think this would only be appropriate if rsx:targetShape becomes part of the SHACL or SHACL-AF. Is there an effort to incorporate rsx: features into SHACL or SHACL-AF as part of the 1.2 work?
There was a problem hiding this comment.
@HolgerKnublauch mentioned it as a possibility.
shacl-compact-syntax/scope.md
Outdated
|
|
||
| The first 2 of these have been supported in [this xtext file](https://gitlab.com/allotrope-open-source/shape-editor/-/blob/master/src/com.osthus.shapes.shaclc.parent/com.osthus.shapes.shaclc/src/com/osthus/shapes/shaclc/SHACLC.xtext) by [allotrope](https://www.allotrope.org/). Some or all of these additions may be ignored in favour of keeping SHACL-C a simple syntax to implement and use. | ||
| A number of features from [SHACLC.xtext](https://gitlab.com/allotrope-open-source/shape-editor/-/blob/master/src/com.osthus.shapes.shaclc.parent/com.osthus.shapes.shaclc/src/com/osthus/shapes/shaclc/SHACLC.xtext) by [Allotrope](https://www.allotrope.org/): | ||
| - [Shape Libraries](https://rawgit2.com/VladimirAlexiev/shacl/shaclc-grammars/shacl-compact-syntax/grammar/shaclc-XText.html#ShaclDoc) (versioned). Packaging shapes into libraries enables modularized development of shapes. |
There was a problem hiding this comment.
Could you please provide additional information or a pointer to describe what triples are produced when parsing this part of the grammar to make it clearer how the shape library works.
There was a problem hiding this comment.
I have no idea whether these are implemented. They are good material for extending the scope of SHACL 1.2. I'll make a separate issue.
Guess we should add a note which are part of SHACL, and which are speculative?
There was a problem hiding this comment.
Guess we should add a note which are part of SHACL, and which are speculative?
That would be great :)
There was a problem hiding this comment.
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
|
hi @jeswr!
Do you have such access? If not, ask Holger to give you access, since he has no time to review SHACL-C stuff. |
|
I do not currently have write access. @HolgerKnublauch can you grant me access, or would I need to become a member of the SHACL working group first (noting w3c/data-shapes#187). |
|
Posted w3c/data-shapes#199 that corresponds to |
Co-authored-by: Ted Thibodeau Jr <[email protected]>
| A shape library is very similar to an OWL ontology and technically works in the same way. | ||
| In fact, we now use OWL ontologies because of inference from `owl:import`, but there was quite some discussion about whether the assembly of shapes is an ontology in the OWL sense. | ||
| For any large scale application of SHACL, it is necessary to modularize, and it felt like this was a serious gap in the specification. | ||
| - [Imports](https://rawgit2.com/VladimirAlexiev/shacl/shaclc-grammars/shacl-compact-syntax/grammar/shaclc-XText.html#ImportsDecl) (how is this different from `owl:imports`?) |
There was a problem hiding this comment.
Looking at the example, this is exactly translated to owl:imports. Nothing more...
No description provided.