See also: IRC log
<LeeF> ericP, make it to a phone yet?
<LeeF> SteveH, planning on calling in?
<SteveH> LeeF, I can if there's a good reason
<SteveH> LeeF, what's on the cards for today?
<LeeF> Main thing I was going to ask you is if you have any sort of timetable for test suite results from JXT?
<SteveH> LeeF, yeah, nowish, I was considering dialing in v's updating my EARL output...
<SteveH> infact I was going to ask where's a good sample to crib from
<LeeF> only other question is interest-level on the protocol
<LeeF> Andy's is probably a good place to crib from
<SteveH> we don't currently use the protocol, but our next product will use it in a big way
<SteveH> cool, cheers
<LeeF> might be worth you dialing in then :-)
<SteveH> ok, has it started?
<SteveH> so did I, but a while ago :)
<AndyS> I only have CSS-ish stuff for rq25
<AndyS> + some wording tweaks from comments.
<LeeF> EliasT, joining?
<EliasT> yes coming...
<EliasT> good timing
<LeeF> <group agreement that no energy to extend charter beyond November>
<LeeF> SteveH: will be using HTTP protocol bindings in the future
<LeeF> LeeF: What would people in the WG like for the future of the protocol?
<LeeF> SteveH: Would be happy with it as a Note
<LeeF> LeeF: What is the status of the test materials for the protocol?
<LeeF> EliasT: We parsed the spec for examples
<LeeF> ... verify that the queries were correct
<LeeF> ... every example in the spec has a manifest that describes the operation
<LeeF> AndyS: (earlier) I think we can at least show the HTTP bindings as interoperable through via discussion between implementors
<LeeF> tests extracted from spec are in ...proto-tests/data
<LeeF> python client is in .../proto-tests/tools
Elias's code for testing HTTP impls at http://www.w3.org/2001/sw/DataAccess/proto-tests/tools/
plan: Lee to solicit endpoints
that claim to do HTTP or SOAP bindings of the protocol
... elias to work to be able to run the python code to test HTTP impls
<AndyS> SPARQL endpoint / Joseki
plan: andy to see if his code can
be resuscitated to test SOAP endpoints
... orri and ivan to see how much work it would be to use their SOAP client to test SOAP endpoints
ericP: have a few uncomitted
... need to figure out Jeremy's changes re: EBV of an invalid literal
<AndyS> Eric - when you done your changes, ping me and I'll do the last of mine (CSS-ish stuff - one comment rewording)
Orri and SteveH will try to look at diffs between CR text and CR text + editorial changes over the next few weeks
<scribe> ACTION: Orri and Ivan to try the results XML schema and report back the results [recorded in http://www.w3.org/2007/08/28-dawg-minutes.html#action01]
<scribe> ACTION: EricP to publish xml format CR pending OK of the results schema [recorded in http://www.w3.org/2007/08/28-dawg-minutes.html#action02]
<AndyS> from http://www.w3.org/2001/sw/DataAccess/proto-wd/ (sec 2)
-> http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2007Aug/0014.html SPARQL WSDL Problems
-> http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JulSep/0100.html EricP with initial implementation report work
<SteveH> JXT EARL results: http://plugin.org.uk/misc/earl.ttl
<SteveH> feedback on goodness welcome
<scribe> ACTION: LeeF to advertise existence of test materials and solicit implementation reports [DONE] [recorded in http://www.w3.org/2007/08/28-dawg-minutes.html#action03]
<scribe> ACTION: LeeF to generate archive of test materials which includes license [DONE] [recorded in http://www.w3.org/2007/08/28-dawg-minutes.html#action04]
<scribe> ACTION: EliasT to come up with feature list for protocol testing [DONE] [recorded in http://www.w3.org/2007/08/28-dawg-minutes.html#action05]
<scribe> ACTION: Eric+Andy to identify and collect mf:requires URIs and put in documentation [CONTINUES] [recorded in http://www.w3.org/2007/08/28-dawg-minutes.html#action06]
<scribe> ACTION: ericP to answer "EBV of invalid numeric literals" email from Arjohn [CONTINUES] [recorded in http://www.w3.org/2007/08/28-dawg-minutes.html#action07]
<scribe> ACTION: ericP to incorporate text to fix EBV of illformed numeric literals bug in spec [CONTINUES] [recorded in http://www.w3.org/2007/08/28-dawg-minutes.html#action08]
<scribe> ACTION: ericP to poke IETF folks about registering SPARQL media types (esp. application/sparql-query) [CONTINUES] [recorded in http://www.w3.org/2007/08/28-dawg-minutes.html#action09]
<scribe> ACTION: ericP to write explanatory text saying that, like xsd:inteter and xsd:dateTime, the relative order of simple literals and xsd:strings is not defined here [CONTINUES] [recorded in http://www.w3.org/2007/08/28-dawg-minutes.html#action10]
<scribe> ACTION: LeeF to solicit endpoints for HTTP and SOAP implementations of the SPARQL protocol [recorded in http://www.w3.org/2007/08/28-dawg-minutes.html#action11]
<iv_an_ru> I'm sorry for being late, I'm experiencing a hardware problem.
np, iv_an_ru - I believe that Orri has some stuff to talk about with you in the wake of today's meeting
ericP, AndyS - I think I know what must have changed
we republished the XML Result format
as a Last Call
we might have clobbered the good versions of files?
I will try to dig into that (see Petr's stack trace which references http://www.w3.org/TR/rdf-sparql-XMLres/result2.xsd )
and that one also references xsi.xsd
I am guessing the difference is between result2.xsd in the proto-wd dir. and in the rf1 dir
but not sure how else they relate
this needs some looking into...
This is scribe.perl Revision: 1.128 of Date: 2007/02/23 21:38:13 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: LeeF_ Inferring Scribes: LeeF_ Default Present: AndyS, LeeF, Orri_Erling, SteveH, EliasT, EricP Present: AndyS LeeF Orri_Erling SteveH EliasT EricP Regrets: IvanM Souri Chimezie Agenda: http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JulSep/0098.html Got date from IRC log name: 28 Aug 2007 Guessing minutes URL: http://www.w3.org/2007/08/28-dawg-minutes.html People with action items: andy eric ericp ivan leef orri[End of scribe.perl diagnostic output]