14:58:09 RRSAgent has joined #ldp 14:58:09 logging to http://www.w3.org/2014/11/10-ldp-irc 14:58:11 RRSAgent, make logs public 14:58:11 Zakim has joined #ldp 14:58:13 Zakim, this will be LDP 14:58:13 ok, trackbot; I see SW_LDP()10:00AM scheduled to start in 2 minutes 14:58:14 Meeting: Linked Data Platform (LDP) Working Group Teleconference 14:58:14 Date: 10 November 2014 14:58:34 SW_LDP()10:00AM has now started 14:58:38 azaroth has joined #ldp 14:58:44 SW_LDP()10:00AM has ended 14:58:45 Attendees were 14:59:04 SW_LDP()10:00AM has now started 14:59:11 +deiu 14:59:22 that was a quick call 14:59:26 +azaroth 14:59:48 +Arnaud 15:00:51 +Sandro 15:01:50 Ashok has joined #ldp 15:02:24 +Ashok_Malhotra 15:02:45 +OpenLink_Software 15:02:57 Zakim, OpenLink_Software is temporarily me 15:02:59 Zakim, mute me 15:02:59 +TallTed; got it 15:03:01 TallTed should now be muted 15:03:02 +bblfish 15:03:15 hi 15:05:24 +Steve_Speicher 15:05:33 zakim, Steve_Speicher is me 15:05:33 +SteveS; got it 15:07:46 scribenick: deiu 15:08:04 Topic: approving minutes 15:08:08 pchampin has joined #ldp 15:08:24 Arnaud: there was an error in the last minutes, which tells me people don't read the minutes 15:08:41 ...we can safely approve them since there was no resolution 15:08:47 ...minutes approved 15:08:48 minutes are useful, and are important in that case 15:08:59 +??P13 15:09:02 Topic: actions & issues 15:09:11 -??P13 15:09:18 action-150 15:09:18 action-150 -- Alexandre Bertails to Add support for arbitrary text/turtle for the add operation in ldpatch -- due 2014-10-06 -- OPEN 15:09:18 http://www.w3.org/2012/ldp/track/actions/150 15:10:34 deiu will address action-150 15:10:49 Arnaud: status update 15:10:58 ...I sent the transition request but I didn't hear anything 15:11:08 ...I believe Eric needs to set up the call with W3M 15:11:22 ...but I haven't heard anything from him 15:11:30 ...too bad he's not available right now to hear what the status is 15:11:47 ...paging is not doing better either; the editors have updated the spec 15:11:54 maybe SteveS can tell us more about it? 15:12:09 s/maybe SteveS can tell us more about it?/...maybe SteveS can tell us more about it? 15:12:42 ...the process seems to have changed lately, merging two steps into one 15:12:57 sandro: try sending an email to Ralph just to make sure (informally) 15:13:02 +ericP 15:13:13 Arnaud: what I meant about the paging spec: you get to LC and then CR 15:13:46 ...you cannot do the disposition of comments and implementation reports at the same time 15:14:40 ...there's no real change to the timeline, even if theoretically it should be faster 15:15:19 ...in conclusion: the spec is ready 15:15:34 SteveS: the key thing to cover is that there were a couple of items marked "at risk" 15:15:53 ...I only got some pushback for the new status code (we didn't get support from IETF) 15:16:17 ...so I removed that from the spec, as well as the "at risk" markers from a couple of places in the spec 15:16:35 Arnaud: ok, so that should have been formally minuted 15:16:58 ...the point is 2NN is abandoned so SteveS removed it from the spec 15:17:22 ...John worked really hard on 2NN and it's a pity we had to remove a big chunk from the spec 15:17:58 ...so Eric, I'm waiting for a confirmation for the call re. the TR 15:18:20 ericP: I can reply to your email 15:19:00 ...people on the W3M call can be you, staff contacts and maybe editors 15:19:29 ericP: it might be easier to get a different call for the paging req 15:19:41 ...let's try not to sneak it in 15:19:48 Topic: LD patch format 15:20:07 zakim, who's on the phone? 15:20:07 On the phone I see deiu, azaroth, Arnaud, Sandro, Ashok_Malhotra, TallTed (muted), bblfish, SteveS, ericP 15:20:10 pchampin: ? 15:20:27 can't manage to reach zakim, sorry :-( 15:21:00 not much progress to report anyway, I'm afraid... 15:23:01 + +33.9.51.77.aaaa 15:24:43 pchampin: we're looking at having some SPARQL-like syntax allowed in the add operation 15:24:53 pchampin: we haven't made a lot of progress 15:25:12 Arnaud: it seems like the spec has been sitting there 15:25:26 ...we haven't seen a lot of updates 15:25:56 ...what is our position as a group? We agreed overall that we want to push it further... 15:26:07 ...I don't feel like there's a strong motivation to push it at this point 15:26:09 I think we need a PATCH format 15:26:34 q+ 15:26:39 Arnaud: are you still interested in putting in effort? 15:26:42 ack azaroth 15:27:03 azaroth: we're still interested in it, mostly because the PUT operation to update is constrained 15:27:19 ...we haven't worked on it yet, but it's something that we think is valuable 15:27:19 q+ 15:27:24 q+ 15:27:24 q+ 15:27:27 ack deiu 15:29:19 To clarify, we don't particularly care about the style, we just need the functionality 15:29:28 s/style/format/ 15:29:31 well everyone I think needs PATCH, but we could vote on it. 15:29:42 ack bblfish 15:30:22 bblfish: I think everyone needs PATCH 15:30:45 ...the format I see as being mostly used is SPARQL UPDATE 15:31:01 i suspect the fastest path is to publish http://www.w3.org/2005/01/yacker/uploads/SPARQL_patch?lang=perl&markup=html#productions with an at-risk crazy scheme for lists 15:31:06 q+ 15:31:09 semantics are done 15:31:11 -SteveS 15:31:35 ack pchampin 15:31:43 +SteveS 15:31:52 pchampin: I understand Henry, and I think it is a pragmatic solution 15:32:12 ...assuming that a SPARQL query fails, you would have a non-atomic operation 15:32:31 ...we need atomicity and you can't have it right now with the current SPARQL UPDATE 15:32:50 ...I believe there's room for a dedicated language with real PATCH semantics 15:32:58 ack SteveS 15:33:11 pchampin: the atomiticy problem in SPARQL Update is due to what? Is that due to the ability to PATCH subgraphs ?