To Last Call
From SPARQL Working Group
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.
Contents |
Query
WG issues & needed decisions
- Freeze grammar
Editorial tasks
- General editing (Andy)
- General editing (Steve)
- 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)
Pre-LC Reviewers
- Axel
- Matt
- Birte
- Lee
Update
WG issues & needed decisions
Editorial tasks
- MIME type registration
- UPDATE shortcuts to be added and marked "At Risk"
Pre-LC Reviewers
- Andy
- Greg
Protocol
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.
Ready for review!
WG issues & needed decisions
-
Availability of an unnamed graph -- proposal to resolve this? [Greg: I don't recall specifics of this issue, and there's basically no details in the email history of the issue. I believe the current modeling gives us all the "unnamed graphs" (default graphs?) we need, but if anyone has more specific thoughts, please let me know.]
Editorial tasks
- Align links and text with protocol document (Greg, Lee) - note dependency on protocol here
-
Add feature URI for basic federated queries
Pre-LC Reviewers
- Lee
- Nico
Uniform HTTP Protocol
Uniform HTTP protocol editor's draft.
Pre-LC Reviewers
- Andy
- SteveH
- NickH
Entailment
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
- someone from Oracle (Matt to decide)
Federated Query
Federated query editor's draft.
WG issues & needed decisions
- Clarify optional nature of feature -- proposal to resolve this?
- Question regarding description of semantics in document: which notation to use? any comments wo what it is written there?
- behavior in presence of errors - silent vs error (open WG discussion)
Editorial tasks
Pre-LC Reviewers
- Axel
- Lee
JSON Results
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
Editors happy to go directly to LC (no immeditate internal review needed)
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
