17:03:44 RRSAgent has joined #social 17:03:44 logging to http://www.w3.org/2016/07/05-social-irc 17:03:46 RRSAgent, make logs public 17:03:46 Zakim has joined #social 17:03:48 Present+ 17:03:48 Zakim, this will be SOCL 17:03:48 ok, trackbot 17:03:49 Meeting: Social Web Working Group Teleconference 17:03:49 Date: 05 July 2016 17:03:51 present+ 17:03:53 eprodrom has joined #social 17:03:53 present+ 17:03:55 present+ 17:03:56 present+ 17:03:59 present+ 17:04:07 present+ 17:04:11 present+ 17:04:12 present+ 17:04:20 chair: eprodrom 17:04:27 scribe: ben_thatmustbeme 17:04:29 scribenick: ben_thatmustbeme 17:04:40 (Do I have to re-do my "present+", since I typed it before trackbot? (Just curious) 17:04:52 Okie dokie 17:04:56 Present+ 17:05:18 eprodrom: okay, lets get started 17:05:44 TOPIC: welcome new IEs 17:05:59 present+ 17:06:01 present+ Benjamin_Young 17:06:18 present+ 17:06:18 new person Julian (sp?) 17:06:28 Julien 17:06:35 sandro: he is in the process of moving this week 17:06:37 present+ 17:06:40 present+ 17:06:52 I'm glad julien is finally here haha 17:06:52 eprodrom: we will defer the welcome to next week 17:06:57 https://twitter.com/julien51 17:07:05 TOPIC: approval of last week's minutes 17:07:16 PROPOSAL: approve https://www.w3.org/wiki/Socialwg/2016-06-28-minutes as minutes for 2016 06 28 meeting 17:07:41 +1 I have reviewed 17:07:43 +1 17:07:46 +1 17:07:48 +1 17:07:50 +1 17:07:51 eprodrom: please do a quick review 17:07:51 +1 17:07:54 +1 17:08:14 RESOLVED: approve https://www.w3.org/wiki/Socialwg/2016-06-28-minutes as minutes for 2016 06 28 meeting 17:08:26 (I'm particularly interested if the editorial change to AS2 was accepted) 17:08:39 TOPIC: closed issues for AS2 17:09:33 eprodrom: as we take as2 to CR, one of the things we have to show is that any comments on spec have been resolved to the commenter's satisfaction. Doesn't mean they have to be happy with the results, but at least they acknowledge the issue was dealt with 17:09:43 ... amy has been following up with everyone 17:10:02 q+ to ask about update on the editorial request from bengo 17:10:19 rhiaro: after last week we gave them another week. At this point everyone has had at least 2 weeks. in my messages I said that any silence we would just close them 17:10:23 https://www.w3.org/wiki/Socialwg/Addressing_Issues#ActivityStreams_2.0 17:10:38 ... I would propose we finalize by close all the remaining as commentor timed out 17:11:01 eprodrom: amy, you said everyone had two weeks? 17:11:25 rhiaro: they had one week, and then we extended them more 17:11:33 eprodrom: do we need to agree to close them out? 17:11:42 sandro: I don't think so ... (couldn't hear) 17:11:50 that sounds more than reasonable 17:11:57 rhiaro does such good work 17:12:02 eprodrom: as editor i think we have the concensus to close them all out 17:12:15 Sandro -- can't hear you .. Or very barely (can others?) 17:12:21 eprodrom: lets talk about the PR from bengo 17:12:31 https://github.com/w3c/activitystreams/pull/329 17:12:38 sandro is very quiet yeah 17:12:41 q- 17:12:58 eprodrom: here is the PR itself and the PR was merged but have not pushed a new version of the WD 17:13:09 ... i will put those other changes on the agenda at the end 17:13:22 ... at least with repect to that PR, it has been closed 17:13:36 sandro: the most important part is there be a draft that is ready for CR 17:13:41 q+ 17:13:46 ... then if we have approval it will go out 17:14:07 eprodrom: explain to me processwise, would that be a WD that says CR, or an ED that says CR 17:14:15 sandro: neither, its a document that says CR 17:14:35 ... its as if you were going to do a publication through echidna, but it doesn't handle CR 17:14:43 eprodrom: i can do that this week. 17:14:56 sandro: it would be great if we could have it before the meeting tomorrow 17:15:17 eprodrom: that sounds fine 17:15:23 ... since we are on AS2 17:15:38 ... i wonder if we could stay on as2 for a moment 17:15:47 rhiaro: i have another thing on as2 issues 17:15:52 https://github.com/w3c/activitystreams/issues/53 17:16:14 ... dret raised an issue, we discussed last week, but you weren't here evan, just wanted to make sure you saw it 17:16:27 ... its editorial so we can deal with it later, but just wanted to call your attention to it 17:17:13 eprodrom: i've just read this, let me just review the core doc very quickly 17:17:36 aaronpk, can you get me a July 12 CR doc, too ? 17:17:52 for micropub? 17:17:54 rhiaro: its more just a clarification point 17:17:57 yes 17:18:30 eprodrom: it makes sense as people trying to push arrays through AS2 validator, but it would need to be a collection 17:18:44 ... i'm okay resolving this as some text calling that it 17:19:00 rhiaro: sandro, do we need all issues closed before CR call? 17:19:02 yes, i have some minor edits to publish so i will want to publish a new WD first 17:19:09 sandro: no, as long as its clear its editorial 17:19:19 eprodrom: do we need a resolution of any type on that? 17:19:41 eprodrom: i'm going to reopen this and i'll resolve it after the meeting 17:19:50 not if the commenter is happy 17:19:51 i don't think we need a resolution on it 17:20:10 q- 17:20:19 eprodrom: i can just resolve this quickly after 17:20:34 Q+ not about AS2 .. Wonder if Melvin's micropub objection was adequately resolved? 17:20:35 eprodrom: i'd like to talk about a couple of other items that were closed out 17:20:45 https://github.com/w3c/activitystreams/issues/328 17:20:56 Q+ 17:21:03 ... first is 328, which is test documents of known invalid documents 17:21:22 https://github.com/w3c/activitystreams/tree/master/test/fail 17:21:24 ... i created about 20 documents that would be useful for testing failures, bad documents 17:21:40 ... they are in a subdirectory, specifically called out as failure ones 17:21:54 ... they are all valid json, but not valid as2 docs 17:22:12 https://github.com/w3c/activitystreams/tree/master/test 17:22:18 ... the other issue i closed out this week was a link to the validator, its now in the readme for the test directory 17:22:38 ... i think that closes those two out 17:22:58 ... i just wanted to call those out here and see if they were satisfactory to aaronpk and sandro 17:23:19 ... if so thats all we needed to discuss for as2 today. i 17:23:20 https://rawgit.com/csarven/ldn/master/index.html 17:23:27 TOPIC: linked data notifications 17:23:33 Q- 17:24:09 rhiaro: over the laste fiew months we have been working on a LD notifications spec, it sends JSON-LD objects around 17:24:17 q? 17:24:17 q? 17:24:30 ... we'd like to bring it to the WG as an ED and see how far we can get with it 17:24:47 eprodrom++ for the AS2 failure examples. looks great 17:24:48 eprodrom has 34 karma 17:24:59 eprodrom: this is a generalized notification protocol. Is it within our charter? is it something within our sphere of work to work on? 17:25:14 +1 on charter question 17:25:15 q+ 17:25:16 s/laste fiew/last few/ 17:25:23 eprodrom: would another group like LDP group or a community group more accurate? 17:26:14 rhiaro: its not LDP, we leverage it, and its similar, but its not. You don't need to be a full LDP implmentation to be a receiver 17:26:52 eprodrom: i guess my question was more about, it seems to be a general notification protocol, is it right for the socialWG to do? 17:27:07 ... i wanted to just hear from the authors what they think of that 17:27:35 rhiaro: i think it is, its compatible with activity pub, its also compatible with the annotations protocol, which is a social use-case 17:28:04 ... and any other kinds of social interactions. the actual content of the notification is really broad 17:28:09 q? 17:28:14 ack sandro 17:29:39 melvster has joined #social 17:30:20 sandro: there is a permathread between me and melvin about him wanting webmentions to be something it isn't. I think this is more of what he wants. People come to webmention saying 'can i use this' and they can, but have to do some things. Its a little more straight forward if you have an authentication method already. Also the other thing is that webmention doesn't have that is, that there is some way to fetch those messages after that fact 17:30:31 q+ to ask about permathread 17:30:39 q? 17:30:42 ack tantek 17:30:42 tantek, you wanted to ask about permathread 17:31:17 tantek: question to the authors, does this proposal address melvin's concerns? would this resolve that permathread? 17:31:45 rhiaro: we've run it by melvin and yes 17:31:52 ... he has said it looks good 17:32:07 tantek: well thats a good way of resolving that issue 17:32:33 eprodrom: is there an issue on webmention's issue tracker that we can point to? 17:32:38 https://github.com/aaronpk/webmention/issues/51 17:32:40 ... something we could resolve there 17:32:41 my suggestion was to write out an example of what webmention would look like in JSON-LD 17:33:00 to that extend I have written out two proposals 17:33:02 q? 17:33:09 eprodrom: maybe we could just explicitly note it in that issue 17:33:17 tantek: but this isn't webmention right? 17:33:34 sandro: yes, but i think this is what melvin wanted to turn webmention in to, but it isn't 17:34:01 q? 17:34:05 tantek: the question is from the process perspective, does this satisfy the commenter? 17:34:12 sandro: i don't htink he has said yet 17:34:18 q+ 17:34:58 eprodrom: at our last f2f, we discussed the difficulty we will have to close out the existing documents. does it make sense to take on a new document this late in the game? 17:35:18 ... i'm not objecting to this particular doc. I am saying in general for any new documents 17:35:31 ... is it ok for us to take on a new document at this time in our lifecycle 17:36:02 rhiaro: i would say, we are bringing more resources in from the solid end in to work on this, so its adding new resources not just more workload 17:36:16 rhiaro++ 17:36:17 rhiaro has 210 karma 17:36:42 tantek: i think when i made that argument was when Arnaud pointed out that we don't have time to deal with lots of different documents in the group, but we are at least trying to spread around the authorship 17:36:57 rhiaro: this is something i would be working on anyway 17:37:14 tantek: the only real resource this takes up then may be just telcon and f2f time 17:37:33 ... if we can resolve that, we can resolve the resource issue 17:38:04 eprodrom: i think we need the editors to at least recognize its possible we don't finish the document as we only have 6 months left 17:38:19 rhiaro: we are certainly prepared to publish as a note if all else fails 17:38:26 q? 17:38:33 ack tantek 17:38:38 tantek: that poses a good follow up then, do you have an intended date for CR? 17:39:18 ... i think we had said that anything this late we would push toward note track to make sure to set expectations inside and outside of the group 17:39:21 can we let them TRY for CR-track, and then back up to Note? 17:39:42 ... do you think this is simple enough to get to CR that quickly? 17:39:58 rhiaro: we are pretty sure we can get our specs to CR by lisbon right? 17:40:31 ... we are aiming for that, but if we have to drop to note track thats fine 17:40:50 ... its easier to go from rec to note than note to rec right? 17:41:10 sandro: it depends on implementations flocking to it or not 17:41:50 tantek: i think that makes sense. and we continue to focus on any new docs we bring to the group, we let them know its more to keep it to note track 17:42:07 annbass_ has joined #social 17:42:15 ... with PuSH its very well known and has been implmented so the process is very different 17:42:49 rhiaro: we have implemented a lot of it and we have leaned on LDP for a lot of the work, and its just discovery of endpoints and such 17:43:16 rhiaro: for LDN we wrote it around the implementations we have had for some time 17:43:45 tantek: i think that just leaves the question evan raised about, is it in our charter? 17:43:54 ... what section does this fall under 17:44:00 rhiaro: federation 17:44:14 ... possibly social depending on how you use it 17:45:02 tantek: you said this is compatible with activity pub, the way you just described it could be client to server or server to server. what does this add beyond activity pub? 17:45:55 rhiaro: activitypub specifically uses json format, thats just a specialized form of LDN. we do content-type negotiation so you can send in other formats 17:46:08 tantek: so its more general then AP? 17:46:22 rhiaro: yes, AP would be a more specialized case of this 17:46:54 tantek: thats one of the concerns thats been raised to date, is that we need to have some kind of story of when we want one or the other 17:47:08 .. this seems like its even more confusing of when to use one or the other 17:47:53 rhiaro: my hope with this is take some of the work away from the AP side. We don't want it to be reliant on this spec 17:48:17 ... AP has the additional info on what to do after you receive the notification. thats out of scope of this spec 17:48:53 tantek: i think i get what you are saying, i'm in favor of modularizatino in general but i would like to hear from cwebber2 17:49:06 ... and how does this impact getting AP to CR 17:49:21 ... if this is going to slow AP at risk, i'm a bit more concerned 17:49:35 ... i accept that you are working on fitting this all together 17:49:55 tantek: is he worried or not? 17:50:03 rhiaro: i don't know 17:50:12 ... he's not on the call today 17:50:24 tantek: i'd like to hear from him before we accept this as an ED 17:50:44 tsyesika: are you on the call? 17:50:46 Whilst chris is handling the splitting of the documentation, I don't think it'd put us at risk 17:50:52 eprodrom: that puts us in a little of a bind time wize, but i would like ot hear from cwebber2 or tsyesika on this before we accept it 17:51:12 I'd support this document 17:51:30 eprodrom: if we have a thumbs up from editors there from AP, i think its time for a proposal 17:51:40 tsyesika++ 17:51:42 tsyesika has 16 karma 17:51:49 PROPOSE: accept https://rawgit.com/csarven/ldn/master/index.html as new Editor's Draft for federation protocol 17:51:56 +1 17:52:01 +1 17:52:02 +1 17:52:02 +1 17:52:03 +1 17:52:04 +1 17:52:06 +1 17:52:06 +1 17:52:08 +1 17:52:10 s/PROPOSE/PROPOSAL 17:52:11 thanks rhiaro for answering all the questions - no objections 17:52:12 (I don't think it's a question of taking on an additional risk so much as splitting the risk along multiple paths, which might decease the overall risk) 17:52:14 +1 17:52:23 eprodrom: if there are any objections to that working please say so now before the immediate+1s 17:52:32 PROPOSAL: accept https://rawgit.com/csarven/ldn/master/index.html as new Editor's Draft for federation protocol 17:52:37 +1 17:52:44 +0 17:52:51 0, i haven't read the document 17:52:51 +1 17:52:53 +1 17:52:53 +1 17:53:08 +1 17:53:11 +0 17:53:14 eprodrom: don't need to vote again, minor change there 17:53:56 RESOLVED: accept https://rawgit.com/csarven/ldn/master/index.html as new Editor's Draft for federation protocol 17:53:58 melvster, does accepting this document close webmention #51 for you then? 17:54:01 eprodrom: we have mostly +1s and some +0s. I'm a bit concerned about the timeline, but accepting we may not take this to CR 17:54:38 tantek: i think aaronpk had a good quesiton on IRC, does this resolve melvster's concerns on webmention 17:54:47 aaronpk: if there is a way to map a webmention to a linked data notification, yes 17:55:16 I read the LDN document, it looks good, similar to what we'd be doing and if it can get that to CR I'd be happy for AP to point to it as the general mechanism that we'd specify how to do it (as amy explained) 17:55:21 eprodrom: i think this does close this out unless there is something else to discuss about it 17:55:27 ... it looks like its a yes 17:55:34 s/aaronpk:/aaronpk,/ 17:55:45 TOPIC: document status 17:55:55 Thanks a lot rhiaro (and sarven and whoever else) 17:56:01 eprodrom: do we have any updates on document status 17:56:36 tantek: we were about to publish PTD FPWD and JF2 FPWD but we ran in to apublication holiday we didn't know about 17:57:07 sandro: maybe plan for doing them at the same time on the others, the 12th? 17:57:14 tantek: thats fine with me 17:57:21 ben_thatmustbeme: thats fine with me too 17:57:30 eprodrom: tsyesika any updates on AP? 17:57:42 ... she's on IRC actually, so i'll give her a pass 17:57:48 I've been busy with a family situation this week sorry 17:57:49 eprodrom: is there any other business? 17:57:56 TOPIC: other business 17:58:07 tantek: upcoming F2F in lisbon 17:58:15 How many think they'll be in Lisbon? (Curious) 17:58:16 ... i think we have a wiki page for that, i hope so 17:58:26 I plan to go 17:58:27 https://www.w3.org/wiki/Socialwg/2016-09-22 17:58:57 I'm going to try to go but I've unfortunately not booked anything yet 17:58:59 tantek: we should start collecting, 'going', 'interested in going' etc 17:59:08 ... so we know what size room to ask for 17:59:36 sandro: during the f2f amy and i committed but we had a budget issue and hopefully we will know in the next day or two 17:59:55 tantek: hopefully people can add themselves to that wiki page 18:00:01 eprodrom: thanks everyone for coming 18:00:04 thanks all 18:00:14 trackbot, end meeting 18:00:14 Zakim, list attendees 18:00:14 As of this point the attendees have been annbass, rhiaro, sandro, dmitriz, csarven, eprodrom, aaronpk, wilkie, ben_thatmustbeme, akuckartz, Benjamin_Young, KevinMarks, tsyesika, 18:00:17 ... tantek 18:00:22 RRSAgent, please draft minutes 18:00:22 I have made the request to generate http://www.w3.org/2016/07/05-social-minutes.html trackbot 18:00:23 RRSAgent, bye 18:00:23 I see no action items 18:00:25 Thanks a lot Evan and Ben