RDF DAWG Weekly -- 2 Jan 2007

<LeeF> Scribe: SimonR

<AndyS> Ah = +44 number now. In Bristol as well.

<AndyS> I'll redial.

<LeeF> sort of :)

<LeeF> mostly not :)

Not in any structured way, no.

<LeeF> Dec 12 minutes: http://www.w3.org/2006/12/12-dawg-minutes

Meeting proper starting: 14:37

<LeeF> Dec. 19 minutes: http://www.w3.org/2006/12/19-dawg-minutes

Minutes from 12 Dec approved (seconded by AndyS)

Minutes from 19 Dex approved (also seconded by AndyS)

Convene

Review ACTION Items

I did my ACTION to check out the XML reporting format from xUnit: http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2007Jan/0000.html

PatH's ACTION to change the entailment text is DONE; others CONTINUE

Would this be an example: { _:a :p 1 } UNION { _:a :p 2 } -- because we can't have _a: be in the same scope between the two BGPs?

<LeeF> SimonR, might be, but I don't claim to be able to read Bob M's mind :-)

Test suite process

<AndyS> { _:a :p ?v . FILTER(?v = 1 || ?v = 2) }

<AndyS> but that is an easy one :-)

LeeF: Having second thoughts about leaving BobMcG's objection; would like at least one example of queries that can't be expressed.

EricP: Wrote down SPARQL's feature list, associated them with grammar productions -- can associate test cases with the features they exercise

Jeen: Thought that features were associated implicitly to tests by the way we group them, but if doing it explicitly is useful, sees no harm in it

<ericP> http://www.w3.org/2001/sw/DataAccess/tests/facets.ttl

<ericP> http://www.w3.org/2001/sw/DataAccess/tests/facets

<ericP> http://www.w3.org/2001/sw/DataAccess/tests/facets#WhereClause-noWhere

<ericP> :WhereClause-noWhere a test:DAWGfacet; test:order 17;

<ericP> rdfs:comment "WHERE^H^H^H { ... }";

<ericP> test:production "WhereClause";

<ericP> test:productionURI sparql:rWhereClause .

<ericP> :SelectQuery-star a test:DAWGfacet; test:order 9;

<ericP> rdfs:comment "SELECT *";

<ericP> test:production "SelectQuery";

<ericP> test:productionURI sparql:rSelectQuery;

<ericP> test:yaccProduction "_O_QVar_E_Plus_Or__QTIMES_E__C";

<ericP> test:rule "TIMES" .

<ericP> test#PrefixDecl

<ericP> test#SelectQuery-Var1

<ericP> test#GraphPattern-spo

<ericP> test#WhereClause-noWhere

<ericP> test#OrderCondition-rVar

<ericP> ...

<ericP> !?s ?p []

<ericP> !?x+?y

<ericP> !?x-?y

<ericP> http://tinyurl.com/ybxr85

ericP: Would like to annotate existing tests before migrating to new tests

(Sorry, mea culpa)

AndyS: If tests have a URI, then the detail about language features associated with tests can be put in a separate file -- they're really only of interest to the WG rather than external testers

EricP: Currently facets have URIs; tests don't yet. Inclined to drop the facets into the existing tests, and give tests URIs during the changeover

<scribe> ACTION: EricP to run the yacker tool over and annotate the existing tests [recorded in http://www.w3.org/2007/01/02-dawg-minutes.html#action01]

Jeen: Can make a start at some of the less controversial tests to get the process shaken down

EricP: Talked about using EARL as the reporting format; is Jeen interested in doing that?

Jeen: slightly reluctant since EARL is new and different from the current tests. What's the benefit?

<LeeF> ACTION: Jeen to get started setting up new test directory and picking some initial tests for the working group to approve on 9 Jan [recorded in http://www.w3.org/2007/01/02-dawg-minutes.html#action02]

<ericP> SimonR: JUnit exports an XML summary of passed and failed tests

<LeeF> SimonR: When JUnit runs it outputs an XML summary of the tests that failed and passed -- other tools can consume this XML (e.g. automated build tools)

<ericP> ... there are tools that provide summaries

<ericP> ... there are a couple other communities in python and maybe C++ that are using this

<ericP> ... hasn't become a (defacto) standard yet

<ericP> ... if you could query the EARL test reports, you could XSLT that to JUnit's xml format

<Zakim> AndyS, you wanted to ask if this Junit3 or Junit4 or both?

<ericP> AndyS: something we can look at?

<AndyS> can't find it at junit.org

<ericP> SimonR: no schema specified for JUnit

<ericP> LeeF: seems we wouldn't gain anything over EARL, so lets stick close to our roots

<ericP> SimonR: you can still XSLT to JUnit

<ericP> +1

LeeF: Defer discussing the algebra until Fred is available

<LeeF>

AndyS has the text to be added to the spec in order to enact the bnode/cardinality decision

Issue: punctuationSyntax

<LeeF>

LeeF: In this thread, agreed that could live without commas in the SELECT clause

EricP: Does LeeF see a path towards mandatory commas?

LeeF: Once SPARQL 1 is released, unlikely.

<LeeF> PROPOSED: To close http://www.w3.org/2001/sw/DataAccess/issues#punctuationSyntax issue, with no change (no commas in the SELECT list or ORDER BY list)

Seconded by EricP with no objections or abstentions

<LeeF> ACTION: LeeF to update the issues list marking http://www.w3.org/2001/sw/DataAccess/issues#punctuationSyntax closed [recorded in http://www.w3.org/2007/01/02-dawg-minutes.html#action03]

<jeen> (actually it was me seconding it)

Next meeting: Jan 9

(No scribe nominated yet)

Meeting adjourned at 15:30.

<LeeF> thanks for scribing, Simon! Do you have what you need to get a copy of the minutes to the WG?

Oops, yes I will.

Usually someone does the voodoo for me, but I might be able to figure it out with a bit of fiddling...

<LeeF> let's see

- DRAFT -

RDF DAWG Weekly

2 Jan 2007

Attendees

Contents

Convene

Review ACTION Items

Test suite process

Issue: punctuationSyntax

Summary of Action Items

Scribe.perl diagnostic output