17:02:58 RRSAgent has joined #tagmem 17:02:58 logging to http://www.w3.org/2013/04/18-tagmem-irc 17:03:18 zakim, who is here? 17:03:18 On the phone I see Noah_Mendelsohn, JeniT, ??P9 17:03:20 On IRC I see RRSAgent, Zakim, JeniT, timbl, noah, Marcos, annevk, slightlyoff, wycats_, plinss, Yves, trackbot 17:03:22 + +1.415.997.aaaa 17:03:32 zakim, $$P9 is Marcos 17:03:33 sorry, noah, I do not recognize a party named '$$P9' 17:03:54 zakim, who is here? 17:03:55 On the phone I see Noah_Mendelsohn, JeniT, Marcos, +1.415.997.aaaa 17:03:56 On IRC I see RRSAgent, Zakim, JeniT, timbl, noah, Marcos, annevk, slightlyoff, wycats_, plinss, Yves, trackbot 17:04:17 scribenic 17:04:22 +Yves 17:04:24 scribenick: slightlyoff 17:04:24 Zakim, passcode? 17:04:24 the conference code is 0824 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), annevk 17:04:31 annevk: 0824 17:04:38 +[IPcaller] 17:04:42 date: 18 April 2013 17:04:53 Zakim, [IP is me 17:04:53 +annevk; got it 17:04:55 meeting: W3C TAG Teleconference of 18 April 2013 17:05:10 agenda: http://www.w3.org/2001/tag/2013/04/18-agenda 17:05:15 chair: Noah Mendelsohn 17:05:19 marcos_ has joined #tagmem 17:05:52 regrets: Henry Thomposon 17:06:00 RRSAgent, make logs public 17:06:00 are those nicks or names? 17:06:02 Zakim, this will be TAG 17:06:02 ok, trackbot, I see TAG_Weekly()1:00PM already started 17:06:03 Meeting: Technical Architecture Group Teleconference 17:06:03 Date: 18 April 2013 17:06:03 thanks 17:06:15 + +1.718.877.aabb 17:06:25 zakim, who is here? 17:06:25 On the phone I see Noah_Mendelsohn, JeniT, Marcos, +1.415.997.aaaa, Yves, annevk, +1.718.877.aabb 17:06:27 On IRC I see marcos_, RRSAgent, Zakim, JeniT, timbl, noah, Marcos, annevk, slightlyoff, wycats_, plinss, Yves, trackbot 17:07:43 Marcos will scribe on 2 May 17:08:36 RESOLUTION: Minutes of 18-20 March 2013 F2F at http://www.w3.org/2001/tag/2013/03/18-agenda are approved 17:08:44 http://www.w3.org/2001/tag/2013/04/04-minutes 17:09:05 RESOLUTION: Minutes of 4 April at http://www.w3.org/2001/tag/2013/04/04-minutes are approved 17:09:47 TPAC 2013 17:09:47 11-15 November 2013 17:09:47 Shenzhen, China 17:09:48 present: Yehuda Katz, Marcos Cáceres, Jeni Tennison, Anne van Kesteren, Noah Mendelshon, Tim Berners-Lee, Yves Lafon, Peter Linss 17:10:04 topic: logistics 17:10:14 (TimBL isn't on the call, just in IRC) 17:10:27 thanks...is there a way to minus? 17:11:00 noah: we haven't talked much about TPAC, but it's a productive opportunity to talk with other groups and unless there are objections, will ask for a room 17:11:11 topic: fragment identifier semantics 17:11:22 ACTION-790? 17:11:22 ACTION-790 -- Jeni Tennison to do new Editor's Draft of fragids spec for approval to publish as CR -- due 2013-04-16 -- OPEN 17:11:22 http://www.w3.org/2001/tag/group/track/actions/790 17:11:36 http://www.w3.org/2001/tag/doc/mimeTypesAndFragids-2013-04-04.html 17:11:46 I can commit to reviewing it for the next meeting 17:11:47 noah: we have a draft from Jeni, comments were received, and the new draft is http://www.w3.org/2001/tag/doc/mimeTypesAndFragids-2013-04-04.html 17:11:55 noah: current status is review to go to CR 17:11:58 wycats_, I did email it to you privately too 17:12:01 noah: do we need to review anything in detail? 17:12:19 JeniT: lets review the changes and then we can decide what to go over in detail 17:12:25 http://lists.w3.org/Archives/Public/www-tag/2013Apr/0033.html 17:12:59 http://www.w3.org/2001/tag/doc/mimeTypesAndFragids-2013-04-04.html#publishers 17:13:02 JeniT: have added a note to emphasize that if you have conneg, not all versions must resolve all identifiers 17:13:05 JeniT: I somehow missed the email (I see it now) 17:13:23 Note 17:13:23 Note that this best practice does not imply that every structure that is addressable within one content-negotiated representation must have an equivalent structure addressable by the same fragid in all other content-negotiated representations. It is likely that some fragids will have meaning only in one of the content-negotiated representations, for example because they are interpreted by a 17:13:24 script within an HTML representation but not in any others. 17:13:24 JeniT: I'm sure it's fine 17:13:44 Looks very good to me. 17:14:33 Scripts can also be used to map a fragid on a document that contains an embedded resource (such as an image or video) into a fragid that applies to that embedded resource. Scripts can use the fragid of the location navigated to within an iframe to alter the display of the embedding document. 17:14:36 JeniT: second point: pages that embed images/video and use fragids in the outer page to resolve to the sub-resource content is addressed just following the previous note (see link above) 17:15:11 http://www.w3.org/2001/tag/doc/mimeTypesAndFragids-2013-04-04.html#fragid-structures 17:15:24 JeniT: final major change is the addition of an appendix: http://www.w3.org/2001/tag/doc/mimeTypesAndFragids-2013-04-04.html#fragid-structures 17:15:33 if I recall correctly, my concern was just to make sure that people knew to try to create their own key/values for fragments that they didn't expect to be interoperable with other mime types 17:15:47 JeniT: this goes thorough many formats that define fragids and outlines them 17:15:56 looks like Best Practice 8 covers this 17:16:15 8 and 9 I should say 17:16:41 JeniT: the point is to make authors aware of the other prevalant formats to avoid overlap 17:17:32 noah: the TAG has published a finding, and there's specific practices around hashbang...it's addressed in B7, but not mentioned elsewhere and the finding isn't referenced...should it be? 17:17:39 JeniT: it's referenced but not linked 17:19:25 wycats_: we're revisiting a lot of this now 17:19:57 wycats_: the outcome will be that people won't do this any more 17:20:37 specifically, insofar as we're telling people not to conflict with existing practices for other MIME types, the fact that we're calling out the use of #! on the web means that people won't use it in other contexts 17:21:05 I'm fine with going to CR 17:21:05 JeniT: the other change is the exit criteria 17:21:22 wycats_: what will we do about the potential JSON-pointer conflict? 17:21:48 JeniT: it says this is a fragid syntax you *can* use with JSON, it's not a "must" 17:22:30 JeniT: will expand that section in the appendix and make it explicit that if you use it as-is, it may conflict with thigns that use #/ in a different way 17:22:42 wycats_: if you conneg this way, yes, this is probably a bad idea 17:23:49 JeniT: if they're declaring conneg'd content with pointers that will map to both, the advice will be to make up your own pointer syntax in the fragid 17:24:03 wycats_: I care about this because I have systems that do this 17:24:44 JeniT: the other conflict we're likely to see will be the "+json" mimetype registration 17:24:54 wycats_: will take this offline and reply to your email 17:25:39 JeniT: if people can get back to me within the week, I'll work around wrapping up the exit criteria and JSON-pointer points and get this to Yves next week for publication 17:25:56 I'm fine with provisional approval 17:25:56 noah: this is about provisional approval for this...objections? 17:26:11 Yves: we agreed exit criteria at F2F, I just somehow didn't include them in the draft from what I can see 17:26:12 slightlyoff: provisional approval to go ahead with the CR with the document as-is 17:26:12 ACTION-790 17:26:12 ACTION-790 -- Jeni Tennison to do new Editor's Draft of fragids spec for approval to publish as CR -- due 2013-04-16 -- OPEN 17:26:12 http://www.w3.org/2001/tag/group/track/actions/790 17:26:13 no objection from me. Thanks JeniT for getting this done! 17:26:44 ACTION-790 17:26:44 ACTION-790 -- Jeni Tennison to do new Editor's Draft of fragids spec for approval to publish as CR -- due 2013-04-25 -- OPEN 17:26:44 http://www.w3.org/2001/tag/group/track/actions/790 17:27:35 Yves, oh yes, they are there! 17:27:41 . RESOLUTION: We will publish Best Practices for Fragment Identifiers and Media Type Definitions 17:27:41 W3C Editor's Draft 04 April 2013 www.w3.org/2001/tag/doc/mimeTypesAndFragids-2013-04-04.html (with minor mods at Jeni's discretion) as a CR draft, unless objections received by 23 April 2013 17:27:44 just in the wrong place 17:27:51 I was looking for then in the SoTD, but here is fine 17:28:09 I'll add a pointer from the SoTD when publishing 17:28:16 W3C Editor's Draft 04 April 2013 www.w3.org/2001/tag/doc/mimeTypesAndFragids-2013-04-04.html (with minor mods at Jeni's discretion) as a CR draft, unless objections received by 25 April 2013 17:28:38 no objection here 17:28:40 RESOLUTION: We will publish W3C Editor's Draft 04 April 2013 www.w3.org/2001/tag/doc/mimeTypesAndFragids-2013-04-04.html (with minor mods at Jeni's discretion) as a CR draft, unless objections received by 25 April 2013 17:28:56 RESOLUTION: We will publish W3C Editor's Draft 04 April 2013 www.w3.org/2001/tag/doc/mimeTypesAndFragids-2013-04-04.html (with minor mods at Jeni's discretion) as a CR draft, unless objections received by 25 April 2013 17:29:10 noah: anything else to do on this? don't think so 17:29:16 http://www.w3.org/2001/tag/products/fragids.html 17:29:25 noah: we have a product page for this work...thought we had a plan to update it 17:29:56 do product pages see much traffic? 17:30:01 ACTION: Jeni to tweak product page for Fragment ids - Due 2013-04-30 17:30:01 Created ACTION-797 - tweak product page for Fragment ids [on Jeni Tennison - due 2013-04-30]. 17:30:11 slightlyoff, maybe Yves can find out 17:30:23 topic: Authoritative Metadata 17:30:24 Yves: is that possible? do we have analytics on our pages? 17:30:30 ACTION-793? 17:30:30 ACTION-793 -- Anne van Kesteren to draft disclaimer text for Authoritative Metadata -- due 2013-04-05 -- PENDINGREVIEW 17:30:30 http://www.w3.org/2001/tag/group/track/actions/793 17:30:34 topic: Authoritative Metadata 17:30:49 Finding http://www.w3.org/2001/tag/doc/mime-respect-20060412 17:30:51 a bit difficult, but I can ask for some stats 17:30:51 ACTION-793? 17:30:52 ACTION-793 -- Anne van Kesteren to draft disclaimer text for Authoritative Metadata -- due 2013-04-05 -- PENDINGREVIEW 17:30:52 http://www.w3.org/2001/tag/group/track/actions/793 17:31:19 noah: annevk to review and draft disclaimer text because there's controversy about sniffing. 17:31:19 Anne's email: http://lists.w3.org/Archives/Public/www-tag/2013Apr/0007.html 17:31:46 noah: annevk's mail has generated some discussion and noah likes it 17:31:57 annevk: no comments for now about the proposal or responses 17:32:00 wycats_: seems fine 17:32:00 happy with it 17:32:09 I'm alright with it 17:32:13 same 17:32:38 noah: are you proposing that the typography is the same as in the draft? 17:32:42 that is how I would prefer the typography 17:32:55 annevk: hoping the typography would be pretty obvious 17:32:56 Take a look at the proposed formatting: http://www.w3.org/2001/tag/doc/mime-respect-20130405.html 17:32:59 noah: what do we think? 17:33:08 I'm fine wit hthat 17:33:15 question: is Content-Type the only header for which this is true? 17:33:29 btw: Chrome has started allowing servers to opt into authoritative metadata 17:33:33 We don't have much precedent for doing things this way. I don't think this point is more important than many others that are made in the finding. 17:33:33 wycats_: afaik 17:33:35 and Github has started using that 17:33:35 JeniT: is there any standard way to put notices in specs? 17:33:40 Yves: ? 17:33:58 JeniT: is there a standard way to put in notices for things like version succession 17:34:06 http://www.w3.org/TR/2008/REC-CSS2-20080411/ <- has a similar warning 17:34:09 I would prefer adding it in two places: 17:34:18 in ordinary text as a 2nd para in the abstract 17:34:25 http://www.w3.org/TR/CSS1/ 17:34:30 annevk: we've put warning in REC's, e.g. CSS1 17:34:31 Following point 4 in the summary at the top 17:34:35 X-Content-Type-Options:nosniff 17:34:39 is what Chrome and IE support 17:34:41 annevk: it's been a big red box 17:35:03 noah: I think this is important, but not more important than other things the finding says 17:35:09 q+ 17:35:17 wycats_: I believe that doesn't actually remove all sniffing 17:35:28 noah: counter is to put it in 2 place: 2nd paragraph of abstract and below/near summary of key points 17:35:38 noah: won't stand in the way, but it doesn't feel like an emergency 17:36:14 wycats_: e.g. will still sniff, it'll only check if Content-Type mentions an image type of sorts if that header is present 17:36:16 noah: feeling that the right way to fix this in the long run is to fix 2016 17:36:57 wycats_: don't think that's true. Recollection is that it tells you to do it, not based on "do what the specs say" 17:37:04 s/2016/2616/ 17:37:22 wycats_: IE + chrome have a header for authoritative metadata 17:37:31 wycats_: github is using it to prevent hot-linking 17:37:53 I'll just note that the idea of metadata opting into authoritative metadata is HALARIOUS 17:38:30 wycats_: the desire for a big-red-box is to help people who are in the mind of thinking about sniffing to see the point 17:38:50 wycats_: should we be investigating the state of nosniff? 17:39:08 noah: suggesting that we deal with formatting first, then nosniff in a sec 17:39:31 noah: there's no publication process for TAG findings 17:39:32 http://msdn.microsoft.com/en-us/library/ie/gg622941(v=vs.85).aspx 17:39:41 https://bugzilla.mozilla.org/show_bug.cgi?id=471020 17:39:44 noah: we just put it up and send a couple of emails 17:39:53 http://philip.html5.org/tests/ie8/cases/content-type-nosniff.html 17:39:57 noah: the way to do this might be to just re-publish the finding 17:39:58 wycats_: I think it might be interesting to look into the specifics of that if we think we can make it work 17:39:59 ^^ some nosniff links 17:40:05 noah: objections? (none heard) 17:40:27 RESOLTUION: The TAG will republish the authoritative metadata finding to include the content and formatting proposed in http://www.w3.org/2001/tag/doc/mime-respect-20130405.html 17:40:29 wycats_: and maybe define it as part of http://mimesniff.spec.whatwg.org/ if it actually does what it suggests (which I'm doubting to some extent) 17:40:45 RESOLUTION: The TAG will republish the authoritative metadata finding to include the content and formatting proposed in http://www.w3.org/2001/tag/doc/mime-respect-20130405.html 17:41:01 action: noah will republish 17:41:01 Created ACTION-798 - Will republish [on Noah Mendelsohn - due 2013-04-25]. 17:41:02 ACTION: Noah to republish authoritative metadata finding 17:41:02 Created ACTION-799 - Republish authoritative metadata finding [on Noah Mendelsohn - due 2013-04-25]. 17:41:10 oh balls 17:41:14 "This is not needed because Gecko doesn't violate the Http RFC unlike IE and doesn't do content-sniffing at all if a content-type is given." 17:41:18 I suspect that that is incorrect 17:41:22 I think I just did something automated and incorrect 17:41:23 ACTION-793? 17:41:23 ACTION-793 -- Anne van Kesteren to draft disclaimer text for Authoritative Metadata -- due 2013-04-05 -- PENDINGREVIEW 17:41:23 http://www.w3.org/2001/tag/group/track/actions/793 17:41:29 close ACTION-793 17:41:29 Closed ACTION-793 draft disclaimer text for Authoritative Metadata. 17:41:31 noah: fwiw, smaller type as in http://www.w3.org/TR/CSS1/ would work for me 17:41:41 me? or wycats_ ? 17:41:42 noah: it being super clear is what's most important 17:42:20 wycats_: it seems like Chrome has adopted it, there are publishers using it, and FF is loooking to adopt 17:42:23 Can we gt a link to the spec for this header? 17:42:27 s/gt/get/ 17:42:32 wycats_: we might want to revisit the conclusions in light of the world changing 17:42:43 noah: is there a spec? 17:42:58 wycats_: linked to http://msdn.microsoft.com/en-us/library/ie/gg622941(v=vs.85).aspx 17:43:05 http://msdn.microsoft.com/en-us/library/ie/gg622941%28v=vs.85%29.aspx 17:43:13 MIME-Handling Change: X-Content-Type-Options: nosniff 17:43:17 wycats_: annevk has raised a legit question: does it do what it says? or are there caveats? 17:43:26 noah: ugg...X-? 17:43:33 wycats_: IE created, others followed 17:43:58 Seems Gecko is awaiting a spec 17:44:20 noah: Yves, do you have a sense for who we might coordinate with? 17:44:26 https://github.com/mozilla-services/cornice/issues/102 17:44:33 Yves: there's no need to register experimental headers 17:44:34 apparently the sniffing can trigger XSS attacks 17:44:42 (from skimming the bug, which matches what I'd like us to do) 17:45:23 noah: was talking about something else: some future change to the flag might make it legit, and there's a coordination question around who owns "content-type" 17:45:27 everyone always says the "I really mean it" thing, but it never actually turns out to be true 17:45:32 noah: what's the best role for the TAG? 17:45:34 I think http://mimesniff.spec.whatwg.org/ should own this. 17:45:35 it's usually just unfortunate legacy behavior 17:45:41 see: 17:45:43 It's an explicit opt out for the thing defined there... 17:46:01 Yves: it was discussed in the HTTP WG so there's not a ton of need to cooridnate 17:46:42 wycats_: used to be sympathetic to the "I really mean it" argument, but as I've seen it play out over time, you can imagine that people MIGHT misuse, but I don't observe that 17:46:45 To be clear, I was raising a point relating to coordination across groups, not the "I really mean it" technical point 17:47:30 I filed a bug on MIME Sniffing: https://www.w3.org/Bugs/Public/show_bug.cgi?id=21742 17:47:43 wycats_: happy to investigate with annevk and slightlyoff 17:48:00 wycats_: if annevk is correct in that it doesn't actually mean what it says, we might come to different conclusions 17:48:12 noah: a group to collect and report seems good 17:48:24 yes 17:48:31 doing it now 17:48:45 relevant thread: http://lists.w3.org/Archives/Public/ietf-http-wg/2009AprJun/0104.html 17:49:17 ACTION: wycats, slightlyoff, and annevk to investigate nosniff current status 17:49:17 Error finding 'wycats,'. You can review and register nicknames at . 17:49:48 sorry 17:49:52 I'm not great at this = \ 17:50:00 due before F2F? 17:50:03 would prefer that 17:50:05 Seems I filed a duplicate :-) 17:50:08 https://www.w3.org/Bugs/Public/show_bug.cgi?id=19865 is the bug 17:50:22 ACTION: yehuda with help from slightlyoff, and annevk to investigate nosniff current status - Due 2013-05-14 17:50:22 Created ACTION-800 - with help from slightlyoff, and annevk to investigate nosniff current status [on Yehuda Katz - due 2013-05-14]. 17:50:46 Note: this may be a topic for F2F, we will decide after telcon on 16 May 17:51:18 topic: Publishing & Linking 17:51:36 F2F disussion: http://www.w3.org/2001/tag/2013/03/19-minutes#item02 17:51:54 noah: my recollection is that we'll put out P&L as a NOTE 17:52:00 noah: couldn't find a formal decision to do that 17:52:11 noah: there was an action for Ashok to update it, and he has done it 17:52:20 noah: can others confirm that that's true? 17:52:33 annevk: yes, to be published as a note and then perhaps go forward from there 17:52:42 http://www.w3.org/2001/tag/doc/publishingAndLinkingOnTheWeb-2013-04-08 17:52:53 no objections 17:52:56 noah: with that clarification, latest draft is above, and the question is: are we ready to publish as a NOTE? 17:53:00 would love to get this off our plate 17:53:03 no objections 17:53:28 . RESOLUTION: We will publish http://www.w3.org/2001/tag/doc/publishingAndLinkingOnTheWeb-2013-04-08 as a W3C Note. The TAG does not commit to further work. 17:53:30 wycats_: might still get updated though ;) 17:53:41 We note that Ashok may choose to propose some updates. 17:53:53 +1 17:53:58 RESOLUTION: We will publish http://www.w3.org/2001/tag/doc/publishingAndLinkingOnTheWeb-2013-04-08 as a W3C Note. The TAG does not commit to further work. 17:54:01 RESOLUTION: We will publish http://www.w3.org/2001/tag/doc/publishingAndLinkingOnTheWeb-2013-04-08 as a W3C Note. The TAG does not commit to further work. 17:54:32 ACTION: Yves to publish http://www.w3.org/2001/tag/doc/publishingAndLinkingOnTheWeb-2013-04-08 as a W3C Note and announce - Due 2013-04-30 17:54:32 Created ACTION-801 - publish http://www.w3.org/2001/tag/doc/publishingAndLinkingOnTheWeb-2013-04-08 as a W3C Note and announce [on Yves Lafon - due 2013-04-30]. 17:54:43 ACTION-776? 17:54:43 ACTION-776 -- Ashok Malhotra to with help from Larry to redraft Publishing and Linking, responding to comments, for review at F2F -- due 2013-04-02 -- OPEN 17:54:43 http://www.w3.org/2001/tag/group/track/actions/776 17:54:48 close ACTION-776? 17:54:48 Closed ACTION-776 With help from Larry to redraft Publishing and Linking, responding to comments, for review at F2F. 17:55:28 noah: nothing else formal on the agenda, so inclination is to close the call 17:55:43 noah: adjourned! call in 2 weeks and Marcos will scribe 17:55:43 -Marcos 17:55:44 -JeniT 17:55:45 -Noah_Mendelsohn 17:55:47 -Yves 17:55:49 -wycats_ 17:55:50 -annevk 17:55:50 -Alex 17:55:51 TAG_Weekly()1:00PM has ended 17:55:51 Attendees were Noah_Mendelsohn, JeniT, +1.415.997.aaaa, Marcos, Yves, [IPcaller], annevk, +1.718.877.aabb, wycats_, Alex 18:14:53 JeniT has joined #tagmem 19:08:05 JeniT has joined #tagmem 19:38:36 Zakim has left #tagmem 20:45:05 marcosc has joined #tagmem