13:57:42 RRSAgent has joined #ldp 13:57:42 logging to http://www.w3.org/2013/10/07-ldp-irc 13:57:44 RRSAgent, make logs public 13:57:44 Zakim has joined #ldp 13:57:46 Zakim, this will be LDP 13:57:46 ok, trackbot; I see SW_LDP()10:00AM scheduled to start in 3 minutes 13:57:47 Meeting: Linked Data Platform (LDP) Working Group Teleconference 13:57:47 Date: 07 October 2013 13:59:07 pchampin has joined #ldp 13:59:46 SW_LDP()10:00AM has now started 13:59:48 +Arnaud 14:00:17 Zakim, please dial ericP-mobile 14:00:17 ok, ericP; the call is being made 14:00:19 +EricP 14:00:37 JohnArwe has joined #ldp 14:00:45 +JohnArwe 14:00:45 -JohnArwe 14:00:45 +JohnArwe 14:00:54 betehess_ has joined #ldp 14:01:17 zakim, who's here? 14:01:17 On the phone I see Arnaud, EricP, JohnArwe 14:01:18 On IRC I see betehess_, JohnArwe, pchampin, Zakim, RRSAgent, davidwood, bhyland, TallTed, betehess, jmvanel, deiu, Arnaud, Yves, thschee, trackbot, sandro, ericP 14:01:20 +EricM 14:02:18 Zakim, EricM is Alexandre 14:02:18 +Alexandre; got it 14:04:14 +[IPcaller] 14:04:21 Ashok has joined #ldp 14:04:25 roger has joined #ldp 14:05:09 +Ashok_Malhotra 14:05:19 zakim, IPcaller is roger 14:05:19 +roger; got it 14:05:47 +bblfish 14:06:23 krp has joined #ldp 14:06:48 +OpenLink_Software 14:06:54 Zakim, OpenLink_Software is temporarily me 14:06:54 +TallTed; got it 14:06:55 Zakim, mute me 14:06:55 TallTed should now be muted 14:07:20 zakim, who's on the phone? 14:07:20 On the phone I see Arnaud, EricP, JohnArwe, Alexandre, roger, Ashok_Malhotra, bblfish, TallTed (muted) 14:07:55 +??P25 14:08:03 bblfish has joined #ldp 14:08:14 +??P24 14:08:25 hi 14:08:27 zakim, P25 is pchampin 14:08:27 sorry, Arnaud, I do not recognize a party named 'P25' 14:08:38 zakim, ??P25 is pchampin 14:08:38 +pchampin; got it 14:08:39 zakim, ??P24 is me 14:08:39 zakim, ??P25 is pchampin 14:08:40 +krp; got it 14:08:40 I already had ??P25 as pchampin, Arnaud 14:09:44 scribe: pchampin 14:09:51 http://www.w3.org/2013/meeting/ldp/2013-09-30 14:09:52 topic: administrative 14:10:09 PROPOSED: approve minutes from 2013-09-30 14:10:10 second approving last week's minutes 14:10:10 I looked at them, but don't know if they reflect what was said 14:10:26 RESOLVED: approve minutes from 2013-09-30 14:10:45 Zakim, unmute me 14:10:45 TallTed should no longer be muted 14:10:46 arnaud: next meeting will be next week, same time 14:10:51 Zakim, mute me 14:10:51 TallTed should now be muted 14:10:54 topic: open actions and issues 14:11:17 arnaud: anyone claiming victory? 14:12:25 action-47? 14:12:25 action-47 -- Eric Prud'hommeaux to Review the Use Cases section of the document -- due 2013-03-21 -- OPEN 14:12:25 http://www.w3.org/2012/ldp/track/actions/47 14:12:53 arnaud: Erik was supposed to review the UC a long time ago 14:13:07 ... it has been reviewed by other in the meantime; can close it 14:13:19 s/erik/eric/ 14:13:25 close action-47 14:13:25 Closed action-47. 14:13:29 regrets: bart 14:13:33 regrets: steves 14:13:41 regrets: stevebattle 14:14:57 arnaud: I tried to make it clear in the agenda what would be discussed, and the decisions that would be made 14:15:30 regrets: sandro 14:15:32 ... Steve Battle has updated the UC&R with comments. 14:15:57 (I did send that. in meeting another meeting.) 14:16:27 Proposal: Publish the latest editor's draft of the Use Cases & Requirements 14:16:34 +1 14:16:35 +1 14:16:37 +1 14:16:38 +1 14:16:38 +1 14:16:40 +1 14:16:40 +1 14:16:53 Resolved: Publish the latest editor's draft of the Use Cases & Requirements 14:16:54 RESOLVED: Publish the latest editor's draft of the Use Cases & Requirements 14:17:14 topic: change 5.3.5 SHOULD to MUST 14:17:36 http://lists.w3.org/Archives/Public/public-ldp-wg/2013Oct/0004.html 14:18:06 arnaud: it is an important change, as it impacts all implementations 14:18:22 ... but there seem to be consensus that we should make this change 14:18:30 Proposal: change 5.3.5 SHOULD to MUST per John's email: http://lists.w3.org/Archives/Public/public-ldp-wg/2013Oct/0004.html 14:18:31 MOI calls them vanilla/chocolate? WG came up with that. 14:18:46 +1 14:18:47 +1 14:18:49 +1 14:18:49 +1 14:18:52 +1 14:18:54 +1 14:18:56 +1 14:19:10 I think Steve S would also agree with it, FWIW, since he originally suggested it to me. 14:19:10 Resolved: change 5.3.5 SHOULD to MUST per John's email: http://lists.w3.org/Archives/Public/public-ldp-wg/2013Oct/0004.html 14:19:31 5.3.5 -> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-HTTP_PUT 14:19:32 topic: changes to 5.6.2 (container delete) 14:19:43 arnaud: this is in relation with a comment from Mark Baker 14:20:01 ... about us redefining HTTP 14:20:18 this is the article: http://lists.w3.org/Archives/Public/public-ldp-wg/2013Oct/0006.html 14:20:32 Proposal: changes to 5.6.2 (container delete) per John's email: http://lists.w3.org/Archives/Public/public-ldp-wg/2013Oct/0006.html 14:20:43 ... not that we are contradicting it, but merely being redundant 14:20:55 q+ 14:20:55 +1 14:20:56 +1 14:21:20 +1 14:21:25 +1 14:21:27 ack bblfish 14:21:34 +1 14:21:47 +1 14:21:53 +1 14:22:05 Resolved: changes to 5.6.2 (container delete) per John's email: http://lists.w3.org/Archives/Public/public-ldp-wg/2013Oct/0006.html 14:23:27 arnaud: the next points in the agenda are more controversial 14:23:36 ... anyone wanting to push one of them forward? 14:24:04 topic: Discuss Proposal: Change following to informative (re: redefining HTTP) 14:24:42 http://lists.w3.org/Archives/Public/public-ldp-wg/2013Sep/0052.html 14:24:44 john: this is still related to Mark Baker's remark 14:25:13 ... out intend was not to redefine HTTP, but informatively restate information from other specs 14:25:37 s/out intend/our intent/ 14:26:29 Zakim, unmute me 14:26:29 TallTed should no longer be muted 14:26:54 tallted: we will need a restatement of the proposed change, after the discussions in the mailing list 14:27:24 john: I did a mockup of the new sections in the respec draft 14:27:34 https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#base-specs 14:27:43 that's a mockup in the editor's draft 14:28:33 did you post the correct URL? 14:29:48 bblfish: I pulled it from a live browser henry 14:30:16 tallted: having it in the mailing list archive (not in a mutable draft) would be better to track our decision 14:30:38 arnaud: I agree; can you send such an e-mail, so that we can vote on it next week? 14:30:53 john: I can paste it in the IRC right now 14:31:34 eric: it might be too big, you would get kicked off; better send a mail and copy the URL right afterwards 14:31:50 arnaud: in the meantime, let's move to another topic 14:32:34 topic: Discuss Proposals for PUT ignoring triples ACTION-93 14:32:44 http://lists.w3.org/Archives/Public/public-ldp-wg/2013Sep/0051.html 14:33:22 is that the one or not? 14:34:14 http://lists.w3.org/Archives/Public/public-ldp-wg/2013Sep/0051.html 14:35:00 q+ is there a list of server managed properties somewhere? 14:35:28 @bblfish: no list; implementation-defined 14:36:15 ...IIRC our running assumption was that future work like rdf-val would provide a way for clients to introspect them at run time 14:36:24 Is there a way to tell what the implementation-defined list is automatically? 14:36:46 @bblfish: no 14:36:54 ...at least not in LDP, not today 14:36:57 arnaud: this anwsers TimBL's concern about the current spec allowing the server to silently ignore some of the PUT triples 14:38:59 eric: shouldn't it happen for all operations altering triples (POST, PUT, PATCH) that they return an error if triples will be dropped? 14:39:01 q+ 14:39:35 ack bblfish 14:39:44 john: that's what Steve's distinction between "server managed properties" and "unknown properties" is about. 14:40:18 ... which is a problem because we give the client no way to tell the difference 14:42:15 arnaud: the problem seems to be the unclear boundary between the protocol and the data 14:42:28 bblfish: There is way for a client to know what the "server defined server managed properties are". So the proposal currently makes no sense for the client, since it cannot distinguish a vanilla or chocolate server. 14:42:46 s/is way/is no way/ 14:42:48 ... we try to be good citizen by reusing existing vocabularies (e.g. dc:modified), but this may be a mistake 14:43:11 q? 14:43:38 q+ ask how bad it would be if a client were simply given an error if it sent triples that would be rejected 14:43:43 q+ to ask how bad it would be if a client were simply given an error if it sent triples that would be rejected 14:43:48 ... we have neither a pre-defined list of server-managed properties, nor a mean for the server to dynamically expose such a list 14:44:22 q+ 14:44:28 @ericp: doing so means a typical "patch via put" set of interactions, i.e. GET+ change + PUT, fails 14:44:28 ack ericP 14:44:28 ericP, you wanted to ask how bad it would be if a client were simply given an error if it sent triples that would be rejected 14:44:29 davidwood has joined #ldp 14:45:16 eric: how bad would it be to say that the server issues an error whenever it drops triples? 14:45:45 I agree with ericP's view: reject with an error when some triples cannot be accepted 14:46:29 q- 14:46:51 john: a problem is that PATCH would fail whenever you don't change the server-managed properties that would automatically change 14:47:35 q+ 14:47:38 q+ 14:47:52 JohnArwe: the prob with ericP's proposal is the GET/PUT mode of patch where the client GET's data which includes server-managed properties 14:49:17 well, it just means that some data is meant to be modified by the user, some data has to be managed by the application (maintained by the server), they should not belong to the same LDPR 14:49:20 bblfish: some properties are statements by the server rather than statements by the document 14:49:29 q+ to say supposed the server rejects POSTs/PUTs with *unrecognized* properties. 14:49:33 Kalpa has joined #ldp 14:49:36 q+ 14:49:54 ack bblfish 14:49:56 arnaud: it touches what I was saying earlier about the boundary between protocol and data 14:50:11 ack pchampin 14:50:31 pchampin: in my implementation, the client is not supposed to modify server-managed properties. 14:51:16 ... if there is no attempt to modify those properties, the server accepts and returns a 20x½ 14:51:27 Arnaud: so that's your way of doing a PATCH 14:51:46 It's not clear to me that doing what Pierre does (while logical) conforms with the normative language. 14:51:51 ack ericP 14:51:51 ericP, you wanted to say supposed the server rejects POSTs/PUTs with *unrecognized* properties. 14:51:55 pchampin: how does the client know what it is not allowed to touch? 14:52:31 pchampin: my solution to this problem is to disallow the client to *modify* the server-managed properties 14:53:07 ack betehess 14:53:13 ... *then* the server changes the values 14:54:12 cool idea: put server managed properties in a meta file 14:54:13 eric: but then the server has to check that the values are actually not modified 14:54:13 +1 14:54:34 meta file is linked to from the original file in a link header 14:54:55 betehess: in our solution, there are two kinfs of LDPR : those entirely managed by the clients, and those partly managed by the server 14:54:57 q? 14:55:03 ... a header field is used to tell the difference 14:55:17 informative/diffs reminder before we break 14:55:27 arnaud: this was a useful discussion 14:55:48 ... please post yout proposals to the mailing list in response to steve's message 14:55:58 ... so that we can look at them and think about them 14:56:17 s/kinfs/kinds/ 14:56:37 link to diffs: https://dvcs.w3.org/hg/ldpwg/rev/eeff2a51723d 14:56:56 -bblfish 14:56:58 Zakim, mute me 14:56:58 TallTed should now be muted 14:57:11 topic: Discuss Proposal: Change following to informative (re: redefining HTTP) again 14:57:31 link to diffs: https://dvcs.w3.org/hg/ldpwg/rev/eeff2a51723d 14:59:47 arnaud: it is almost the end of the hout 15:00:03 ... do we have the time for a quick vote? or do you need more time? 15:00:37 -roger 15:00:51 ... I'll put it on the agenda next week, then. 15:00:52 -JohnArwe 15:00:59 ADJOURNED 15:01:01 -Ashok_Malhotra 15:01:09 -Alexandre 15:01:10 -EricP 15:01:12 -TallTed 15:01:33 -Arnaud 15:01:34 Kalpa has left #ldp 15:01:40 trackbot, end meeting 15:01:40 Zakim, list attendees 15:01:40 As of this point the attendees have been Arnaud, EricP, JohnArwe, Alexandre, Ashok_Malhotra, roger, bblfish, TallTed, pchampin, krp 15:01:48 RRSAgent, please draft minutes 15:01:48 I have made the request to generate http://www.w3.org/2013/10/07-ldp-minutes.html trackbot 15:01:49 RRSAgent, bye 15:01:49 I see no action items 15:01:49 -krp