17:00:24 RRSAgent has joined #social 17:00:24 logging to http://www.w3.org/2016/06/21-social-irc 17:00:26 RRSAgent, make logs public 17:00:26 Zakim has joined #social 17:00:28 Zakim, this will be SOCL 17:00:28 ok, trackbot 17:00:29 Meeting: Social Web Working Group Teleconference 17:00:29 Date: 21 June 2016 17:01:11 oh hi Arnaud 17:01:17 all my technology is failing 17:01:19 present+ 17:01:21 present+ 17:01:37 agenda: https://www.w3.org/wiki/Socialwg/2016-06-21 17:01:41 chair: Arnaud 17:01:56 tantek can't make the call today and asked me to take over chairing 17:02:12 present+ 17:02:39 can you hear me? 17:02:53 present + 17:02:55 present+ 17:03:03 present+ 17:03:10 redialing 17:03:52 I'm on but muted, didn't hear aaron 17:03:57 present+ 17:04:07 I hear you! 17:04:09 woo 17:04:13 present+ 17:04:21 ironically hangouts never seems to work for me in chrome. had to dial from safari 17:05:03 present+ 17:07:01 present+ 17:07:01 scribenick: rhiaro 17:07:23 TOPIC: Approval of f2f minutes 17:07:51 https://www.w3.org/wiki/Socialwg/2016-06-06-minutes 17:07:52 https://www.w3.org/wiki/Socialwg/2016-06-06-minutes 17:07:59 https://www.w3.org/wiki/Socialwg/2016-06-07-minutes 17:07:59 https://www.w3.org/wiki/Socialwg/2016-06-07-minutes 17:08:00 https://www.w3.org/wiki/Socialwg/2016-06-07-minutes 17:08:06 is where micropub is discussed 17:08:17 Arnaud: there's a -1 from tantek about approval of micropub for CR is missing 17:08:33 the resolution is in that 17:08:57 ... MIcropub going to CR was discussed on 2nd day, June 7th, resolution is there to publish new ED 17:08:59 I don't think it was there at the time of his -1 17:09:03 ... But no resolution on CR 17:09:10 ... Does anybody remember? 17:09:10 oh, nevermind 17:09:37 eprodrom: did we vote on that at the f2f or in the previous telecon 17:09:40 sandro: at the face to face I'm pretty sure 17:10:09 ben_thatmustbeme: I know it stopped tracking minutes at some point 17:10:18 rhiaro: the bot caught that up, that was fixed 17:10:26 Arnaud: we can approve June 6, we need to do archeology on the 2nd day 17:10:34 ... If we are missing minutes maybe somebody has a personal log? 17:10:37 or public log? 17:10:58 logs here: http://socialwg.indiewebcamp.com/irc/social/2016-06-07 17:11:23 http://socialwg.indiewebcamp.com/irc/social/2016-06-07/line/1465317064307 17:11:53 Arnaud: this resolution was captured about WD, no mention of CR 17:12:05 ... Maybe it's the way the proposal and the resolution were worded? 17:12:08 we started this document too https://www.w3.org/wiki/Socialwg/Micropub_CR 17:12:23 should we just make the official resolution again? 17:12:37 sandro: we wouldn't have made the transition request document if we hadn't 17:12:42 ... I'm checking my irc logs 17:13:58 Arnaud: let's not spend too much time on this, see if we can track this down 17:14:02 eprodrom: tantek and I will do that 17:14:11 PROPOSED: Approve minutes of June 6 2016 17:14:12 iirc Loqi logs this channel right? 17:14:19 +1 17:14:22 +1 17:14:23 +1 17:14:26 +1 17:14:32 _1 17:14:34 cwebber2: that's the url i pasted above (socialwg.indiewebcamp) 17:14:38 oh oops 17:14:41 I could not find it in my irc logs 17:14:43 +1 17:14:43 thx aaronpk 17:14:44 +1 17:14:48 RESOLVED: Approve minutes of June 6 2016 https://www.w3.org/wiki/Socialwg/2016-06-06-minutes 17:15:11 TOPIC: AS2 17:15:17 Arnaud: evan, anything blocking? 17:15:52 eprodrom: At the f2f we had gone through some additional requirements for the document including implementation report template, that kind of stuff, those are all now in the documents 17:16:01 ... We also chose to move it from jasnell's personal github to w3c github namespace 17:16:06 http://w3c.github.io/activitystreams/vocabulary/ 17:16:12 http://w3c.github.io/activitystreams/url/ 17:16:12 ... So as of right now we have up to date documents at these two urls 17:16:22 http://w3c.github.io/activitystreams/core/ 17:16:26 and I fixed the links on the socialwg wiki to point to them 17:16:30 not sure if there are any other links 17:16:43 ... These are mostly editorial changes, the big editorial change was adding an implementation report template and including that 17:17:02 ... Ready for submission of new implementation reports by email or github PR 17:17:13 https://github.com/w3c/activitystreams 17:17:14 ... Our issue list is at 0 17:17:29 ... The last outstanding task for me is making sure the transition req is filled out. I have to answer some questions on that. 17:17:44 Arnaud: Ist here a schedule for the call? 17:17:59 sandro: Is the test suite stuff done, the cross linking between two different testing systems? 17:18:17 eprodrom: links from the document to the different test suites, link to the paresable data and a link to the validator 17:18:22 sandro: they don't link to each other but I guess that's okay 17:18:30 eprodrom: I can put links on each of them if that's what we need to get done 17:18:58 q+ 17:19:08 ... I'll do an issue for a link to the validator from the test documents directory with a readme 17:19:45 ... And a link from the validator to ... one thing that I did with this last push is that I moved the test data into the spec document repo, it was easier to keep everything all together. May do that with the validator code too 17:19:48 ack aaronpk 17:20:18 aaronpk: I just found a random URL in the test suite and dropped it into the validator and it gives a warning that it should have an 'id' property, so I thought that it might be good to check the test suite data actually validates 17:20:23 ... Looks like the examples are missing ids 17:20:38 Arnaud: we can keep working on the test suite, but good that you point that out 17:21:39 eprodrom: with AS2, there are very few required properties. A name is almost always required, an id is usually required, so we give warnings. We have examples.. one example we have is an empty object. So we have examples that processors should be able to consume and should be able to parse, however when they're put through the validator they'll show warning because they're poor style. Does that make sense? 17:21:54 q? 17:22:13 https://as2.rocks/validate?url=https%3A%2F%2Fraw.githubusercontent.com%2Fw3c%2Factivitystreams%2Fmaster%2Ftest%2Fvocabulary-ex129-jsonld.json 17:22:14 ... If you put an empty document through as2.rocks ... I think need to have a testable system for consumers and we need to have test data that's useful to help them test edge cases, but we also have to have those notifications in the validator for those edge cases 17:22:22 ( Arnaud, I'd like to return to Micropub CR this meeting, soon ) 17:23:05 ok 17:23:14 aaronpk: How do I know what to do with the data ? How do I know if my code is properly handling it? 17:23:30 q+ 17:23:40 eprodrom: What should your code do? Send an email, fetch a url, put a pin into a map. I'm not sure if there's a correct behaviour we can require out of these processors. What we're looking for is can you parse it, does it look right within your framework 17:23:44 ack cwebber2 17:23:49 ack cwebber 17:24:32 cwebber2: I just wanted to follow up; we've discussed this before, AS2 is a vocab and the testing toosl around it don't and can't enfoce side effects. That's what AP and ActivitySub do, they're examples of real requirements of implementing that. This has come up before and we specifically went against requiring side effects to have in the tests, as this isn't specified in the vocabulary 17:24:55 aaronpk: I just want to know how I know if my code is handling it 17:25:10 eprodrom: How would we know that? Ther'es no way to know that? There are a million different things you could do 17:25:16 ... We can't require any behaviour out of these systems 17:25:27 ... One way you might know is if you're writing a parser and your parser doesn't throw any errors, that's one good way 17:25:40 ... So what wev'e done is provide some documents that are known good, and that's about the extent we can go to 17:25:47 Arnaud: I'd rather not we have this discussion again, we've gone over it 17:25:55 ... There's only so much testing we can do 17:26:18 eprodrom: One thing we could do is are you looking for some comments on this? Like this is a place, this has all the optional attributes of a place... something like that? 17:26:46 aaronpk: The other way to handle that is are there examples of documents that are known bad, so I know that if I parse this document I should see an error? That would help give me something to test 17:26:54 ... Otherwise I'm just parsing a json document and tha'ts all I'm testing 17:27:06 ... If there are examples of valid json documents that are invalid AS2 documents I can use that to test parsing as2 17:27:10 q? 17:27:13 q+ 17:27:25 eprodrom: That sounds good. We can put together test documents that are known invalid AS2 documents 17:27:29 aaronpk: THat would definitely help me 17:27:37 ack sandro 17:28:08 sandro: but mostly I think you have to hand inspect each one. You're supposed to look at the document, read the spec, and see if your app does whatever makes sense to do for that content. That's my expectation of what it means to be a conforming consumer. You can't automate consumer testing of AS2 17:28:17 ... That may be something to say prominently on the readme around these files 17:28:43 cwebber-argh has joined #social 17:28:47 ... The implementation report around consumers presumably say something like my appication understands what this vocabulary temr means and does something meaningful with it. There's no way to automatically test that given it's all human behaviours.. it turns into some html or pixels on the screen 17:28:52 aaronpk: makes sense 17:28:58 server I was connected to for irc is unreachable 17:29:41 eprodrom: Yeah the implementation document covers all of the object classes, each property of each object class, the core and extended vocab, and asks whether you implemented that class, and for each property did you implement it, and a place for comments 17:29:55 ... So if you implemented audio class but you don't necessarily process wav files or something, you could put that kind of comment into there 17:30:04 also we had a heavy discussion about this in SF and after and came to the conclusions about how to go about testing and etc, I really feel like this has been move forwarded with after already being discussed to death 17:30:09 sandro: do you think it's possible peopel might see that and go.. I have a json parser therefore I'm implementing all of this? 17:30:30 eprodrom: We say in our document your application must use this, just passing through unrecognised properties doesn't count as an 'implementation' 17:30:35 "For each core class your application implements, note which properties of the class it uses. Here, "implements" means that your application uses the property directly; just passing through unrecognized properties doesn't count as an "implementation"." 17:31:11 Arnaud: I think this is good, still some things to be tied up, but I don't hear anything that would stop us on the CR request 17:31:18 ... We already have a resolution 17:31:32 eprodrom: I'd like to take the current version and take the new links to WD and we do need a resolution on that 17:32:04 PROPOSED: publish the latest editor's draft of AS 2 17:32:12 +1 17:32:14 +1 17:32:14 +1 17:32:15 +1 17:32:21 +1 17:32:23 +1 (as new WD) 17:32:44 RESOLVED: publish the latest editor's draft of AS 2 as new WD 17:32:54 +1 17:33:12 Arnaud: sandro, you'll work on the scheduling and sending the request? 17:33:14 sandro: yes 17:33:32 sandro: Back to micropub. I did find me IRC log and it looks like we messed up and we didn't record that 17:33:45 obviously tantek did understand that was well 17:33:45 ... I certainly understood that we had. I've talked to Wendy about it. But it's not in the record, so that's an oops 17:33:54 ... I guess the easiest thing to do would be to do that resolution now? 17:34:00 makes sense 17:34:04 PROPOSED: Move MicroPub to CR 17:34:07 +1 17:34:09 +1 17:34:13 +1 17:34:14 +1 17:34:14 +1 17:34:29 +1 (I feel we decided this as the F2F but it didnt get recorded) 17:34:55 +1 17:34:58 +1 17:35:05 RESOLVED: Move MicroPub to CR 17:35:05 whew, back on this server :) 17:35:08 RRSAgent, pointer? 17:35:08 See http://www.w3.org/2016/06/21-social-irc#T17-35-08 17:35:22 TOPIC: Micropub 17:35:28 Arnaud: want to add anything on status of WD? 17:35:43 aaronpk: I went through all the issues from the f2f and published a new WD yesterday. All work we had agreed on at the f2f 17:35:47 ... No more open issues on that 17:36:08 https://www.w3.org/TR/micropub/ 17:36:10 sandro: as far as you know we're ready to finish the transition request. Wouldn't hurt for people to give it another read 17:36:28 ... Later today I'll look over them both and try to send them 17:36:37 ... Evan do you think you'll be able to do your publication today? 17:37:05 eprodrom: I think so. There may be some trickiness with the fact we've moved to a different ED location. I'm not sure if the echidna token stays valid... 17:37:10 aaronpk: I'm pretty sure they do 17:37:21 eprodrom: If that works then I should probably be able to do it after the call 17:37:33 sandro: I will circulate a doodle poll once I have a little more data from folks 17:37:49 TOPIC: jf2, fpwd 17:38:15 ben_thatmustbeme: I ran out of the meeting early last time and we resolved to get there. I don't know where to go next. I need to work out with sandro to get a token to publish 17:38:20 Arnaud: It doesn't work for the fpwd 17:38:23 ben_thatmustbeme: So then I don't know 17:38:50 sandro: we've already got the approval from wendy for that so it's the talking with the webmaster 17:38:59 ... I guess send me an email with the pointers to what you've got and I'll try to help you from there 17:39:12 ben_thatmustbeme: ok 17:39:30 TOPIC: post type discovery 17:39:39 Arnaud: tantek is not here, so we skip for this week? 17:39:57 eprodrom: he presented a new version at the f2f but I'm not sure if there have been any new devleopments on it since then 17:40:13 FPWD was approved 17:40:28 Arnaud: I see there are open issues so this is work in progress obviously 17:40:43 sandro: the main thing is this was approved for fpwd by the group and wendy, so we are ready to publish once he turns the crank, same as ben 17:40:58 Arnaud: unelss anybody else has anything to add I think we can leave it at this for this week? 17:41:02 TOPIC: Webmention 17:41:29 aaronpk: We have received a couple of implementation reports, one from ben and one from GNU Social 17:41:31 https://github.com/aaronpk/webmention/blob/master/implementation-reports/gnusocial.md 17:41:33 ... That's pretty exciting 17:41:50 ... Three including mine. HOpefully we'll get more coming in 17:42:12 ... I have been working on the issues and published a new ED with a lot of the issues addressed. Still a couple of open ones 17:42:27 http://webmention.net/draft/ 17:42:28 ... One in particular I would like to get some help on, but I can chat offline about that, it's a minor thing 17:42:32 ... So new ED yesterday 17:42:37 ... Not ready to publish a WD of that yet 17:42:51 q+ 17:43:05 ack eprodrom 17:43:13 i had wanted to show off mf2 -> as2 conversion for SOME things, but my hosting provider is having issues, so i'll hold off on that 17:43:20 eprodrom: I have a question for aaronpk 17:43:41 ... I looked through exit criteria for webmention. Report for GNU Social has a couple of unchecked boxes, I assume that's going to be the case for all implementations 17:43:58 ... What happens if we have 3 implementations or 5 implementations, and none of them pass discovery test 17 for example 17:44:14 aaronpk: my understanding is that each part needs to be implemented by at least 2, but no implementation has to implement everything 17:44:29 ... If there is something that nobody has implemented we take it out of the spec because it had no purpose. But correct me if I'm wrong 17:44:31 sandro: that sounds right 17:44:50 Arnaud: The exit criteria is every feature has to be implemented by two implementations at least 17:45:06 ... If one part is not implemented, one way to deal with it is to prompt implementors to implement it 17:45:28 ... Then you can declare victory and move forards. Downside is you're focring peopel to implement something they don't care about 17:45:34 ... Other thing to do would take a resolution from the wg, to publish a new CR without that feature 17:45:40 Yeah -- nudging people to implement something just for the spec is a BAD IDEA. (and I confess I've done it several times. With lots of regret.) 17:45:42 ... Still delayed because of process 17:45:53 ... Just a matter of a few weeks 17:46:10 aaronpk: is this non-normative things, or only normative? 17:46:17 Arnaud: non-normative is editorial, we can change anything we want 17:46:24 ... Between CR and PR you can change anything that's not normative 17:46:33 ... Only talking about what impacts compliance 17:46:38 sandro: I'm a little fuzzy about the SHOULDs 17:47:00 Arnaud: Do you think that we can .. I don't think we can freely change places where the spec says you SHOULD do this.. we can't just take those out or add those 17:47:09 s/Arnaud/sandro 17:47:13 Arnaud: I think technically you can 17:47:22 sandro: I think it would invalidate reivews. I wouldn't want to do that withotu careful thought 17:47:33 Arnaud: I agree with that, just because you can doesn't mean you should. Probably wise not to do that casually 17:47:38 q+ 17:47:45 ack eprodrom 17:48:52 eprodrom: the only thing that I'm getting out of.. looking at the gnu social implementation.. seems like they skipped some of the security and verification suggestions, which I think are that's up to you if you choose not to implement the security ocnsiderations, but if we see a pattern there where we see no-one implements the chekc of not accepting webmentions that are in an html comment, I wonder if that informs any decision making we do later on. Do we 17:48:52 change it in the spec? 17:49:25 ... We're suggesting some verification, validation and security parts of the implementation. We have at least one case where somoene has skipped a lot. If we see people skipping a lot is that cause for concern for us? 17:49:40 q+ to ask about test 13 & 17 17:49:43 Arnaud: You could write up an issue to say you think we got it wrong about security and we need to change the spec to make it reuqired 17:49:58 ... Then we'd need a new CR and new implementation reports 17:50:21 aaronpk, i don't actually see in the spec reference to ignoring links in HTML comments actually 17:50:52 eprodrom: I'm going to keep an eye open. i think that in writing most of our specs we are saying it's okay to do x because you will also do y. It's okay to include this link in your page because you're also going to be verifying the link was in this webmention. It's okay to include unverified properties in your AS2 because you're going to be checking this and this. But if you don't do the checks, i makes those other parts more dangerous 17:50:53 q- 17:51:00 ... I'll keep an eye on this. I'll raise it if it seems to be a pattern 17:51:07 ... Aaron, for your implementation did you do these security considerations? 17:51:17 aaronpk: My implementation passes all of the webmention.rocks test 17:51:37 ... In security I think mine.. I don't moderate, I displya them immediately. I don't reverify. I don't have a byte limit, but I do have a time limit 17:52:13 i had wanted to show off mf2 -> as2 conversion for SOME things, but my hosting provider is having issues, so i'll hold off on that 17:52:16 +q 17:52:22 Arnaud: We have 8 minutes left, anything else? 17:52:24 ack cwebber 17:52:31 cwebber2: I thought I'd give an update on activitypub stuff 17:52:59 ... One thing is that jessica and I have done some large refactoring of the document that's making things structurally better to reduce effort when we split into two documents 17:53:02 ben_thatmustbeme, i don't think it needs to explicitly say ignore links in comments since it says to explicitly look for and