16:28:07 RRSAgent has joined #tagmem 16:28:07 logging to http://www.w3.org/2013/07/25-tagmem-irc 16:28:16 Zakim has joined #tagmem 16:28:24 zakim, this will be tag 16:28:24 ok, plinss; I see TAG_Weekly()1:00PM scheduled to start in 32 minutes 16:55:26 TAG_Weekly()1:00PM has now started 16:55:32 +TimBL 16:55:37 timbl has joined #tagmem 16:57:53 +plinss 17:00:09 +dka 17:00:58 +[IPcaller] 17:01:53 annevk has joined #tagmem 17:01:56 RRSAgent, make logs public 17:01:58 Zakim, this will be TAG 17:01:59 Meeting: Technical Architecture Group Teleconference 17:01:59 Date: 25 July 2013 17:01:59 ok, trackbot, I see TAG_Weekly()1:00PM already started 17:02:08 Scribe: Jeni Tennison 17:02:14 ScribeNick: JeniT 17:02:23 Chair: Peter Linss 17:02:43 Agenda: http://www.w3.org/wiki/TAG/Planning/2013-07-25-TC 17:05:09 +Yves 17:07:34 Zakim, who is making noise? 17:07:45 timbl, listening for 10 seconds I heard sound from the following: plinss (19%), dka (36%) 17:07:56 Regrets: Henry Thompson 17:09:22 + +1.415.254.aaaa 17:09:52 +[IPcaller] 17:10:38 plinss: we'll go round the room 17:10:49 plinss: slightlyoff, do we have minutes from the other week? 17:10:57 slightlyoff: I'll get them in, sorry 17:11:02 zakim, who is on the phone? 17:11:02 On the phone I see TimBL, plinss, dka, JeniT, Yves, slightlyoff, marcosc 17:12:06 plinss: no work on github syncing, but set up repo for website redesign 17:12:47 dka: updated actions, outreach to web apps WG (Chaals) very receptive to collaborative session around Promises 17:13:09 ... we're starting to get a reputation for the TAG being the place to go to ask for guidance on the use of Promises 17:13:15 ... which we wanted 17:13:18 +q 17:13:30 ... we discussed doing a F2F meet up with Art when meeting in Boston 17:13:50 ... I'm going to follow up with Art & hope for a good session then 17:14:00 ... don't think we want to do anything before Boston, but open to suggestions 17:14:06 ... next F2F is sooner than we think 17:14:30 marcosc: should we be dealing with the Promises stuff? 17:14:37 ack next 17:14:43 ... or should we post to script-coord list? 17:14:54 slightlyoff: we should lay down neutral guidance 17:15:14 ... the crypto guys asked who should deal with it, can do it personally 17:15:32 https://github.com/w3ctag/promises-spec-text 17:15:35 marcosc: we're going to get more and more questions 17:15:47 slightlyoff: not next call but one after I will have something done in that area 17:16:19 dka: the other thing I've progressed is getting XX from YY to come in 17:16:41 s/XX/Anssi/ 17:16:41 s/yy/intel/ 17:16:57 ... tangentially, Larry & Ashok collaborated on a blog post 17:17:07 I've just updated the README.MD quickly https://github.com/w3ctag/promises-spec-text/blob/master/README.md 17:17:10 https://twitter.com/w3ctag/status/360077819939794945 17:17:14 ... I tweeted from the TAG account 17:17:25 ... it's a follow-on around the publishing & linking document 17:17:45 ... we're not going to do anything further, it's just a matter of amplifying 17:18:18 marcosc: I did a review of the orientation block API 17:18:25 ... ended up rewriting parts of the spec 17:18:33 ... worked with XX to get changes integrated 17:18:52 https://github.com/w3ctag/spec-reviews/issues/7 17:18:56 ... some of the things still stand, particularly moving to Promises model 17:19:03 ... I'd appreciate further comment from TAG members 17:19:05 you got a +1 from me ;) 17:19:06 s/orientation block/orientation lock/ 17:19:11 slightlyoff: I'll take a look at that this week 17:19:13 apart from the 'should' part 17:19:28 marcosc: I might have a chance to push the changes before you take a look 17:19:32 ... it's a short spec 17:19:36 ... took me one hour 17:19:42 ... a review won't take long 17:20:18 slightlyoff: spent more time on web audio review 17:20:24 ... think the draft is good to go, want feedback 17:20:34 ... fielded request for review from XX 17:20:36 +1 to posting it to the public audio forum 17:20:54 ... to make sure things are in line & invite them to a call 17:21:05 ... at TC39 I'm going to try to broach the topic of TPAC 17:21:22 marcosc: it's great to see developers sending feedback on web audio 17:21:25 Agree 17:21:40 ... I saw people tweet about it too, which I think was really cool 17:21:50 slightlyoff: I'm excited about it too 17:22:07 ... but the longer it sits in our repo without sending it on, it could reflect badly 17:22:13 ... anyone opposed to sending it? 17:22:29 plinss: good to go 17:22:37 SHIP IT!!!! 17:22:37 ... send it 17:22:42 +1 17:22:43 slightlyoff: I'll do that today 17:22:50 timbl: can we have a pointer for the minutes? 17:22:52 https://github.com/w3ctag/spec-reviews/blob/master/2013/07/WebAudio.md 17:22:59 PROPOSED RESOLUTION: Send the feedback Alex has drafted over to Web Audio working group (officially). 17:23:01 "the somewhat liberal use of SHOULD in that spec is going to lead to user agents doing bad things" yes 17:23:13 RESOLUTION: Send the feedback Alex has drafted over to Web Audio working group (officially). 17:23:22 timbl: I haven't done a lot of TAG-related stuff 17:23:37 ... there have been discussions within W3C about dependencies between specs 17:23:43 ... the TAG might be asked to get involved 17:24:00 ... about whether one spec can move forward when a referenced spec doesn't 17:24:20 ... a guide about when it's a good idea and when not, an enumeration of different cases, could be useful 17:24:31 ... we might get pinged on that 17:24:44 on dependencies - I took ACTION-820 at some point but I have not followed up on it yet... 17:25:21 dka: I need to contact AB about this, is this something we should do? 17:25:26 ... should we be proactive? 17:25:59 timbl: I think it's good to say that we're willing to pick it up if we need to 17:26:47 Yves: I reviewed the marcosc review, which was good 17:27:00 ... for HTTP 2.0, I put my thoughts on the mailing list 17:27:14 ... it's another kind of serialisation and use of the network for HTTP 1.1 17:27:19 ... not different architecturally 17:27:29 ... the major change is the possibility of doing server push 17:27:58 ... which is defined in the spec as a way to send replies that contain additional resources 17:28:08 ... such as the icons/CSS related to a page 17:28:14 ... so the client doesn't have to request them 17:28:27 ... that's one thing in HTTP 2.0 that isn't in HTTP 1.1 and might have architectural implications 17:29:05 ... part of the HTTP effort was to look at being able to change the transport 17:29:19 ... HTTP 2.0 is built with that information from HTTPbis in mind 17:29:25 Somewhat relevant (as it involves SPDY and also the concept of split browsing which the TAG has touched on before) interesting to note Google's plans to implement network-based compression proxy for Chrome for IOS /Android - I blogged here: http://www.torgo.com/blog/2013/07/data-compression-proxy.html 17:29:26 ... so they can reference the relevant part of HTTPbis 17:29:43 -slightlyoff 17:29:55 ... for everything that's connection-related, like compression, it's just implementation detail 17:29:59 ... it doesn't change the semantic 17:30:32 dka: is there a reason to draft a document of feedback in the same way as we've done for WebAudio? 17:30:56 Yves: it's not feedback, but just what the differences are and what the implication is for architecture 17:31:04 ... what's the implication of being able to do push? 17:31:15 ... it's more a list for us 17:31:19 dka: what about a blog post? 17:31:22 Yves: I can do that 17:31:44 ACTION: Yves to write a blog post on http 2.0. 17:31:45 Created ACTION-823 - Write a blog post on http 2.0. [on Yves Lafon - due 2013-08-01]. 17:32:11 Jeni: I've asked Phil Archer to talk to the TAG ACTION-806 - he can make it next week. 17:32:58 DKA: Yes I think makes sense. 17:33:22 Jeni: I sent the draft around httpr***-** stuff... 17:33:44 Jeni: My aim for next week is to create an outline for capability URLs document. 17:34:41 DKA: Please ask Phil to post an intro to the TAG mailing list as well. 17:34:46 JeniT: sure 17:34:47 Jeni: Ok. 17:34:56 sorry to drop off the call 17:36:11 plinss: aob? 17:36:24 dka: is there anything we can do to accelerate the web design stuff? 17:36:33 ... should we investigate other options? 17:36:38 can anyone advise me on how/when we might be able to invite the Crypto folks to present? 17:36:41 2 weeks from now? 17:36:52 plinss: other people? 17:36:55 do folks prefer that I work up feedback before or after? 17:37:17 ... we just need to decide what the page needs to contain 17:37:28 dka: shall we put that in a README in the github repo you created? 17:37:37 plinss: yes 17:38:00 ACTION: DKA to add some ideas to the tag-site-redesign readme file.. 17:38:01 Created ACTION-824 - Add some ideas to the tag-site-redesign readme file.. [on Daniel Appelquist - due 2013-08-01]. 17:38:26 plinss: ADJOURNED 17:38:30 -dka 17:38:34 -TimBL 17:38:35 -marcosc 17:38:35 -JeniT 17:38:38 -Yves 17:38:44 -plinss 17:38:46 TAG_Weekly()1:00PM has ended 17:38:46 Attendees were TimBL, plinss, dka, JeniT, Yves, +1.415.254.aaaa, slightlyoff, marcosc 17:38:53 I have made the request to generate http://www.w3.org/2013/07/25-tagmem-minutes.html JeniT 17:44:44 any help? plinss? dka? 17:44:59 help with? 17:50:55 plinss: logistics/timing for inviting WebCrypto to present 17:51:21 should I just send mail introducing y'all and let you work out scheduling? or should I propose the call in 2 weeks? 17:52:24 Go ahead and propose the call in 2 weeks, and also introduce us and we can handle scheduling if two weeks doesn't work 18:11:16 alrighty 18:11:20 thanks 20:16:18 Zakim has left #tagmem 20:32:56 JeniT has joined #tagmem 23:37:52 timbl has joined #tagmem