14:59:33 RRSAgent has joined #rdf-wg 14:59:33 logging to http://www.w3.org/2013/08/21-rdf-wg-irc 14:59:38 Zakim, this will be RDF 14:59:38 ok, davidwood, I see SW_RDFWG()11:00AM already started 14:59:45 Chair: David Wood 15:00:22 + +1.408.992.aaaa 15:00:24 - +1.408.992.aaaa 15:00:24 + +1.408.992.aaaa 15:00:29 Agenda: http://www.w3.org/2011/rdf-wg/wiki/Meetings:Telecon2013.08.21#Admin 15:00:38 zakim, aaaa is me 15:00:38 +pfps; got it 15:00:45 + +081165aabb 15:00:51 Zakim, who is here 15:00:51 davidwood, you need to end that query with '?' 15:00:56 +OpenLink_Software 15:00:59 Zakim, who is here? 15:01:00 On the phone I see bhyland1, pfps, +081165aabb, OpenLink_Software 15:01:00 On IRC I see RRSAgent, Zakim, AZ, gkellogg, AndyS, pfps, TallTed, ivan, manu, gavinc, davidwood, trackbot, yvesr, sandro, ericP 15:01:05 - +081165aabb 15:01:05 Zakim, OpenLink_Software is temporarily me 15:01:06 +TallTed; got it 15:01:06 Zakim, mute me 15:01:07 zakim, dial ivan-voip 15:01:07 TallTed should now be muted 15:01:07 Zakim, bhyland is me 15:01:07 ok, ivan; the call is being made 15:01:07 +davidwood; got it 15:01:09 +Ivan 15:01:25 +Sandro 15:01:30 zakim, mute me 15:01:30 Ivan should now be muted 15:01:31 +[IPcaller] 15:01:39 zakim, ipcaller is me 15:01:40 +AndyS; got it 15:02:01 +??P13 15:02:03 +??P14 15:02:11 zakim, drop P13 15:02:11 sorry, sandro, I do not see a party named 'P13' 15:02:14 zakim, drop ??P13 15:02:14 ??P13 is being disconnected 15:02:14 TallTed has changed the topic to: RDF WG -- http://www.w3.org/2011/rdf-wg/ -- Agenda: http://www.w3.org/2011/rdf-wg/wiki/Meetings:Telecon2013.08.21 15:02:15 -??P13 15:02:33 Zakim, ??P14 is me 15:02:33 +yvesr; got it 15:02:48 + +081165aacc 15:03:02 Zakim, aacc is me 15:03:02 +AZ; got it 15:03:24 + +1.415.686.aadd 15:03:42 zakim, aadd is me 15:03:42 +gkellogg; got it 15:03:48 Zakim, who is here? 15:03:48 On the phone I see davidwood, pfps, TallTed (muted), Ivan (muted), Sandro, AndyS, yvesr, AZ, gkellogg 15:03:50 On IRC I see RRSAgent, Zakim, AZ, gkellogg, AndyS, pfps, TallTed, ivan, manu, gavinc, davidwood, trackbot, yvesr, sandro, ericP 15:04:46 Zakim, unmute me 15:04:46 TallTed should no longer be muted 15:04:57 Zakim, mute me 15:04:57 TallTed should now be muted 15:05:19 scribenick: pfps 15:06:01 +gavinc 15:06:13 markus has joined #rdf-wg 15:06:22 +Souri 15:06:36 PROPOSED to accept the minutes of the 07 August telecon: https://www.w3.org/2013/meeting/rdf-wg/2013-08-07 15:06:42 Souri has joined #rdf-wg 15:06:55 agendum: admin 15:07:07 david: accept minutes from last time 15:07:16 RESOLVED to accept the minutes of the 07 August telecon: https://www.w3.org/2013/meeting/rdf-wg/2013-08-07 15:07:20 david: no objections -> minutes acceptes 15:07:29 Review of action items 15:07:29 http://www.w3.org/2011/rdf-wg/track/actions/pendingreview 15:07:29 http://www.w3.org/2011/rdf-wg/track/actions/open 15:07:46 ACTION-282 is done 15:07:51 I claim that EricP did ACTION-280 15:08:34 david: second editor for trig 15:08:53 andy: I will if it helps 15:08:54 CLOSE ACTION-282 15:08:54 Closed ACTION-282. 15:09:32 CLOSE ACTION-280 15:09:32 Closed ACTION-280. 15:09:43 greg: so far 9 conforming Turtle implementation 15:09:46 Excellent news on the implementation reports. 15:09:53 david: primer still in progress 15:09:54 s/greg/gkellogg/ 15:10:51 david: next meeting *next* week 15:12:16 david: I won't be available next week 15:12:27 sandro: I can chair if needed 15:12:59 Request for Review: ITS 2.0 15:12:59 15:12:59 See: http://lists.w3.org/Archives/Public/public-rdf-wg/2013Aug/0000.html 15:12:59 15:13:01 agendum: request for review of ITS 2.0 15:13:15 q+ 15:13:59 david: they want some some review from us re converting markup into RDF 15:14:20 topic: request for review 15:14:34 Section in question, http://www.w3.org/TR/its20/#conversion-to-nif 15:14:47 david: I'm not sure what we would say except "hurray" and check to see if they have done anything bad 15:14:59 I am happy to say hurray 15:15:14 ack ivan 15:15:30 ivan: I can take a look at the document 15:16:05 action: ivan review ITS 2.0 document 15:16:05 'ivan' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., ivan, imikhail). 15:17:27 Topic: JSON-LD 15:17:37 zakim, mute me 15:17:37 Ivan should now be muted 15:17:40 PROPOSED to publish JSON-LD as CR: http://lists.w3.org/Archives/Public/public-rdf-wg/2013Aug/0060.html 15:18:03 +EricP 15:18:10 sandro: we need to agree on exit criteria 15:18:11 q+ to ask about testing (minor, clarification) 15:18:34 q+ 15:18:40 ack AndyS 15:18:40 AndyS, you wanted to ask about testing (minor, clarification) 15:18:41 sandro: the standard criteria should be acceptable, but there should be a resolution 15:18:42 +??P20 15:18:51 zakim, ??P20 is me 15:18:51 +lanthaler; got it 15:19:11 zakim, ??P20 is me 15:19:11 I already had ??P20 as lanthaler, markus 15:19:21 andy: for the RDF tests, isomorphism appears to be the right standard 15:19:28 ack gkellogg 15:19:40 gregg: this was discussed yesterday 15:20:06 gregg: for testing to-RDF isomorphism is OK, but the output is n-quads 15:20:13 http://json-ld.org/test-suite/reports/ 15:20:24 andy: so n-quads isomorphism is what to use 15:20:38 q+ 15:20:43 gregg: here is an EARLy report 15:21:07 q- 15:21:14 gregg: pretty broad conformance over six implementations 15:21:32 +q to ask if 3 of those aren't translations of the same implementation? 15:21:46 ack gavinc 15:21:46 gavinc, you wanted to ask if 3 of those aren't translations of the same implementation? 15:21:52 gregg: this indicates that CR exit critera have already been met, but there are other groups that may be waiting for CR to actually to the testing 15:22:20 I think on yesterday's call we agreed on a minimum CR duration of 2 weeks 15:22:30 gavin: are three of the implementations machine translations? 15:22:46 gregg: no, they are separate, but the Java one is the primary 15:22:54 s/Java/Javascript 15:22:58 s/java/javascript/ 15:23:59 q? 15:23:59 david: sandro can you craft a proposal for exit criteria? 15:24:38 gregg: the tests are all via the API 15:25:06 -EricP 15:25:27 sandro: are any of the proposed tests contential 15:25:49 gregg: to RDF-100 had some discussion yesterday because it was generating relative-IRIs 15:26:07 +q to ask about dataset tests 15:26:11 gregg: we dropped it so that the results are all legal generalized RDF 15:26:36 ack gavinc 15:26:36 gavinc, you wanted to ask about dataset tests 15:27:30 gavin: are there tests around datasets that contain more than one graph? the bugs I've in seen in are in this area 15:27:38 +EricP 15:28:08 gregg: I don't know - we will be discussing this next week on the JSON-LD call 15:28:17 AZ_ has joined #rdf-wg 15:28:33 Don't need test suite to go to CR. 15:28:47 gavin: how can we approve exit criteria without a full set of tests? 15:29:08 PROPOSED: The Exit Critera for JSON-LD shall be that at least two implementations pass each approved test in the test suite. We approve the tests as they stands today, but intend to add more. We may also make corrections if bugs are found. The test are all on JSON-LD-API but we consider them to cover both JSON-LD documents. 15:30:23 gregg: we need more tests. we only have only one test on error condititions. 15:30:24 We DO need more tests. There are no tests for datasets, only single named graphs 15:30:48 q+ 15:30:49 gregg: more tests are needed, e.g., test variations on native types, dataset tests 15:31:01 gregg: should we approve the current tests? 15:31:12 sandro: let's approve now and add later 15:31:37 sandro: there are about two weeks before CR can be announced, so the tests should be finalized by then 15:31:39 of course you never know when a test suite is *really* done 15:32:02 david: do we need one resolution or two? 15:32:11 ack markus 15:32:12 sandro: either 15:32:22 The exit criteria I put in the spec is: "Before this specification exits Candidate Recommendation, two or more independent implementations must pass each test, although no single implementation must pass each test. The working group will decide when the test suite is of sufficient quality to test interoperability and will produce an implementation report (hosted together with the test suite)." 15:32:33 markus: are we trying to define the exit criteria 15:32:49 sandro: yes 15:32:56 -EricP 15:33:07 sandro: the exit criteria usually go in the transition request, not the document 15:33:33 david: let's resolve on the wording from the document 15:33:45 PROPOSED: (as in spec draft) Before this specification exits Candidate Recommendation, two or more independent implementations must pass each test, although no single implementation must pass each test. The working group will decide when the test suite is of sufficient quality to test interoperability and will produce an implementation report (hosted together with the test suite). 15:33:49 +1 15:33:52 +1 15:33:55 +1 15:33:55 +1 15:33:57 +1 15:33:59 +1 15:34:03 +1 15:34:05 +1 15:34:06 +1 15:34:09 +1 15:34:12 +1 15:34:16 +1 15:34:35 zakim, who is talking? 15:34:41 RESOLVED: (as in spec draft) Before this specification exits Candidate Recommendation, two or more independent implementations must pass each test, although no single implementation must pass each test. The working group will decide when the test suite is of sufficient quality to test interoperability and will produce an implementation report (hosted together with the test suite). 15:34:46 pfps, listening for 10 seconds I heard sound from the following: davidwood (53%), AndyS (19%), Sandro (15%) 15:35:30 JSON-LD 1.0 Processing Algorithms and API 15:35:38 PROPOSED: Publish both JSON-LD 1.0 and JSON-LD 1.0 Processing Algorithms and API as CR. 15:35:49 +1 15:35:49 +1 15:35:51 +1 15:35:52 +1 15:35:52 +1 15:35:55 +1 15:35:56 +1 15:36:00 +1 15:36:04 +1 15:36:05 +1 15:36:23 +1 15:36:25 PROPOSED: The test are all on JSON-LD-API but we consider them to cover both JSON-LD documents. 15:36:27 RESOLVED: Publish both JSON-LD 1.0 and JSON-LD 1.0 Processing Algorithms and API as CR. 15:36:50 sandro: there should be some comment that the JSON-LD tests cover both documents 15:36:58 PROPOSED: The test are all on JSON-LD-API but we consider them to cover both JSON-LD documents. 15:37:02 gregg: Implementing all the processing algorithms effectively tests all the normative requirements of the JSON-LD documents. 15:37:04 +1 15:37:35 PROPOSED: The test are all on JSON-LD Processing Algorithms, but we consider them to cover both JSON-LD documents in their entirety. 15:37:37 +1 15:37:41 +1 15:37:41 +1 15:37:43 +1 15:37:43 +1 15:38:05 +1 15:38:18 sandro: are there actual API tests? 15:38:24 gregg: yes 15:38:43 gregg: We should be careful that the API tests are in the report, since they aren't in the EARL. 15:39:11 gregg: That part is intended for JS impls, but my (Ruby) one doesn't do the API with Promises. 15:39:27 +1 15:39:28 +1 15:39:33 david: I don't see any issues here 15:39:34 RESOLVED: The test are all on JSON-LD Processing Algorithms, but we consider them to cover both JSON-LD documents in their entirety. 15:39:34 +1 15:39:35 Need to make sure IDL tests are included with the test manifests and in the EARL report 15:40:04 markus: how long for CR? 15:40:46 sandro: let's just ask for a short time and end whenever 15:41:01 markus: we were thinking of two weeks and extend if necessary 15:41:10 -Ivan 15:41:22 sandro: two weeks seems a little short - three weeks might be more normal 15:41:35 sandro: two weeks might raise some flage 15:41:38 markus: ok 15:42:16 andy: groups that are waiting for start of CR might want longer 15:43:10 From http://www.w3.org/2005/10/Process-20051014/tr.html#transition-reqs : "The Working Group is not required to show that a technical report has two independent and interoperable implementations as part of a request to the Director to announce a Call for Implementations. However, the Working Group should include a report of present and expected implementations as part of the request." 15:43:19 markus: we might send out an informal communication to get these people to start 15:43:28 "must specify the deadline for comments, which must be at least four weeks after publication, and should be longer for complex documents." 15:44:43 david: minimal duration of implementation period is required 15:44:56 sandro: should be at least three weeks 15:44:57 "The announcement must indicate a minimal duration, before which the Working Group must not request ahttp://www.w3.org/2005/10/Process-20051014/tr.html#cfr; this minimal duration is designed to allow time for comment." 15:45:07 There is no definition of minimal. 15:45:13 yep, and the newest draft process document https://dvcs.w3.org/hg/AB/raw-file/default/tr.html does define, and that's 4 weeks 15:45:27 gavinc, that's not CR 15:45:33 david: let's try for three 15:45:52 markus nope, since CR is gone :D 15:46:06 sandro: resolving on three weeks would be helful 15:46:22 s/hellful/helpful/ 15:46:29 gavinc, oh sorry, didn't realize you pasted a different link 15:46:40 PROPOSED: The WG will request a duration of three (3) weeks for the JSON-LD implemention period. 15:46:46 +1 15:46:48 +1 15:46:50 +1 15:46:57 +1 15:47:00 +1 (are you sure that you needed the (3)?) 15:47:00 +1 15:47:05 +1 15:47:13 +1 15:48:28 RESOLVED: The WG will request a duration of three (3) weeks for the JSON-LD implementation period. 15:48:33 sandro: we may be able to publish the documents on the day that the CR request is approved 15:48:55 +1 15:49:13 Topic: TriG / N-Triples / N-Quads 15:49:20 topic: lions and tigers and bears 15:49:50 david: progress in TriG document 15:50:04 david: please accept Andy's help 15:50:13 zakim, dial ivan-voip 15:50:13 ok, ivan; the call is being made 15:50:14 +Ivan 15:50:20 david: Andy will join Gavin as the second editor of the TriG document 15:51:25 gavin: the end result for TriG is that two things need to be added - optional "graph" and {} 15:51:28 q+ 15:51:45 gavin: there were a number of other grammars for other things 15:51:46 zakim, mute me 15:51:46 Ivan should now be muted 15:51:48 ack gkellogg 15:52:36 gregg: allowing a blank node as a graph name was an issue - what syntax is allowed - easiest is blank node label 15:52:53 andy: either labelled or [] 15:53:05 gavin: a bit strange 15:53:19 andy: yes, a corner case, but graphs can be discovered 15:54:02 andy: graph name syntax has to be just for a blank node - nothing else 15:54:33 gavin: I'll put together the result into the document 15:54:50 The editors will record this corner case in the document. 15:54:51 editors will include [ ] for blank node graph labels 15:55:00 gavin: that covers everything I can think of 15:55:01 +EricP 15:55:07 david: N-TRIPLES 15:55:17 PROPOSED to publish N-Triples as LCWD 15:55:58 q? 15:56:39 gavin: comment from Andy re whitespace as a token, the situation has gone back and forth 15:57:22

