Agenda - 22 May 2007 @ 14:30 UTC

Onwards to tests, implementation reports, and fun goodies like that.

hope to see everyone (modulo Elias, Chimezie, and Jeen) tomorrow.

If anyone has input on the points below, email discussion before and after 
the telecon is always in order :)


Note: The meeting is still at 14:30 UTC. Please make sure to check that 
you're attending at the right time: 

0. Convene [1]RDF Data Access WG meeting of Tuesday, 15 May 2007
at 14:30:00 UTC
         + LeeF chairing
         + teleconference bridge: tel:+1.617.761.6200 
tel:+ tel:+44.117.370.6152 code:7333
           Note that Zakim is back up and running, so we'll be using it 
for our telecon.
         + on irc at: irc://
         + Scribe: @@
         + Regrets: EliasT, Chimezie, Jeen
         + roll call
         + approve 
           + 1 May minutes [2]
           + 8 May minutes [3]
           + 15 May minutes [4]
         + next meeting 29 May. @@ recruit scribe
         + agenda comments?

1. Review ACTION Items

These actions appear DONE:

Let's check on the status of the following actions:

ACTION: ericP to poke IETF folks about registering SPARQL media types 
(esp. application/sparql-query)
ACTION: EricP to run the yacker tool over and annotate the existing tests
ACTION: ericP to get in touch with SteveH re: setting up an environment to 
generate an Overview page for tests in data-r2 a la
ACTION: ericP, jeen, or LeeF to update with info on possible 
results format and on changes to manifest and test vocabularies
ACTION: ericP to write a test showing that langMatches doens't do extended 

ACTION: LeeF to add `chimezie's leading digit test to the test suite
ACTION: LeeF to remember that the wee, lost filter tests should be put 
[recorded in]
ACTION: LeeF to mark the 4 regex tests approved

2. CR publication status

(From Lee.)

3. XML and JSON Results Format publication status

(From Eric.)

4. Implementation report

Discussions of EARL and alternatives; consensus was that we should try to 
use EARL for implementation report.


Our CR exit criteria is to have two implementations of each feature. 

+ Eric has a tool that identifies "features" as parts of the grammar. 
Eric: how much manual massaging of the resulting list of features needs to 
be done?
+ Similarly, Eric can classify existing tests as to which features they 
cover. Is there a way to produce a summarized view of the coverage of our 
test suite?
+ We'd like to capture implementations results as EARL. Can someone 
produce an example of this output? Do we require implementations to 
produce the EARL output, or will we take other formats and generate the 
EARL ourselves?
+ How do we want to visually represent the implementation report?

5. Testing

5a. Query Language

Let's keep moving tests over and approve them, hopefully in conjunction 
with monitoring test coverage. 

5b. Protocol

Elias sends his regrets, but says that protocol testing is on his radar. 
Let's find out if anyone else is interested in working with him on that. 


Received on Monday, 21 May 2007 20:41:24 UTC