Skip to content

SHACL-SHACL Note #303

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 15 commits into
base: gh-pages
Choose a base branch
from
Open

SHACL-SHACL Note #303

wants to merge 15 commits into from

Conversation

nicholascar
Copy link
Contributor

@nicholascar nicholascar commented Mar 5, 2025

This is the intended WG NOTE that will introduce and point to the SHACL-SHACL validator - the RDF asset.

Closes #289

@nicholascar nicholascar self-assigned this Mar 5, 2025
@nicholascar nicholascar marked this pull request as draft March 5, 2025 03:25
Copy link
Contributor

@HolgerKnublauch HolgerKnublauch left a comment

Choose a reason for hiding this comment

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

The PR could also remove the appendix shacl-shacl from SHACL 1.2 Core, currently starting at https://github.com/w3c/data-shapes/blob/gh-pages/shacl12-core/index.html#L4258

@PapoutsoglouE
Copy link

I will echo what someone (@ajnelson-nist?) mentioned in the last meeting: I think it may be good to include the intended governance mechanism for the SHACL-SHACL file too.

@nicholascar
Copy link
Contributor Author

Agree with the points in comments above: we will remove the Core SHACL-SHACL from Core and include governance.

nicholascar and others added 2 commits March 17, 2025 13:07
@nicholascar nicholascar marked this pull request as ready for review April 7, 2025 12:20
Copy link
Contributor

@ajnelson-nist ajnelson-nist left a comment

Choose a reason for hiding this comment

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

I just have one question I'd like resolved before I log an Approve, on the scope of SHACL-SHACL: Limited to Core, or instead covering all SHACL concepts?

There are also a few minor typos, but I forget how much trouble it causes if I hit "Request changes," so will just trust those will be addressed.

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
@nicholascar
Copy link
Contributor Author

I just have one question I'd like resolved before I log an Approve, on the scope of SHACL-SHACL: Limited to Core, or instead covering all SHACL concepts?

I think, for simplicity, we should include all validation of all Recommendations' SHACL within the since SHACL-SHACL deliverable.

If someone is using only SHACL Core then the validation of non-Core shapes simply won't apply to them.

There are also a few minor typos, but I forget how much trouble it causes if I hit "Request changes," so will just trust those will be addressed.

I've fixed one and the others can be fixed post initial release.

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.

Create a SHACL-SHACL WG Note
6 participants