13:58:44 RRSAgent has joined #ldp 13:58:44 logging to http://www.w3.org/2014/09/15-ldp-irc 13:58:46 RRSAgent, make logs public 13:58:48 Zakim, this will be LDP 13:58:48 ok, trackbot, I see SW_LDP()10:00AM already started 13:58:49 Meeting: Linked Data Platform (LDP) Working Group Teleconference 13:58:49 Date: 15 September 2014 13:59:28 +Matt 13:59:34 Zakim, Matt is me 13:59:34 +deiu; got it 14:00:15 JohnArwe has joined #ldp 14:00:23 + +1.857.928.aabb 14:00:29 Zakim, aabb is Alexandre 14:00:29 +Alexandre; got it 14:00:39 +JohnArwe 14:00:46 +Arnaud 14:00:52 MiguelAraCo has joined #ldp 14:01:15 +[IPcaller] 14:01:23 Zakim, IPcaller is me. 14:01:23 +codyburleson; got it 14:01:44 Ashok has joined #ldp 14:01:46 sergio has joined #ldp 14:01:56 +[IBM] 14:02:05 Zakim, [IBM] is SteveS 14:02:05 +SteveS; got it 14:02:31 +Ashok_Malhotra 14:02:32 + +43.660.274.aacc 14:02:45 Zakim, +43.660.274.aacc is me 14:02:45 +sergio; got it 14:02:57 nmihindu has joined #ldp 14:03:26 zakim, who's on the phone? 14:03:26 On the phone I see +1.505.603.aaaa, Sandro, deiu (muted), Alexandre, JohnArwe, Arnaud, codyburleson, SteveS, Ashok_Malhotra, sergio 14:03:28 +OpenLink_Software 14:03:40 Zakim, OpenLink_Software is temporarily me 14:03:40 +TallTed; got it 14:03:42 Zakim, mute me 14:03:42 TallTed should now be muted 14:04:20 scribe: codyburleson 14:04:28 like this s/old/new/ 14:05:00 3 dots actually 14:05:04 chair: Arnaud 14:05:07 2 or 3 14:05:16 …Arnaud continues on 14:05:19 agenda: https://www.w3.org/2012/ldp/wiki/Meetings:Telecon2014.09.15 14:05:32 TOPIC: Approval of Minutes from Sep 8 meeting. 14:05:37 zakim, aaaa is me 14:05:37 +azaroth; got it 14:05:59 Arnaud: RESOLVED: Minutes of Sep 8 approved. (no objection heard) 14:06:28 +??P2 14:06:32 TOPIC: Actions and Issues 14:06:43 Zakim, ??P2 is me 14:06:43 +nmihindu; got it 14:06:50 Zakim, mute me 14:06:50 nmihindu should now be muted 14:06:53 TOPIC: Paging 14:07:19 Arnaud: Paging is now in last call and we have received a couple of comments; one, in fact, which I forgot to put on the agenda to discuss. 14:09:01 … We have to prove to W3C mgmt that we have kept track of all the comments we have received. There is a tracker tool for this, but I haven't found it very helpful. We are free to use whatever tool we want. In my opinion, it would be better just to use a wiki page and list the comments (links) and outcome for each. Thoughts? 14:09:10 I’m fine with using wiki for this, unfortunate the tool isn’t that helpful 14:09:34 Ashok: The wiki ought to be OK. 14:09:58 Arnaud: OK. We'll use the wiki. 14:10:11 … OK. First comment on Paging. 14:10:36 http://lists.w3.org/Archives/Public/public-ldp-comments/2014Aug/0002.html 14:11:09 … The comment is about - Why do you guys don't choose something closer to HTTP where you use HTTP Range. 14:11:45 … We need to agree on how we respond to this and then somebody needs to send the response. So, how do we want to respond? 14:12:30 q+ 14:12:34 q+ 14:12:45 roger has joined #ldp 14:12:55 +Roger 14:13:22 JohnArwe: I don't think it's practical for RDF. It goes against the grain of RDF. Sets are unordered and every graph is a set of triples. Also, HTTP Range, from every thing I've heard, is not well implemented. That is to say, not a lot of servers implement it at all. I think this is why we threw it out a couple of years ago; we had this discussion long ago. 14:13:29 ack azaroth 14:14:00 Roger: I agree. RDF not being supported seems like a problem for paging in general. 14:14:10 ack sandro 14:14:35 s/Roger/azaroth/ 14:14:48 range changed while we were working... http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7233.html 14:15:04 particularly http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7233.html#range.units.other 14:15:53 Sandro: I'm having a hard time actually seeing a problem with range. 2 possible problems. I don't know how to do server initiated paging with range. The other is that we lose the ability to have metadata on pages, but I haven't been able to come up with a compelling use case. 14:16:10 s/in general./in general. So order isn't a good response for the comment./ 14:17:08 Zakim, unmute me 14:17:08 TallTed should no longer be muted 14:17:39 Sandro: One of the problems with Paging is that it doesn't solve: you can't traverse a resource while it's changing in any safe way. 14:17:48 sandro: doesn't allow server initiation 14:18:09 sandro: doesn't allow getting the date safely while things are being added/removed 14:18:22 TallTed: It's based on something, which is static to some degree. We're doing this hybrid sort of thing. Decisions we've already made make using range more difficult. 14:19:32 Sandro: RDF graph is changed often by adding or deleting a few triples. 14:20:16 Arnaud: I think the difference is what you guys are touching on. With Paged resources, like what we have in our model, there is an indirection, which you lose if you go down to the level of triples as you likely would with HTTP Range. 14:20:45 JohnArwe: I don't think Jena gives me any guarantee I'm gonna get the same amount of triples in the same order. 14:22:00 you need more than a Jena Graph/Model to do paging 14:22:01 Sandro: In the general case, with a Jena based server, how would you do paging? First 10,000 triples, from that first batch, how would you continue? 14:22:09 +q to ask about max-triple-count param 14:22:57 JohnArwe: What I would probably do is a sort of imperfect compromise. It gets ugly, I admit. But you could iterate through…. use predicate names themselves to divide the graoph into thin slices, and just keep track of the predicates you've already gone through. 14:23:08 Sandro: What if it's pretty much all the same predicates. 14:23:28 q+ 14:24:20 ack azaroth 14:24:20 azaroth, you wanted to ask about max-triple-count param 14:24:29 sandro: another problem with range: our data structures don't generally support integer indexing 14:24:32 Sandro: I guess an answer here is that the data structures typically used by this sort of thing are not easy to implement. There is an implementation burden trying to add an extra index. 14:25:24 I agree w/ Rob 14:26:04 ack Ashok 14:26:58 Ashok: If you do not want to order triples, then you get some kind of default order. And if you are storing this stuff in any tables, there is always an order. You can take advantage of that. 14:27:34 Sandro: Ashok, is it reasonable for any table to ask for the arbitrary Nth row? In your technology is that something you can easily do? 14:27:38 Ashok: Yes. 14:27:58 TallTed: There is no assurance the order is going to be set unless you put an ORDER BY. 14:28:12 Ashok: That's what the SQL standard "says", yes. 14:28:45 Arnaud: So…Do we have an answer for the commenter? 14:28:57 afaik, SQL doesn't expose the row number to the user 14:29:09 not even the row id 14:29:30 … the level of indirection we're getting from our model makes it easier to implement than if we were going to use HTTP Range with triples. 14:29:40 Yes, Alexandre, but many implementations support this 14:29:51 proposed answer: our data structures don't expose integer indexes 14:30:08 + server initiation 14:30:20 + safe changes during paging 14:30:28 … I'm suggesting that's our answer to the commenter. My first reaction was "Yeah! Why don't we use this?" But I am convinced now that there are advantages to the model we have adopted so far. Some might think it is overkill but... 14:31:00 Sandro: 1) Our data structures … indexes 2) Don't know how to do server initiation with paging 3) Don't know how to do safe changes while paging 14:31:18 … I'm not sure that's a comment back to the commenter or a question back to him or her. 14:31:22 "We don't know how to do these things" 14:32:08 Arnaud: We can make it both ways. We state that this is WHY we have what we have and leave it open for the commenter to continue the thread. 14:32:28 SQL idiom included in this sample: SELECT * FROM MyTable OFFSET 50 LIMIT 25 14:32:40 Arnaud: Sandro, can you answer the commenter? 14:33:14 Sandro: I think I should bring this up with the HTTP working group first. 14:33:19 ericP, you around 14:33:24 JohnArwe: How long will that take? 14:33:45 Sandro: It's completely unpredictable; I don't know.' 14:33:58 JohnArwe: We have a 3 week last call period. 14:34:28 Arnaud: OK. We will go with HTTP Working Group. 14:34:42 … Another comment on Paging… 14:35:03 http://lists.w3.org/Archives/Public/public-ldp-comments/2014Sep/0003.html 14:35:50 sounds like we need a paging best practices doc 14:36:21 /me was thinking the same thing 14:36:24 Arnaud: The commenter is asking for us to document a comparison of options and why we made the choices we made. 14:36:42 JohnArwe: Is that asking for A W3C Note? 14:36:50 Arnaud: I think an email will do. 14:37:55 JohnArwe: We're taking a conservative approach that is least likely to break anything. 14:38:15 … and we have two levels of ETag. On the page and the container. 14:38:24 Arnaud: Can you reply to this email, John? 14:38:45 JohnArwe: I can put something out by Wed this week. 14:40:22 Arnaud: I suggest John responds to this email unless anyone has any differing opinions that what John has expressed. 14:42:05 -Roger 14:43:04 s/that what/than what/ 14:43:22 TOPIC? 2NN? 14:44:05 Sandro: On that particular problem, the RC says that any client that does not recognize a 2NN code for any 2NN has to treat it as a 200. 14:44:18 Topic: 2nn 14:44:22 Arnaud: What is the status of the 2NN draft? 14:44:31 it's an ietf draft 14:45:08 Sandro: …and the working group is kind of engaging an email on it. It's hard to tell. 14:45:50 ietf draft statuses are more opaque from the outside than w3c, imo 14:46:52 Sandro: I am willing to engage more with the HTTP group on it. But, I am not personally too motivated for 2NN on paging. 14:47:22 TOPIC: TEst Suite 14:47:37 s/TEst Suite/Test Suite 14:47:56 Arnaud: I think there are like 14 tests that are waiting for approval? 14:47:57 http://w3c.github.io/ldp-testsuite/manifest/#tobeapproved 14:48:39 (There are 19 ready for approval on the list.) 14:49:14 Arnaud: I'd like to approve those tests. Anybody object? 14:49:15 https://dvcs.w3.org/hg/ldpwg/raw-file/default/tests/reports/ldp.html 14:49:30 SteveS: There are a number of implementations reporting to pass those tests already. 14:49:56 +1 to approve 14:50:03 Arnaud: Sounds like we can approve those tests then. Any concerns? Are we rushing it? 14:50:24 PROPOSAL: approve new tests listed at http://w3c.github.io/ldp-testsuite/manifest/#tobeapproved 14:50:36 +1 14:50:36 +1 14:50:37 +1 approving the 17 tests there 14:50:38 +1 (most seemed fine to me) 14:50:42 +1 14:50:44 +1 14:50:44 +1 14:50:46 +1 14:50:52 +1 14:51:00 RESOLVED: : approve new tests listed at http://w3c.github.io/ldp-testsuite/manifest/#tobeapproved 14:51:00 +1 14:51:08 cool 14:51:23 SS trying to get word in 14:51:24 thanks all, sergio I can make the change 14:51:28 TOPIC: Status of various documents 14:51:44 I was just going to say that I fixed the link in the agenda 14:51:48 perfect, SteveS 14:51:50 Arnaud… LDP Spec is about to be published to LAST CALL. 14:52:04 … Same is true for Access Control Use Cases Requirements Note 14:52:07 SS, did you make the pub request for main-LDP for tomorrow? 14:52:29 … LDP PATCH format: We got the request on getting the short name approved 14:52:29 JA, no..I will now 14:52:53 … all of our documents have been published now or in the middle of process now. 14:52:59 if not Tues, I wills shoot for Thurs, etc 14:53:24 s/wills/will/ 14:53:42 Arnaud: LDP Spec - we are waiting for implementation reports. We are republishing it as Last Call with indirect containers marked as At Risk. 14:54:19 Arnaud: We had some problems on Primer with JSON-LD examples. 14:54:29 nandana's on IRC... 14:54:32 Arnaud, the JSON-LD examples are fixed 14:54:36 … it would be nice to publish an update on the Primer with those updates fixed. 14:54:57 SteveS: I had some minor side comments that Nandana and Roger were going to work in. 14:55:04 Arnaud: Nandana responded. 14:55:06 I am on the call, I can hear you 14:55:16 yes, we can publish an updated version. 14:55:33 Arnaud: We should publish the updated draft of the Primer. 14:55:37 q+ 14:55:43 Zakim, ack me 14:55:43 unmuting deiu 14:55:44 I see no one on the speaker queue 14:55:45 ack deiu 14:56:00 I'm off; see folks in a month 14:56:01 Roger is making some updates to the introductions section, as soon as it is done, we can publish another version. 14:56:04 -JohnArwe 14:56:10 deiu: The date for LDP Patch document should be October 18th? 14:56:23 what if we're ready for tomorrow? 14:56:25 Arnaud: It should be Sept 18th. That's a mistake. 14:57:12 yes, we can probably still do that for tomorrow 14:57:19 …change the date to Sept 16th. 14:57:36 Arnaud: I think we're done for the day. 14:57:45 -Ashok_Malhotra 14:57:50 … I'll put together the wiki page for the Last Call comments. 14:58:04 -TallTed 14:58:08 -deiu 14:58:09 -Sandro 14:58:09 Thanks all :) 14:58:09 -codyburleson 14:58:12 -sergio 14:58:13 -SteveS 14:58:14 -Arnaud 14:58:15 -Alexandre 14:58:21 azaroth has left #ldp 14:58:31 -azaroth 15:20:50 bblfish has joined #ldp 15:35:00 disconnecting the lone participant, nmihindu, in SW_LDP()10:00AM 15:35:01 SW_LDP()10:00AM has ended 15:35:01 Attendees were +1.505.603.aaaa, Sandro, deiu, +1.857.928.aabb, Alexandre, JohnArwe, Arnaud, codyburleson, SteveS, Ashok_Malhotra, sergio, TallTed, azaroth, nmihindu, Roger 15:54:18 bblfish has joined #ldp 16:02:01 bblfish_ has joined #ldp 16:17:08 bblfish has joined #ldp 16:35:55 JohnArwe has joined #ldp 16:52:22 SteveS has joined #ldp 17:05:22 Zakim has left #ldp 17:05:33 trackbot, make logs public 17:05:33 Sorry, Arnaud, I don't understand 'trackbot, make logs public'. Please refer to for help. 17:05:51 rssagent, make log public 17:06:07 rrsagent, make log public 17:38:09 jmvanel has joined #ldp 18:23:02 bblfish has joined #ldp 18:25:03 SteveS has joined #ldp 19:39:28 bblfish has joined #ldp 20:39:33 bblfish has joined #ldp 21:24:44 deiu has joined #ldp 21:41:19 bblfish has joined #ldp 22:39:29 bblfish has joined #ldp 23:39:28 bblfish has joined #ldp