18:03:00 RRSAgent has joined #social 18:03:00 logging to http://www.w3.org/2016/12/06-social-irc 18:03:02 RRSAgent, make logs public 18:03:02 Zakim has joined #social 18:03:04 Zakim, this will be SOCL 18:03:04 ok, trackbot 18:03:05 Meeting: Social Web Working Group Teleconference 18:03:05 Date: 06 December 2016 18:04:00 present+ 18:04:03 present+ 18:04:20 present+ 18:07:18 present+ 18:07:32 present+ 18:09:00 present+ 18:09:17 scribenick: rhiaro 18:09:24 TOPIC: Last week's minutes 18:10:44 Sorry, dropped 18:10:49 Rejoining.. 18:11:23 https://www.w3.org/wiki/Socialwg/2016-11-29-minutes 18:12:16 +1 18:12:20 +1 18:12:29 PROPOSED: approve last week's minutes https://www.w3.org/wiki/Socialwg/2016-11-29-minutes 18:12:33 +1 18:12:36 +1 18:12:39 +1 18:12:39 +1 18:12:46 RESOLVED: approve last week's minutes https://www.w3.org/wiki/Socialwg/2016-11-29-minutes 18:12:46 +1 18:12:50 +1 18:13:00 TOPIC: AS2 18:13:08 jasnell, are you around? 18:13:13 jasnell, any chance you're around? 18:13:17 :-) 18:13:28 yes and no. I cannot join a call but I can answer questions here 18:13:56 tantek: DO we have a CR draft ready for publication 18:14:04 sandro: I think Evan's email said he had made all the changes 18:14:07 ... I have not reviewed them yet 18:14:14 tantek: could someone drop a link to the changes? 18:14:21 ... so we can at least review it 18:14:23 Evan updated the editor's draft this morning 18:14:29 jasnell, have you seen Evan's recent changes? 18:15:02 http://w3c.github.io/activitystreams/core/#changelog 18:15:05 http://w3c.github.io/activitystreams/core/index.html#changelog 18:15:05 [James M Snell] Activity Streams 2.0 18:15:07 [James M Snell] Activity Streams 2.0 18:15:07 I very briefly glanced at it this morning 18:15:36 tantek: I can't review, so I'm going to leave it to other folks 18:15:54 ... The key thing is to make sure the stuff that we discussed at the f2f and subsequent telecons 18:15:59 ... the whole name, summary, should 18:16:10 sandro: Am I right that there's no changes to vocab, just core? 18:16:17 ... vocab does not have a changelog 18:16:19 that's how it appears 18:16:22 http://w3c.github.io/activitystreams/vocabulary/index.html#changelog shows nothing since CR 18:16:29 [James M Snell] Activity Vocabulary 18:16:35 tantek: if there are other changes, could you take a look at those 18:17:06 jasnell, are you okay with this being a new Candidate Recommendation? Do you want more time to review it -- like another day or two to yell if there's a problem? 18:17:27 "The summary property SHOULD be used as a fallback text representation, possibly automatically generated by the publisher. If there is no name property, the summary property SHOULD NOT include markup, and SHOULD be as short enough to be used as a text representation in the language context. " 18:17:53 sandro: let's do that, I've had a ton of context switching the past couple of days so I wouldn't feel comfortable signing off without a better readthrough 18:17:55 I don't think I understand the last part of that sentence about language context? 18:18:09 give me until tomorrow and if I don't raise any objections by then go for it 18:19:09 sandro: We can publish so long as jasnell doesn't raise objections by tomorrow? 18:19:11 tantek: I would be fine with that 18:19:29 PROPOSED: Publish new CR of AS2, giving people another 24 hours to review, pending no objections 18:19:42 +1 18:19:45 +1 18:19:46 +1 18:19:47 +1 18:20:21 +1 18:20:23 sorry :) 18:20:25 +1 18:20:38 tantek: +1 18:20:44 RESOLVED: Publish new CR of AS2, giving people another 24 hours to review, pending no objections 18:21:14 tantek: Next AS2 discussion item is a dependency the Annotation group would like to see resolved 18:21:25 ... They depend on a bunch of vocabulary terms and want us to go to PR to make sure the terms are stable 18:21:39 ... and there's a proposal from sandro 18:22:02 sandro: They were hoping we would go to PR and we talked a bunch in the staff IRC and realised we don't actually need to go to PR for them to be able to reference us, just that we intend to proceed to PR 18:22:21 tantek: you noted that there's only one term we dont' have implementations for 18:22:24 ... startIndex 18:22:35 sandro: They have at least one implementation, and may have two others 18:22:46 tantek: If we don't get implementation reports from them for that, we'll drop it, and they should too 18:22:56 ... I feel we should have this on the record for a resolution 18:22:59 ... so that it's clear 18:23:07 PROPOSED: We consider the 12 AS2 terms used by WebAnnotations to be stable and will not substantively change their definitions from those in our 06 September 2016 CR. We expect to go to PR in Jan 2017 and see no likely impediments, given our plan to drop any vocabulary terms lacking 2 impls. We currently lack 2 impls of as:startIndex, but assume Anno can provide them. 18:23:26 PROPOSED: We consider the 12 AS2 terms used by WebAnnotations to be stable and will not substantively change their definitions from those in our 06 September 2016 CR. We expect to go to PR in Jan 2017 and see no likely impediments, given our plan to drop any vocabulary terms lacking 2 impls. We currently lack 2 impls of as:startIndex, but assume Anno can provide them. 18:23:27 +1 18:23:29 +1 18:23:30 +1 18:23:31 👍 18:23:32 +1 18:23:44 +1 18:24:03 RESOLVED: We consider the 12 AS2 terms used by WebAnnotations to be stable and will not substantively change their definitions from those in our 06 September 2016 CR. We expect to go to PR in Jan 2017 and see no likely impediments, given our plan to drop any vocabulary terms lacking 2 impls. We currently lack 2 impls of as:startIndex, but assume Anno can provide them. 18:24:20 jasnell, are you cool with that? 18:24:35 The terms are: 3 classes (as:Application | as:OrderedCollection | as:OrderedCollectionPage) and 9 properties (as:first | as:generator | as:items | as:last | as:next | as:partOf | as:prev | as:startIndex | as:totalItems) 18:24:42 yep 18:25:15 I think? Can't hear hm anymore :/ 18:25:33 sandro: While we're waiting for tantek, I think that's it for what's explicitly on the agenda 18:25:37 TOPIC: Document status 18:25:50 sandro: Raise your hand if you have a document status update to report 18:25:56 👋 18:26:05 he waives 18:26:13 raises his hand I believe ;) 18:26:14 q- sits 18:26:37 various: discussion of aaronpk's problemantic use of emoji 18:27:04 sandro: giving tantek another minute.. 18:27:20 ... Did everyone see the list of AS2 implementations? 18:27:24 http://as2.amy.gy/reports.html 18:27:45 ... It does make me wonder how many things we're going to have to drop from as2 18:27:59 annbass: it's a great way to present that information 18:28:10 sandro: Shall we go ahead and proceed without tantek? 18:28:12 ... aaronpk, go ahead? 18:28:24 tantek: *returns* 18:28:43 I do no have a status report :/ sorry for the confusion 18:28:53 aaronpk: this is for WebSub, from julien as well 18:28:59 ... We've been working on getting it ready for CR 18:29:04 https://w3c.github.io/websub/ 18:29:12 ... I have the editor's draft up to date with the conformance classes and the last trailing issues that julien's been merging in 18:29:19 ... I have one pendin gPR to add the exit criteria to it 18:29:19 https://github.com/w3c/websub/pull/77 18:29:31 ... the same stuff that was written in the issue 18:29:47 ... that should take us to everything we were planning on doing for taking it to CR 18:30:02 tantek: does that mean you have a CR draft ready? 18:30:07 done and done! 18:30:08 aaronpk: once that PR is merged it should be 18:30:12 PR merged and CR ready 18:30:14 tantek: changelog? 18:30:23 https://w3c.github.io/websub/#changes-from-20-october-fpwd-to-this-version 18:30:29 aaronpk: Oh I didn't update that yet 18:30:47 ... I believe the list is very small though 18:30:54 tantek: any outstanding non-editorial issues open? 18:31:00 aaronpk: A couple waiting for commenter 18:31:12 ... julien, do you know offhand? 18:31:27 julien: One waiting for commenter feedback, but I don't think there's anything blocking 18:31:39 tantek: if it's still open it's blocking 18:31:56 ... If we previously resolved on then that should be clear in the issue. If youthink you have a resolution but the commenter hasn't responded yet then walk us through that issue 18:32:10 ... basically by this discussion we should see if we have zero non-editorial issues that need input from the group 18:32:15 https://github.com/w3c/websub/issues/68 18:32:17 julien: number 68 18:32:25 ... The proposal is to replace rel=self with rel=canonical 18:32:36 ... I don't think there's any benefit to it, but it would break a lot of implementations 18:32:44 tantek: do we have a proposal to resovle that issue without changes? 18:33:01 ... can you propose that both in the issue and IRC 18:33:04 sandro: hold on.. 18:33:15 ... it's currently tagged as waiting for commenter, but the commenter has since replied, an dnobody has answered 18:33:25 julien: he's asking for the same thing over 18:33:42 sandro: he phrased as a 'new suggestion', so to close without answering him.. how do you reply? 18:33:51 julien: I think we should not ?? the rel=canonical urls 18:34:00 sandro: his point is he wants people to be able to use rel=canonical in their html 18:34:06 julien: I don't think there is any good reason for it 18:34:33 aaronpk: everything is the same, except in html people should look for rel=canonical and THEN rel=self 18:34:46 ... since canonical is already existing, people might already have it, and then wouldn't have to add a new one 18:34:57 sandro: what does websub use this for? what happens if you don't have either? 18:35:04 aaronpk: then you don't know what topic url to send 18:35:10 sandro: can't be the URL of the page? 18:35:19 aaronpk: theoretically the same but some cases where it's not 18:35:32 ... the spec makes it explicit that it should always use the advertised the value 18:35:49 tantek: one of my requests from a while ago was that if there's no self then just use the URL of the page 18:36:00 julien: one of the problems that we've found over and over with feeds is query strings 18:36:15 ... having urls with query strings, people subscribe to that, but that is not what gets sent to the hub, so the subscriber never gets data 18:36:35 sandro: the arguements for requiring rel=self, already implemented, but aside, we want to avoid the error cases where the URL is wrong, and rel=canonical might have the wrong URL as well? 18:36:41 julien: it's different things 18:36:50 ... a need for a way to identify the topic, should not be implicit, it will fail silently 18:36:58 ... if it's explicit, I don't see the point in having two possible values 18:37:07 aaronpk: is there something about rel=canonical that has a different meaning? 18:37:29 ... the example I could think of is an atom feed sometimes points to a rel=canonical of the html page 18:37:53 ah... so the rel=canonical would be wrong 18:37:54 ... so if you want to subscribe to the atom feed, you can't use the rel=canonical that would be wrong 18:38:09 tantek: the confusion here is from the fact that the term self as an English term si very overloaded 18:38:39 ... and what it really means is like rel=update. Yes your'e looking at this page, and if you want to get updates of the kind of stuff you see on this page, here's the URL that you subscribe to. That's my understanding of the meaning of rel=self in WebSub 18:38:49 ... the unfortunate thing is that people see rel=self and think of the english term 18:39:02 ... it does not mean all the things people think when they see self 18:39:12 ... and it's unfortunate, but there's so much interop on this I would not propose changing 18:39:12 maybe rel='websubChannel" would be the clearest English :-) 18:39:19 ... maybe an informative note about what does rel=self mean 18:39:22 yiiiikes! 18:39:34 ... I do think .. wasn't there an atom rel=self alsothat meant something else? 18:39:41 julien: ours is the meaning of atom rel=self that we're using here 18:40:15 sandro: it sounds like if we modify the draft to include a note including what we mean by self 18:40:17 rel=topic would have been a better choice but that ship has sailed 18:40:37 ... and tell the commeter we thought about it and are too concerned about the fact that canonical might be different, and we want to keep it a separate relation 18:40:42 tantek: mention the experience of ?? 18:40:58 s/??/silent failure/ 18:41:19 julien: silent failure, if you do not subscribe to a URL that's the one the publisher advertises you will not get data and will not understand why 18:41:27 aaronpk: most obvious example is query string parameters 18:41:34 +1 silent failure is a bigger issue than convemience of re-using rel=canonical 18:41:44 tantek: our irc logs, with /today 18:42:25 tantek: can we move this along? 18:42:32 julien: I will add a note to the spec about why it is like this 18:42:42 ... as well as why it's important to have a value and not nothing 18:43:22 PROPOSED: Add note to spec about the naming of rel='self', and do not change to use rel=canonical at all 18:44:42 tantek: if you're willing to consider it, julien, the example of IRC logs, really helped convince me when aaronpk told me about that of the value of self 18:47:14 +1s? ^^^^ 18:47:28 +1 18:47:31 tantek: vote on proposal 18:47:34 +1 18:47:35 +1 18:47:37 +1 18:48:02 +1 18:48:04 (back) 18:48:09 RESOLVED: Add note to spec about the naming of rel='self', and do not change to use rel=canonical at all rehttps://github.com/w3c/websub/issues/68 18:48:29 https://github.com/w3c/websub/issues/13 18:48:37 tantek: Next issue? 18:48:45 sandro: URL vs URI inconsistency? 18:48:52 tantek: I think we had something similar with webmention? 18:49:02 ... we expect browser like behaviour with discovery 18:49:21 ... I think I commented on the issue 18:49:31 but then what's the resoltuion tantek? 18:50:00 sandro: in webmention we reference the URL spec 18:50:27 tantek: and that's based on what other specs at w3c are doing, and it better reflects how URLs are treated in html, and that's essentially what we're doing, makes more sense than the IETF rfcs 18:50:39 Basically change RFC 3986 to https://url.spec.whatwg.org/ ? 18:51:03 sandro: one of the counter arguements would be that it is a political statement 18:51:09 tantek: if anything that's an arguement *for* 18:51:25 Is this the one that was updated in webmention with a note to go with it? 18:51:38 tantek: we should do what web platform wg is doing 18:51:42 sandro: you mean what html has been doing? 18:51:55 tantek: if there's a question of politics, politial inertia, that's on the side of using the urls pec 18:51:59 sandro: could be either way 18:52:09 ... there will be people who will be upset with either choice 18:52:16 ... hopefully not terribly 18:52:19 present+ 18:52:35 tantek: not clear that it will make any difference. Worse for us to be inconsistent 18:52:36 sandro: consistency is better 18:53:00 tantek: we should record if people are upset, and if they implement, and move on 18:53:27 PROPOSED: resolve https://github.com/w3c/websub/issues/13 saying we're going to consistently us the https://url.spec.whatwg.org/ 18:53:43 +! 18:53:45 +1 18:53:48 +1 18:53:52 +0 not sure about the politics, but I guess, and consistency is important, and we went this way with WebMention 18:53:52 +1 18:54:11 tantek: unless there are necessary technical reasons for referencing one over another, we should have the TAG say something 18:54:28 RESOLVED: resolve https://github.com/w3c/websub/issues/13 saying we're going to consistently use the https://url.spec.whatwg.org/ 18:54:28 +! 18:55:02 +1 18:55:05 Do we need that note that was added to webmention too though? 18:55:26 sandro: I think it's better to ask the commenter to close it 18:55:48 tantek: as long as we have a group consensus recorded, for the purposes of going to CR, it's better to leave it open as sandro suggests 18:56:46 sandro: somebody needs to go back and tag the 39 closed issues 18:57:01 ... so we can have an analysis in the CR transition meeting 18:57:14 ... most of the ones that don't have tags are by the editors, but still 18:57:56 ... We do have to check over the closed issues and make sure they are legitimately closed 18:58:07 tantek: for the open ones, if it doesnt' say editorial then we need a resolution. Any left/ 18:58:11 sandro: I see three 18:58:31 tantek: Unless those are mis-tagged I don't think we're going to resolve 3 issues in 2 minutes 18:58:35 sandro: two are raised by aaron 18:58:46 aaronpk: 27 is just waiting on me to write up, already resolved 18:58:50 ... I lost track of 47 18:59:03 ... I dont' remember why it's important any more 18:59:25 ... and there's a new one after last eweks' call, I haven't analysed yet, 73 18:59:29 ... 73 is the only one to talk about now 18:59:34 tantek: sounds like we need more time on that one 18:59:56 ... I think we have enough edits done that you can publish a new WD with a changelog 19:00:06 ... preferably with the edits we all just agreed on as of this call 19:00:30 PROPOSED: Publish a new WD of WebSub including the resolutions from today's call 19:00:35 +1 19:00:35 +1 19:00:37 +1 19:00:44 +1 19:01:04 RESOLVED: Publish a new WD of WebSub including the resolutions from today's call 19:01:15 sandro: do the editors want to try to do a CR vote next week? 19:01:21 +1 19:01:25 julien: yep 19:01:26 aaronpk: yep 19:02:57 sandro: should we try to super-rush to get it out before the moratorium 19:03:05 sandro: probably not... 19:03:26 tantek: we can publish WDs any time 19:03:28 tantek: yeah, probably not 19:03:57 tantek: next week I'm hoping Evan can chair 19:04:25 trackbot, end meeting 19:04:25 Zakim, list attendees 19:04:25 As of this point the attendees have been aaronpk, rhiaro, cwebber, sandro, julien, annbass, ben_thatmustbeme, ! 19:04:33 RRSAgent, please draft minutes 19:04:33 I have made the request to generate http://www.w3.org/2016/12/06-social-minutes.html trackbot 19:04:34 RRSAgent, bye 19:04:34 I see no action items