13:55:52 RRSAgent has joined #ldp 13:55:52 logging to http://www.w3.org/2013/04/22-ldp-irc 13:55:53 RRSAgent, make logs public 13:55:54 Zakim has joined #ldp 13:55:55 Zakim, this will be LDP 13:55:56 ok, trackbot; I see SW_LDP()10:00AM scheduled to start in 5 minutes 13:55:56 Meeting: Linked Data Platform (LDP) Working Group Teleconference 13:55:57 Date: 22 April 2013 13:58:07 nmihindu has joined #ldp 13:58:33 SW_LDP()10:00AM has now started 13:58:40 +??P3 13:58:46 krp has joined #ldp 13:58:54 Ashok has joined #ldp 13:59:11 zakim, ??P3 is me 13:59:11 +pchampin; got it 13:59:27 BartvanLeeuwen has joined #ldp 14:00:06 +[IPcaller] 14:00:16 +??P5 14:00:27 +Arnaud 14:00:27 rgarcia has joined #ldp 14:00:40 +OpenLink_Software 14:00:46 +Ashok_Malhotra 14:00:47 +??P8 14:00:55 Zakim, ??P8 is me 14:00:55 +BartvanLeeuwen; got it 14:00:57 +??P10 14:01:10 Zakim, OpenLink_Software is temporarily me 14:01:10 +TallTed; got it 14:01:11 +??P12 14:01:11 Zakim, mute me 14:01:13 TallTed should now be muted 14:01:35 Zakim, ??P12 is me 14:01:35 +svillata; got it 14:01:49 +[IBM] 14:01:54 Zakim, [IBM] is me 14:01:55 +SteveS; got it 14:02:01 zakim, who's on the phone? 14:02:01 On the phone I see pchampin, [IPcaller], ??P5, Arnaud, TallTed (muted), Ashok_Malhotra, BartvanLeeuwen, ??P10, svillata, SteveS 14:02:18 roger has joined #ldp 14:03:13 +??P15 14:03:36 zakim, ??P15 is me 14:03:36 +rgarcia; got it 14:03:40 +??P17 14:03:43 + +44.208.573.aaaa 14:03:43 +[GVoice] 14:03:50 cody has joined #ldp 14:04:00 scribenick: Ashok 14:04:04 -[IPcaller] 14:04:12 +SteveBattle 14:04:36 zakim, ??P17 is me 14:04:36 +nmihindu; got it 14:04:42 -??P10 14:04:50 Topic: Minutes from lat week 14:04:52 http://www.w3.org/2012/ldp/meeting/2013-04-15 14:04:55 +[IPcaller] 14:05:00 s/lat/last/ 14:05:08 zakim, IPCaller is me 14:05:08 +cody; got it 14:05:44 http://www.w3.org/2013/meeting/ldp/2013-04-15 14:05:46 +??P1 14:05:47 -??P5 14:05:55 http://www.w3.org/2013/ldp/meeting/2013-04-15 14:06:06 zakim, ??P1 is me 14:06:06 +krp; got it 14:06:10 Note revised link above 14:06:27 It was 2012 for the previous minutes as well 14:06:29 Arnaud - Ashok's link is correct ... differs from yours 14:06:58 sorry, I'm wrong. *this* works -- http://www.w3.org/2013/meeting/ldp/2013-04-15 14:07:07 Zakim, unmute me 14:07:07 TallTed should no longer be muted 14:07:41 +bblfish 14:07:54 object to what? 14:08:06 ah yes, the meetings from last week. 14:08:08 thanks 14:08:39 RESOLUTION: Minutes from 4/15 are accepted 14:08:55 Topic: f2f in Madrid 14:09:02 +??P10 14:09:06 ah that's cool. When is it? 14:09:15 Raul has added hotel info to f2f 14:10:09 When is the next F2F? I have not been following closely enough 14:10:12 Arnaud: You can get a hotel anywhere in downtown Madrid and take public transport 14:10:25 Raul: Yes ... may take 30 minutes 14:10:35 +q 14:10:38 q- 14:10:45 Topic: Actions and Issues 14:10:47 what was the URL for the next meeting? 14:10:48 sergio has joined #ldp 14:10:53 bblfish, it will be June 18-20 14:11:02 Mh. ok. thanks perfect 14:11:02 http://www.w3.org/2012/ldp/wiki/F2F3 14:11:22 +[IPcaller] 14:11:38 -BartvanLeeuwen 14:11:45 Zakim, mute me 14:11:45 TallTed should now be muted 14:11:49 Zakim, who's noisy? 14:11:49 Somebody needs to mute. 14:11:52 Zakim, [IPcaller] is me 14:11:52 +sergio; got it 14:12:00 TallTed, listening for 10 seconds I heard sound from the following: cody (57%), Arnaud (86%), [IPcaller] (56%) 14:12:03 +??P8 14:12:08 Zakim, ??p8 is me 14:12:08 +BartvanLeeuwen; got it 14:12:16 -krp 14:12:26 Arnaud: Please do your action items 14:12:52 Roger: I have been on vacation will try this week 14:13:38 zakim, who is making noise 14:13:38 I don't understand 'who is making noise', bblfish 14:13:39 krp has joined #ldp 14:13:43 zakim who is making noise 14:13:51 Arnaud: Nandana, when can you do the review of the PROV documents? 14:14:19 Zakim, who's noisy? 14:14:25 Erik has already provided some comments on the mailing list and I will provide mine within next week 14:14:36 sergio, listening for 10 seconds I heard sound from the following: Arnaud (29%) 14:15:07 Arnaud: No new issues 14:15:38 Topic: ISSUE-35: POSTing to a container MUST yield a fresh URI 14:15:43 Issue-35? 14:15:43 ISSUE-35 -- POSTing to a container MUST yield a fresh URI -- open 14:15:43 http://www.w3.org/2012/ldp/track/issues/35 14:16:18 Arnaud: There has been a long discussion on this 14:16:57 but restauring a URL with a POST should not be a good reason. Use a PUT then 14:17:19 SimpsonTP_ has joined #ldp 14:17:22 +??P1 14:17:29 zakim, ??P1 is me 14:17:29 +krp; got it 14:17:42 +??P21 14:17:47 Zakim, ??p21 is me 14:17:47 +SimpsonTP_; got it 14:18:03 Zakim, ??p21 is me 14:18:03 I already had ??P21 as SimpsonTP_, BartvanLeeuwen_ 14:18:11 q+ 14:18:23 ack bblfish 14:18:31 PROPOSAL: Close ISSUE-35: POSTing to a container MUST yield a fresh URI, by adding that servers SHOULD not reuse URLs while acknowledging that they MAY under certain circumstances, per Arnaud's suggestion 14:18:35 Arnaud: I suggest we say servers SHOULD not reuse URIs ... but may be reused in some cases 14:18:49 Zakim, unmute me 14:18:49 TallTed should no longer be muted 14:18:59 q+ 14:19:06 Kalpa has joined #ldp 14:19:12 I don't think we need to encourage re-use. just say "SHOULD" 14:19:15 ack tallted 14:19:17 Exactly, MacTed swayed me to his cause with this compelling argument as well. 14:19:27 bblfish: ... Due to past history being lost 14:19:30 +1 14:19:31 +1 14:19:32 +1 14:19:33 +1 14:19:33 +1 14:19:34 +1 14:19:34 +1 14:19:35 +1 14:19:36 +1 14:19:38 +1 14:19:41 +1 14:19:41 +1 14:19:45 +1 14:19:46 Zakim, mute me 14:19:46 TallTed should now be muted 14:19:47 +1 14:19:48 +1 14:19:58 Resolved: Close ISSUE-35: POSTing to a container MUST yield a fresh URI, by adding that servers SHOULD not reuse URLs while acknowledging that they MAY under certain circumstances, per Arnaud's suggestion 14:20:20 Issue-59? 14:20:20 ISSUE-59 -- Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior -- open 14:20:20 http://www.w3.org/2012/ldp/track/issues/59 14:20:37 Topic: ISSUE-59: Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior 14:21:30 Arnaud: Discusses the issue and current positions 14:21:55 ... SteveS had suggested a single type of container 14:22:50 ... if container deleted it goes away ... server MAY delete some of the contained resources 14:23:45 ... some folks want an attribute that says members are deleted or not 14:24:07 q+ 14:24:32 ack bblfish 14:24:41 q+ 14:24:46 Zakim, unmute me 14:24:46 TallTed should no longer be muted 14:25:51 bblfish: You could create a weak container ... 14:26:13 <.> ldp:contains <> 14:26:46 I think if you are POSTing to a container, then it is always a 'strong member', IMO. 14:26:49 ... That would be a strong member ... if not it would be a weak member 14:28:20 q+ 14:28:36 ack tallted 14:29:08 Ted: Decisions were made and then we decided we did not consider everything 14:29:23 ... I would rather not revisit decisions 14:29:32 ack pchampin 14:29:41 (sorry my voip is very bad) 14:29:43 I'll type 14:29:50 Well Ted, the vote for weak aggregation was very weak. 2+1 only, so it was not that strong 14:29:55 If we decide that containers are mostly for creating resources 14:29:58 s/then we decided/then we realized/ 14:30:06 and have no comitment w.r.t delete 14:30:14 may be it would be better to rename them otherwise 14:30:18 factory? 14:30:57 q+ 14:31:06 ./me sorry TallTed, I wasn't there, and I missed that in the minutes, then... 14:31:19 creation, pagination, update 14:31:29 ack steves 14:32:14 SteveS: Maybe we could agree on semantics and leave naming for later 14:33:10 ... Henry suggested that a contains relation could be added when a member is added and these would 14:33:29 ... deleted when container is deleted 14:33:44 Zakim, mute me 14:33:44 TallTed should now be muted 14:33:59 ... lot of open issues with contains type model as well 14:34:30 q? 14:35:02 PROPOSAL: close ISSUE-59 per Steve's suggestion, per Arnaud's email: http://lists.w3.org/Archives/Public/public-ldp-wg/2013Apr/0088.html 14:35:17 Arnaud: Let me make a proposal ... 14:35:19 so you're proposing the first option from your mail? 14:35:30 +1 (with questions) 14:35:36 +1 14:35:39 +1 14:35:45 +0 14:35:47 +1 (first option) 14:35:54 +1 14:35:56 -0.7 (not sure why we have problems with what is there now) 14:35:57 Zakim, unmute me 14:35:57 TallTed should no longer be muted 14:36:12 +1 14:36:13 +1 14:36:16 rgarcia has left #ldp 14:36:24 +1 14:36:27 rgarcia has joined #ldp 14:36:37 +1 I can live with this 14:36:40 -1 14:36:46 +1 14:36:50 +1 14:36:53 +0 14:37:03 q+ 14:37:17 Arnaud: We have a single type of container and postpone the recursive delete issue 14:38:14 it's all here -- http://lists.w3.org/Archives/Public/public-ldp-wg/2013Apr/0088.html 14:38:27 Arnaud has joined #ldp 14:39:02 http://lists.w3.org/Archives/Public/public-ldp-wg/2013Apr/0088.html 14:40:08 http://www.w3.org/2012/ldp/track/issues/14 14:40:12 Issue-59? 14:40:12 ISSUE-59 -- Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior -- open 14:40:12 http://www.w3.org/2012/ldp/track/issues/59 14:41:09 DRAFT PROPOSAL: Close ISSUE-59 by having only 1 single type of container: ldp:Container, deletion of container will remove membership triples (server may remove member resources), put recursive delete on wish list 14:41:42 it's here now -- http://www.w3.org/2012/ldp/track/issues/59 14:41:44 dangit 14:41:56 q+ 14:42:05 q- 14:42:46 -SimpsonTP_ 14:42:46 q+ 14:42:57 What's the difference between these two options? 14:43:03 STRAWPOLL: option a, option b from note at http://www.w3.org/2012/ldp/track/issues/59 14:43:11 Bart has the best excuses for leaving a meeting. 14:43:57 A +0 B +0.5 (I'd prefer B to have "SHOULD delete ldp:contains" rather than MUST) 14:44:16 A:+1, B:-.5 14:44:27 +1,0 14:44:48 ack ashok 14:44:57 ack bblfish 14:45:13 +1, -0.51 14:45:31 A:+0 B:-1 14:45:33 A:+1, B:-0.49 14:45:47 q+ 14:45:56 A: +1, B: 0 14:46:24 A: +1, B: -1 14:46:36 ack me 14:46:44 ok, after thinking a bit, I change my vote: A: +1, B: 0 14:46:51 q+ 14:47:43 ack cody 14:48:20 q+ 14:48:41 q+ 14:49:09 ack bblfish 14:49:17 A: +0.8, B: -0.2 14:50:10 Henry: Asks why not 2 kinds of containers ... we should recap arguments that appeaed after TPAC 14:50:30 q+ 14:50:32 Zakim, unmute me 14:50:32 TallTed was not muted, TallTed 14:50:35 ... you shouldn't be deleting stuff on the Web in any case 14:51:51 Ted: Argus by analogy with file system ... you have to delete members manually 14:52:13 s/Argus/Argues/ 14:52:26 DELETE -r /container HTTP/1.0 ? 14:52:33 ... people find that tedious 14:52:47 bblfish: and by the way, you don't really delete the file (in *nix filesystems at least) by removingit from a directory 14:53:11 ... it only gets deleted when no hard link to it exists anymore 14:54:00 pchampin, oof, another challenge associated with recurssive delete, *known* links to a contained resource 14:54:07 If people want filesystem semantics, I wonder why they just don't use WebDAV 14:54:28 SteveS, does WebDAV offer recurssive delete? 14:54:37 ack pchampin 14:54:40 about option B: As an implementer, I don't feel comfortable in letting the client deciding which resources are strongly contained and which are not. I would rather leave it to the implementation to decide that. 14:54:54 Arnaud: We have a third option ... keep spec as is ... two types of containers 14:55:06 ericP, that is the default model and only one 14:55:18 q+ 14:55:29 hence my -1 on option B 14:55:48 ack steves 14:56:04 pchampin: I don't think option B is saying the client would decide that. 14:56:34 SteveS: Agrees with pchampin argument 14:57:07 gavinc has joined #ldp 14:57:11 ... if we have 2 types of containers we need to define how we can switch from to another, etc. 14:57:20 ack cody 14:57:40 I never liked the two different kinds of containers. 14:58:12 -ericP 14:58:50 Ashok: I was worried about DELETE semantics 14:59:18 +0.5 14:59:22 @bblfish: may be I misread item 3; I was assuming that the client can specify the ldp:contains arc at POST time 14:59:34 +1 14:59:34 PROPOSAL: close ISSUE-59 per Steve's suggestion, option a in note http://www.w3.org/2012/ldp/track/issues/59 14:59:39 +1 14:59:41 pchampin: that was something I was thinking of 14:59:42 +1 14:59:46 +1 14:59:47 +1 14:59:48 @bblfish: re-reading it, that's still how I understand it... 14:59:49 +1 15:00:48 q+ 15:01:04 ack bblfish 15:01:17 Ashok: Option 1 may cut off an option for recursive delete 15:01:59 +1 15:02:09 bblfish, the origins of this issue is that it is not simpleā€¦per discussions at Cambridge 15:02:11 Henry: Perhaps work out option 2 more fully 15:02:33 Arnaud: Please send mail with worked out proposals 15:02:46 one additional week to discuss by mail make sense 15:03:09 -bblfish 15:03:14 thanks 15:03:15 -cody 15:03:17 Arnaud: Let's take a week otherwise we will close with option A 15:03:19 -Yves 15:03:22 MEETING ADJOURNED 15:03:22 - +44.208.573.aaaa 15:03:24 -sergio 15:03:25 -SteveS 15:03:25 -svillata 15:03:26 -TallTed 15:03:26 -nmihindu 15:03:29 -krp 15:03:31 -Arnaud 15:03:31 -SteveBattle 15:03:32 -Ashok_Malhotra 15:03:33 -rgarcia 15:03:36 -pchampin 15:06:36 SteveS has joined #ldp 15:08:37 disconnecting the lone participant, BartvanLeeuwen, in SW_LDP()10:00AM 15:08:38 SW_LDP()10:00AM has ended 15:08:38 Attendees were pchampin, Arnaud, Ashok_Malhotra, BartvanLeeuwen, TallTed, svillata, SteveS, rgarcia, +44.208.573.aaaa, ericP, SteveBattle, nmihindu, cody, krp, bblfish, Yves, 15:08:38 ... sergio, SimpsonTP_ 15:11:14 Kalpa has left #ldp 15:13:46 sorry about that ;) 15:19:33 got the RDF to prove it: http://data.brandweeraa.nl/data/messages/c89b8140690204b1f10bc27edd81b86eede3003f 15:19:35 cya 16:40:32 hi all 16:40:39 does anyone who SimpsonTP is? 17:01:05 Zakim has left #ldp 17:12:46 Arnaud, at 10:17, I read * SimpsonTP_ is now known as BartvanLeeuwen_ 17:12:56 also, Bart <-> Simpson 17:32:16 jmvanel has joined #ldp 17:32:57 ah, thanks Alexandre! 18:40:14 bblfish has joined #ldp