13:57:20 RRSAgent has joined #ldp 13:57:20 logging to http://www.w3.org/2013/04/29-ldp-irc 13:57:22 RRSAgent, make logs public 13:57:22 Zakim has joined #ldp 13:57:24 Zakim, this will be LDP 13:57:24 ok, trackbot, I see SW_LDP()10:00AM already started 13:57:24 cody has joined #ldp 13:57:25 Meeting: Linked Data Platform (LDP) Working Group Teleconference 13:57:25 Date: 29 April 2013 13:57:56 +Sandro 13:58:03 +??P7 13:58:10 zakim, ??P7 is me 13:58:10 +pchampin; got it 13:58:29 +[IPcaller] 13:58:36 zakim IPcaller is me 13:58:38 sergio has joined #ldp 13:58:51 zakim, IPcaller is cody 13:58:51 +cody; got it 13:59:02 +JohnArwe 13:59:21 rgarcia has joined #ldp 13:59:23 + +329331aaaa 13:59:39 +Arnaud 14:00:05 - +329331aaaa 14:00:33 svillata has joined #ldp 14:00:46 AndyS has joined #ldp 14:00:54 nmihindu has joined #ldp 14:01:10 + +329331aabb 14:01:12 +??P17 14:01:18 zakim, +329331aabb is me 14:01:18 +mielvds1; got it 14:01:41 +??P2 14:01:53 Ashok has joined #ldp 14:01:54 zakim, ??P2 is me 14:01:54 +rgarcia; got it 14:01:55 zakim, who's on the phone? 14:01:56 On the phone I see SteveBattle, Sandro, pchampin, cody, JohnArwe, Arnaud, mielvds1, ??P17, rgarcia 14:02:19 +[IPcaller] 14:02:26 roger has joined #ldp 14:02:36 +Ashok_Malhotra 14:02:37 +[IPcaller.a] 14:02:42 Zakim, [IPcaller] is me 14:02:42 +sergio; got it 14:02:52 +??P24 14:02:56 zakim, IPCaller.a is me 14:02:56 +AndyS; got it 14:02:59 regrets: steve speicher, eric p 14:03:08 +??P25 14:03:09 regrets: bart 14:03:23 zakim, who's making noise? 14:03:30 + +44.208.573.aacc 14:03:34 JohnArwe, listening for 10 seconds I heard sound from the following: Arnaud (38%), ??P25 (42%) 14:03:41 Partial apologies - limited to 30 mins. 14:03:48 zakim, who's on the phone? 14:03:49 On the phone I see SteveBattle, Sandro, pchampin, cody, JohnArwe, Arnaud, mielvds1, ??P17, rgarcia, sergio, Ashok_Malhotra, AndyS, ??P24, ??P25, +44.208.573.aacc 14:04:18 -??P25 14:04:34 kakim, +44.208.573.aacc is me 14:04:43 +bblfish 14:04:46 zakim, ??P24 is me 14:04:46 +nmihindu; got it 14:04:52 zakim, +44.208.573.aacc is me 14:04:52 +roger; got it 14:04:58 +??P27 14:05:16 Zakim, ??P27 is me 14:05:16 +svillata; got it 14:05:44 scribe: svillata 14:05:51 zakim, who's making noise? 14:06:03 JohnArwe, listening for 11 seconds I heard sound from the following: SteveBattle (46%), JohnArwe (9%), Arnaud (64%), mielvds1 (3%) 14:07:22 Topic: approval minutes last call 14:08:24 +??P31 14:08:26 -??P31 14:08:59 +OpenLink_Software 14:09:04 Zakim, OpenLink_Software is temporarily me 14:09:04 +TallTed; got it 14:09:19 +Yves 14:09:30 Arnaud: we can change the minutes accoding to TallTed argument 14:09:37 arnaud: will clean up minutes to address JohnArwe's email 14:09:50 s/accoding/according/ 14:09:59 Thanks 14:10:07 Arnoud: I will update the monutes 14:10:19 Transactions? 14:10:30 RESOLVED: minutes approved 14:10:46 s/monutes/minutes 14:10:56 Topic:next F2F meeting 14:11:15 Arnaud: please specify your participation to the next F2F meeting 14:11:25 http://www.w3.org/2012/ldp/wiki/F2F3 14:11:30 just for info, next Monday is public holliday here in UK ... 14:11:44 Zakim, mute me 14:11:44 TallTed should now be muted 14:11:53 Topic: Actions and Issues 14:12:23 Action-54> 14:12:23 ACTION-54 -- Nandana Mihindukulasooriya to review the 'PROV-AQ: Provenance Access and Query' document and provide feedback -- due 2013-04-01 -- PENDINGREVIEW 14:12:23 http://www.w3.org/2012/ldp/track/actions/54 14:12:34 resolved: close action-54 14:12:35 RESOLVED: Close ACTION-54 14:13:04 Arnaud: Any other action to be consider for closure? 14:13:33 krp has joined #ldp 14:14:27 Arnaud: time is going by, we have quite a few actions we are waiting for 14:15:02 Arnaud: there was an action about the patch, do you know the status of it? 14:15:17 The PATCH format action is important 14:15:34 q+ 14:15:36 Is there a PATCH Action? 14:16:04 ack steveb 14:16:26 Arnaud: at the F2F we agree on the direction, we need to make sure we don't are lost 14:16:47 ... we don't have an action on that 14:16:59 ... Sandro is working on the PATCH action 14:17:29 Arnaud: we have one rased issue 14:17:30 +??P35 14:17:48 zakim, ??P35 is me 14:17:48 +krp; got it 14:17:48 http://www.w3.org/2012/ldp/track/issues/61 14:18:00 Topic: ISSUE-61 14:18:23 Arnaud: why do you think it is a problem? 14:18:43 SteveS has joined #ldp 14:18:50 SteveS has left #ldp 14:19:20 zakim, who's making noise? 14:19:29 q+ 14:19:31 JohnArwe, listening for 10 seconds I heard sound from the following: rgarcia (9%), mielvds1 (4%) 14:19:32 bblfish - you moved from a clear vocal space, to the bottom of a well... 14:20:20 ack steveb 14:20:49 stevebattle: the membership subject is not necessarily a separate LDPR 14:21:03 q+ 14:21:13 ... I agree with your point of view, maybe removing flexibility 14:21:15 ack john 14:21:28 Issue-61 14:21:28 ISSUE-61 -- remove membershipSubject -- raised 14:21:28 http://www.w3.org/2012/ldp/track/issues/61 14:22:24 q? 14:22:42 zakim, mute me 14:22:42 rgarcia should now be muted 14:23:16 JohnArwe: we have existing resources to be structured naturally, I assign membership subject or vary membership predicate 14:24:14 bblfish: you only allow the content to be placed to another container 14:24:35 Inline members which may be containers (so type triple is not unique)? 14:24:36 -??P17 14:24:42 ... for the moment the relations can only be a sub-relation of RDF member 14:25:07 zakim, who's on the phone? 14:25:07 On the phone I see SteveBattle, Sandro, pchampin, cody, JohnArwe, Arnaud, mielvds1, rgarcia (muted), sergio, Ashok_Malhotra, AndyS, nmihindu, roger, bblfish, svillata, TallTed 14:25:11 ... (muted), Yves, krp 14:25:33 ... we could think to a way of doing things in a more general way 14:26:02 bblfish: the new container is related to the new content 14:26:40 ... membership predicate does not say LDP membership 14:26:46 krp has joined #ldp 14:27:09 Arnaud: there is no restriction to RDF member 14:27:17 q+ 14:27:38 +??P17 14:27:53 zakim, ??P17 is me 14:27:53 +krp; got it 14:27:56 q? 14:28:08 ack steveb 14:28:32 stevebattle: I agree with John, there is not such a kind of restriction 14:29:18 q+ 14:29:39 @steveabattle ... on the subject, is my opinion 14:30:10 Arnaud: you may have a resource which has nothing to do with LDP resource 14:30:19 Sounds like there's a difference of interpretation here then? 14:30:22 q- 14:30:27 ack pchampin 14:30:27 Arnaud: we need to move on 14:30:47 pchampin: I can ask my question on the mailing list 14:31:31 Zakim, unmute me 14:31:31 TallTed should no longer be muted 14:31:38 Arnaud: it's better to go on with the open issues and actions 14:32:33 q? 14:32:57 "I don't understand" (which is rather open) needs to be turned into "If I read it as XYZ, then ABC is a problem" 14:33:49 Arnaud: either we close it or we rename it as membership subject 14:34:03 bblfish: I can rename for next week 14:34:22 e.g., "membershipSubject needs better description, or possible removal" 14:34:33 Zakim, mute me 14:34:33 TallTed should now be muted 14:34:41 agreed, rename and retake 14:34:46 Arnaud: unless somebody makes a concrete proposal 14:34:51 I'd prefer to see clarification. 14:35:13 bblfish: you can close the issue and then I'll reopen it clarifying 14:35:40 yes 14:35:41 ok 14:35:44 ok 14:35:49 ok 14:35:54 resolved: close issue-6`, henry to raise another issue asking for clarification 14:36:03 resolved: close issue-61, henry to raise another issue asking for clarification 14:36:11 close Issue-61 14:36:11 Closed ISSUE-61 remove membershipSubject. 14:36:23 Topic: open issues 14:36:32 Issue-26? 14:36:32 ISSUE-26 -- creation model for LDP -- open 14:36:32 http://www.w3.org/2012/ldp/track/issues/26 14:36:36 Arnaud: proposal close Issue-26 14:37:11 Arnaud: suggested to put it in the wish list, and close Issue-26 14:37:19 ... any problem with this? 14:38:05 ashok: what are we closing? what are we not specifying now? 14:38:18 +q 14:39:03 ashok: do we have an open issue on how do we create a container? 14:39:43 Arnaud: the answer I believe the spec is silent about how to create a container, you can create a container as you create the other resources 14:40:39 ack roger 14:40:41 Issue-36? 14:40:41 ISSUE-36 -- Can applications create new containers? -- closed 14:40:41 http://www.w3.org/2012/ldp/track/issues/36 14:40:42 Where I'm stuck is how you know whether a particular container will look at the POSTed content to see if it should make a subcontainer. We need a way to say what stuff is looked for in POST. 14:40:58 IIRC we have talked about capturing that answer in some of the non-Rec-track documents (primer/whatever) to keep it clear what's part of the normative content vs what's an implication of the normative content. 14:41:02 (aka affordances.) 14:41:25 Roger: I'm not talking about create a container inside a container 14:42:53 Arnaud: the editors have an action item to specify how to create containers in the spec 14:42:54 I mean containers as 'siblings' of other containers ... 14:43:39 Proposed: close issue 26 14:43:47 PROPOSAL: Close ISSUE-26: Creation model for LDP as is, add it to the wishlist for LDP.next 14:43:51 what's the open action? 14:44:01 +1 issue-26 is incredibly vague 14:44:08 +1 14:44:09 Zakim, unmute me 14:44:09 TallTed should no longer be muted 14:44:09 +1 14:44:10 +1 14:44:15 +1 14:44:16 +1 14:44:20 cody has joined #ldp 14:44:22 +1 14:44:24 Arnaud: no action on the tracker, it's issue-26 14:44:26 +1 14:44:26 q? 14:44:26 +1 14:44:27 +1 14:44:29 +1 14:44:51 +1 as long as isse-36 remains open 14:45:18 You mean providing 36 is reopened? 14:45:23 roger's sibling example: using the existing spec example (net-worth has 2 containers, assets and liabilities), how would roger create a 3rd container within the net-worth resource? 14:45:33 Issue-36 is closed at the moment 14:45:34 action: steve to propose text clarifying the creation of container, per resolution of issue-36 14:45:34 'steve' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., sspeiche, sbattle2). 14:45:39 +1 pending action creation and association with both issues (reviewing action completion will inform whether a new issue is needed... and clarity of that issue) 14:45:45 Zakim, mute me 14:45:45 TallTed should now be muted 14:45:46 action: steves to propose text clarifying the creation of container, per resolution of issue-36 14:45:46 Created ACTION-55 - Propose text clarifying the creation of container, per resolution of issue-36 [on Steve Speicher - due 2013-05-06]. 14:45:49 +1 move issue-26 to ldp.next 14:45:53 Ah! thanks, Cody! 14:46:13 resolved: Close ISSUE-26: Creation model for LDP as is, add it to the wishlist for LDP.next 14:46:14 RESOLVED: Issue-26 14:46:37 Issue-59? 14:46:37 ISSUE-59 -- Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior -- open 14:46:37 http://www.w3.org/2012/ldp/track/issues/59 14:46:37 issue-59? 14:46:37 ISSUE-59 -- Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior -- open 14:46:38 Issue-59 14:46:38 http://www.w3.org/2012/ldp/track/issues/59 14:46:38 ISSUE-59 -- Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior -- open 14:46:38 http://www.w3.org/2012/ldp/track/issues/59 14:47:20 Arnaud: we revert to the original spec, when you delete a container there is no guarantee, you delete the content too 14:47:21 @JohnArwe, I am opening a issue on this now. 14:47:33 i.e. about the siblings 14:47:38 ... I put together a new proposal based on bblfish one 14:48:15 ...you have the members, and then when you delete the container you delete these members only, and not the others 14:48:18 Arnaud is summarising http://lists.w3.org/Archives/Public/public-ldp-wg/2013Apr/0123.html 14:49:34 Arnaud: A) we have one container, B) we get rid of the two types of container, C) we stick with what we have 14:49:57 1,0,0 14:49:57 A (I think) 14:50:04 +1 A 14:50:06 A 14:50:06 A 14:50:07 A (leaning towards) 14:50:10 A 14:50:11 A 14:50:11 A 14:50:27 q+ 14:50:29 A 14:50:32 I think the difference between A and B is whether or not clients can "introspect" which member resources the server will delete if the container is deleted. 14:50:34 B 14:50:37 A 14:50:40 A +0.5 B +1.0 C -1.0 14:50:54 Currently: A 14:51:07 +1, +0, -0.5 14:51:33 Arnaud: A also implies we do not do a recursive deletion automatically 14:51:43 +0.8 A 14:51:44 A: +1, B: -0.5, C: -1 14:51:45 ... we have two different delete operations 14:51:57 ... there are also other options we can invent 14:52:05 q? 14:52:14 ... Does anybody object to option A? 14:52:16 Zakim, unmute me 14:52:16 TallTed should no longer be muted 14:53:41 -AndyS 14:53:44 bye AndyS 14:53:44 AndyS has left #ldp 14:54:31 Arnaud: personally I prefer option B, it addresses the main issue 14:54:48 Zakim, unmute me 14:54:48 TallTed was not muted, TallTed 14:54:53 A: 0 B: +1.0 C 14:55:21 q? 14:55:42 ack sergio 14:56:19 sergio: we should do the same as for the resources 14:57:15 Arnaud: objections to option A? 14:57:29 proposal: close issue-59, with option A 14:57:34 +1 14:57:37 +1 14:57:38 +1 14:57:41 +1 14:57:41 +1 14:57:42 +1 14:57:44 +1 amending 3rd point 14:58:02 +1 14:58:04 +1 14:58:14 +0 14:58:18 Arnaud: we can do something more robust in the future, as TallTed says 14:58:21 +1 14:58:39 +1 14:58:56 close Issue-59 14:58:56 Closed ISSUE-59 Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior. 14:59:02 +1 14:59:42 resolved: close issue-59, with option A 15:00:42 bye 15:00:43 -bblfish 15:00:48 -Ashok_Malhotra 15:01:45 bye 15:01:45 -cody 15:01:47 -TallTed 15:01:48 -JohnArwe 15:01:49 -krp.a 15:01:50 cody has left #ldp 15:01:50 -roger 15:01:50 -SteveBattle 15:01:51 -sergio 15:01:51 -svillata 15:01:51 -rgarcia 15:01:52 -mielvds1 15:01:54 -Arnaud 15:01:55 -nmihindu 15:01:55 -pchampin 15:01:57 -Yves 15:03:59 -Sandro 15:07:48 mielvds has joined #ldp 15:09:00 disconnecting the lone participant, krp, in SW_LDP()10:00AM 15:09:02 SW_LDP()10:00AM has ended 15:09:02 Attendees were SteveBattle, Sandro, pchampin, cody, JohnArwe, +329331aaaa, Arnaud, mielvds1, rgarcia, Ashok_Malhotra, sergio, AndyS, bblfish, nmihindu, roger, svillata, TallTed, 15:09:02 ... Yves, krp 15:15:45 mielvds has left #ldp 17:04:44 Zakim has left #ldp 17:41:35 bblfish has joined #ldp 17:57:32 davidwood has joined #ldp 18:40:12 jmv has joined #ldp 19:12:57 AndyS has joined #ldp