16:57:47 RRSAgent has joined #social 16:57:47 logging to http://www.w3.org/2015/06/16-social-irc 16:57:49 RRSAgent, make logs public 16:57:49 Zakim has joined #social 16:57:51 Zakim, this will be SOCL 16:57:51 ok, trackbot; I see T&S_SOCWG()1:00PM scheduled to start in 3 minutes 16:57:52 Meeting: Social Web Working Group Teleconference 16:57:52 Date: 16 June 2015 16:58:51 we don't parse lang explicitly in mf2 parsing at the moment 16:59:17 cwebber2 has joined #social 16:59:27 hello everyon 16:59:29 http://climbtothestars.org/ is a good example of a bilingual blog marked up with lang 16:59:30 everyone 17:00:26 zakim, this is socl 17:00:26 ok, Arnaud; that matches T&S_SOCWG()1:00PM 17:00:35 zakim, who's on the phone? 17:00:35 On the phone I see Sandro, Arnaud, aaronpk, Ann 17:00:56 + +1.773.614.aaaa 17:01:02 +??P5 17:01:11 hi 17:01:11 + +1.401.305.aabb 17:01:14 Zakim, aabb is me 17:01:14 +ben_thatmustbeme; got it 17:01:19 Zakim, mute me 17:01:19 ben_thatmustbeme should now be muted 17:01:20 Zakim, aaaa is me 17:01:21 +cwebber2; got it 17:01:27 hopefully my connection holds up 17:01:32 connectivity around here is... spotty :) 17:01:55 are you some place exotic? 17:01:56 same here cwebber2, but its more of an issue of my cell phone has been behaving really oddly lately 17:02:32 btw tsyesika is not on this call 17:02:34 she is camping 17:02:55 zakim, who's on the phone? 17:02:55 On the phone I see Sandro, Arnaud, aaronpk, Ann, cwebber2, rhiaro (muted), ben_thatmustbeme (muted) 17:03:01 small group 17:03:22 hhalpin has joined #social 17:03:26 I can if nobody else wants to :) 17:03:30 I can't scribe this time anyway 17:03:34 spotty connection 17:03:46 Zakim, code? 17:03:46 the conference code is 7625 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), hhalpin 17:03:51 I'll scribe, no problem 17:04:14 scribenick: rhiaro 17:04:26 + +1.857.445.aacc 17:04:40 Topic: Approval of last week's minutes June 9th 17:04:45 PROPOSED: Approval of Minutes of 9 June 2015 https://www.w3.org/wiki/Socialwg/2015-06-09-minutes 17:04:51 +1 17:04:55 +1 17:04:58 Arnaud: any objections? +1s please 17:05:01 RESOLVED: Approval of Minutes of 9 June 2015 https://www.w3.org/wiki/Socialwg/2015-06-09-minutes 17:05:04 ... Hearing no objections, they are approved 17:05:14 Topic: Tracking of actions and issues 17:05:21 Arnaud: Any actions anyone wants to declare victory for? 17:05:28 ... There are a bunch of open actions, would be nice to see some closed 17:05:35 ... Anyone? 17:05:40 http://www.w3.org/Social/track/actions/open 17:05:56 ... Some of them have been here for a while 17:06:11 Everyone should just look at them and then announce 17:06:14 if they have done some 17:06:19 ... We'll move on 17:06:25 Topic: Social API 17:06:25 topic: Social API 17:06:43 Zakim, who's on the phone? 17:06:43 On the phone I see Sandro, Arnaud, aaronpk, Ann, cwebber2, rhiaro (muted), ben_thatmustbeme (muted), +1.857.445.aacc 17:06:51 ... When we had the f2f we decided it would make sense to converge the proposals and start to draft a document 17:07:03 ... Starting with a strawman, then fill in the blanks 17:07:11 ... Look at the different proposals, have some alternatives and see which we prefer 17:07:19 ... There are several people who volunteered to be editors 17:07:25 ... Aaron, Amy and Jessica 17:07:37 I think Tysekia also volunteered to help 17:07:44 ... So, update? Is there progress? 17:07:49 q+ 17:07:50 zakim, who's on the phone? 17:07:51 On the phone I see Sandro, Arnaud, aaronpk, Ann, cwebber2, rhiaro (muted), ben_thatmustbeme (muted), +1.857.445.aacc 17:07:57 ack: aaronpk 17:07:57 In particular, any unresolvalbe differences? 17:08:02 ... This is an opportunity for everyone to get on the same page 17:08:08 aaronpk: We've been making slow progress 17:08:10 +bblfish 17:08:16 ... What I'm trying to do is base it on actual implementation experience 17:08:22 ... Been slow because I have a backlog of things to do 17:08:31 ... However there's now an updated version of the brainstorming document 17:08:37 https://github.com/w3c-social/Social-APIs-Brainstorming#micropub 17:08:37 ... Updated micropub section 17:08:54 ... I implemented this for creating, editing and deleting posts 17:09:00 big thanks to rhiaro, aaronpk, tsyesika! 17:09:06 ... Plan is to use that as my new micropub endpoint on my own site, had a good experience following this spec 17:09:13 ... There are two ways to do each post, one form encoded, one json 17:09:22 ... If you take a look at that, you see examples of both versions 17:09:42 ... Still more to do to demonstrate this in a useful format, because all it's doing right now is modifying my storage files, not generating output anyone else can see yet 17:09:50 ... This syntax is based on the idea of edit-posts 17:10:05 http://indiewebcamp.com/edit 17:10:07 ... The idea that an operation like an edit can be represented with its own URL and the chnages can be described at that URL using microformats 17:10:14 ... More background on that wiki page ^ 17:10:29 i can scribe for amy 17:10:31 scribenick: aaronpk 17:10:44 https://github.com/w3c-social/activitypump/blob/master/implementation.md 17:10:52 started going through the activitypump spec and rewrote it in a checklist form ^ 17:11:18 understand how to implement activitypump and how it maps to micropub and the others, micropub is basically a subset of AP, as well as webmention is 17:11:45 next steps are going through micropub and seeing what's missing that can be achieved with activitypump and see how they can fit toghether that way 17:11:50 that might be the basis for this document we were talking about 17:12:09 haven't gotten much feedback from jessica on that document yet, would like to hear from her soon 17:12:34 + +1.314.777.aadd 17:12:49 Zakim, aadd is AdamB 17:12:49 +AdamB; got it 17:12:53 are we agreed on implementing inboxes and outboxes? SoLiD doesnt do that yet, but we've discussed it ... 17:12:56 Arnaud: right now we have different documents describing the two approaches, but still need to get started on pulling them togetehr into *the* spec 17:13:10 is someone going to do the comparable work with linked data perspective? 17:13:20 +q 17:13:44 AnnB asked the question she typed in IRC 17:13:56 bblfish: haven't looked at this yet but had some questions and will send them on the list 17:14:07 ... i think melvin might have been following closer 17:14:21 ... or Andreas 17:14:31 ack aaronpk 17:14:40 Arnaud: you will need to figure out who there will step up to do that 17:14:42 ack cwebber 17:14:56 scribenick: rhiaro 17:15:21 cwebber2: The convergence doc is affecting how both micropub and activitypump documents are developing 17:15:34 ... From seeing forechannel and backchannel discussions between Jessica, Aaron and Amy 17:15:41 dog: bark, bark 17:15:45 ... I'd like to see strawman document, but it does seem to be affecting real things 17:15:46 :-) 17:15:47 Zakim, noise? 17:15:47 I don't understand your question, hhalpin. 17:15:55 sorry I couldnt's mute my phone 17:16:06 Arnaud: How long is it going to take before we can try to have this document? 17:16:08 sorry about the barks 17:16:15 ... Investigate further what's possible, what's missing etc 17:16:20 ... Sounds like people are busy with prep work 17:16:28 q+ 17:16:34 scribenick: aaronpk 17:16:35 ack rhiaro 17:16:44 From W3C's perspective, we'd want a FPWD by TPAC at latest - we're quite behind schedule :) 17:16:56 rhiaro: we could start putting something together this week, would be a starting point 17:17:01 Whenever the editors are comfortable, quite happy to do a Respec.js training and set them up in CVS etc. 17:17:09 hhalpin, are you going to dial in? 17:17:15 Arnaud: i understand the challenge of doing this but it was harry's suggestion that we try and mgiht just be a strawman 17:17:22 ...but that would give us a sense of what needs to be specified 17:17:22 q+ 17:17:37 ack hhalpin 17:18:11 hhalpin: i agree with amy that we don't want to create yet a third or 4th document that is a fork of the practical work being done 17:18:28 .. my proposal would be whenever folks are comfortable to converge at least two of the docs, we can do the first editor's draft 17:18:42 .. i would jhust say whenever you guys are ready ping the WG and we can start the editor's document 17:19:37 (discussion about github vs csv editing flow) 17:19:50 s/csv/cvs 17:20:02 Arnaud: this is a new tool that makes publishing in TR space as easy as it can possibly be 17:20:16 See here for links: 17:20:16 https://github.com/w3c/echidna/wiki/How-to-use-Echidna-with-ReSpec-and-GitHub 17:20:17 .. which is a lot lot better than the old process 17:20:18 Much *easier*! 17:20:37 q+ 17:20:39 Here's the other link: 17:20:40 https://github.com/w3c/echidna/wiki/How-to-use-Echidna 17:20:42 ack sandro 17:20:59 sandro: is aaron's new json document enough to implement this? 17:21:16 q+ 17:21:43 rhiaro: the brainstorming doc is a comparison of activitypump and micropub, both are implementaable. both do things that the otiher doesn't do, and use slightly different vocabularies 17:21:53 ack aaronpk 17:21:55 sandro: both of you said you're implementing before you write more down 17:22:07 scribenick: rhiaro 17:22:19 aaronpk: the document there right now is part of the picture, the micropub syntax for creating things 17:22:36 ... you can implement it, but it doesn't have the other half of it which is rendering html, what you do with it when you get the commands 17:22:43 ... because that's where I am in my implementation process 17:22:49 ... I've been writing the document, then writing the code, and going back and forth 17:22:56 ... So it'll keep progressing that way for a while 17:22:58 + +1.408.335.aaee 17:23:15 ... Part of the goal of the brainstorming document is pulling in the things from activitypump that I'm going to need to do that aren't in micropub yet 17:23:24 ... that's where the convergence is happening 17:23:34 ... I find it more useful to have code alongside it to justify things in the spec 17:23:34 ack AnnB 17:23:37 zakim, aaee is me 17:23:37 +KevinMarks; got it 17:24:18 AnnB: Sounds great. Amy proposed to write a strawman document, although harry said we don't need another document. It sounds like what you're working on now are technical explorations, and maybe it is valuable to have a comprehnsive draft of what the ultimate document might be like 17:24:23 Ann, to be precise I said there was no need to rush it, but I'm happy to set-up an editor's draft when Amy, Aaron, and Tysika are ready 17:24:27 Arnaud: I second this, I thought that was the plan 17:24:44 ... Current documents are useful in documenting the status quo, but not necessarily what we need in the end 17:24:55 ... So you could keep working on that and slowly morph it into the spec that we want to produce 17:25:09 ... Might be easier to start a fresh document that is meant to be the final spec, and have the outline and fill in the blanks 17:25:18 ... It's a matter of editorial method 17:25:27 q+ 17:25:33 ... Happy for editors to figure out what works best 17:25:35 ack bblfish 17:25:38 I agree .. it's up to the editors, which way works for you guys 17:25:59 q+ 17:26:18 bblfish: As I understand, it's going very deeply into how you can tie activitypump and micropub together. Before you go to deep it would be helpful to try to do the opposite with activitypump and linked data. Start with major alignments and see if the pieces fit together 17:26:25 ... How would one do that 17:26:29 ack AnnB 17:26:36 AnnB: We're waiting for someone from the linked data side to do that work 17:26:44 Arnaud: go ahead! 17:27:11 ... Someone needs to step up, they are willing to accommodate this, but they can't invent the information. Someone from SoLiD needs to step up and provide this 17:27:20 bblfish: In order to do this one needs to work at the big pieces first, see how they align 17:27:21 It's also fine to go linearly - i.e. see how activitypump and micropub goes together, and then align that result with SoLID 17:27:26 whatever works for folks 17:27:37 ... That you can do by writing up the different pieces that exist and trying to tie one to the other 17:27:39 great, bblfish ... do it! 17:27:44 bblfish, that's what the brainstorming doc is doing already 17:27:47 ... Then you can have a discussion 17:27:53 but it needs help from solid 17:28:14 ... Wanted to check that everybody agreed this is the right proces 17:28:33 AnnB: it seems like you or melvster or any of the other SoLiD people just need to start doing something 17:29:21 Arnaud: what we're trying to tell you is there is no disagreement with this approach, there's a lack of putting things in writing from the linked data side 17:29:37 bblfish - please do make a PR to the brainstorming doc to fill in the same things fro SoLiD! 17:29:40 Well, I think Andrei is updating the SoLID docs 17:29:45 Q+ 17:30:17 ack rhiaro 17:31:05 rhiaro: that document is what we've been doing, comparing activitypump and micropub, we'd love to get SoLiD in there as well. just make a pull request, we'd be happy to see that 17:31:15 https://github.com/w3c-social/Social-APIs-Brainstorming 17:31:18 bblfish: which document? 17:31:28 bblfish: its in the agenda too i believe 17:31:57 thanks 17:32:33 scribenick: rhiaro 17:32:43 sandro: I'd like to encourage LDP people to try the implementation first approach 17:32:57 sandro++ 17:33:00 sandro has 14 karma 17:33:03 bblfish: in LDP we had the implementations a year before the WG 17:33:18 Arnaud: you can do both approaches at the same time 17:33:27 ... aaron is trying to document and implement and going back and forth, you could do something similar 17:33:42 ... What sandro is saying is we don't want just vapourware, we want to ground the work in real implementations 17:34:07 sandro: the SoLiD code works, there are a bunch of servers and a bunch of clients, we could try to get them to speak some elements fo activitypump and micropub and see what changes that requires (just thinking aloud) 17:34:16 Arnaud: hopefully people have a better understanding of where we stand 17:34:19 yes 17:34:20 ... Is ben_thatmustbeme on the call? 17:34:24 very tired 17:34:46 Topic: AS2 language support 17:35:00 ben_thatmustbeme: Jessica would also have a lot to say and isn't here 17:35:13 ... Basically I've been going through AS2 and fixing microformats examples to match real world implementation 17:35:29 ... Highlighting parts where I question whether they're needed or if microformats needs to add features 17:35:34 ... One that did come up was multi-language support 17:35:39 +q 17:35:44 ... in AS2 you can add multiple translated versions of the same post 17:35:46 (contentMap) 17:36:00 ... I want to float the idea of saying that it doesn't match any user story, no discusison anywhere of multiple languages 17:36:07 +1 multiple languages 17:36:09 ... And discuss possibly removeing that 17:36:13 q+ 17:36:17 FYI: (not just *post*, any text) 17:36:18 ... But without james and without jessica I don't know how far we can get 17:36:19 ack cwebber 17:36:32 cwebber2: I have a suggestion that might make things easier 17:36:33 Note that W3C does have staff that can help with this 17:36:44 if we need some advise, i.e. Richard Ishida 17:36:44 ... The handling things in multiple langues is already handles in json-ld 17:36:57 ... It might simplify things if we don't mention it in the AS2 spec, but don't exclude it either 17:37:01 ... It's still possible via json-ld 17:37:13 ... But we don't actually specify it in the spec, so we can kind of explore it more in the future 17:37:30 ... But it doesn't necessarily set up a barrier when we don't know how hard it's going to be 17:37:40 ... I do agree that we don't need to conclude anything while jessica isn't here 17:37:45 ack hhalpin 17:37:46 language is also included in microformats implicitly as html has the lang attributr 17:37:50 I also assume elf would have something to say 17:37:56 -cwebber2 17:37:59 harry: w3c actually has i18n staff who can give us advice 17:38:08 though currently not part of the mf2 parsing spec 17:38:09 sorry, spotty connection as I said 17:38:17 ... Sounds like we can lean on json-ld, but if we need it, the w3c has people whose full time job thi sis 17:38:19 I'll ust have to participate via text for now 17:38:30 q+ 17:38:37 ... I agree that multiple language support is a good thing for specs in general 17:38:50 ack sandro 17:38:52 http://www.w3.org/International/ 17:38:54 Arnaud: from the i18n working group, we should have this 17:39:05 If we have any questions, W3C has specialist staff can help 17:39:11 sandro: json-ld inherits from rdf a halfway decent notion of multi language stuff 17:39:29 ... but it doesn't have really clarified is 'is a given value available in multiple languages' 17:39:54 ... eg. does a particular city have a name in english and a name in french and a name in russian.. does that count as multiple values, or one value with multiple tags 17:40:03 ... json-ld isn't going to solve that for us 17:40:13 ... we need to solve or worry about it later 17:40:19 ... the i18n activity doesn't know anything about this either 17:40:33 ... they're happy to work through use cases like ltr vs rtl script and we'll have to get them to review that 17:40:39 ack ben_thatmustbeme 17:40:40 ... but they don't know anything specific about these technologies that would be helpful 17:41:09 ben_thatmustbeme: Just want to be clear that I understand setting a language and saying this text is english, this is an entire post drafted in english then draft the same post in another language 17:41:13 ... and have that be the same object 17:41:24 sandro: then it gets weird because your objects model gets confused about how many posts that is 17:41:32 rel="alternate" hreflang="fr" etc works for whole posts 17:41:40 -Ann 17:41:47 aaargh 17:41:55 it's mixed language within a post that is trickier 17:42:07 brb 17:42:16 Arnaud: We should have the possibility of making posts in different languages, but not necessarily handle this case of multiple versions of the post in multiple languages 17:42:23 ben_thatmustbeme: yes 17:42:29 q+ for html lang and hreflang 17:42:39 ... On facebook/G+ this isn't a feature. I have friends who will include two languages in one post 17:42:45 back 17:42:58 +Ann 17:43:19 Arnaud: how is ti marked up? 17:43:24 ben_thatmustbeme: it's not 17:43:44 sandro: some languages you can't tell what it is by looking at it, but a screenreader would need to know the language to know how to pronounce things 17:43:56 ben_thatmustbeme: as soon as you mix languages, this is always going to be ap roblem 17:44:00 ... unless you markup every sentence 17:44:05 sandro: html has 20 years of support for that 17:44:14 ack KevinMarks 17:44:14 KevinMarks, you wanted to discuss html lang and hreflang 17:44:37 KevinMarks: That's what I was going to say. THe microformats response is the lang= on individual elements 17:44:41 ... This is existing practce 17:45:09 ... The challenge is, you can do mixed languages within a document and I've seen people do that. What we haven't seen so far in microformats is parsing that out and putting it into the parsed json format 17:45:29 ... Possibly because we haven't seen much use yet 17:45:40 ... Another thing is a Google-imposed cultural bias that assumes people only want one language at once 17:45:47 ... They have documented this, they don't recognise multilingual text 17:45:57 ... We have ways to express this in html. We should find examples. 17:46:08 ... What I haven't seen in html or json-ld is a way of saying here's a phrase that translates multiple ways 17:46:11 ... We did have that in OpenSocial 17:46:34 ... We had ways of expressing activitystreams stuff with different language markup, but made the same assumption that you're reading in multiple languages 17:46:40 sandro: I just wonder if this is in scope 17:46:47 Its worth thinking about IMHO 17:46:50 q+ 17:46:54 ... It's obviously a real world problem, but we're still well behind silos, not sure it makes sense for us to try to get ahead of them on this one 17:47:00 ack AnnB 17:47:24 AnnB: I agree with sandro in terms of priority, but it seems like a really important thing especially since we're doing social 17:48:01 I just don't want to lose it 17:48:04 as a concept 17:48:05 Arnaud: don't see anyone else on the queue, we can continue this discussion. Seems like general agreement we should go light on this, may be too early for us to try to tackle this problem 17:48:21 ... That's the end of the agenda. Anything else? 17:48:33 sandro: WebEx. THis is the last week with Zakim 17:48:38 FYI: jessica was strongly in favour of keeping multi lang 17:48:47 ... There will be a phonenumber, or webex software 17:48:52 In an plus, SIP should work better! 17:48:54 ... We'll send an email with the details 17:48:59 yay for Jessica! 17:49:02 ... We'll also do a practice next Monday, 24 hours ahead 17:49:11 ... And try joining 15 minutes early next week 17:49:15 I definitely don't want to lose the multi lang concept 17:49:27 ... IRC will be used the same, webex is just for audio 17:49:36 Arnaud: I've done it with other groups, the biggest loss is the tracking of attendance 17:49:43 ... We'll have to have people tell Zakim that they're present on the call 17:49:49 ... So the minutes reflect the people attending 17:49:53 why webex and not WebRTC? 17:50:11 too early, I think, KevinMarks 17:50:27 I believe they're looking for WebRTC solution on longer term 17:50:40 https://talky.io/ is pretty good 17:50:54 right, it's great .. but only handles ~5 people 17:50:59 KevinMarks: can't call in to talky.io can you? 17:51:06 talky.io isn't good for large groups, beta.talky.io is better at that. also no phone bridge for talky 17:51:14 Arnaud: talks about ways webex might go wrong, peopel should call in early 17:52:01 sandro: I've been using android version, I guess there's an iOS version, that might work well 17:52:24 Arnaud: if you use the client you join the meeting officially 17:52:28 connecting via browser did not work for me with Firefox, but did work with IE 17:52:31 I use google voice to phone into the phone bridge here 17:52:36 ... client offers 3 ways to connect audio 17:52:40 might be some issue with my Boeing-configured FF 17:52:42 dunno 17:52:56 ... Let us know if you have any questions about webex 17:52:57 sandro: is there a link on how to clal in via SIP or phone somewhere, or will there be? 17:52:57 - +1.857.445.aacc 17:53:07 goodbye Zakim! *tear* 17:53:09 good bye Zakim 17:53:10 -aaronpk 17:53:11 ... Thanks for joining, talk to you next week! 17:53:13 -Sandro 17:53:15 bye bye Zakim :( 17:53:17 Aww, bye Zakim 17:53:18 trackbot, end meeting 17:53:18 Zakim, list attendees 17:53:18 As of this point the attendees have been Sandro, Arnaud, aaronpk, Ann, +1.773.614.aaaa, rhiaro, +1.401.305.aabb, ben_thatmustbeme, cwebber2, +1.857.445.aacc, bblfish, 17:53:18 aww, cheer up 17:53:21 ... +1.314.777.aadd, AdamB, +1.408.335.aaee, KevinMarks 17:53:23 aww 17:53:25 -bblfish 17:53:26 RRSAgent, please draft minutes 17:53:26 I have made the request to generate http://www.w3.org/2015/06/16-social-minutes.html trackbot 17:53:27 RRSAgent, bye 17:53:27 I see no action items 17:53:29 -rhiaro 17:53:29 waaaa ... Zakim ..