Warning:
This wiki has been archived and is now read-only.
Agenda-2010-03-09
From SPARQL Working Group
Call in details
When joining please don't identify yourself verbally; instead, identify yourself to Zakim on IRC
- Date of Call: Tuesday March 09, 2010
- Time of Call: 15:00 UK, 10:00 (East US)
- Dial-In #: +1.617.761.6200 (Cambridge, MA)
- Dial-In #: +33.4.26.46.79.03 (France)
- Dial-In #: +44.203.318.0479 (UK)
- Participant Access Code: 77277# (SPARQ)
- IRC Channel: irc.w3.org port 6665 channel #sparql ([irc:irc.w3.org:6665/sparql])
- Web-based IRC (member-only): http://www.w3.org/2001/01/cgi-irc (Firefox IRC addon: chatzilla)
- Duration: 60 minutes
- Chair: Lee Feigenbaum
- Scribe: Souri (Scribe List)
- Link to Agenda: http://www.w3.org/2009/sparql/wiki/Agenda-2010-03-09
Agenda
- Admin
- PROPOSED: Approve minutes at http://www.w3.org/2009/sparql/meeting/2010-03-02
- Next meeting: 2010-03-16 @ 14:00 UK / 10:00 EST (scribe: Matt) - NOTE ONE HOUR EARLIER THAN USUAL OUTSIDE OF THE US
- Comment handling - see http://www.w3.org/2009/sparql/wiki/Comments
- Liaisons - Is there anything to report of relevance to the SPARQL WG?
- RIF WG (Sandro)
- RDB2RDF WG (Orri)
- eGov (Sandro)
- Update - open issues
- ISSUE-51 Shall dataset clauses be allowed in SPARQL/Update?
- See Lee's message at http://lists.w3.org/Archives/Public/public-rdf-dawg/2010JanMar/0165.html and surrounding thread & links
- Blank nodes in DELETE
- See http://lists.w3.org/Archives/Public/public-rdf-dawg/2010JanMar/0428.html & surrounding thread
- Decide between two proposals:
- 1. No blank nodes in DELETE template
- 2. Blank nodes in DELETE templates act as "wild cards"--effectively variables pre-bound to all RDF terms
- ISSUE-51 Shall dataset clauses be allowed in SPARQL/Update?
- Protocol - open issues
- Dataset for update - currently the spec allows a dataset to be defined for an update operation. This needs to be brought in line with the Update specification.
- This probably follows pretty directly from the resolution of the update dataset operation.
- Update fault types - what faults should be defined for update?
- See Andy's message of http://lists.w3.org/Archives/Public/public-rdf-dawg/2010JanMar/0432.html -- Does it even make sense to have more than 2 faults when the protocol is mainly bound to HTTP?
- MalformedUpdate (a la query)
- UpdateRequestRefused (a la query)
- GraphDoesNotExist
- GraphAlreadyExists
- See Andy's message of http://lists.w3.org/Archives/Public/public-rdf-dawg/2010JanMar/0432.html -- Does it even make sense to have more than 2 faults when the protocol is mainly bound to HTTP?
- Dataset for update - currently the spec allows a dataset to be defined for an update operation. This needs to be brought in line with the Update specification.
- To Last Call
- HTTP Update Protocol (next week?)
- Property Paths (next week?)
- Query
- Entailment
Regrets
- Sandro
- Chimezie
- Paul