16:59:42 RRSAgent has joined #social 16:59:42 logging to http://www.w3.org/2014/10/21-social-irc 16:59:42 I put a strawman schedule 16:59:44 RRSAgent, make logs public 16:59:44 Zakim has joined #social 16:59:46 Zakim, this will be SOCL 16:59:46 ok, trackbot; I see T&S_SOCWG()1:00PM scheduled to start in 1 minute 16:59:47 Meeting: Social Web Working Group Teleconference 16:59:47 Date: 21 October 2014 16:59:56 chair: evanpro 17:00:05 Oh, I'm just slightly early for a change :) 17:00:11 Yes 17:00:13 so, we need to merge the two :) 17:00:22 Zakim, who's on the call? 17:00:22 T&S_SOCWG()1:00PM has not yet started, evanpro 17:00:23 On IRC I see RRSAgent, jasnell, oshepherd, elf-pavlik, evanpro, Tsyesika, jtauber, Loqi, tantek, AdamB, cmhobbs, Arnaud, shepazu, KevinMarks, cwebber2, rhiaro, wilkie, bret, 17:00:23 ... tommorris, kylewm, mattl, aaronpk, trackbot, botie, sandro, wseltzer 17:00:32 Hmmm 17:00:33 OK 17:00:43 I think I'm in 17:01:00 Zakim, what's the code? 17:01:00 the conference code is 7625 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), jtauber 17:01:14 No hello/goodbye notifications? 17:01:29 Apologies for absence: been feeling sub-par as a result of continuing medical treatment. 17:01:33 Arnaud: that's such a better structure 17:01:43 Let me see if I can copy that over 17:02:11 Probably not quickly 17:02:13 zakim, this is socl 17:02:13 ok, Arnaud; that matches T&S_SOCWG()1:00PM 17:02:26 zakim, who's on the phone? 17:02:27 On the phone I see +1.514.554.aaaa, jasnell, ??P5, Arnaud, ??P7, [IPcaller], AdamB 17:02:34 Zakim, aaaa is me 17:02:34 +evanpro; got it 17:02:37 +??P10 17:02:46 Zakim, [IPcaller] is me 17:02:46 +jtauber; got it 17:02:49 Zakim, ??P10 is me 17:02:49 +bret; got it 17:02:58 (I think) 17:03:05 fyi... laptop battery likely not going to last the full hour.. may end up dropping off irc at some point... we will see tho 17:03:06 -??P7 17:03:17 wow.. that's super irritating 17:03:20 +??P7 17:03:23 Zakim: , ??P5 is me 17:03:26 oops 17:03:26 Whoever is leaning on their phone, PLEASE STOP 17:03:29 Zakim, ??P5 is me 17:03:29 +cwebber2; got it 17:03:38 +[IPcaller] 17:03:39 Zakim, who's on the call? 17:03:40 On the phone I see evanpro, jasnell, cwebber2, Arnaud, jtauber, AdamB, bret, oshepherd, [IPcaller] 17:03:41 MarkCrawford has joined #social 17:03:43 Zakim, IPcaller is me 17:03:43 +wilkie; got it 17:03:49 honk honk 17:03:50 Zakim, mute me 17:03:50 bret should now be muted 17:04:11 + +1.703.670.aabb 17:04:33 -oshepherd 17:04:46 https://www.w3.org/wiki/Socialwg/2014-10-21#Agenda 17:05:08 Zakim, +1.703.670.0920 is me 17:05:08 sorry, MarkCrawford, I do not recognize a party named '+1.703.670.0920' 17:05:14 Zakim, who's on the call? 17:05:14 On the phone I see evanpro, jasnell, cwebber2, Arnaud, jtauber, AdamB, bret (muted), wilkie, +1.703.670.aabb 17:05:34 AdamB, would you mind scribing? 17:05:37 zakim, +1.703.670.aabb is me 17:05:37 +MarkCrawford; got it 17:05:40 +??P7 17:05:44 scribe: AdamB 17:05:56 +Lloyd_Fassett 17:06:06 evan: first item approving last weeks minutes 17:06:16 http://www.w3.org/wiki/Socialwg/2014-10-14-minutes 17:06:37 ...pretty important resolutions in the minutes .... 17:06:41 harry has joined #social 17:06:47 ... any objections to approving? 17:06:59 .... minutes have been approved 17:07:14 Lloyd_Fassett has joined #social 17:07:42 RESOLVED: Approval of Minutes of 14 October 2014 17:08:02 evan: like to talk about upcoming face to face ... unfortunately have 2 diff schedules 17:08:17 ... will use Arnaud version 17:08:24 +q 17:08:28 +??P16 17:08:35 ack ??P5 17:08:35 .... first covering overall direction as a group, where we are going 17:08:38 Zakim, ??P16 is me 17:08:38 +tantek; got it 17:08:47 ... discussing AS 2.0 and moving that forward 17:09:06 ack Arnaud 17:09:07 .... new efforts coming up around Social API and Federation protocol ... F2F best time to discuss those 17:10:09 Arnaud: first would like to ask people ...schedule of tpac provides 11am to 5pm for adhoc group breakouts ... put together on F2F page for two possible options to choose from 17:10:32 agreed that f2f is a good time to discuss API and federation protocol work 17:10:51 ... ... as a working group we should decide our approach ... on that list is straw man to start discussion 17:11:21 + +1.408.335.aacc 17:11:51 ... think we should choose between these 2 options 17:12:08 q+ re: any news from OpenSocial? 17:12:37 ... could mix for example, could do option 1 on monday and option 2 on tuesday 17:12:45 I am also participating in the AC meeting as an AB member. So would prefer not to conflict with that. 17:12:57 evan: one way to max. productivity by taking first day to address 3 major goals of this group 17:13:22 ... if conversation goes well on monday will likely have tuesday then to do more break out sessions 17:13:44 evan: suggesting option 1 on monday and 2 on tuesday 17:13:52 Option 1 on Monday, and Option 2 on Tuesday works for me too 17:14:13 I would drop "WG Dinner" since usually that's a good time for cross-group pollination 17:14:23 Shane has joined #social 17:14:38 jkorho has joined #social 17:14:56 proposal of: option 1 on monday and tuesday do more break out sessions during the mid day break 17:15:00 q- 17:15:03 +1 17:15:05 +0 17:15:06 +0 17:15:09 +0 17:15:10 +0 17:15:16 +1 with including federation protocol on Monday, and no WG Dinners 17:15:30 +0 17:15:35 +1 17:15:41 I'm abstaining from all the TPAC votes since I won't be there ;) 17:15:45 +??P18 17:15:47 harry has joined #social 17:15:51 -??P18 17:15:55 Zakim, q? 17:15:55 I see no one on the speaker queue 17:16:16 WG dinner on Monday or Tuesday? 17:16:21 Zakim, what's the code? 17:16:21 the conference code is 7625 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), harry 17:16:27 +??P18 17:16:33 Tuesday is AC dinner 17:16:33 Zakim, ??P18 is me 17:16:33 +Shane; got it 17:16:36 Zakim, mute me 17:16:36 Shane should now be muted 17:16:40 Monday would work! 17:16:41 +??P19 17:16:45 -??P19 17:16:45 Hi all, sorry I'm late 17:16:50 +[IPcaller] 17:16:57 Zakim, IPcaller is hhalpin 17:16:57 +hhalpin; got it 17:17:03 Tuesday has AC dinner that Arnaud (and Tantek) will attend 17:17:33 can we have a quick poll of who where in IRC will be at TPAC and which days? 17:17:35 e.g. 17:17:39 MTWThF 17:17:43 evan: given this structure can we break up the day on monday in to 3 blocks 17:17:57 MTWThF 17:18:05 MTWThF 17:18:06 MTWThF 17:18:31 MTWTh 17:19:06 evan: are ok with leaving agenda for day 2 relatively open and putting that together at the end of day 1 17:19:09 Can we have some time for use case presentation from the SocialIG? 17:19:15 arnaud: seems to make sense 17:19:53 evan: some have been discussing proposals ... this is the optimal time to start making suggestions for presentations etc 17:20:14 ... asking that folks that are willing to do that to post to the email list and will fit in to those slots on afternoon of monday 17:20:25 Notes that Matt Marum isn't on the call - not sure who from OpenSocial is presenting their take on things 17:20:26 ... 5-10 minute presentations 17:20:30 I have a proposal I'll email in this week (but unfortunately can't attend TPAC) 17:20:40 oshepherd: that sounds great 17:20:43 can we skip email middleman and just edit wiki schedule directly to add ourselves? 17:20:47 Zakim, who's making noise? 17:20:52 tantek: yes, that's fine 17:21:02 harry, listening for 10 seconds I heard sound from the following: Arnaud (28%) 17:21:06 harry, anyone from OpenSocial in https://www.w3.org/2002/09/wbs/35125/TPAC2014/registrants#SW ? 17:21:09 q+ 17:21:19 ack MarkCrawford 17:21:24 arnaud: referencing marks question about giving some time to social IG use cases 17:21:36 TPAC attendance: All week 17:21:54 MarkCrawford: have narrowed down the use cases ... continuing to work them ... would like to share them to the WG 17:22:07 ... important for us in the IG to report back on where we stand at this point 17:22:23 evan: sounds great, make time on tuesday morning on that? 17:22:49 MarkCrawford: that should work, schedule around use case task force leader availability 17:23:02 evan: lets plan on tuesday barring any objections 17:23:05 +q 17:23:10 q- 17:23:13 ack Arnaud 17:23:35 I may be remote too 17:23:36 Arnaud: remote participation .. elf and shane remote is all right now? are there others planning to call in? 17:23:39 I might try and call in - haven't had time to look at timing yet 17:23:45 I've not checked the times yet for whether I can remote, I think there will be issues with timezones, but we shall we 17:23:46 *see 17:24:11 q+ re: who will participate on Wed in Schema.org and Social WG? https://www.w3.org/wiki/TPAC2014/SessionIdeas#Schema.org_and_Social_WG 17:24:15 Harry: all the rooms have polyphones ... can put a bridge booking request in now 17:24:30 q+ to also offer broadcasting AV with talky.io for remote particpants to listen/watch 17:24:57 ack tantek 17:24:57 tantek, you wanted to also offer broadcasting AV with talky.io for remote particpants to listen/watch 17:25:07 evan: sounding like a general framework and with the chairs can resovle the schedule 17:25:25 tantek: think its fine to just add directly to wiki 17:25:53 that'd be great 17:25:55 ... for remote participation I can setup a audio/video broadcast using Talkie RTC session 17:25:56 talky++ 17:25:59 talky has 3 karma 17:26:06 evan: will be able to show screen? 17:26:07 Yeah talky has show screen 17:26:27 tantek: it can pick from multiple inputs 17:26:31 +??P19 17:26:33 talky sounds great! 17:26:37 -??P19 17:26:38 ..including screen share 17:26:43 KevinMarks, I can't find your W3C account. 17:26:50 waht about the network issues ? 17:26:50 Do you have one? 17:26:50 A user-name? 17:26:56 slow network? 17:27:20 tantek: also setup an etherpad (sp?) especially if we start doing breakouts 17:27:31 ... can be hard to follow IRC 17:27:38 During indiewebcamps etherpads have been extremely useful 17:27:45 evan: sounds great, lets do both 17:27:54 ack elf-pavlik 17:27:54 elf-pavlik, you wanted to discuss who will participate on Wed in Schema.org and Social WG? https://www.w3.org/wiki/TPAC2014/SessionIdeas#Schema.org_and_Social_WG 17:27:57 ^ 17:28:23 tantek: this is all in addition to IRC 17:28:44 bblfish has joined #social 17:28:49 kmarks2 is apparently my username, but when I try to reset I get stuck 17:29:33 harry: in response to elf-pavlik question .... breakout session on wednesday to talk about Schema.org and Social WG 17:29:49 I'm happy to start a new account but it didn't like me trying that with an email it had seen (kevinmarks@gmail.com) 17:30:02 evan: I will be there 17:30:22 ... def some coordination needed there 17:30:36 evan: could you add yourself to that section in a wiki? 17:30:52 harry: its an open space 1hr session. good to be there from beginning but can drop in at any time 17:30:53 q+ to advocate asking for folks to join the SocialWG 17:31:05 https://www.w3.org/wiki/TPAC2014/SessionIdeas#Schema.org_and_Social_WG 17:31:17 arnaud: tpac registry is officially closed but can register on site 17:31:34 oh wow 17:31:49 Note we are running at capacity 17:31:49 guess for sure doing remote participation then now :) 17:31:54 harry: our social group space is completely booked 17:32:04 However, some folks who are "observers" won't show 17:32:19 Zakim, who is being noisy? 17:32:19 I don't understand your question, tantek. 17:32:24 Probably me! 17:32:24 Zakim, who's making noise? 17:32:37 harry, listening for 12 seconds I heard sound from the following: hhalpin (71%) 17:32:48 harry: space is booked because of observers ... members have priority over them 17:33:20 Also, speaking of WG members, I'm trying to double-check IEs - one of chairs, e-mail me the list of folks that need to be approved so I can double-check? 17:33:26 q? 17:33:33 ack tantek 17:33:33 tantek, you wanted to advocate asking for folks to join the SocialWG 17:34:06 For schema.org meeting, please add name to wiki here: 17:34:09 https://www.w3.org/wiki/TPAC2014/SessionIdeas#Schema.org_and_Social_WG 17:34:09 tantek: regarding about participation ...since we are full for monday and tuesday if you are attending as observer please join as member 17:34:31 Actually, I suspect Ralph Swick will be leading, but I proposed 17:34:45 ... for folks that do plan on wednesday session about schema and social wg .. for those attending from social wg strongly encourage them to join 17:35:08 q? 17:35:15 agenda? 17:35:32 evan: this wraps up tpac conversation 17:35:33 jasnell has joined #social 17:35:33 encourage them to join *the Social WG*, so that we don't have to do discussions in side-meetings. 17:35:39 ... next want to talk about AS 2.0 working draft 17:35:47 q+ 17:36:05 -oshepherd 17:36:07 OK, harry, will ack in a moment after jasnell 17:36:24 jasnell: first cut working draft are in and been working with harry fixing up details on html validation. hopefully those are resolved 17:36:25 +??P3 17:36:31 ... one question about the Actions draft 17:36:31 if you're not registered but plan to attend, please add your name to https://www.w3.org/wiki/Socialwg/2014-10-27#Participation 17:36:41 q+ re Reference issues inline in the spec. https://github.com/jasnell/w3c-socialwg-activitystreams/issues/29 17:36:41 Its kinda weird to hold on actions since the drafts are very interlinked. 17:36:55 ... way the docs are right now the first public working draft points to the editor draft 17:36:56 Zakim, who's making noise? 17:37:08 harry, listening for 11 seconds I heard sound from the following: evanpro (34%), jasnell (100%) 17:37:18 Sorry, other people in my office 17:37:20 I missed the question 17:37:22 has anything changed re: the questions asked last week about Actions? 17:37:23 due to noise 17:37:31 if no new information, let's not re-open the question 17:37:57 harry: still trying to aim for thursday pub date ... because all 3 drafts are linking to each other the linking validation fails 17:38:08 the AS and vocab drafts shouldn't need to link to Actions - this doesn't make sense 17:38:13 ... wouldn't be good to publish all 3 together would have re-write links 17:38:15 the question is whether we can publish Actions draft along with AS 2.0 Core and Vocab 17:38:21 I am logged in now, but boy that was hard 17:38:38 tantek, core has section on PotentialAction which uses terms from Actions Vocab 17:38:43 using pub process as an excuse to publish a previously unapproved draft is kind of bad form 17:38:56 so drop the crosslinks to Actions 17:38:59 ... in terms of just pure publication have them heavily linked and not on w3c space makes publishing little bit trickier 17:39:00 just comment them out 17:39:11 substantial reasons / questions - all in last week's minutes 17:39:23 no implementation experience with Actions 17:39:27 The problem is everything is densely interlinked so we have to do changes to drafts. 17:39:39 it was a bunch of political +1s with no pragmatic questions asked 17:39:42 just remove PotentialAction section? 17:39:45 jasnell: actions piece is still an open question ... def. interesting in working on but was missing clear use cases so objection was raised due to that 17:39:55 arnaud: minutes from last week show that clearly 17:39:56 Zakim, q? 17:39:56 I see harry, elf-pavlik on the speaker queue 17:40:20 s/remove/move to dedicated spec/ 17:40:21 ... there is interest in group but non documented yet 17:40:22 elf-pavlik meant to say: just move to dedicated spec PotentialAction section? 17:40:32 jasnell: base on that we don't have documented ones for AS either 17:40:50 implementations are not necessary until we get further along 17:41:06 why not just cut everything to do with Action from the first two drafts? 17:41:10 Sorry, W3C team publishing requires links to resolve 17:41:13 is such commenting out more than 5 min of work?!? 17:41:13 +1 tantek 17:41:18 jasnell: does look to be a public link issues from publishing perspective 17:41:18 and github.io doesn't do fragment id links 17:41:29 So, we can just remove links to Actions Drafts 17:41:34 that's fine with me, it may delay things a bit. 17:41:45 +1 on links having to resolve 17:41:45 ... could just publish with actions but that still doesn't commit the wg to do anything with it 17:41:47 ack harry 17:41:49 harry - why does a 5 minute commenting-out task delay things? 17:41:49 Or we can put a weird snapshot of the Editors Draft somewhere outside github.io 17:42:02 Shouldn't use cases be examples where there exists some kind of implementation, standardized or not? 17:42:11 we're spending more time talking about it than it would take to comment out the links 17:42:13 not just, ideas 17:42:27 harry: we hit a hitch in w3c because of the links not resolving .. in general want them to resolve properly 17:42:39 ... it might slow things down past thursday 17:42:52 evan: is it reasonable to kick out actions for the first version 17:42:59 q+ 17:43:08 jasnell: could do that .. basic actions has been in AS since the begining 17:43:14 That makes sense to me 17:43:17 ... could do that if that is what this group wants 17:43:29 +1 move actions to dedicated spec 17:43:37 as an editors draft, why can't we publish w/o the links to gain a broader audience for the work and get more feedback? 17:43:45 evan: from my view ... since some discussion and not competely essential to core would suggest trim them out now and address later on 17:43:50 q+ to discuss this as evidence of modularity failure 17:44:04 ack elf-pavlik 17:44:04 elf-pavlik, you wanted to discuss Reference issues inline in the spec. https://github.com/jasnell/w3c-socialwg-activitystreams/issues/29 17:44:10 ^ 17:44:32 i got impression last week that James agreed 17:44:40 Tsyesika has left #social 17:44:41 activitystrea.ms 17:44:50 it is a modularity failure because an AS2 implementation does not need to know anything about Actions 17:44:56 elf-pavlik: jasnell said that they would be included in the spec as yellow highlighted sections that link to the github issue I believe 17:44:56 therefore the spec shouldn't need to 17:45:03 harry: its not a modularity issue but a links not resolving ..other issue was AS namespace referenced within 17:45:03 Harry - does the resolving links requirement apply to all versions, or just final? 17:45:04 404 errors 17:45:10 which is just not acceptable 17:45:15 ... lot of links get 404 errors which is not acceptable 17:45:28 ... could monkey patch the links out 17:45:52 Proposal: comment out all the links to Actions (and relevant contextual text) from the two drafts. 17:45:55 jasnell: the AS namespace is personally owned by ??? is maintained by AS on github 17:46:09 s/???/Chris Messina 17:46:13 ... i have access to that domain. larger question is do we want to keep that domain / namespace or not? 17:46:13 Would it be better to move them to the w3 domain, perhaps wiki? 17:46:24 good question, shouldn't we switch to a w3c namespace? 17:46:24 q+ 17:46:27 ack harry 17:46:28 q+ 17:46:29 -Shane 17:46:37 https://w3id.org/ ? 17:46:45 +??P4 17:46:48 is the namespace issue a FPWD blocker? 17:46:48 Zakim, ??P4 is me 17:46:48 +Shane; got it 17:46:50 Zakim, mute me 17:46:50 Shane should now be muted 17:46:58 if it's not a FPWD blocker then we should postpone discussing 17:47:01 elf-pavlik: No, http://w3.org/ 17:47:07 let's get past FPWD please 17:47:08 it is currently kinda blocking FPWD 17:47:15 q? 17:47:18 evan: two big issues: 1. adding or removing actions 2. removing AS in the namespaces 17:47:20 ack tantek 17:47:20 tantek, you wanted to discuss this as evidence of modularity failure 17:47:29 i.e. I'd like to make some changes to the doc but want to make sure the WG is OK with it. 17:47:32 evanpro, can we come back to my question after you ack me? 17:47:37 acked 17:47:41 i.e. we can probably monkey-patch the Action links out 17:47:44 elf-pavlik: yes, please put yourself back on the queue 17:47:47 q+ re Reference issues inline in the spec. https://github.com/jasnell/w3c-socialwg-activitystreams/issues/29 17:47:48 Sorry about that 17:47:51 but we need to also resolve activitystrea.ms 17:48:08 tantek: given existing impl have not had to know anything about actions that the spec rec doesn't need to refer to it either. that is what i mean by modularity failure 17:48:19 ... its like a layering failure 17:48:21 -Lloyd_Fassett 17:48:28 +1 on modularising spec appropriately. If ActivityStreams is extensible, actions should be able to live on its' own 17:48:30 Tsyesika has joined #social 17:48:31 I think the activitystrea.ms should redirect to a page on w3.org, it is unlikely it will dissapear then 17:48:47 ... no reason core spec should have to mention it at all. so suggestion its completely commenting out from spec. 17:49:04 ack harry 17:49:07 .. lets pospone any first draft issues 17:49:14 Zakim +Lloyd_Fassett 17:49:16 any *non* first draft issues 17:49:20 harry: namespace is pretty close to a blocker 17:49:26 We can remove all links to activitystrea.ms 17:49:30 let's do that 17:49:34 remove all links that break 17:49:34 1) we could comment them out directly 17:49:47 2) we could replace them with w3.org names 17:49:47 harry: could remove them, comment them out but that is weird cause they are referenced 17:49:52 .. could replace with w3c ones 17:49:56 3) we could ask ChrisM to update real quick so they don't 404 17:50:01 I'm OK with any with those 17:50:02 ... or could update domain so they don't 404 17:50:02 If we go for (2), is it possible to make those names always redirect to latest draft? 17:50:08 jasnell: does have access so can do it 17:50:11 +Lloyd_Fassett 17:50:13 ... just need to have the time 17:50:27 evan: its more about the 404 than the namespace issue 17:50:44 harry: its kind of weird ... its been done but not common 17:50:52 Can we use http://www.w3.org/Social/WG ? 17:50:53 +q 17:50:54 I'm ok with external URLs / namespace 17:50:58 ... should at least dedicate real thought sometimebefore last call 17:51:01 simplest thing 17:51:04 Tsyesika has left #social 17:51:04 .. have to fix broken links now 17:51:06 s/activitystrea.ms/www.w3.org/Social/WG/ 17:51:07 evanpro meant to say: Can we use http://www.w3.org/Social/WG ? 17:51:09 comment out the broken links, "fix" in next draft 17:51:13 we gotta do something about broken links now, the external namespace issue we can deal with later 17:51:24 evan: james, can we setup way to fix broken links 17:51:27 The easiest thing is to just probably comment them out 17:51:39 solution: remove the links for now, open an issue on namespace to use 17:51:42 jasnell: can try to get it done before end of week but not positive i can get it done 17:51:47 I'd say if you can't fix the links in the next hour, then let's comment them out for FPWD 17:51:54 That's probably the best way, for FPWD 17:51:59 that buys us more time to make a considered decision rather than rushed 17:52:02 harry: i can comment them out for now and add them back in later? are people ok with this? 17:52:04 +1 on commenting out the links 17:52:13 evan: maybe comment out and open issues to add them back in 17:52:18 I'll put an clearly editors draft 17:52:22 harry: will do that and mark as editors draft 17:52:25 redirect Actions links to the Editors draft 17:52:28 q? 17:52:30 that should solve all our linking issues 17:52:37 why not just comment out Actions? 17:52:41 Yeah, we could also comment out Actions as well. 17:52:43 that's better for modularity anyway 17:52:48 which is why I'm pushing for that 17:52:59 harry: will just comment out all broken links 17:53:06 +1 move actions out of core 17:53:14 this also sets a good precedent for the group 17:53:21 We can probably still push things out by Thursday if Webmaster isn't too rushed and all this link commenting works 17:53:26 if your spec has broken links after we've agreed to publish it, then we will comment out the links 17:53:34 I think that's a reasonable policy to adopt 17:53:37 +1 17:53:47 it will strongly encourage editors to do a trivial linkcheck EARLY and OFTEN 17:53:51 just need to be fair but also realize W3C, being what it is, can't publish broken links :) 17:54:05 q? 17:54:06 harry - totally agree with not publishing broken links (404) 17:54:09 ack elf-pavlik 17:54:09 elf-pavlik, you wanted to discuss Reference issues inline in the spec. https://github.com/jasnell/w3c-socialwg-activitystreams/issues/29 17:54:12 [from last week minutes] elf-pavlik: jasnell said that they would be included in the spec as yellow highlighted sections that link to the github issue I believe 17:54:20 jasnell has joined #social 17:54:25 [from last week minutes] elf-pavlik: jasnell said that they would be included in the spec as yellow highlighted sections that link to the github issue I believe 17:54:26 evan: discussing elf question 17:54:45 ... not sure understand what the issue is yet elf 17:55:00 OK... I forgot that line item 17:55:07 Arnaud: it has to highlighting within the text with the issue 17:55:18 I can add those in today 17:55:28 jasnell, thx! 17:55:31 is this a fragmention use case? 17:55:35 That's a minor fix 17:55:36 tantek: believed would be called out inline within the document. we agreed to publish with that being the case 17:55:40 Yes 17:55:44 evan: jasnell can we get this in? 17:55:48 That's a quick one 17:55:50 jasnell: yes 17:55:52 I would say we do "inline issues" on next WD 17:55:56 q? 17:56:01 ack Arnaud 17:56:30 q+ 17:56:32 harry, how about -comments mailin list? 17:56:35 Arnaud: we should use what ever is the most efficient way to the document out. but should put in a tracker for what namespace should be used going forward 17:56:37 ack harry 17:56:44 Oy... Ok 17:56:48 harry - except that we agreed to publish *with* the issues inline. 17:56:50 harry: need those inline issues within the next hour to make it by thursday 17:56:53 jasnell - can you add those issues inline in next hour? 17:57:18 jasnell, please :) 17:58:04 The issue is that this requires yet another cycle from W3C to fix up, so I say send *exact* issues to mailing list 17:58:13 jasnell: i can try to get it in the next hour but very difficult. if there are higher priority ones send email and i can try to do them by most important 17:58:32 harry: webmaster needs 1 day to review it 17:58:35 issues: https://github.com/jasnell/w3c-socialwg-activitystreams/issues/29 17:58:44 ... thats how publications always worked 17:59:04 jasnell, just 4 main issues there 17:59:06 how hard does that make it for adding issues in the future? does webmaster always have to review those too ? 17:59:20 I'm ok with waiving this requirement for FPWD 17:59:51 elf - are you ok with postponing linking inline to issues until next draft? 17:59:53 Is the issue about Hydra actually an issue of the spec? I don't think it is, just perhaps something to discuss later possibly 17:59:59 I think we at least need to mention missing JSON-LD @context in examples, but other 3 would also make sense from my POV 18:00:01 yep 18:00:04 harry: inclined to suggest to link this in later 18:00:06 https://github.com/jasnell/w3c-socialwg-activitystreams/issues 18:00:15 https://github.com/jasnell/w3c-socialwg-activitystreams/issues/36 18:00:20 and does anyone else object to publishing FPWD without the inline issues? 18:00:21 I mean, we link to the identifers 18:00:24 there's 15 issues 18:00:25 all RDF related 18:00:27 and opened by elf 18:00:34 I'm not sure if this is really blocking 18:00:40 Arnaud: sounding like we go with out the links are we don't go .. not sure if elf would like to hold up the process for that or not 18:00:41 Those links aren't critical in my opinion. Not as a blocker. 18:00:54 There is a link to the issues list in the draft 18:01:00 can we at lest mention missing @context ? 18:01:01 Yes, we do link directly to the tracker 18:01:05 elf-pavlik: are you comfortable with going to FPWD without these links? 18:01:06 tantek: if there is only a single objection its the chair prerogative to declare rough consensus 18:01:09 I think we need to get it to FPWD 18:01:10 I'm inclined to say "no" 18:01:12 Otherwise, we won't get the doc out 18:01:30 ... if we are risking not getting it out i don't think its worth postponing for this right now 18:01:47 i will not block but would appreciate at least mention of missing JSON-LD @context in examples, and maybe one about _:post 18:02:04 OK, so that's already linked and examples have @context assumed called out 18:02:30 jasnell: yeah thats as simple as a link ... but if we have no place to host that officially but there is a link to that context in document already 18:02:31 elf-pavlik: that's already called out 18:02:53 evan: since it's called out maybe take an action to link directly but willing to go with what we have right now 18:02:53 with a link to context at that stage? 18:02:55 Sorry I have to rush away, thanks everyone. 18:02:59 -Shane 18:03:04 elf-pavlik: we'll have that, yes 18:03:06 harry: most working groups only call out substantial issues directly in the spec 18:03:25 anyways, i trust in your decision folks so just go ahead without including that request from me 18:03:29 For example, WebCrypto had 170+ bugs 18:03:33 we called like 5 out in text 18:03:36 inline 18:03:58 ok, end of this topic? 18:03:59 q? 18:03:59 agenda? 18:04:06 admin: we're also 4 min over 18:04:24 evan: would like to wrap up agenda items we have open and defer to next week at F2F, any objections? 18:04:31 no objection 18:04:31 ... ok would like to adjourn 18:04:32 -jtauber 18:04:36 +1 adjourn 18:04:40 -jasnell 18:04:43 nice meeting have fun next week 18:04:44 Regrets on not being there in person 18:04:44 I'll do some editing and will keep trying to get docs out by Thursday, but no promises :) 18:04:45 -tantek 18:04:46 will try to remote 18:04:46 -Arnaud 18:04:46 -Lloyd_Fassett 18:04:48 -MarkCrawford 18:04:50 -evanpro 18:04:55 -hhalpin 18:04:56 -cwebber2 18:04:58 c'mon harry, commit! 18:05:04 -AdamB 18:05:05 -oshepherd 18:05:08 -bret 18:05:09 harry, do we have a meeting room #? 18:05:19 I'll ask Susan, but I haven't been told 18:05:21 would be good to add that info to the meeting page 18:05:21 -wilkie 18:05:21 susan@w3.org knows 18:05:36 Arnaud, please send me list of accepted IEs 18:05:42 so I can double-check right now 18:05:50 this info seems to be lagging 18:06:02 here is what's currently available (because I asked ;-) http://www.w3.org/2014/11/TPAC/schedule.html 18:06:05 I think there's some last minute room re-arrangment going on to TPAC being overbooked. 18:06:10 trackbot, end meeting 18:06:10 Zakim, list attendees 18:06:10 As of this point the attendees have been +1.514.554.aaaa, jasnell, Arnaud, AdamB, evanpro, jtauber, bret, cwebber2, oshepherd, wilkie, MarkCrawford, Lloyd_Fassett, tantek, 18:06:13 ... +1.408.335.aacc, Shane, hhalpin 18:06:18 RRSAgent, please draft minutes 18:06:18 I have made the request to generate http://www.w3.org/2014/10/21-social-minutes.html trackbot 18:06:19 RRSAgent, bye 18:06:19 I see no action items