To Last Call

From SPARQL Working Group

Revision as of 03:10, 8 February 2011

This page is for the SPARQL WG to record issues to be resolved and tasks to be completed before documents are ready for Last Call.

Query

Query editors' draft.

WG issues & needed decisions

• Freeze grammar

Editorial tasks

WG Process:

• See SPARQL_Namespaces : Update page at the namespace URI of SPARQL functions
• Boilerplate text for suite of SPARQL docs.

Query doc:

• Property paths discussions (Andy)
• Syntactic constraints (Andy)
• Check "Testing values" => "Expressions and Testing Values" (Andy)
• General editing (Steve)
• General editing (Andy)
• CONSTRUCT WHERE short form (Andy)
• Library sections on numerics, datetimes and hash functions.(Andy)
• MIME type registration for application/sparql-query
• Names for ENDS/STARTS [DONE: now STRSTARTS/STRENDS]
• ACTION-209: Steve to Disallow projected variables being reused in HAVING in the spec (Steve)
• ACTION-328: Steve to Implement the common understanding in ListEval() on unbound treated like errors (Steve)
• ACTION-331: Andy to Clarify the meaning of "potentially bound" vis a vis what can go on the right hand side of an AS in a SELECT list (Andy) See Variable Scope
• Incorporate function library test (Axel/string functions) All function text now written (Andy)
• SERVICE SILENT in grammar (Andy)
• Add section on BINDING

Pre-LC Reviewers

• Axel
• Matt
• Birte
• Lee

Update

Update editors' draft.

WG issues & needed decisions

• Check Grammar with modify_template (Paul / see below)
• Formal model: Reviewer comments [1] [2] and comments from Ross Horne (?)
• DELETE and graph_triples contains bnodes (comment 23b of that email) (Paul)
• blank node in a delete template (comment 27 of that email) (Paul)

Editorial tasks

• INSERT/DELETE vs INSERT vs DELETE (Alex)
• modify_template (Paul)
• sequence of operations (Alex)
• Clarification on WITH / WHERE (comment 25 and 26 of that email) (Paul)

Pre-LC Reviewers

• Andy
• Greg

Protocol

Protocol editors' draft.

See summary of protocol open issues and recommendations.

Issues

• JSON-P support? (c.f. CORS, which should make this unnecessary in the future(?)) Co-ordinate with JSON results format.

Pre-LC Reviewers

• Andy
• Carlos

Service Description

Service description editor's draft.

Reviews received; awaiting editor's response.

WG issues & needed decisions

• Availability of an unnamed graph

• <s>Lee (ACTION-355)
• Nico (ACTION-356)

RDF Dataset HTTP Protocol

RDF Dataset HTTP Protocol editor's draft.

Ready for review

Pre-LC Reviewers

• Andy -- Review
• SteveH (ACTION-381)
• NickH (ACTION-382)

Entailment

Entailment editors' draft.

Ready for review!

WG issues & needed decisions

• Should we incude an entailment regime for OWL with non-distinguished variables and no result bnodes?

Editorial tasks

Pre-LC Reviewers

• Kendall & colleagues (ACTION-361)
• Zhe Wu -- Oracle (ACTION-362)

Federated Query

Federated query editor's draft.

WG issues & needed decisions

• behavior in presence of errors - silent vs error (open WG discussion)
• Clarify optional nature of feature -- proposal to resolve this?

Editorial tasks

• Address comments from Andy

Pre-LC Reviewers

Reviewers are asked to comment specifically on the two approaches of presenting the semantics within the document.

• Axel (ACTION-384)
• Lee (ACTION-385)

JSON Results

http://www.w3.org/2009/sparql/docs/json-results/rdf-sparql-json-res.html

Ready for review

WG issues & needed decisions

• Greg's action to identify issues. (Done)
• JSON-P support

JSON-P

Principally a protocol decision (c.f. CORS) . If WG decides it wants JSON-P support in the protocol then mention in JSON result format.

Editorial tasks

Pre-LC Reviewers

• Comments to deal with:
  • MH-2
  • RC-1
  • Paul's WG comments

Overview document

• Add whole working group as editors (a la OWL Overview Doc) (Axel)
• reduce examples (Axel)
• ACTION-290: Lee to Make sure that the relationship between SPARQL protocol and HTTP protocol is clearly laid out before Last Call