14:03:52 RRSAgent has joined #ldp 14:03:52 logging to http://www.w3.org/2013/03/11-ldp-irc 14:03:54 RRSAgent, make logs public 14:03:56 Zakim, this will be LDP 14:03:56 ok, trackbot, I see SW_LDP()10:00AM already started 14:03:57 Meeting: Linked Data Platform (LDP) Working Group Teleconference 14:03:57 Date: 11 March 2013 14:04:35 -ericP 14:04:59 +[GVoice] 14:05:19 zakim, who's on here? 14:05:20 I don't understand your question, Arnaud. 14:05:46 zakim, who is here? 14:05:46 On the phone I see Sandro, Arnaud, [GVoice], pchampin, Ashok_Malhotra, ??P10, TallTed (muted), ??P13, dret, JohnArwe 14:05:48 On IRC I see RRSAgent, Arnaud, JohnArwe, dret, Zakim, Ashok, TallTed, pchampin, jmvanel, gavinc, sandro, ericP, Yves, thschee, betehess, trackbot 14:06:14 Zakim, [GVoice] is me 14:06:14 +ericP; got it 14:08:38 i can step in 14:08:46 ok, i won't step in 14:08:53 scribe: sandro 14:11:00 two unidentified callers. mysterious! 14:11:23 +1 14:11:24 +1 14:11:27 Arnaud: At our last F2F, we arranged for an informal telecon afterwords. 14:11:32 PROPOSED: accept minutes from last week 14:11:45 RESOLVED: accept minutes from last week (March 4) 14:12:20 Arnaud: At informal telecon right afterwords, we went over what happened, to catch up people who missed it. That's the plan for next week's telecon. 14:12:44 Arnaud: So people who come to the F2F, you don't have to join the telecon next week. We wont be making any decisions or anything like that. 14:12:58 Arnaud: On the F2F -- do we have the final list of participatns? 14:13:29 Arnaud: I haven't heard any feedback on the agenda. 14:14:25 Arnaud: Maybe breakouts. Long list of issues; no proposal for some of them. 14:15:00 Arnaud: I STRONGLY suggest if you care about an issue, you send out a proposal BEFORE the meeting. 14:15:05 the break-out groups would be chartered with preparing proposals for those issues which don't have any right now. 14:15:20 q+ 14:15:51 Arnaud: If people are remote and really care, we can try to work around their schedule. 14:16:05 ack ashok 14:16:47 Ashok: We still have arguments and disagreements on the overall @@. I was hoping we could talk about that early 14:16:55 s/@@/model/ 14:17:20 Arnaud: I'm kind of torn on that. 14:17:57 Arnaud: If we could agree on the model, things would be easier, yes. But it doesn't seem to be working, so maybe bottom up will work better. 14:18:03 +Yves 14:18:06 .. like develop the test suite, and see how that goes. 14:18:11 switch from topd-down to bottom-up mode, yes. i think we have established that top-down doesn't seem to work all that great for us. 14:18:29 +1 bottom up 14:18:51 Arnaud: We'll end up needing to make the same design decisions, but without the details we don't understand each other. 14:18:54 and then when we have better spec'd bottom-up cases, we need to distill the model. 14:19:23 eric: There's a possibility that working with test cases will get us toward the model than discussion the model theoretically 14:19:28 Arnaud: exactly. 14:19:35 yup, i agree that the tests are an excellent way to go forward. 14:19:52 ericP: Ashok, do you see a way to have the Test discussion first, in a way that will help us have a grounded Model discussion. 14:19:55 q? 14:20:04 dret, can you take over scribing for 10-15 now? 14:20:12 Ashok: I need to think about this. 14:21:34 i can do that... 14:22:46 Arnaud: keep breakout sessions as an option, but in such a fragmented group it may be counter-productive; will be decided on demand 14:23:06 -??P13 14:23:20 Topic: Actions and Issues 14:23:49 -??P10 14:24:13 Proposal: close ACTION-29 14:24:54 Decision: ACTION-29 closed 14:26:22 ACTION-38 remains opne while we switch to bottom-up mode for the model discussion 14:30:00 But is this a LDP issue? 14:30:44 ack Yves 14:31:47 discussing ISSUE-49 and whether it's part of LDP or should be considered orthogonal 14:32:46 Yves: pointing to metalink and saying that we should be very cautious about making mirroring/equivalence a part of LDP 14:32:52 TallTed has joined #ldp 14:33:02 Ashok: agrees with Yves 14:33:19 Arnaud: seems like most people agree that it's not an LDP issue 14:33:20 ...yves said he would put reference to other materials on the public list; some issues with attack vectors. 14:33:43 ack sandro 14:34:26 Sandro: use OWL sameas in data or in the HTTP header 14:35:04 these are RDF solutions, we might also recommend HTTP-level ones? 14:35:14 q+ to notice that owl:sameAs is symetrical 14:35:21 ack pchampin 14:35:21 pchampin, you wanted to notice that owl:sameAs is symetrical 14:36:28 pchampin: not sure about sameas, because it is supposed to be symmetrical 14:37:05 SteveS has joined #ldp 14:37:39 +[IBM] 14:37:39 See https://tools.ietf.org/html/rfc6249 14:37:44 scribe: sandro 14:38:03 zakim, [IBM] is me 14:38:03 +SteveS; got it 14:38:12 q+ 14:38:15 thanks, sandro! 14:38:23 proposal: close issue-49, making no change 14:38:34 ack ashok 14:38:59 Ashok: There's a section 4.1.4 that spoke to this. Does that get clarified or removed or what? 14:39:16 Arnaud: No one has proposed that 14:39:54 Arnaud: There is one MUST in the spec. 14:40:32 Ashok: I recommend keeping it open and figuring out what to do with that part of our spec. 14:41:04 Arnaud: I don't want to just leave it open, and then we'll come back in 2 months 14:41:13 Ashok: give me an action 14:41:38 q+ 14:41:38 Arnaud: So we'll leave ISSUE-49 open for now, and Ashok with produce a recommendation about what to do about 4.1.4 14:41:47 ack steves 14:42:14 bhyland has joined #ldp 14:43:42 action Ashok to propose how to modify the text of 4.1.4 to go with closing ISSUE-49 (with no material modification to spec) 14:43:42 Created ACTION-40 - Propose how to modify the text of 4.1.4 to go with closing ISSUE-49 (with no material modification to spec) [on Ashok Malhotra - due 2013-03-18]. 14:44:42 i'm fine with ignoring ISSUE-37 for now and then attempt to distill it from tests 14:45:22 Arnaud: We were going to talk about Reverse Membership Predicate, but Steve Battle asked we not decide in his absence, so we'll put it off. 14:45:35 Arnaud: He did send email with example. 14:46:59 dret: I liked Steve's notion that navigability and data model are different things. What are the concepts that we identify and represent; and THEN decide on the affordances, where do we encode it, so clients can find that part of the data model in that place. 14:47:35 .. I really like the idea of splitting them. Make membership part of model, then later talk about how to make it navigable, maybe in both directions. 14:47:55 Arnaud: I thought you might agree with that. :-) 14:48:10 Arnaud: Steve's example was very useful. I had no understood it. 14:48:20 Arnaud: We need more examples posted. 14:49:06 Arnaud: I had thought it was a back-link, but he's just using a different membership property. The link is in the same direciton, container to member. 14:50:13 topic: issue-35 14:50:16 issue-35? 14:50:16 ISSUE-35 -- POSTing to a container MUST yield a fresh URI -- open 14:50:16 http://www.w3.org/2012/ldp/track/issues/35 14:50:41 Arnaud: We had a similar discussion about whether URIs could be reused after delete. 14:51:07 .. Like MUST you get an error doing a GET after a DELETE? 14:51:22 .. people seemed to think there may be cases where a URI is reused. 14:51:26 issue-24? 14:51:26 ISSUE-24 -- Should DELETED resources remain deleted? -- closed 14:51:26 http://www.w3.org/2012/ldp/track/issues/24 14:51:39 i hope we don't say anywhere that you MUST get an error.. 14:51:45 Arnaud, so issue-35 and issue-24 seem linked 14:51:59 I agree that they seem linked 14:52:01 (your logic sounds good to me, Arnaud) 14:52:31 seems an accurate assessment... 14:52:57 dret, I don't think we have liberty to decide this. if a server decides to re-use URIs, that's up to it. clients shouldn't make those assumptions. 14:53:12 s/dret,/dret:/ 14:53:29 dret: I don't think clients have business looking at URIs like this. 14:53:43 Arnaud: Richard proposed server must not re-assign URI. 14:54:00 q+ 14:54:19 POSTing to a container MUST yield a URI ... it's server's choice what that URI is, and I think whether that URI is guaranteed new or re-used is and should remain outside our control 14:54:47 Arnaud: To be consistent with 24 we can't change anything on 35. because we already said URIs may be reused 14:54:51 ack sandro 14:55:32 sandro: i'm concearned about the situation where client A deletes and client B continues to use 14:56:03 ... if something else creates , the meaning will change out from under client B. 14:56:23 Arnaud: Yeah, "under certain cirumstances". So in the NORMAL case you'd get a new URI. 14:56:28 ... we need text which talks about "delete if if you're *sure* the URL hasn't leaked out" 14:56:33 Arnaud: So I'm okay with a SHOULD. 14:56:34 ack tallted 14:56:43 i think this is "deployment guide" stuff: don't do it, because of this and that. 14:56:57 TallTed: This is no different from any other situation where URIs change. 14:57:42 I agree with TallTed 14:57:49 me too 14:57:54 TallTed: I don't think this is an undetectable error condition. You just have to document your server behavior 14:58:20 i'd prefer non-spec level, this is just best practice 14:58:57 sandro: documenting server bevavior means there's no spec here. 14:59:18 I like increasing the awareness from what we have, like with should or recommended, and possibly update some guidance into the deployment guide 14:59:45 sandro: MUST is too hard to implemnt, but strongly worded SHOULD is okay 15:00:04 Arnaud: Sounds like we're coming to SHOULD, but let's not decide until we have Richard present. 15:00:11 not sure. this is not a protocol issue. it's just a recommendation. 15:00:57 yup, and if people want to shoot themselves in the foot, they are allowed to do so. they just dimish the vaue of their service. 15:00:59 TallTed: I think SHOULD might be too strong. eg in the case of a reboot 15:01:19 sandro: if the client can't assume the URIs will be stable on a given server, we have a huge problem. 15:01:21 -Ashok_Malhotra 15:01:23 thanks everybody! thanks, sandro! 15:01:29 -dret 15:01:33 thanks, dret! 15:01:41 Arnaud: See many of you in Boston!! 15:01:45 ADJOURN 15:01:49 -Yves 15:01:50 -TallTed 15:02:09 -pchampin 15:03:17 -JohnArwe 15:03:30 sergio has joined #ldp 15:03:35 hi 15:03:43 https://www.csail.mit.edu/mrbs/view_entry.php?id=94640&area=1&day=14&month=03&year=2013 15:03:57 we just ended sergio --- US daylight savings started this past weekend 15:04:14 cygri has joined #ldp 15:04:34 -SteveS 15:05:07 -Sandro 15:05:08 -Arnaud 15:05:10 what' the new conference code? 15:05:12 -ericP 15:05:13 SW_LDP()10:00AM has ended 15:05:13 Attendees were pchampin, Ashok_Malhotra, TallTed, dret, JohnArwe, Sandro, Arnaud, ericP, Yves, SteveS 15:06:01 cygri, meeting just ended. daylight saving time shift. 15:06:15 ooooh 15:06:25 same error than cygri 15:07:07 i updated the calendar for RDF-WG and GLD-WG but must have forgotten LDP-WG 15:07:23 me too 15:07:27 sorry guys 15:07:29 ETOOMANYWORKINGGROUPS 15:08:00 cue rant about non-interoperable implementations of daylight saving time 15:09:28 cygri: trick if you are using google calendar: set the time zone in us for that event 15:09:41 oh, you can do that? 15:12:24 -> http://www.energy.ca.gov/daylightsaving.html#earlydst daylight saving time shift 15:15:42 ericP, I'm glad the compromise bill didn't involve shifting for half an hour 15:19:30 17.45 mins 15:22:19 xD 15:22:43 sandro: yes, google calendar supports that, I just never use it, from I'll do it for sure ;-) 15:23:41 "yes i can make tuesday 11am GMT, but that will be a cygri from a timeline where today's meeting has not happened yet" 15:24:12 *laugh* 15:24:22 I know that guy! He's brilliant! 15:24:34 mysteriously well informed 15:29:04 xDDD 15:30:25 at least for me, the event is showed in my local timezone, even if the time is for GMT-05:00 15:33:30 sorry you missed the call guys 15:33:41 I did my part sending a reminder to the list 15:34:29 I'll admit that I forgot to set my alarm clock and woke up right about the time of the call! 15:42:04 Arnaud, historical W3C data shows that 10% of WG members bungle this, regardless of how many warnings the chairs send... i think it's a natural constant, like the speed of light 15:56:50 Or everyone could just get rid of this horrible idea, screw interop, just abandon Daylight Savings time completely! 16:02:35 just stick to local local time. 16:02:39 grrr 16:02:43 local solar time 16:02:54 to my fingers, "local" and "solar" are the same word. 16:05:11 GMT everywhere! 16:08:50 might as well go to decimal time as well. 16:08:52 :-) 16:09:18 and a decimal calendar. 16:10:12 if we just speed up the rotation of the earth a little, we could get 400 days in a year, that would help a bit. Then we'd have 100 days in a season, etc. 16:10:51 or moving the earth to a larger orbit; that would also get us 400 days in a year, AND help reduce global warming. 16:11:07 (how come I never hear anyone propose this!) 16:11:37 (y) 16:12:14 this would also dodge the doomsday asteroid 16:45:10 bblfish has joined #ldp 17:05:07 Zakim has left #ldp 17:30:22 cygri, sandro: given the US track record on failing to adopt the metric system despite all its advantages and a much easier change to make than adopting a decimal calendar there is little hope that a decimal calendar would ever be accepted!... 17:43:56 Arnaud: We did adopt it! ... and then ignored it ;) 17:44:34 On the other hand, you can't service a car, bike, toaster, oven, or much of anything in the US with anything other then Metric tools 17:44:50 Mostly we haven't changed speed limits ;) 17:45:10 or other road signs 17:45:20 and labelling! 17:46:23 going to the grocery or hardware store still requires a good understanding of the american system 17:46:50 after 15 years in the US I still struggle with the different measures of volumes and weight 17:49:31 and it pains me to think that this is what my kid is being taught in school 17:50:32 eh? food labeling ist mostly dual 17:50:46 "mostly" :) 17:50:57 price tags aren't 17:51:09 Okay, the butcher looks at you very funny if you ask for grams of meat 17:51:32 you want to compare the price of two similar items and one has a price per lb the other per ounce, etc. 17:51:47 Eh, science education for me was all in SI 17:52:43 and because the items are sized in ounces etc you always end up with odd metric measures 17:53:28 which kind of defeats the points 17:53:40 s/points/point/ 18:13:43 bblfish has joined #ldp 18:17:38 bblfish has joined #ldp 18:35:12 bblfish has joined #ldp 18:44:02 bblfish has joined #ldp 23:36:20 bblfish has joined #ldp