Agenda-2010-06-30



Call in details

• Date of Call: Tuesday June 30, 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: 120 minutes
• Chair: Axel Polleres
• Scribe: ??? (Scribe List)
• Link to Agenda: http://www.w3.org/2009/sparql/wiki/Agenda-2010-06-30

Agenda

Test Cases Teleconf

• Overall organisation of the test suite
  • Lee, can you recap/report briefly from DAWG experiences (I think we decided to go the same route, in the end)
• Manifest format
  • Axel's proposal
  • Andy's reminder on structure from DAWG
  • Shall we rather go with TriG for describing datasets?
• Collected Test Cases so far?
  • Aggregates
    • ACTION-191 Axel's proposed testcases
  • Subqueries
    • ACTION-192
    • ACTION-193 Olivier's test cases
  • Negation
    • ACTION-194 Chime's test cases
  • Project Expressions
    • ACTION-195 Olivier's test cases
    • ACTION-196
  • Property Paths
    • ACTION-198 Olivier's proposed test cases
  • Entailment
    • ACTION-199
• What's missing?
  • Update
  • Protocol
  • http-update-protocol
  • service description
  • federated query
• Is this overall structure ok for creating separate manifests? Shall we have one responsible overall, or several responsibles (one for each manifest/category)?
• Suggest to bring a standard agenda item to the weekly agenda to approve/discuss new test cases, collect any test cases that appeared in mail conversations
• Implementation status? How can implementations run the testsuite?

Regrets