18:00:31 RRSAgent has joined #social 18:00:31 logging to http://www.w3.org/2015/12/08-social-irc 18:00:33 RRSAgent, make logs public 18:00:35 Zakim, this will be SOCL 18:00:35 I do not see a conference matching that name scheduled within the next hour, trackbot 18:00:36 Meeting: Social Web Working Group Teleconference 18:00:36 Date: 08 December 2015 18:00:46 present+ eprodrom 18:00:46 present+ 18:01:17 present- ben_thatmust 18:01:20 preset+ 18:01:23 present+ 18:01:25 So close 18:01:43 absent+ 18:02:05 present+ 18:02:15 present+ rhiaro 18:02:30 melvster has joined #social 18:02:32 present+ 18:05:00 I'll scribe 18:05:05 ben_thatmustbeme++ 18:05:07 ben_thatmustbeme has 127 karma 18:05:11 scribenick: ben_thatmustbeme 18:05:19 bengo has joined #social 18:05:19 I think that's the right incantation 18:05:27 Sometimes it's a colon and sometimes it's a comma 18:05:38 scribe:Ben Roberts 18:05:57 present+ 18:06:00 eprodrom: as it is 5 minutes after the hour, lets get started 18:06:05 https://www.w3.org/wiki/Socialwg/2015-12-08 18:06:06 agenda is linked in the topic 18:06:15 present+ tantek 18:06:21 TOPIC: approval of minutes 18:06:22 oops 18:06:26 sorry, dialing in now 18:06:33 eprodrom: two sets of minutes to approve last telcon and F2F 18:06:38 PROPOSED: approve minutes of Nov 24 https://www.w3.org/wiki/Socialwg/2015-11-24-minutes 18:06:43 present+ 18:07:00 +1 18:07:02 +1 18:07:04 +1 18:07:07 +1 18:07:10 +1 18:07:17 present+ 18:07:18 ... unless there is a minus 1 we will move on quickly 18:07:19 +1 18:07:22 +1 18:07:31 RESOLVED: approve minutes of Nov 24 https://www.w3.org/wiki/Socialwg/2015-11-24-minutes 18:07:59 eprodrom: next order of business is minutes from F2F, these are significantly longer 18:08:00 PROPOSED: approve minutes Dec 1 https://www.w3.org/wiki/Socialwg/2015-12-01-minutes 18:08:02 present+ cwebber2 18:08:41 eprodrom: lets treat both days as a single proposal 18:08:44 PROPOSED: approve minutes Dec 1 https://www.w3.org/wiki/Socialwg/2015-12-01-minutes and https://www.w3.org/wiki/Socialwg/2015-12-02-minutes 18:08:49 +1 18:08:58 +1 18:08:59 +1 18:09:06 +1 18:09:15 rhiaro++ 18:09:18 rhiaro has 191 karma 18:09:19 eprodrom: we have had some problems with F2F minutes before so bravo Amy 18:09:20 rhiaro++ 18:09:23 rhiaro has 192 karma 18:09:24 ... any objections? 18:09:27 thanks to whoever bot-wrangled sufficiently to mean there were no problems with the minutes! 18:09:33 +1 18:09:44 RESOLVED: approve minutes Dec 1 https://www.w3.org/wiki/Socialwg/2015-12-01-minutes and https://www.w3.org/wiki/Socialwg/2015-12-02-minutes 18:09:52 ... barring any objections we'll mark this resolved 18:09:56 +1 18:10:22 https://www.w3.org/wiki/Socialwg/resolutions 18:10:30 ben_thatmustbeme++ for the resolutions summary! 18:10:32 ... while we are on the subject of minutes, ben_thatmustbeme has taken the time to group resolutions from previous minutes 18:10:33 ben_thatmustbeme has 128 karma 18:10:43 present+ 18:10:49 ... if it possible i would love to see this kept up to date 18:11:04 ben_thatmustbeme++ this is great 18:11:04 ... moving on with admin tasks 18:11:07 ben_thatmustbeme has 129 karma 18:11:12 TOPIC: github procedure 18:11:47 eprodrom: one of the controversies going in to F2F is how github procedure works and if we were being fair and how that was documented 18:11:58 https://www.w3.org/wiki/Socialwg/github 18:12:07 me 18:12:12 ... at the F2F amy put together a basic set of procedures and we hammered on them 18:12:19 present+ kevinmarks 18:12:38 ... we approved these at the F2F but wanted to bring them up since not everyone was at the F2F 18:13:01 ... we have already resolved this as the law of the land for github, but wanted to bring it up in telcon 18:13:03 q? 18:13:09 ... any comments or questions on this? 18:13:30 ... no, given that, lets move on 18:13:52 TOPIC: ActivityStreams 2.0 18:14:13 we had resolved to publish a new WD ASAP at the f2f 18:14:24 eprodrom: james updated the editors draft, but did not publish a new WD 18:14:45 ... would like to move toward CR in Jan 18:14:58 ... there was some editorial issues around adding eprodrom as a co-editor 18:15:03 I think there is a new WD? http://jasnell.github.io/w3c-socialwg-activitystreams/activitystreams-core/index.html 18:15:08 Looks updated 18:15:15 ... he is not on today so i am trying to fill in in my co-editor role 18:15:23 Oops I mean http://www.w3.org/TR/activitystreams-core/ 18:15:28 rhiaro, I think James has to just pull the trigger because we already resolved to publish 18:15:34 ... we cleared up a lot of things at F2F, i don't think we have significant blocking issues right now 18:15:40 Never mind 18:15:41 that is updated, yes 18:15:46 https://github.com/jasnell/w3c-socialwg-activitystreams/issues/ 18:15:50 ... the idea is to go to a new editors draft in the next few days 18:16:03 http://jasnell.github.io/w3c-socialwg-activitystreams/activitystreams-core/ http://jasnell.github.io/w3c-socialwg-activitystreams/activitystreams-vocabulary/ 18:16:12 "RESOLUTION: publish a new WD of AS2 drafts as of / by Friday. " from https://www.w3.org/wiki/Socialwg/2015-12-02-minutes 18:16:47 s/editors draft in the next few days/working draft in the next few days/ 18:16:47 so http://jasnell.github.io/w3c-socialwg-activitystreams/activitystreams-core/index.html should move to http://www.w3.org/TR/activitystreams-core/ 18:16:55 eprodrom: the hold up may be on my end 18:17:04 ACTION eprodrom get w3cid to jasnell asap 18:17:04 Created ACTION-85 - Get w3cid to jasnell asap [on Evan Prodromou - due 2015-12-15]. 18:17:05 tantek: can you take an action to get this fixed? 18:17:13 q? 18:17:26 eprodrom: anything on the queue for AS2? 18:17:33 tantek: love the rapid progress 18:17:40 eprodrom: i think everyone does 18:17:55 http://w3c-social.github.io/social-web-protocols/social-web-protocols 18:18:02 TOPIC: social web protocols 18:18:38 rhiaro: FYI: SoLiD is now called Solid 18:18:38 rhiaro: this morning i closed a bunch of issues that were opened at the F2F as they looked like there was concensus 18:19:09 ... if anyone feels this is inadiquate please bring it up 18:19:19 can you add links? 18:19:25 ... I added a section on relation between different documents 18:19:34 ... i would like feedback on what people think about it 18:19:53 ... ask for FPWD issues be posted on Github 18:20:07 ... would like to ask if there are none to go to FPWD by next call 18:20:22 eprodrom: we'll put on agenda for next call to move this FPWD 18:20:31 q+ to ask didn't we ask for that last week to be done by this week? 18:20:36 q? 18:20:43 ack tantek 18:20:43 tantek, you wanted to ask didn't we ask for that last week to be done by this week? 18:20:45 ... assuming people will put in there issues there before next call and hopefully close them 18:20:55 s/issues/FPWD blocking issues/ 18:21:17 tantek: reviewing the minutes from F2F we made that same request for today already 18:21:24 ... are you asking to extend? 18:21:43 rhiaro: yes, they were not posted until very recently, and feel it should have a week 18:21:49 q? 18:21:57 shall we re-resolve on that then? 18:22:01 tantek: thats reasonable, other editors should take note to do this as well 18:22:05 https://github.com/w3c-social/social-web-protocols/issues 18:22:15 eprodrom: we are collecting issues on github? 18:22:24 hm, do we need a profile type discovery like post type? 18:22:25 rhiaro: yes (gives link) 18:22:26 q? 18:22:27 PROPOSED: make any FPWD- issues on Social Protocols Comparison visible before next telecon 12/15 18:22:27 eprodrom: thank you 18:22:35 "The subject of a profile document can be a person, persona, organisation, bot, location, … the type of the subject of the profile is not required." 18:22:48 Social Web Protocols 18:22:55 PROPOSED: make any FPWD- issues on Social Web Protocols visible before next telecon 12/15 18:22:56 eprodrom: lets update that for the correct name 18:23:13 +1 18:23:15 +1 18:23:17 +1 18:23:19 +1 18:23:20 eprodrom: we had a similar proposal at F2F, we are updating to push it another week 18:23:21 +1 18:23:23 +1 18:23:33 eprodrom: i think that makes sense since the minutes just came out 18:23:43 RESOLVED: make any FPWD- issues on Social Web Protocols visible before next telecon 12/15 18:23:53 +1 18:24:13 rhiaro: one last thing to add, i am going to be opening a bunch of issues i would like WG to review, its not just for me its that I don't know where to go with some of them 18:24:20 ... if people could keep an eye on that 18:24:43 eprodrom: i just talked to myself with my microphone off :) 18:24:48 TOPIC: webmention 18:25:12 melvster has left #social 18:25:14 aaronpk: after the f2f all the issues that we discussed i have incorporated issues in to the doc and closed others 18:25:30 ... there are some remaining issues i want to discuss on the call and close a batch of them 18:26:00 ... I commented on each issue with the diff so you can see exactly what the differences are 18:26:07 webmention issues that have been addressed: #22, #18, #17, #13, #12, #5 18:26:23 ... they are all linked in the agenda 18:26:50 ... i would like to propose closing all those on the call here 18:27:16 eprodrom: i'm not quite sure what the proposal is, these have been closed? 18:27:27 aaronpk: they have been addressed, but not closed 18:27:57 eprodrom: i don't want to get rules-wordy about this, but by my understanding, unless there is some objection by the people in the thread or by the requester 18:28:03 ... we don't need to address them 18:28:31 aaronpk: my understanding was the opposite, and i thought we all had to agree but i'm happy to close them proactively 18:28:51 PROPOSED: close webmention issues #22, #18, #17, #13, #12, #5 as resolved either having incorporated feedback or rejected with justification 18:28:56 +1 18:29:01 +1 18:29:02 +1 18:29:05 +1 18:29:12 eprodrom: lets just do this really quickly and in the future we can be more efiicient 18:29:13 +1 18:29:22 +1 18:29:36 RESOLVED: close webmention issues #22, #18, #17, #13, #12, #5 as resolved either having incorporated feedback or rejected with justification 18:29:38 eprodrom: i'm going to mark resolved 18:29:55 aaronpk: in the future i will be proactive about closing them unless there are explicit objections 18:30:09 +1 18:30:16 eprodrom: as the editor its mostly up to you unless there are objections to your mechanism to close them 18:30:39 aaronpk: on issue #21 is in regards to the .well-known 18:31:03 ... i feel there are good reasons for allowing and not allowing, we don't need to discuss on the call but did want to bring the attention to the group 18:31:12 tantek: do you think its a FPWD blocker? 18:31:22 q+ 18:31:32 ack eprodrom 18:31:33 https://tools.ietf.org/html/rfc6415 18:31:37 aaronpk: it might be as it requires a change for the sender and that can be a significant change for the implementor 18:31:56 eprodrom: postmeta uses the well-known 18:32:08 s/postmeta/hostmeta/ 18:32:22 q+ to note that in practice host-meta has also been broken by the big sites that have asked for this, e.g. Google 18:32:28 eprodrom: that might be the most efficient way 18:32:42 ... without setting up a whole new well-known endpoint 18:32:53 aaronpk: this looks like it adds even more work for senders 18:33:13 ack tantek 18:33:13 tantek, you wanted to note that in practice host-meta has also been broken by the big sites that have asked for this, e.g. Google 18:33:17 aaronpk: anyway, i'll add that to the thread and you can see why i don't have an obvious path to closing this right now 18:33:31 tantek: To be clear, you don't have to close all issues to go to FPWD 18:33:42 ... or even have them all documented, though its nice to have 18:33:55 ... regarding this in particular, i don't think its a FPWD 18:34:04 ... maybe in the draft list it as an open issue 18:34:36 ... historically this type of discovery has been requested by large companies who break their own host-meta by themselves for months at a time 18:34:53 ... as an editor you should consider that no current implmentations have yet to use this 18:35:09 ... and also that those requesting it often break it themselves 18:35:32 ... I don't think we can do that on the call, but i wanted to bring that up, but it may require synchronous discussion 18:35:51 aaronpk: i like the plan of not having it as a FPWD blocker and just making sure to note it as an open issue 18:36:04 eprodrom: there are a lot of ways to go from a link relation to an endpoint 18:36:20 ... that discovery process does get rather complicated as there are a lot of methods to do it 18:36:21 not a FPWD blocker but IMO "one big company messed up one time" isn't a good reason to ignore the use case 18:36:46 ... it might not be necessary to actually specify them in webmention either 18:36:50 it's more like "all big companies that supported it dropped it" 18:36:51 bengo - hence worth keeping as an open issue 18:36:54 yep 18:36:56 cool with me 18:36:57 - not ignoring 18:37:02 aaronpk: I also wanted to call for FPWD blockers to be added by next week 18:37:12 ... same as the Social Web Protocols document 18:37:16 you just need to realize that to do practical interop you'll need to implement 3 or 4 different methods of discovery because everybody thinks every other method is dumb 18:37:24 PROPOSED: make any FPWD- issues on Webmention visible before next telecon 12/15 18:37:27 wilkie++ 18:37:29 wilkie has 25 karma 18:37:30 +1 18:37:37 +1 18:37:37 +1 18:37:38 +1 18:37:40 +1 18:37:45 +1 18:38:04 +1 18:38:05 wilkie: or makes up their own 18:38:08 wilkie, or we pick the most common subset (HTTP LINK header and HTML a/link rels) and go with that 18:38:15 RESOLVED: make any FPWD- issues on Webmention visible before next telecon 12/15 18:38:37 TOPIC: Post Type Discovery 18:38:57 tantek: I feel like PTD is a very constrained spec, there are only a few issues 18:39:06 ... I don't need to discuss any specific issues 18:39:30 .... I too would like to request anyone with FPWD blockers to make them visible by next week 18:40:02 ... and also to request people to continue to just raise issues and look at the doc, I do appreciate those that have thus far 18:40:14 eprodrom: that makes sense 18:40:18 PROPOSED: make any FPWD- issues on Post Type Discovery visible before next telecon 12/15 18:40:22 +1 18:40:26 +1 18:41:02 eprodrom: this does mean that we have 3 documents to review before next telcon but that may get us working more 18:41:08 +1 18:41:13 +1 18:41:19 +1 18:41:24 tantek: and with any luck we'll have 3 documents to bring to FPWD next week, which will be a great note to end the year on 18:41:30 +1 18:41:35 RESOLVED: make any FPWD- issues on Post Type Discovery visible before next telecon 12/15 18:41:46 bengo's use case for .well-known seems pretty solid. If this discovery mechanism is the only way bigger/media/cms-constrained orgs can even implement webmention, I think we should avoid excluding them.. otherwise we go from 'probably will not implement / will screw it up' to 'definitely will not implement' and lose out a whole bunch. Particularly as these are orgs who are likely to benefit from federation, as it is optimising for their customers and probably 18:41:46 isn't damaging their business interests. 18:42:07 TOPIC: tracker actions 18:42:24 eprodrom: there are no raised issues right now 18:42:36 ... we have no issues pending review either 18:42:41 ... only pending review actions 18:42:45 rhiaro I don't see the evidence for "is the only way bigger/media/cms-constrained orgs can even implement webmention" - such claims were made in the past about webfinger etc. and either have shown to not be true, or even if they do implement it that way, it's fragile and fails anyway. 18:42:59 ... a lot of these are on you tantek from a few days ago, do you want to take a look at these? 18:43:09 tantek: based that comment from what bengo said, he's the one with experience with these orgs 18:43:12 it looks like a lot of those are about adding things to the f2f agenda so they are done by default now 18:43:28 Can we close ACTION 74 and 75? 18:43:37 tantek: yes I claim i did all these 18:43:44 actions 76-79 18:43:46 in particular 18:43:59 eprodrom: can you close those actions please 18:43:59 close action 76 18:44:08 close action-76 18:44:08 Closed action-76. 18:44:12 close action-77 18:44:12 Closed action-77. 18:44:17 close action-78 18:44:17 Closed action-78. 18:44:20 eprodrom: amy you had a question about 74 and 75 18:44:21 close action-79 18:44:21 Closed action-79. 18:44:31 ... aaronpk and rhiaro are those complete? 18:44:51 q? 18:44:51 rhiaro: I added a section to the SWP document that i think completes it, so long as everyone is happy with that 18:45:08 eprodrom: any other questions? 18:45:31 aaronpk: the webmention page has been updated, so that is done as well 18:45:34 close action-81 18:45:34 Closed action-81. 18:45:43 eprodrom: i love closing issues 18:46:02 did evan just hang up? 18:46:09 it sounds like it 18:46:11 eprodrom: ping 18:46:12 Augh 18:46:16 i think so 18:46:19 I was giving a really good speech too 18:46:31 ... we are now at 45 minutes, i think we have done pretty well here.... (evan's phone dies) 18:46:51 tantek: can't pick a subset. others don't agree wrt interop. 18:47:04 eprodrom: alright, back in the game 18:47:21 tantek: i enjoy your boundless optimism though :) 18:47:24 ... we are at 45 minutes, i'm happy to give the rest of the 13 minutes back 18:47:34 ... however if anyone has any issues we should discuss 18:47:51 ... in particular i'd like to ask in cwebber2 has an update on activitypump 18:47:57 wilkie - in practice no one does "only" host-meta, thus picking a subset of HTTP LINK and HTML rel can work in practice. 18:48:02 Arnaud1 has joined #social 18:48:28 cwebber2: this weekend was kind of crazy for me, but i plan to spend this week closing as many issues as i can, i hope i will have things to report by next call 18:48:29 wilkie - happy to be disproven with documented examples of real-world host-meta *only* implementations. 18:48:57 eprodrom: i don't know that we are at the FPWD request yet for this or micropub 18:49:07 do we have a call on 12/22? 18:49:17 progress on jf2? 18:49:17 it may be that we don't get much more work done on these in the next few weeks 18:49:40 eprodrom: i believe we do have calls scheduled for 12/22 and 12/29 18:49:47 ... we have cancelled those last year 18:49:57 ... do we want to cancel one or both of those calls? 18:50:12 ... specifically for tantek... 18:50:23 ... actually i and the other chairs will talk about that 18:50:28 ... and we will discuss next week 18:50:29 q+ 18:50:30 ok by me 18:50:33 q? 18:50:42 ack ben_thatmustbeme 18:50:48 mostly I want to give the opportunity for cwebber2 and aaronpk to ask for FPWD on ActivityPump and Micropub 18:50:59 so for me it is up to their preference 18:51:22 to 1) call for FPWD- issues by a certain date, and then 2) ask for resolution to publish FPWD by a later date after that 18:51:23 tantek: host-meta is prioritized in my code. i'm not even sure how to get certain endpoints (dialback, salmon) on just page links or headers. i don't think I do. 18:51:37 wilkie - good to know - is that in rstatus or ? 18:51:56 q? 18:52:01 ben_thatmustbeme: do we want make it a workflow that scribe should move resolutions to the /resolutions page in the future? 18:52:12 eprodrom: yes sure, can you do that for F2F and this week 18:52:17 ben_thatmustbeme: sure 18:52:21 trackbot, end meeting 18:52:21 Zakim, list attendees 18:52:21 As of this point the attendees have been Arnaud, csarven, rhiaro, aaronpk, shanehudson, sandro, elf-pavlik, kevinmarks, wilkie, eprodrom, jasnell, ben_thatmustbeme, cwebber, 18:52:24 ... tantek, hhalpin, james, tsyesika, wseltzer, akuckartz, shepazu, Rob_Sanderson, Shane_, rene, cwebber2, Benjamin_Young, bengo, ben_thatmust, KevinMarks_ 18:52:29 RRSAgent, please draft minutes 18:52:29 I have made the request to generate http://www.w3.org/2015/12/08-social-minutes.html trackbot 18:52:30 RRSAgent, bye 18:52:30 I see no action items