. is legal TTL but not NT. Some may find it odd. 15:57:30 andy: want the two to be the same 15:57:46

. needed in NT. 15:57:47 gavin: can't allow NL in the middle of triples 15:58:01 david: date in document is next week 15:58:07 gavin: that can be changed easily 15:58:25 +1 15:58:29 +1 15:58:29 +1 15:58:30 +1 15:58:31 +1 15:58:32 go for it 15:58:34 +1 15:58:42 +1 15:58:45 +1 15:58:53 +1 15:58:53 +1 15:58:54 +1 15:59:06 RESOLVED to publish N-Triples as LCWD. 15:59:56 david: try for LC of N-Triples next week 16:00:04 topic: semantics and concepts 16:00:17 s/Triples/Quads/ 16:00:36 ISSUE-140? 16:00:36 ISSUE-140 -- RDF Dataset Comparison (Ivan Herman) -- open 16:00:36 http://www.w3.org/2011/rdf-wg/track/issues/140 16:01:51 andy: also need to consider blank nodes shared between the graphs - need to move the isomorphism to the outside 16:01:52 q+ 16:02:26 andy: graph isomorphism is OK, just need to fix this one 16:02:49 -> http://lists.w3.org/Archives/Public/public-rdf-wg/2013Aug/0022.html Pat's definition 16:03:59 andy: this message has the right change 16:04:06 +1 to Pat's definition 16:04:46 -Souri 16:04:51 david: let's accept Pat's definition 16:05:18 q- 16:05:21 -EricP 16:05:28 pfps: looks good to me 16:05:31 zakim unmute me 16:05:37 zakim, unmute me 16:05:37 Ivan should no longer be muted 16:06:49 PROPOSED: Close ISSUE-140 by accepting Pat's suggested change documented in http://lists.w3.org/Archives/Public/public-rdf-wg/2013Aug/0022.html 16:06:53 +1 16:07:02 +1 16:07:04 +1 16:07:05 +1 16:07:12 +1 16:07:17 +1 16:07:17 +1 16:07:24 +1 16:07:38 +1 16:07:56 +1 16:08:22 RESOLVED: Close ISSUE-140 by accepting Pat's suggested change documented in http://lists.w3.org/Archives/Public/public-rdf-wg/2013Aug/0022.html 16:09:08 Grad students! 16:09:57 ACTION: davidwood to apply the resolution to ISSUE-140 in Concepts 16:09:57 Created ACTION-283 - Apply the resolution to issue-140 in concepts [on David Wood - due 2013-08-28]. 16:10:13 zakim, mute me 16:10:13 Ivan should now be muted 16:10:18 david: comments from Jeremy ... 16:10:31 Comments Jeremy Carroll 16:10:31 rdfs:Graph ? comment and Issue 35: http://lists.w3.org/Archives/Public/public-rdf-comments/2013Jul/0021.html 16:10:31 owl:imports, graph names and Issue 38: http://lists.w3.org/Archives/Public/public-rdf-comments/2013Jul/0022.html 16:10:31 Turn into issues 16:11:46 ISSUE-35? 16:11:46 ISSUE-35 -- Should there be an rdf:Graph construct, or something like that? -- closed 16:11:46 http://www.w3.org/2011/rdf-wg/track/issues/35 16:12:26 andy: I think that the modeling in his example is somewhat dubious 16:12:36 david: is there a resolution on ISSUE-35? 16:13:37 pfps: I'm unsure just what Jeremy wants 16:13:55 david: there is nothing prohibiting making graph names denote graphs 16:14:22 q+ 16:14:30 pfps: Jeremy wants there to be a way to require graph names denoting graphs 16:14:47 david: that proposal has been before the working group and has not been approved 16:15:13 ack ivan 16:15:42 ivan: there was a plan to have something like this 16:16:16 ivan: ... in a note 16:16:33 sandro: correct, but I was hoping ... 16:17:43 david: we need to reply to Jeremy and at least say that a similar proposal was rejected and that nothing prohibits this 16:17:50 and there's a plan to make a note on dataset-semantics, which I have to finish (ED at https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-dataset/index.html#) 16:18:00 sandro: and could ask what the minimum is here 16:18:17 david: and there is a note possibly in progress 16:18:17 +q 16:18:25 ack markus 16:18:34 sandro: jeremy knows this already 16:19:12 markus: are we planning to added rdf:bounddataset to note 16:19:31 sandro: that would be in there 16:19:49 david: a non-arbitrary deadline for the WG would be mid-Nov 16:20:02 q+ 16:20:06 sandro: Jeremy might object to proceeeding unless the note exists 16:20:37 david: sandro please respond with history and say that a note on the issue will appear later and whether he is OK with that 16:20:43 Topic: AOB 16:20:47 q- 16:20:53 Adjourn 16:20:56 -Ivan 16:21:36 AZ: the note on dataset semantics is in progress since January and should be ready by September 16:21:52 david: please try to finish soon - discussion may take some time 16:22:29 bye! 16:22:35 -gavinc 16:22:39 AZ: would be nice if peter or pat could take a look at it 16:22:41 -Sandro 16:22:41 bye 16:22:42 -davidwood 16:22:43 ADJOURNED 16:22:43 -AZ 16:22:45 -TallTed 16:22:46 -gkellogg 16:22:47 -lanthaler 16:22:52 -AndyS 16:24:59 pfps, please see the directions at the top of http://www.w3.org/2011/rdf-wg/wiki/Scribes 16:41:57 pfps, thanks. 16:42:02 looking at it. 16:43:34 RRSAgent: make logs public 16:43:56 pfps, there's a bug where some scribe errors produce that instead of a proper error message. 16:44:20 this line 16:44:22 15:02:14 Topic: Administrivia 16:44:24 should have been 16:44:34 15:02:14 Topic: Administrivia 16:45:33 I just fixed it by manually going to https://www.w3.org/2013/meeting/rdf-wg/2013-08-21?edit=1 16:54:30 -pfps 16:59:30 disconnecting the lone participant, yvesr, in SW_RDFWG()11:00AM 16:59:32 SW_RDFWG()11:00AM has ended 16:59:32 Attendees were bhyland1, +1.408.992.aaaa, pfps, +081165aabb, TallTed, davidwood, Ivan, Sandro, AndyS, yvesr, +081165aacc, AZ, +1.415.686.aadd, gkellogg, gavinc, Souri, EricP, 16:59:33 ... lanthaler 18:32:36 Zakim has left #rdf-wg 20:05:33 gkellogg_ has joined #rdf-wg 20:20:34 gkellogg_ has joined #rdf-wg 22:04:50 gkellogg_ has joined #rdf-wg