16:59:12 RRSAgent has joined #social 16:59:12 logging to http://www.w3.org/2016/05/24-social-irc 16:59:14 RRSAgent, make logs public 16:59:14 Zakim has joined #social 16:59:16 Zakim, this will be SOCL 16:59:16 ok, trackbot 16:59:17 Meeting: Social Web Working Group Teleconference 16:59:17 Date: 24 May 2016 16:59:36 having probs getting webex going 17:00:00 +present 17:00:10 I dialed in, but silence 17:00:25 present+ 17:00:25 trackbot, start meeting 17:00:27 RRSAgent, make logs public 17:00:28 present+ 17:00:29 Zakim, this will be SOCL 17:00:29 ok, trackbot 17:00:30 present+ 17:00:30 Meeting: Social Web Working Group Teleconference 17:00:30 Date: 24 May 2016 17:00:54 present+ 17:00:58 KevinMarks, we're on the call.... 17:01:03 I think i was first 17:01:11 yes 17:03:02 present+ 17:03:25 dialing in 17:03:35 present+ 17:03:39 present+ 17:04:01 present + 17:04:19 eprodrom has joined #social 17:04:31 i can scribe 17:04:36 present+ 17:04:48 scribenick: ben_thatmustbeme 17:04:55 Chair: Arnaud 17:05:03 Approval of Minutes of 2016-05-17 https://www.w3.org/wiki/Socialwg/2016-05-17-minutes 17:05:12 TOPIC: approval of last weeks minutes 17:05:16 looks good 17:05:20 Arnaud: any objections to approving those minutes? 17:05:21 +1, approve 'em 17:05:36 Arnaud: hearing no objections, i'll declare them approved 17:05:44 TOPIC: update on F2F 17:06:14 Arnaud: we are two weeks away. again, please go to the wiki page and indicate your attendance, even if its regrets, or remote participation 17:06:22 I'm so bummed to not be able to go; ditto for IndieWebCamp 17:06:48 ... there aren't too many listed, but the chairs had a meeting and agreed that we had enough key members there 17:07:14 ... we have updated a list of topics, but if there is anything else people wish to add, add proposals and the chairs will try to accomidate 17:07:25 ... any immediate comments, questions, etc on the meeting? 17:07:51 aaronpk: nothing new on our end, we are all set. I added a bunch of information to the wiki page, directions, food, etc 17:08:14 Arnaud: if there are no other questions, we can move on. 17:08:24 q+ 17:08:39 ... there is a question of when the next telcon will be, next weekend is memorial day meeting 17:08:44 ... when do we meet next 17:08:53 ack rhiaro 17:08:57 sandro: I'd like to meet next week so we can hopefully get AS2 to CR 17:09:23 rhiaro: I wanted to ask to meet next week, so i can hopefully get a new WD of SWP 17:09:36 lloyd has joined #social 17:09:43 Arnaud: hearing that i am proposing to keep the normal schedule next week. Any problem with that? 17:09:50 +1 17:09:58 +1 17:10:05 +1 17:10:09 +1 17:10:20 tantek: Arnaud, would you consider that if for some reason, those both fall through, we don't bother. So i'd say +1 to telcon if one of those is ready to ask the group to publish 17:10:23 deciding when? Monday? 17:10:28 Sunday? 17:10:34 Arnaud: so you are specifically interested in not having the call next week? 17:10:49 I'm definitely going to ask about SWP next week 17:10:52 tantek: no, its a matter of being able to make other plans or not 17:10:55 Draft will be ready by end of day tomorrow 17:11:15 ... if we are going to have these drafts ask to be published, hopefully those drafts will be ready a few days before 17:11:30 ... maybe that they have publish ready drafts have them ready by friday? 17:11:41 Arnaud: and then people review them on memorial day weekend? 17:11:54 sandro: you have a better use for a holiday ? :P 17:12:09 tantek: I don't want to do a telcon just to rubber stamp 17:12:48 ... its fine to do a telcon to publish, but to agree to publish, people have to have time to review 17:13:19 Arnaud: we will have the telcon ready next week, per the regular schedule, but if the editors expect to be able to publish, they be ready by friday 17:13:49 tantek: and then there is the one after the meeing too 17:13:58 Arnaud: i think we can decide that at the F2F 17:14:18 TOPIC: Webmention CR update 17:14:28 https://twitter.com/w3c/status/735108163704348672 17:14:30 @w3c :: Webmention is a W3C Candidate Recommendation (Call for Implementation) https://www.w3.org/blog/news/archives/5439 17:14:34 sandro: Webmention has been published as a CR 17:14:34 hubba hubba! 17:14:34 and https://www.w3.org/blog/news/archives/5439 17:14:44 multiple: congratulations 17:14:54 congrats all! 17:14:57 Arnaud: this happend just yesterday? 17:15:24 we did use cases and requirements, I remember 17:15:28 sandro: the transition meeting was fairly uneventful, but for an awkward moment of us not having use-cases and requirements 17:15:42 sandro: I can put that in SWP too 17:15:52 or, links to existing articles about the comparisons 17:16:03 ... I also got some requests from people asking for notes about how it relates to trackback/pingback 17:16:26 SWAT0 has been satisifed with webmention, which is a use case we brought in 17:16:35 Arnaud: for those new to w3c process, we now look for implementation reports, and w3c wide review.. the key is to meet exit criteria 17:16:42 FYI re: webmention over trackback/pingback: https://indiewebcamp.com/Webmention-faq#Why_webmention_instead_of_pingback 17:16:53 sandro: now is the time to drum up publicity for people who might be interested in trying it out 17:17:12 Arnaud: we want to advertise it as much as possible and get them to provide implementation reports 17:17:18 tantek: and feedback too 17:17:21 see https://www.w3.org/wiki/Socialwg#Use_Cases and https://aaronparecki.com/notes/2015/07/14/1/swat0 17:17:54 ... thats part of the goal of CR, get feedback from others trying to implement it. A good spec, they should be able to implement it without talking to us, and if they can't, we should know that 17:18:09 webmention.rocks does that 17:18:21 sandro: here's a dogfoody idea, do we have a webmentionable page about webmention that people can webmention to? 17:18:28 +1000 17:18:30 +1 17:18:39 aaronpk: the validator does that but doesn't hold it permanently 17:18:47 sandro: i think that would be useful 17:18:54 aaronpk: i can make a page for that 17:19:17 tantek: KevinMarks pointed out that we did have the use-case of swat0 and webmention does help implement SWAT0 17:19:20 could we add a wm header to the spec? webmention.io, webmention.herokuapp.com or mention-tech would all work 17:19:53 tantek: just like we should have informative text about pingback, etc. We could have something about swat0 17:19:59 we have done annotations with wm and fragmentions 17:20:09 KevinMarks: it's already there :-) 17:20:11 sandro: i also got feedback from shepazu about including a different use-case 17:20:39 Arnaud: if issues come up in CR that cause changes that would effect compliance, we would have to issue a new CR first 17:21:09 ... in my experience its quite common, but after that point you already have multiple implementations and probably already meet the exit criteria 17:21:39 tantek: thats my experience too, my understanding is we would still need to meet them minimum CR time (4 weeks?) 17:22:10 I also pointed out that the implementation reports can be expected to provide additional use-cases as well (per feedback about including more/different use-cases) 17:22:14 sandro: one other procedural thing that came up, we saw internationalization review, but there are others which we don't have in our charter 17:22:27 ... usually you do that before CR 17:22:36 important liaison! 17:22:58 TOPIC: update on AS2.0 17:23:45 tantek: one more thing to request on webmention, to exit CR, we want a complete test suite, we entered CR with a partial test suite, and thats a critical piece to complete 17:23:58 ... i wanted to give aaronpk a chance to respond before we move on 17:24:36 aaronpk: the implementation report lists all the things to test, and i plan to add them to webmention.rocks, but there are a few things that would have to be done manually by people. 17:24:46 tantek: do you have a rough idea of when it would be ready? 17:24:56 aaronpk: no, i can't say anything to that right now 17:25:05 http://webmention.net/implementation-reports/#receiving 17:25:41 ... my hope with the stuff that i wrote up, is to help you know what it is you need to look for in receiving, if you go through that, you have to self review. 17:25:51 ... some of those i will be able to write tests for, some I won't 17:26:12 tantek: as long as we can document what features we have claimed implementations for but don't necessarily have tests for 17:26:45 ... if we have features that we cannot have tests for, we should be clear about what that list is 17:27:05 ... applies to all of our specs obviously 17:27:20 TOPIC: update on AS2.0 17:27:48 Arnaud: Evan, we were expecting a WD, please tell us whats up? 17:28:42 eprodrom: i just shared links for the editor's draft, but the publish of the WD is taking some time to get going, it should be up in the next 24h, if thats the case, i'll update the group via email. We don't have a WD, we probably can't discuss taking it to CR 17:29:04 Arnaud: to clarify, is the editor's draft ready for publication? is it just a matter of publishing to the TR space? 17:29:20 eprodrom has joined #social 17:29:30 http://jasnell.github.io/w3c-socialwg-activitystreams/activitystreams-core/index.html 17:29:36 http://jasnell.github.io/w3c-socialwg-activitystreams/activitystreams-vocabulary/index.html 17:29:39 eprodrom: yes, everyone can view it in the editor's draft now. there will be minor errors or things i have to clean up, but the content will be what will go up on WD 17:30:04 q? 17:30:08 Arnaud: the expecation is that will happen before friday, and hopefully next week we can have a vote on requesting to take it to CR 17:30:20 Arnaud: any question or comments? 17:30:33 Topic: request for review of JF2 17:31:01 scribenick: rhiaro 17:31:02 URL? 17:31:04 ben: I finally have time to do updates on jf2 and i would like to share them wiht the group 17:31:13 ben_thatmustbeme: Can people look over jf2 and give me some feedback; I made some updates 17:31:13 http://dissolve.github.io/jf2/ 17:31:25 ben: I want to get feedback from the group 17:31:28 summary of changes since we last talked about it? 17:31:53 Arnaud: all the w3c drafts should be in the w3c space? 17:31:58 sandro: no, james resisted that with as2 17:32:10 Arnaud: as far as I know w3c is deploying a bunch of tools to archive, and none of this happen sif it's not in w3c space 17:32:22 sandro: this is true, it's not clear that any of these tools are useful yet, trying to figure out how to deploy the archiving thing 17:32:31 ben_thatmustbeme: none are, are they? 17:32:37 Arnaud: that doesn't mean it's okay 17:32:49 tantek: last time we talked about this we made a deliberate decision to have editors keep the specs in their repos, in SF 17:33:01 sandro: we might want to reconsider if there's a problem, I'll try to find out 17:33:03 Arnaud: thanks 17:33:29 ben_thatmustbeme: I don't think many people have read it yet, it's my first draft, so before I ask I'd like input 17:33:40 tantek: when do you think you'll ask for that 17:34:05 ben_thatmustbeme: barring any issues, it's been very useful for us (aaronpk and I) already, it simplifies things for working with individual objects coming out of microformats 17:34:16 ... could ask any time, just want wg review first 17:34:20 tantek: next week, face to face? 17:34:25 ben_thatmustbeme: next week, sure 17:34:56 scribenick: ben_thatmustbeme 17:35:09 TOPIC: social web protocols 17:35:45 rhiaro: i just updated the mentioning section, i'm going to continue to update the other sections. It was more bullet points before, but now its more prose 17:36:03 ... I'm hoping to have it up in a couple days and certainly by friday 17:36:10 http://w3c-social.github.io/social-web-protocols/ 17:36:16 ... i also added text on how it relates to other specs 17:36:25 Arnaud: any other questions? 17:36:33 yes 17:36:35 TOPIC: tracking of other document status 17:36:35 q+ 17:36:44 q+ 17:36:45 Arnaud: any other updates anyone wants to give? 17:36:46 ack cwebber 17:37:16 http://w3c-social.github.io/activitypub/ 17:37:29 cwebber2: I guess its a big one , but we discussed releasing a new WD of activitypub. I incorporated a few updates, but I don't think anybody raised any other issues to it 17:37:39 awesome! 17:37:40 ack tantek 17:38:03 q+ 17:38:18 ack cwebber 17:38:26 tantek: ben roberts has been helping me get a github version of the post type discovery up and hopefully i'll have it ready by the F2F 17:38:56 cwebber2: i just wanted to make sure that no one raising any issues on the call is it OK for me to publish an updated WD 17:39:11 http://w3c-social.github.io/activitypub/#changes-from-28-january-2016-wd-to-this-version 17:39:11 cwebber2: I guess what i'm asking for is an explicity vote 17:39:22 http://w3c-social.github.io/activitypub/#change-log 17:39:27 tantek: is there a list of changes? 17:39:38 cwebber2: pasted in chat 17:39:39 PROPOSED: Publish the latest ActivityPub editor's draft 17:39:55 +1 17:39:56 +1 17:39:57 +1 17:40:01 +1 17:40:03 +1 17:40:05 +1 17:40:09 +1 17:40:10 +1 17:40:24 +1 17:40:28 Arnaud: anyone else? 17:40:32 RESOLVED: Publish the latest ActivityPub editor's draft 17:40:33 minor editorial nit: s/ActivityStreams Working Group/Social Web Working Group 17:40:51 Arnaud: any other good news? 17:41:12 tantek: now that you have a WD ready to publish, hows the implementation going? 17:41:56 cwebber2: after the F2F i plan on doing a complete and independant implementation and that will be my complete focus between this and the next F2F 17:42:01 Arnaud: anyone else? 17:42:13 ... Any other business people would like to bring up? 17:42:22 horray 17:42:25 ... thank you all 17:42:28 ben_thatmustbeme++ thanks for scribing! 17:42:29 later, * 17:42:30 ben_thatmustbeme has 145 karma 17:42:38 Arnaud: we'll have a meeting next week, 17:42:40 thanks Arnaud and Ben / Amy 17:42:43 ... see you next week 17:42:48 trackbot, end meeting 17:42:48 Zakim, list attendees 17:42:48 As of this point the attendees have been present, Arnaud, sandro, tantek, ben_thatmustbeme, aaronpk, annbass, rhiaro, cwebber 17:42:56 RRSAgent, please draft minutes 17:42:56 I have made the request to generate http://www.w3.org/2016/05/24-social-minutes.html trackbot 17:42:57 RRSAgent, bye 17:42:57 I see no action items