#1174: WG Revision: SHACL 1.2 SPARQL
Discussions
Log in to see TAG-private discussions.
Discussed
Dec 8, 2025 (See Github)
Skipped
Discussed
Jan 19, 2026 (See Github)
Sarven: Review SHACL 1.2 Core. I'll do this next.
Discussed
Jan 26, 2026 (See Github)
Sarven: https://github.com/w3ctag/design-reviews-private-brainstorming/issues/229#issuecomment-3797145530
Sarven: They're splitting the core part from the extensions (SHACL). The changelog didn't show anything new, so looks like it is just a re-org. SHACL will be an optional extension. In and of itself there don't seem to be any new normative requirements.
Martin: Did you confirm with them?
Sarven: Not yet
Martin: May be worth making that the review - doesn't look like any changes, but checking with them.
Hadley: If that is the sum-total of what they have done, I don't have an opinion.
Sarven: Will add a sentence as suggested, but will go ahead.
Hadley: Think so, but maybe don't conclude the review until they've come back to confirm. You could just put the question in first.
Sarven: Will check on the re-shuflling and open up the question for them.
Comment by @csarven Jan 29, 2026 (See Github)
The TAG thanks the Data Shapes WG for requesting this review.
The TAG notes that separating the SPARQL parts from SHACL Core is a reasonable direction to simplify implementations and testing, while also supporting future extensibility of SHACL extensions. Based on the change history, no new features or normative changes affecting web architecture were noted, so a full TAG review is not required at this time. If there are however significant changes that the WG would like TAG's review on, we'd be happy to.
Discussed
Feb 2, 2026 (See Github)
Sarven: We responded, no feedback from the group.
Sarven to close.
OpenedDec 1, 2025
Specification
https://w3c.github.io/data-shapes/shacl12-sparql/
Explainer
https://w3c.github.io/data-shapes/shacl12-overview/#whatsnew
Links
Feature 1:
Cleaner Separation between Core and SPARQL
We now have a cleaner separation of Core and SPARQL concerns into separate specifications. This helps indicate SHACL Core is not dependent on SPARQL, clarify other dependencies, and make some implementations easier.
The specification
Where and by whom is the work is being done?
Feedback so far
You should also know that...
No response
<!-- Content below this is maintained by @w3c-tag-bot -->Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1174