13:58:34 RRSAgent has joined #ldp 13:58:34 logging to http://www.w3.org/2014/06/30-ldp-irc 13:58:36 RRSAgent, make logs public 13:58:36 Zakim has joined #ldp 13:58:38 Zakim, this will be LDP 13:58:38 ok, trackbot; I see SW_LDP()10:00AM scheduled to start in 2 minutes 13:58:39 Meeting: Linked Data Platform (LDP) Working Group Teleconference 13:58:39 Date: 30 June 2014 13:59:08 SteveS has joined #ldp 13:59:27 SW_LDP()10:00AM has now started 13:59:34 +[IPcaller] 13:59:41 Zakim, IPcaller is me. 13:59:41 +codyburleson; got it 13:59:44 +??P5 13:59:53 Zakim, ??P5 is me 13:59:54 +nmihindu; got it 13:59:59 Zakim, mute me 13:59:59 nmihindu should now be muted 14:00:03 +[IPcaller] 14:00:14 zakim, IPcaller is me 14:00:16 +Arnaud; got it 14:00:44 I’m only on IRC today 14:01:07 how are you going to scribe? 14:01:24 I’ll just make it up 14:01:31 zakim, who's on the phone? 14:01:31 On the phone I see codyburleson, nmihindu (muted), Arnaud 14:01:34 Ashok has joined #ldp 14:01:34 scribenick: nmihindu 14:01:35 Arnaud: praises Steve 14:02:26 +Ashok_Malhotra 14:02:27 +bblfish 14:02:45 +??P10 14:02:54 Zakim, ??P10 is me 14:02:54 +deiu; got it 14:02:58 hi 14:02:59 Zakim, mute me please 14:03:00 deiu should now be muted 14:03:01 Hi 14:03:10 +Sandro 14:03:56 he sent regrets I think 14:04:15 +ericP 14:05:15 Topic: Admin 14:05:19 subtopic: Minutes of the 23 June telecon 14:05:24 http://www.w3.org/2013/meeting/ldp/2014-06-23 14:05:46 +??P14 14:05:51 zakim, ??P14 is me 14:05:51 +pchampin; got it 14:06:05 Arnaud: any objections ? 14:06:14 Minutes approved without objection 14:07:05 Arnaud: next meeting will be on July 07th 14:07:10 Topic: Actions and Issues 14:07:30 Arnaud: actions to declare victory ? 14:07:39 ... no actions to report 14:07:43 Topic: Paging spec 14:08:19 Arnaud: summarizing the status of the paging spec 14:08:36 ... there are two items we need to confirm 14:08:50 ... 1. Confirm MUST in section 4.1.1 14:09:12 https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#general 14:10:01 ... do we agree, LDP Paging clients MUST be paging-aware ? 14:10:24 Sandro: we can remove it, it is not a MUST, it is a definition 14:10:45 ... the real question is whether the LDP clients should be LDP Paging clients also 14:11:04 We have that marked at risk https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#atrisk-paging 14:11:19 ... was it in the spec that all LDP clients should be paging aware ? 14:11:30 Arnaud: I think it was 14:12:41 Sandro: Shall we continue or not? we need JohnArwe and SteveS on the call 14:13:19 Arnaud: It is also good to have the opinion of the rest of the group 14:13:23 I have not implemented paging yet, partly also because I have been busy doing other thigns. Am getting some time again to program, perhaps even client side. 14:14:29 Ashok: the 5 kinds of clients are descriptive ? 14:14:30 We have not implemented paging yet because we're still working on other aspects of implementation. We're limited in bandwidth, so just trying to stay as up-to-date as possible with what we hear. 14:14:56 sandro: yes, I don't see much value in making them nominative 14:15:08 I think it is fine to remove the at risk text about warning LDP clients about server-initiated paging. To me, it would seem possible that we could have LDP PAGING clients that would be expected to handle paging responses 14:15:33 ... what matters is what the servers no about the clients 14:15:59 \s\no\know 14:17:27 Arnaud: we have a feature at risk that says LDP clients should handle paging 14:17:45 If I had to prioritize where my own exploration and adoption would be: 1. patch 2. paging . Though there isn’t a big gap in the priorities 14:18:06 sandro: if we finish the paging spec, it is not a feature at risk anymore 14:18:24 ,.. but SHOULD vs MUST, we don't want make paging a MUST 14:18:50 http://www.w3.org/TR/2014/CR-ldp-20140619/#h5_ldpr-cli-hints-ignorable 14:18:54 Ashok: we can only do paging with clients support paging, isn't it ? 14:19:39 sandro: the clients that can't handle might loose some information in the case of paging 14:19:42 -Arnaud 14:19:46 shoot 14:19:47 PROPOSED: LDP servers MUST NOT initiate paging unless the client has indicated it understands paging (such as via the Prefer page-size header) 14:20:24 +1 14:20:24 +1 14:20:26 +[IPcaller] 14:20:28 +1 14:20:29 +1 14:20:35 zakim, IPcaller is me 14:20:35 +Arnaud; got it 14:21:03 +1 14:21:07 +0 14:21:09 RESOLVED: LDP servers MUST NOT initiate paging unless the client has indicated it understands paging (such as via the Prefer page-size header) 14:21:20 sounds reasonable 14:21:52 -0.2 as feels like it should be a SHOULD NOT and not a MUST NOT. 14:22:07 Arnaud: section 4.1.1 doesn't give much information, it is an obvious point 14:22:42 Ashok: should we replace 4.1.1 with the statement that was resolved ? 14:23:11 Arnaud: we could decide it drop it or confirm it JohnArwe 14:23:43 sandro: it seems editorial not normative. we can leave it to the editors 14:24:16 PROPOSED: replace 4.1.1 with a statement that clients which send Prefer page-size MUST act the same whether servers initiate paging or not. 14:24:22 Arnaud: Asok has a point. there is a correlation with 4.1.1 and what was proposed. 14:25:03 sandro: maybe going to far, they must handle it in a way which doesn't cause upstream/user problems 14:25:23 PROPOSED: replace 4.1.1 with a statement that clients which send Prefer page-size MUST act properly, without causing upstream/user problems, if a server decides to initiate paging. 14:25:47 +1 14:25:59 sandro: not wording exact 14:26:27 pchampin: MUST act properly might be a bit vaue 14:26:29 propose: s/act properly/not freak out about/ 14:26:59 s/vaue/vague 14:27:05 PROPOSED: replace 4.1.1 with a statement that clients which send Prefer page-size MUST not break (eg must not cause upsteam/user problems) if a server decides to initiate paging. 14:27:40 +1 I think it is improvement, editors will get intent and edit as needed 14:27:45 PROPOSED: replace 4.1.1 with a statement that clients which send Prefer page-size MUST conform to the other rules of this spec 14:27:59 (general agreement of intent) 14:28:30 Arnaud: don't need a resolution; this should give John enough to chew on 14:28:42 https://www.w3.org/2012/ldp/wiki/Names_in_Paging 14:28:47 Arnaud: the next thing to discuss was about the naming 14:29:01 If server can’t satisfy the request, what status code should be given? I see impls use 403 (Forbidden) 14:29:16 SteveS, do you "superset resource" as the companion to "subset resource" ? 14:29:40 Arnaud: only sandro, JohnArwe, and SteveS has added their preferences 14:29:43 SteveS, by HTTP, servers are allowed to silently ignore Prefer headers. So I'd say no error. 14:30:22 sandro: the term paged resource doesn't match with the rest 14:30:41 sandro, could be superset, or someway I was thinking of “inclusion resource” but didn’t sound right 14:30:55 Does single-page resource mean a single resource within a page? 14:30:55 Arnaud: sandro, what's your favourite at the moment ? 14:32:15 q+ 14:32:16 sandro, so if an HTTP server gets a Prefer header that is doesn’t syntactically validate…would it ignore it? use some fallback logic? or fail the request? I think all would be acceptable, so I don’t think HTTP says that you can’t give an error on an optional piece 14:32:23 sandro: in the initial post, in-sequence resource 14:33:06 subset and superset make sense 14:33:29 subset does not usually contain the notion of order 14:33:57 “ordered subset” can fix that 14:34:23 true 14:35:50 ack ashok 14:35:51 ericP: are we talking about pageable resources ? 14:36:48 Ashok: what we have by default is ok. I don't think people will get confused with page 14:37:30 Arnaud: if we use ldp:Page it might not be ambiguous 14:37:43 sandro: it has to be ldp:PagingPage 14:37:45 sandro: LDPPagingPage ;) ? 14:38:31 Arnaud: we used the generic terms in the LDP spec with ldp namespace such as resource 14:38:59 "sequential part" 14:39:04 what about Iterated 14:39:12 an Iterated Page 14:39:23 sequenced Page is better 14:39:26 sandro: Single Page resource is a confusing term 14:40:02 Ashok: do you agree with what we have today ? 14:40:14 sandro: I vote will be -.7 14:40:36 s/I/my 14:40:42 -1 to forward-thinking clarity 14:40:48 strawpoll: would you prefer keeping what we have or use some other names? 14:41:04 +1 "single page resource" is pretty bad 14:41:12 prefer another name 14:41:19 +1 ericP 14:42:01 does anyone here know if Atom has something to offer? 14:42:12 +1 a better name 14:42:20 Arnaud: paging is worth keeping, we shouldn't ditch it because of the naming 14:42:29 Maybe "Subset page resource" or "In-Sequence page resource" 14:42:31 multi page resource 14:42:33 I see better options on the wiki page 14:42:39 One page in a sequence can also be called a "pagination". 14:43:15 Arnaud: paging resource ? 14:43:34 I think I like "in-sequence page resource" 14:43:43 me too 14:43:55 ORIGIN mid 19th cent.: noun of action from paginate, 14:44:05 sandro: in-sequence resource might be the better option 14:44:36 PROPOSED: replace "Single Page Resource" with "In-Sequence Page Resource", which is still loosely "page" 14:44:43 maybe “Page resource” is an ordered subset and “Superset resource” is the thiing that is being paged 14:45:34 bblfish: I think squence is better than set 14:46:08 o 14:46:32 +1 best we've got 14:46:39 +1 (I think it's better. Klugy maybe. But better) 14:46:41 I don’t think the proposal fixes much but not sure I care that much 14:46:46 0 14:46:55 +1 14:47:09 +1 14:47:10 -1+1=0 14:47:31 RESOLVED: replace "Single Page Resource" with "In-Sequence Page Resource", which is still loosely "page" 14:47:35 bblfish: what is the meaning of "In-Sequence" 14:47:53 sandro: basically resources with previous/next links 14:48:43 Arnaud: we will send the Paging spec soon for LC, it is better to review in the coming week 14:49:06 sandro: better review it for the technical content, there might be more editorial changes 14:49:40 Arnaud: any news on the extension for the working group ? 14:49:52 sandro: yes, we got it. 14:50:00 Topic: Status update 14:50:10 subtopic: Primer 14:50:26 Arnaud: FPWD is published 14:50:34 subtopic: LDP spec 14:50:53 SteveS published an implementation report 14:51:17 Topic: Test Suite 14:51:55 there are several new tests have been proposed 14:52:07 we need at least one more member from the WG to get them approved 14:52:08 We're using the test suite. 14:52:18 But only just got started with it. 14:52:44 we are using the test suite on LDP4j and will submit the implementation report in coming weeeks 14:53:10 There are no other testsuite updates pending, other than that unimplemented test cases I highlighted in email 14:53:27 subtopic: Access Control 14:53:40 Arnaud: any news from TallTed ? 14:54:19 Ashok: TallTed has added some content but I am not sure whether he is finished 14:54:55 bblfish: is it ReSpeced in the repo yet? 14:55:17 Arnaud: we have been waiting for TallTed to finish to do that 14:56:03 Henry, what's the helpful tool? 14:56:36 Arnaud: shall we move forward without the review? 14:57:03 sandro: we can wait for 2 days 14:57:16 makes sense 14:57:57 https://www.atlassian.com/software/sourcetree/overview 14:58:47 Arnaud: Ashok please remind TallTed about the review 14:59:13 subtopic: Best Practices & Guidelines 14:59:39 Arnaud: what is the status of the canonical URL issue ? 15:00:36 codyburleson: I was expecting to get the WG opinion but the discussions didn't go anywhere 15:00:57 I saw the thread but did not read the whole of it. 15:01:14 Arnaud: we agreed to drop the term last week, shall we drop it and move forward ? 15:01:17 s/the whole of it/nearly any of it/ 15:01:23 (was travelling) 15:01:48 Arnaud: I suggest to use primary and move forward 15:02:03 Bye bye 15:02:03 -codyburleson 15:02:05 -Sandro 15:02:06 -bblfish 15:02:08 -nmihindu 15:02:11 -Arnaud 15:02:23 -Ashok_Malhotra 15:02:25 -ericP 15:02:54 -deiu 15:17:21 bblfish has joined #ldp 15:17:48 bblfish has joined #ldp 15:35:01 disconnecting the lone participant, pchampin, in SW_LDP()10:00AM 15:35:03 SW_LDP()10:00AM has ended 15:35:03 Attendees were codyburleson, nmihindu, Arnaud, Ashok_Malhotra, bblfish, deiu, Sandro, ericP, pchampin 16:02:13 bblfish has joined #ldp 16:05:51 bblfish has joined #ldp 16:39:56 jmvanel has joined #ldp 17:04:13 Zakim has left #ldp 17:15:55 deiu has joined #ldp 17:29:13 Arnaud has joined #ldp 17:46:30 bblfish has joined #ldp 17:47:02 bblfish has joined #ldp 17:56:45 bblfish has joined #ldp 18:50:38 bblfish has joined #ldp 19:30:44 bblfish has joined #ldp 19:36:46 bblfish has joined #ldp 19:51:05 SteveS has joined #ldp 20:48:17 bblfish has joined #ldp 21:02:36 jmvanel has joined #ldp 21:20:05 deiu has joined #ldp 21:20:27 bblfish has joined #ldp 22:07:13 Arnaud has joined #ldp 22:30:00 bblfish has joined #ldp