-
Notifications
You must be signed in to change notification settings - Fork 0
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
consider reintroducing property paths {x,y}
syntax dropped in SPARQL 1.1
#147
Comments
I'm definitely in favor of this functionality, but I don't think it's in scope for this WG, and should probably be deferred to the next (maintenance) WG. |
I agree with @rubensworks. I think it's a proposal for SEP https://github.com/w3c/sparql-dev |
{x,y}
syntax dropped in SPARQL 1.1 draft https://www.w3.org/TR/2012/WD-sparql11-query-20120724{x,y}
syntax dropped in SPARQL 1.1
+1 to @rubensworks |
Adding label "ms:future-work". ("ms:" is 'milestone' - the "ms:" labels are WG phasing). |
This was discussed during the #rdf-star meeting on 05 December 2024. View the transcriptConsider reintroducing property paths {x,y} syntax dropped in SPARQL 1.1 1tallted: delay to future work <pchampin> Tpt: I'm confused also because this is much less an errata than the EXIST feature, on which we are having scope-discussion AndyS: agree to postpone <pchampin> + 1 gkellogg gregg: 1.2 specs marked new features ... so not 1.3 ktk: At this point we say "later" and no "when" ora: OK? (agreement by silence) <gkellogg> +1 to future-work. AndyS: I will clear-up the GH issue after the meeting <ora> PROPOSAL: postpone to future work, after main RDF&SPARQL 1.2 are complete <pchampin> +1 <AZ> +1 <ora> +1 <gkellogg> +1 <TallTed> +1 <Tpt> +1 <tl> +1 <doerthe> +1 <AndyS> +1 <james> +1 <gtw> +1 <ktk> +1 <olaf> +1 <niklasl> +1 <gb> Issue 41 Allow dataset formats to be valid in LOAD with no INTO (by afs) [Errata] [needs discussion] [spec:enhancement] pchampin: (wrong link) <gkellogg> w3c/sparql-update#147 <gb> Issue 147 not found <gkellogg> w3c/sparql-query#147 <gb> Issue 147 consider reintroducing property paths `{x,y}` syntax dropped in SPARQL 1.1 (by TallTed) [ms:future-work] [needs discussion] [spec:enhancement] RESOLUTION: postpone w3c/sparql-query#147 to future work, after main RDF&SPARQL 1.2 are complete |
The WG resolved
|
see draft SPARQL 1.1 spec of 2012-07-24
This comes up regularly. Many actually believe this syntax remains an official part of SPARQL, possibly because some engines (including Virtuoso) never dropped it, after implementing during SPARQL 1.1 development.
See (and perhaps transfer) w3c/sparql-dev#101.
The text was updated successfully, but these errors were encountered: