13:59:15 RRSAgent has joined #ldp 13:59:15 logging to http://www.w3.org/2014/07/21-ldp-irc 13:59:17 RRSAgent, make logs public 13:59:17 Zakim has joined #ldp 13:59:19 Zakim, this will be LDP 13:59:19 ok, trackbot; I see SW_LDP()10:00AM scheduled to start in 1 minute 13:59:20 Meeting: Linked Data Platform (LDP) Working Group Teleconference 13:59:20 Date: 21 July 2014 14:00:17 SW_LDP()10:00AM has now started 14:00:22 JohnArwe has joined #ldp 14:00:24 +JohnArwe 14:00:36 trackbot, start meeting 14:00:38 RRSAgent, make logs public 14:00:40 Zakim, this will be LDP 14:00:40 ok, trackbot, I see SW_LDP()10:00AM already started 14:00:41 Meeting: Linked Data Platform (LDP) Working Group Teleconference 14:00:41 Date: 21 July 2014 14:01:03 + +33.9.50.97.aaaa 14:01:04 +[IPcaller] 14:01:11 +Sandro 14:01:13 zakim, aaa is me 14:01:13 sorry, Arnaud, I do not recognize a party named 'aaa' 14:01:16 Zakim, IPcaller is me. 14:01:16 +codyburleson; got it 14:01:17 +??P16 14:01:21 +[IBM] 14:01:21 Ashok has joined #ldp 14:01:24 zakim, aaaa is me 14:01:24 +Arnaud; got it 14:01:29 Zakim, [IBM] is me 14:01:29 +SteveS; got it 14:01:31 Zakim, ??P16 is me 14:01:31 +nmihindu; got it 14:01:36 Zakim, mute me 14:01:36 nmihindu should now be muted 14:02:10 +Ashok_Malhotra 14:02:49 + +43.660.274.aabb 14:02:55 zakim, who's on? 14:02:55 I don't understand your question, JohnArwe. 14:03:02 MiguelAraCo has joined #ldp 14:03:07 Zakim, +43.660.274.aabb is me 14:03:07 +sergio; got it 14:03:12 zakim, who's on the call? 14:03:12 On the phone I see JohnArwe, Arnaud, codyburleson, Sandro, nmihindu (muted), SteveS, Ashok_Malhotra, sergio 14:04:04 +ericP 14:04:16 + +1.857.928.aacc 14:04:29 Zakim, aacc is Alexandre 14:04:29 +Alexandre; got it 14:05:07 regrets: andrei 14:05:53 slides for LD Patch walk-through are at http://lists.w3.org/Archives/Public/public-ldp-wg/2014Jul/att-0068/ldpatch.html 14:06:27 frac 14:06:34 scribe: johnarwe 14:06:54 topic: Minutes of last meeting - July 14 14:07:07 Proposal: Approve the minutes of the 14 July teleconf: http://www.w3.org/2013/meeting/ldp/2014-07-14 14:08:04 Arnaud: since trackbot was not started on time, reconstructed from private irc log 14:08:19 resolved: minutes approved w/o objections 14:08:30 topic: Next meeting 14:08:43 Arnaud: July 28 ... any objections? 14:08:56 resolved: July 28 next meeting 14:09:05 topic: actions + issues 14:09:08 action-143? 14:09:08 action-143 -- Nandana Mihindukulasooriya to Validate the JSON-LD examples of the primer -- due 2014-07-12 -- PENDINGREVIEW 14:09:08 http://www.w3.org/2012/ldp/track/actions/143 14:09:08 Regrets, in advance, for next meeting (July 28th); I'm on vacation. 14:09:33 yes, I corrected few errors and validated them. 14:09:50 resolved: close action-143 14:10:08 action-77? 14:10:08 action-77 -- Ted Thibodeau to Review and comment the WG Access Control draft at http://www.w3.org/2012/ldp/wiki/AccessControl -- due 2013-07-18 -- OPEN 14:10:08 http://www.w3.org/2012/ldp/track/actions/77 14:10:58 Ashok: enough review has happened, ok to close. got some feedback from TallTed. 14:11:07 resolved: close action-77 14:11:23 Arnaud gloats that all actions now closed. 14:12:20 topic: LD Patch Format Walk-through 14:12:39 http://lists.w3.org/Archives/Public/public-ldp-wg/2014Jul/att-0068/ldpatch.html 14:12:51 link to slides above 14:13:06 Andrei presents slides 14:13:18 s/Andrei/Alexandre/ 14:13:23 betehess is presenting 14:15:07 +OpenLink_Software 14:15:13 Zakim, OpenLink_Software is temporarily me 14:15:13 +TallTed; got it 14:15:14 Zakim, mute me 14:15:14 TallTed should now be muted 14:15:55 ashok: what is a pathological graph here? betehess: graphs containing bnodes that cannot be addressed 14:16:11 arnaud: document what it means in here 14:16:19 ...i.e. as limitations 14:16:34 +1 include section on LIMITATIONS, showing what kind of bnode structures CANT be patched 14:20:33 even turtle doesn't technically need '.'s 14:21:00 (i haven't tried without so perhaps some ambiguity would arise) 14:21:10 sandro: wrt syntax on page 5, perhaps could allow quads with relatively simple changes) 14:22:28 s/changes)/changes/ 14:23:46 q+ to ask about /schema:attendee[/foaf:name!]/schema:name 14:24:18 Arwe: need to define "pure" equality; offline email said it means the object, any datatype, and any lang tag need to all match 14:24:31 ...+ exact lexical match 14:24:38 question - recursive constraints? sequential constraints? 14:25:04 ack ericP 14:25:04 ericP, you wanted to ask about /schema:attendee[/foaf:name!]/schema:name 14:25:31 betehess: ericp's example would mean exactly one foaf:name 14:25:35 q+ 14:25:52 ack sandro 14:26:28 sandro: recursive constraints? alex: yes. and sequential? yes. 14:27:01 q+ 14:27:26 ack Ashok 14:27:37 sandro: timbl historically used caret for inverse instead of minus. Alex: authors don't care; left it as in Pierre-Antoinne's solution; wg members can make proposal to change rather than authors responding informally. 14:27:46 how about aligning with http://www.w3.org/TR/sparql11-query/#pp-language ??? 14:28:01 (which uses ^ instead of - ) 14:28:22 sandro, http://www.w3.org/TR/2013/REC-sparql11-query-20130321/#rPathEltOrInverse says "^" for inverse 14:28:37 and dont use ! for this 14:28:45 q+ 14:28:51 ashok: pathological you said have unaddressable bnodes, right? alexandre: used to traverse graph, could reference bnode w/o knowing its ID, using path expression ... that's exactly why that's they're in the syntax. 14:29:26 i guess there's some precedent for using "#" in formal maths, but that'd be nuts 14:29:36 Ashok, a pathological graph: _:x,_:y. 14:29:41 ashok: are there instances where that's still not enough? alex: yes, if the conditions are not unique. recent article published that explores use of bnodes in web datasets. 14:29:48 ...will followup on mailing list. 14:30:02 ack sandro 14:30:53 +1 to re-using SPARQL where possible (hoping there's something left to use in place of '!') 14:30:58 sandro: you should align with sparql property path syntax whereever you overlap, like inverse path. and avoid using bang, since they use it with a different syntax. don't gratuitously differ. Alex: we can review together. 14:31:25 slide 7 14:32:08 slide 8 14:32:45 Bind ?grandparent <#> /gen:parent . 14:32:51 Bind ?grandparent <#> /gen:parent . # now a grandparent? 14:33:17 sorry, s/<#>/?grandparent/ 14:33:57 Suggest ".." instead of ">" as slice operator. 14:33:58 betehess: if not careful, updatelist can lead to graphs 'pointing to nowhere' 14:34:33 ericp: can use a bound variable within its own (subsequent) binding? alexandre: yes 14:34:38 slide 9 14:35:12 q+ to ask why this is better than SPARQL UPDATE ? 14:35:29 q+ to ask why this is better than SPARQL UPDATE or a profile of SPARQL UPDATE 14:37:38 alexandre: very important for specifying operational semantics, i.e. math meaning given to the patch. 14:38:01 ack sandro 14:38:01 sandro, you wanted to ask why this is better than SPARQL UPDATE ? and to ask why this is better than SPARQL UPDATE or a profile of SPARQL UPDATE 14:39:12 sandro: like this in general. what's advantage of this over (some profile of) sparql update? most people's problem with sparql is the potentially exponential performance, and this proposal has the same complexity. 14:39:28 14:39:38 betehess: don't think complexity is exponential; provide example please. 14:41:07 sandro: social graph; /foaf:knows repeated 5x; that has 100million triples. Alex: no, not true. ... sandro: if branching factor is 1K, doesn't this branch rapidly? alex: no, don't remember other branches. ... more words... 14:41:26 Sandro, why is this worse than XPath? 14:44:05 meta-question to arnaud: there are other topics on the agenda, what is the time allocated to this current topic vs the later one(s)? 14:44:34 arnaud: take offline to mailing list 14:44:55 slide 9: status "almost ready" ...for what? Alex: adding operational semantics. 14:45:54 Arnaud: wg had 1 resolution to investigate this. we've fulfilled that. sandro's questions important. now need to decide if overall approach of _this proposal_ is ok with WG. 14:46:14 Alex: agree; if overall approach is ok, ready to publish FPWD 14:47:06 q+ to talk about how we addressed this before 14:47:40 We are actually using a patch format designed by Sandro, so we kind of feel like honoring his opinion on this matter (whatever it may be). And then, our one concern is just the fact that you have to know yet another language to understand LDP. 14:47:42 ack Steves 14:47:42 SteveS, you wanted to talk about how we addressed this before 14:48:04 sandro: would like someone to articulate why they'd use this proposal but would not use sparql update. 14:49:15 arnaud: concerned about spending lots of time fixing details if anyone in the wg has major issues with approach. 14:50:33 ericp: feels like people would have to write another parser, awkward to dup content in "competing" stds aside from an isomorphism. Alex: did not want to rely on sparql implementation(s). 14:51:19 arnaud: Alexandre, can you write the "why not sparql update" section to flush out? 14:51:21 https://www.w3.org/2012/ldp/wiki/LDP_PATCH_Proposals 14:51:59 sandro: fine if we want to publish FPWD saying very explicitly that we recognize overlap and invite comments on that specifically. 14:53:04 ... could also name a subset of sparql update equivalent to this, ericp. If it's not hard to exactly define the subset. 14:53:11 +1 LIMITATIONS section (and I recommend including some of the discussion/experience/justification for why these exist, and possibly what the other options were, and why they were not pursued) 14:53:11 also +1 FPWD with something like "while working through this, we found it to basically respecify SPARQL Update... without relying on a back-end SPARQL implementation. does anyone actually need this?" 14:53:41 Alex: issues with managing the dependencies on syntax etc. Thinks it's harder than Sandro/EricP appear to think/ 14:53:42 https://www.w3.org/2012/ldp/wiki/LDP_PATCH_Proposals#EricP.27s_proposal 14:55:12 discussion... not exactly ericp's proposal, really a version of that which "looks more like LDPatch" 14:55:40 sandro: missing variables and delete that I'd really like. thinking of long string literals. 14:55:52 sandro: I want "delete

*" and "delete * * " 14:55:58 bblfish has joined #ldp 14:57:17 alexandre: path is optional. bind it. sandro: don't want to transmit the literal at all. very hard to do with your proposal, although could be added pretty easily. Alex: if we change binding to be to a set of nodes, should fix that. 14:58:11 Action: betehess to make updates and handle sparql update reasoning 14:58:12 Created ACTION-144 - Make updates and handle sparql update reasoning [on Alexandre Bertails - due 2014-07-28]. 14:58:12 -Arnaud 14:58:33 shoot 14:58:46 should we wait for your chairness? 14:59:05 no, wha'ts the status of paging? 14:59:29 +Arnaud 14:59:35 cody: arnaud said I need to provide a pure-html (no respec) version, put that under TR dir? Steve S: will help. 14:59:51 yes. I am. 15:00:21 Thanks 15:01:23 Cody will submit the pure HTML (final) Best Practices document today into the TR directory. Will be on vacation next week. Nandana will help Cody keep an eye on any process to push that document through. 15:02:01 topic: paging 15:02:21 late-breaking email with list of "must be fixed by LC" changes 15:02:30 thanks, bye 15:02:32 -Alexandre 15:02:34 -Sandro 15:02:34 discussion of process; hope to work most out on list w/o formal issues 15:02:35 -TallTed 15:02:36 -Arnaud 15:02:37 -sergio 15:02:38 -ericP 15:02:39 -Ashok_Malhotra 15:02:40 I had a few comments as well on paging 15:02:43 -SteveS 15:02:48 arnaud: bulk of agenda next week to be paging 15:02:49 -codyburleson 15:02:52 -JohnArwe 15:02:54 -nmihindu 15:02:54 SW_LDP()10:00AM has ended 15:02:54 Attendees were JohnArwe, +33.9.50.97.aaaa, Sandro, codyburleson, Arnaud, SteveS, nmihindu, Ashok_Malhotra, sergio, ericP, +1.857.928.aacc, Alexandre, TallTed 15:14:25 bblfish has joined #ldp 16:10:32 SteveS has joined #ldp 16:28:24 codyburleson has joined #ldp 16:52:51 bblfish has joined #ldp 16:58:38 Zakim has left #ldp 17:03:57 bblfish has joined #ldp 17:25:24 stevebattle11114 has joined #ldp 17:54:11 SteveS_ has joined #ldp 17:59:56 bblfish has joined #ldp 18:21:29 bblfish has joined #ldp 18:24:26 bblfish has joined #ldp 18:48:54 bblfish has joined #ldp 20:17:51 bblfish has joined #ldp 22:13:22 bblfish has joined #ldp