Skip to content

Where should "Potential definition in SPARQL" go? #271

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.

Sign up for GitHub

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

Jump to bottom
Closed
bergos opened this issue Feb 24, 2025 · 1 comment
Closed

Where should "Potential definition in SPARQL" go? #271

bergos opened this issue Feb 24, 2025 · 1 comment
Assignees
@HolgerKnublauch
Labels
Core For SHACL 1.2 Core spec Editorial (would not change implementations) SPARQL For SHACL 1.2 SPARQL extensions spec
Milestone
Phase 1

Comments

@bergos
Copy link
Contributor

bergos commented Feb 24, 2025

We want to remove the "Potential definition in SPARQL" in the core specification, but there is interest in keeping them elsewhere. A new location needs to be found. See #235
@bergos bergos mentioned this issue Feb 24, 2025
Closed
@HolgerKnublauch
Copy link
Contributor

They could become an appendix in the SHACL-SPARQL document.

@HolgerKnublauch HolgerKnublauch added Core For SHACL 1.2 Core spec SPARQL For SHACL 1.2 SPARQL extensions spec labels Mar 3, 2025
@HolgerKnublauch HolgerKnublauch self-assigned this Mar 3, 2025
HolgerKnublauch added a commit that referenced this issue Mar 3, 2025
@HolgerKnublauch
#271: Moved SPARQL definitions from Core into an appendix of SHACL-SP…
995c626 
…ARQL
HolgerKnublauch added a commit that referenced this issue Mar 4, 2025
@HolgerKnublauch
#271: Added TODO for node expressions
0e6202b
@nicholascar nicholascar added this to the Phase 1 milestone Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@HolgerKnublauch HolgerKnublauch

Labels
Core For SHACL 1.2 Core spec Editorial (would not change implementations) SPARQL For SHACL 1.2 SPARQL extensions spec
Projects
None yet
Milestone
Phase 1
Development

No branches or pull requests
3 participants
@bergos @HolgerKnublauch @nicholascar