15:58:10 RRSAgent has joined #rdf-wg 15:58:10 logging to http://www.w3.org/2013/01/09-rdf-wg-irc 15:58:12 RRSAgent, make logs world 15:58:12 Zakim has joined #rdf-wg 15:58:14 Zakim, this will be 73394 15:58:14 ok, trackbot; I see SW_RDFWG()11:00AM scheduled to start in 2 minutes 15:58:15 Meeting: RDF Working Group Teleconference 15:58:15 Date: 09 January 2013 15:58:19 AZ has joined #rdf-wg 15:58:21 davidwood has joined #rdf-wg 15:58:34 yvesr has joined #rdf-wg 15:58:41 zakim, who is here? 15:58:41 SW_RDFWG()11:00AM has not yet started, Guus 15:58:43 On IRC I see yvesr, davidwood, AZ, Zakim, RRSAgent, gkellogg, danbri, SteveH_, AndyS, trackbot, Guus, ivan, gavinc, manu1, manu, mischat, sandro, ericP 15:59:18 zakim, code? 15:59:18 the conference code is 73394 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), AndyS 15:59:53 markus has joined #rdf-wg 16:00:21 zakim, who is on the phone? 16:00:21 SW_RDFWG()11:00AM has not yet started, AndyS 16:00:22 On IRC I see markus, yvesr, davidwood, AZ, Zakim, RRSAgent, gkellogg, danbri, SteveH_, AndyS, trackbot, Guus, ivan, gavinc, manu1, manu, mischat, sandro, ericP 16:00:40 zakim, who is on the phone? 16:00:40 SW_RDFWG()11:00AM has not yet started, AndyS 16:00:41 On IRC I see markus, yvesr, davidwood, AZ, Zakim, RRSAgent, gkellogg, danbri, SteveH_, AndyS, trackbot, Guus, ivan, gavinc, manu1, manu, mischat, sandro, ericP 16:00:47 zakim, who is here? 16:00:47 SW_RDFWG()11:00AM has not yet started, Guus 16:00:48 On IRC I see markus, yvesr, davidwood, AZ, Zakim, RRSAgent, gkellogg, danbri, SteveH_, AndyS, trackbot, Guus, ivan, gavinc, manu1, manu, mischat, sandro, ericP 16:00:50 I can hear andy... 16:01:03 Arnaud has joined #rdf-wg 16:01:57 zakim, who is on the phone? 16:01:57 SW_RDFWG()11:00AM has not yet started, yvesr 16:01:58 On IRC I see Arnaud, markus, yvesr, davidwood, AZ, Zakim, RRSAgent, gkellogg, danbri, SteveH, AndyS, trackbot, Guus, ivan, gavinc, manu1, manu, mischat, sandro, ericP 16:02:54 zakim, this is rdf 16:02:54 ok, Guus; that matches SW_RDFWG()11:00AM 16:03:03 +??P6 16:03:07 Zakim, who's on the phone? 16:03:07 On the phone I see +31.20.598.aaaa, ??P11, [IPcaller], +081165aabb, ??P26, ??P12, Arnaud, ??P6 16:03:13 zaki, ??P6 is me 16:03:16 zakim, IPcaller is me 16:03:16 +AndyS; got it 16:03:17 zakim, ??P6 is me 16:03:18 +markus; got it 16:03:22 zakim, I am ??P11 16:03:22 +gkellogg; got it 16:03:27 zakim, +31.20 is me 16:03:27 +Guus; got it 16:03:34 Zakim, ??P26 is me 16:03:34 +SteveH; got it 16:04:01 Zakim, +081165aabb is me 16:04:01 +AZ; got it 16:04:18 cgreer has joined #rdf-wg 16:04:30 zakim, who is here? 16:04:30 On the phone I see Guus, gkellogg, AndyS, AZ, SteveH, ??P12, Arnaud, markus 16:04:32 On IRC I see cgreer, Arnaud, markus, yvesr, davidwood, AZ, Zakim, RRSAgent, gkellogg, danbri, SteveH, AndyS, trackbot, Guus, ivan, gavinc, manu1, manu, mischat, sandro, ericP 16:04:34 + +1.707.874.aacc 16:04:41 zakim, aacc is me 16:04:41 +cgreer; got it 16:05:06 Zakim, ??P12 is me 16:05:06 +yvesr; got it 16:06:02 +[GVoice] 16:06:25 Zakim, [GVoice] is me 16:06:25 +ericP; got it 16:06:40 scribenick: cgreer 16:07:13 topic: admin 16:07:31 resolved: minutes accepted from last meeting 16:07:56 topic: open actions 16:09:21 Topic: Turtle 16:09:23 +Sandro 16:09:28 zakim, dial ivan-voip 16:09:28 ok, ivan; the call is being made 16:09:29 +Ivan 16:09:41 (Ivan and I were in another meeting, sorry) 16:10:05 Guus: We have three open issues still for Turtle. First is ISSUE-95. 16:11:02 @ericp: I need to keep this in mind and follow up. I spoke with the commenter, who reluctantly agreed... to accept the resolution without overt happiness. 16:11:54 RESOLVED: minutes of 19 Dec telecon accepted http://www.w3.org/2011/rdf-wg/meeting/2012-12-19 16:12:34 Guus: Second open issue for Turtle, ISSUE-100. 16:14:12 Sandro: I think the spec is just fine, and there's not enough information in the issue. 16:14:17 is it related to ACTION-191: Add escaping to Turtle in HTML? 16:15:46 action-191? 16:15:46 ACTION-191 -- Gavin Carothers to add escaping to Turtle in HTML -- due 2012-10-17 -- OPEN 16:15:46 http://www.w3.org/2011/rdf-wg/track/actions/191 16:16:36 @erikp: Trying to understand a document with several graphs embedded in it implicitly. 16:16:49 gkellogg: I put everything I find into the default graph 16:17:13 gkellogg: I even look for microdata when searching for RDFa and include that. 16:17:30 s/@erikp/@ericP/ 16:17:52 Guus: So we need to add some links to this issue description and close it. 16:18:01 + +1.408.992.aadd 16:18:37 Guus: It's still on Gavin's plate for ACTION-191 16:18:49 Subtopic: Well-formed lists 16:19:09 Sandro: I know this one, and it has nothing to do with turtle. 16:19:26 Souri has joined #rdf-wg 16:19:34 Sandro: It's a general RDF issue, with implications for turtle. 16:19:50 + +1.603.897.aaee 16:19:59 zakim, aaee is me 16:19:59 +Souri; got it 16:20:12 @ericp: Are there type constraints for well-formed lists? 16:20:12 Sorry - in a noisy airport and can't get a good connection. Will try to monitor, though. Please IRC me directly if you would like my attention. 16:20:15 pfps has joined #rdf-wg 16:20:24 Sandro: My proposal is to defined well-formed lists as what turtle does here. 16:20:31 sandro: this is based on turtle, no affecting turtle 16:20:52 Guus: This in other words doesn't affect turtle. 16:21:12 i think http://www.w3.org/mid/20130109161231.GD30410@w3.org closes ISSUE-95 16:22:15 @ericp: The feature at risk, second bullet point in http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jan/0025.html 16:22:35 @ericp: Assuming I know what the feature at risk is, I think it's not an issue. 16:22:51 Guus: So we need a new resolution about what 'at risk features' are. 16:23:07 cgreer, there should not be a "@" before "ericp" in scribing.... 16:23:57 Guus: We'll look for a grammar resolution that resolves conflicts. 16:24:06 ericp: And we did that before publication. 16:24:19 +PatH 16:24:21 +GavinC 16:24:30 GRRRRRRRRRRRRR. Stupid css "Feature at Risk" means I can't search for them. 16:25:15 Sandro: Can I propse we not use CSS for "feature at risk?" 16:25:26 s/propse/propose 16:25:28 PatH has joined #rdf-wg 16:25:40 zakim, mute me 16:25:40 PatH should now be muted 16:27:09 action: ericP change the AtRisk styling to allow searching documents for the words "feature" and "risk" to find Features At Risk 16:27:09 Created ACTION-220 - Change the AtRisk styling to allow searching documents for the words "feature" and "risk" to find Features At Risk [on Eric Prud'hommeaux - due 2013-01-16]. 16:27:57 https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#sec-grammar-grammar 16:29:32 Guus: Either today or after telecom I'd like proposal for "Features at Risk" 16:30:12 ericp: If we accept grammar issues I can remove diff markings. 16:30:34 gavinc: They are editorial and only changes are in line with features at risk. 16:31:43 PROPOSAL: the Turtle CR will have one feature at risk: the grammar productions for SPARQL prefix and base 16:32:14 Guus: What determines whether this feature is in or out? Implementation? 16:32:26 ericp: Feedback is invited. 16:32:31 pchampin has joined #rdf-wg 16:32:48 Guus: Usually features at risk are decided by implementation experience, is this OK? 16:32:52 Sandro: Yes 16:32:59 +1 16:32:59 +1 16:33:01 +1 16:33:03 +1 16:33:04 +1 16:33:06 +1 16:33:12 +1 16:33:12 +1 16:33:13 +1 16:33:14 +1 16:33:21 RESOLVED: the Turtle CR will have one feature at risk: the grammar productions for SPARQL prefix and base 16:33:30 +1 16:34:17 Guus: A few more issues in my message... OK HTML5 link. 16:34:29 -cgreer 16:34:36 ... in the transition request we must indicate whether there are normative references to 16:34:38 +??P52 16:34:42 Just lost audio. 16:35:11 +cgreer 16:35:29 Guus: the "normative ref" to HTML5 is actually in an informative section 16:35:53 ... the link is regarding script tags 16:36:04 Guus: I'm unclear as to the status of this document. 16:36:07 gavinc: The HTML5 refrence being nominative is a bug. 16:36:35 Sandro: as long as it's not a normative reference it's OK. 16:37:03 gavinc: The link only leads to another link, to editor's draft. 16:37:21 Guus: The purpose of this whole scheme is that it should work in five years. 16:37:46 ivan: Having a reference to stable CR document is fine and that's what we should do. 16:37:56 gavinc: So we no longer refer to latest editor's draft? 16:38:28 ericp: I'm OK with that regardless of what the link end says. 16:38:54 http://localhost:8001/TR/2012/CR-html5-20121217/ 16:38:58 http://www.w3.org/TR/html5/scripting-1.html#the-script-element 16:39:06 http://www.w3.org/TR/2012/CR-html5-20121217/ 16:39:27 gavinc: I'll get the link fixed. 16:39:43 Guus: What about the date of the documents? 16:40:51 sandro: When you check in, update the date. 16:41:10 ericp: I'll update CSS and Gavin will update link reference. 16:41:20 Guus: It would be good to send request Friday. 16:41:26 ... Can you do this in next 24 hours? 16:41:30 gavinc: Sure. 16:41:48 subtopic: Coverage of Turtle Tests 16:42:30 ericp: The goal is to look through the grammar and concepts of language features and make sure we have tests that cover them all 16:42:52 ... In the process I created a set of minimal tests. One n-triples statement, then features are minimal deviations from that. 16:43:01 https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/coverage/report.html 16:43:50 ericp: There are some redundant tests (with exactly same features) 16:44:16 ericp: So another question - do we want to use existing test suite or minimal tests. 16:44:41 ericp: Minimal tests have advantage of what feature is failing. 16:44:41 "minimal tests?" 16:44:54 where are the minimal tests as a suite online? 16:44:58 ... If we use Andy's tests, we know they're weathered, people have been using them for a while. 16:45:14 q? 16:45:15 sandro: What's the advantage of having both? 16:45:25 s/having/not having/ 16:45:58 ericp: If we're pedantic about it, if somebody passes minimal tests, except the two at the end, then fail a couple of Andy's tests, 16:46:18 ... Andy's tests may not pinpoint feature failures precisely. 16:46:22 That's a failure to implement Turtle :P 16:46:39 Sandro: I'd rather have both sets of tests. 16:46:58 ericp: We ran into this with SPARQL and didn't know how to resolve it. 16:47:05 Turtle is a great deal smaller then a query language. 16:47:31 ... another option is to use minimal tests when reporting on failure, and others as a second set. 16:48:01 Sandro: Submitter should be passing all tests anyhow. 16:48:21 ericp: From SPARQL, a lot of folks failed entailment tests because they didn't implement them. 16:48:50 ... with the minimal tests then I'd rather see a failure than a disabled test. 16:48:57 Turtle is VERY VERY tiny 16:49:03 Sandro: I don't think this will matter for turtle. We expect full implementations. 16:49:23 I expect ALL implementations to implement ALL of Turtle :P 16:49:30 ericp: But it's still useful to know about what the test coverage is for a given language version. 16:50:05 gkellogg: In RDFa we tend to break features out, and have a feature-based test suite. 16:50:14 q? 16:50:30 gkellogg: Failing features are generally removed from the test reports. 16:50:51 Sandro: It seems that Eric's tests are unit tests for debugging, and Andy's are for regression, confidence in whole system 16:51:19 gkellogg: Interaction tests are useful. Beyond minimal feature tests. 16:51:32 ericp: But we've not been diligent to test feature interaction. 16:52:07 No test suite is complete. Lots of weird, obscure interactions possible e.g. all bnodes are all the same. 16:52:46 gkellogg: Also we'll find that people add tests when they hit failures. If we find processors that all pass, but differ in a particular use case, we add a test that covers that combination. 16:52:57 ericp: We can do that same thing here. 16:53:11 Sorry, have to leave early fter arriving late. 16:53:17 gavinc, I wonder if we can find someone to donate a prize to the writer of the smallest turtle parser. :-) 16:53:32 -PatH 16:53:35 Guus: I think we list the minimal test suite in the transition request. 16:53:43 q+ to ask where the minimal suite is 16:54:15 it exists inside a perl module which is now checked in with Turtle 16:54:36 So I can't execute it. Hmm. 16:55:07 checked in with Turtle? 16:55:27 gavinc: Didn't Greg already do reporting for the larger test suite? 16:55:50 ericp: What I don't understand is how to map features to test reports. 16:55:57 gavinc: Why do we have to do that? 16:56:17 ericp: It's a method for finding which implementations have what shortcomings. 16:56:36 sandro: this situation is for when a big test fails, and we don't know what that means. 16:57:05 ericp: So if they've failed a small test... that justifies the division between minimal test suite and the larger one. 16:57:21 sandro: I agree that it's good to have a distinction. 16:57:52 gkellogg: Two manifests would help. In JSON-LD we decided that the tests that start at '1000' are intended to be large, hard tests. 16:58:08 ... for something like SPARQL, you could break it into several manifests. 16:58:38 ... but turtle is small, and bigger tests that fail should probably be rewritten into smaller ones. 16:59:04 q? 16:59:20 ... a single test manifest is probably best here, and more practical. We could partition the tests at some point that distinguishes between minimal tests and larger ones. 17:00:34 -Arnaud 17:00:45 -> https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/coverage/paths minimal tests (3rd column) 17:01:08 q+ 17:03:03 ... again, does ANYONE think that Turtle implementations will NOT be complete? 17:03:30 sandro: all the approved test should be in the transition request. 17:03:56 q- 17:04:03 ack me 17:04:03 AndyS, you wanted to ask where the minimal suite is 17:04:49 ericp: Do we want syntax tests that are the same as evaluation tests? 17:05:21 davidwood: My implemenations that had evaluation tests.. those were also treated as syntax tests. 17:05:22 the eval test, + and - should be syntax correct. 17:05:47 ericp: It sounds like all of these tests had the reference graph with them. 17:06:08 davidwood: Back then, no, there were a lot of positive tests, negative tests, and entailment tests. 17:06:29 ... And I treated the latter as syntax tests too. 17:06:29 s/davidwood/sandro 17:06:37 oops 17:07:16 ericp: The difference between evaluation tests and syntax is reporting. 17:08:18 I'll get it back from Gavin later. 17:09:18 ericp: Do we take all of the evaluation tests, and duplicate them as syntax tests? 17:09:30 ... or the opposite, eliminating redudandancies 17:09:31 No. We don't do that. 17:10:10 gkellogg: I don't see a reason to remove any tests. eval tests are a superset of syntax tests. If you were to fail evaluation tests that passed for syntax, what does that mean? 17:10:23 There should be no syntax tested in eval that is not elsewhere. May well have got coverage wrong and would like to see people submit new tests. 17:10:28 gkellogg: The more ways you test something the better your confidence level is. 17:10:33 Yes. 17:11:15 ivan: We have a bunch of other things to discuss. Testing details should be out of scope for telecon. 17:11:25 agree with Ivan 17:12:21 ivan: The charter is expiring (an example of something we need to discuss as a WG) 17:12:28 tlr has joined #rdf-wg 17:12:36 hi guys, any chance to get off the bridge? 17:13:05 Guus: If you check the open issues list, we seem to be almost done. There are some issues in cleanup tasks. 17:13:16 .. We should mainly be completing the documents. 17:13:29 me AOB -- I have a Q about TriG and NQuads ... we are doing these aren't we? 17:13:29 ivan: But what about the semantic document discussions? We need to bring that back up. 17:14:46 I just scribed last time :) 17:14:50 -Sandro 17:14:52 -yvesr 17:14:53 -AndyS 17:14:55 -Ivan 17:14:57 -SteveH 17:14:57 -AZ 17:14:58 -Souri 17:15:00 -gkellogg 17:15:02 -cgreer 17:15:04 bye 17:15:05 -GavinC 17:15:06 tlr has left #rdf-wg 17:15:07 -markus 17:15:08 -ericP 17:15:15 -pchampin 17:15:36 Zakim, who is here? 17:15:36 On the phone I see Guus, +1.408.992.aadd 17:15:37 On IRC I see pfps, cgreer, Arnaud, markus, yvesr, Zakim, RRSAgent, gkellogg, danbri, SteveH, AndyS, trackbot, Guus, ivan, gavinc, manu1, manu, mischat, sandro, ericP 17:15:44 AndyS has left #rdf-wg 17:15:47 Zakim, please disconnect guus 17:15:47 Guus is being disconnected 17:15:48 -Guus 17:15:51 Zakim, please disconnect aadd 17:15:51 +1.408.992.aadd is being disconnected 17:15:52 SW_RDFWG()11:00AM has ended 17:15:52 Attendees were +31.20.598.aaaa, Arnaud, AndyS, markus, gkellogg, Guus, SteveH, AZ, +1.707.874.aacc, cgreer, yvesr, ericP, Sandro, Ivan, +1.408.992.aadd, +1.603.897.aaee, Souri, 17:15:52 ... PatH, GavinC, pchampin 17:19:11 trackbot, end meeting 17:19:11 Zakim, list attendees 17:19:11 sorry, trackbot, I don't know what conference this is 17:19:19 RRSAgent, please draft minutes 17:19:19 I have made the request to generate http://www.w3.org/2013/01/09-rdf-wg-minutes.html trackbot 17:19:20 RRSAgent, bye 17:19:20 I see 1 open action item saved in http://www.w3.org/2013/01/09-rdf-wg-actions.rdf : 17:19:20 ACTION: ericP change the AtRisk styling to allow searching documents for the words "feature" and "risk" to find Features At Risk [1] 17:19:20 recorded in http://www.w3.org/2013/01/09-rdf-wg-irc#T16-27-09