Hello, W3C Data Access Working Group works on new, extended version of SPARQL language and protocol specs and accumulates feature requests (as well as critics of features proposed already). The wish list is filled in by members of the working group, the current state is visible at http://www.w3.org/2009/sparql/wiki/Category:Features http://www.w3.org/2009/sparql/wiki/Proposed_Language_and_Protocol_Extensions http://www.w3.org/2009/sparql/wiki/Extensions_Proposed_By_OpenLink (sorry for the mess, that's work in progress)
Please send your wishes to me. Of course, if you've got a similar invitation from some other member of WG then you have a choice. At the same time LeeF and ericP can be too occupied by other things so it may be impractical to invoke them into this communication. It would be nice if feature requests are backed by candidate use cases. The deadline is March-09, as group members should reformat and submit everything March-10. Important privacy note. Please note that I'm doing that in favor of W3C Data Access Working Group, not as a person. E-mails and other communications re. SPARQL feature requests can be made public as a whole or in parts without requesting permissions of parties. If you want to keep some discussion private, please state that _in_advance_ (and don't use this mailing list ;) Best Regards, Ivan Mikhailov OpenLink Software http://virtuoso.openlinksw.com On Tue, 2009-03-03 at 20:24 -0500, Lee Feigenbaum wrote: > executive summary: > > 1 - put proposed features on the wiki _this week_ > -----8<----- > 3 - feel free to solicit features from people outside the WG > > full story: > > On today's teleconference, we agreed to frame our survey of potential > deliverables in terms of "features" (which can be motivated by use > cases) rather than in terms of "use cases" (which could cover one or > more features). > > We ran out of time at the end of the teleconference, but the bottom line > is that we are setting a deadline of _next week, March 10_ for SPARQL WG > members to post potential features onto the wiki. > > That's a quick turnaround time, but we need to get started discussing > features and narrowing down our possibilities as soon as possible. > > I will be announcing this shortly in a few public fora to encourage > community members to suggest features that are important to them. Please > feel free to similarly solicit feedback from outside the working group. > > -----8<----- > > 2a) If the feature already has a page, feel free to add to the page with > new examples or implementation information. > -----8<----- > 2b) If the feature does not have a page, create a new one > -----8<----- > 6) Fill in the details, including > a) summary & description - what capability does the feature add? > b) example of what the feature might look like (i.e. syntax) > c) info on existing implementations > d) info on existing specification/documentation materials > e) any issues with backwards compatibility > f) links to any related postponed issues from DAWG > g) links to any related features > h) potential people/organizations that would champion/advocate for > the feature > i) short use cases that motivate addition of this feature to SPARQL > j) any other reference material > > Of course, you need not fill in all of this, but the more fleshed out a > feature is, the easier it will be for the WG to evaluate it and decide > on its merits. > -----8<----- > Feel free to email the list or me with any questions / comments. > > Lee
