00:09:13 gitbot has joined #html-wg 00:09:13 [13html] 15rubys pushed 1 new commit to 06feature/whatwg: 02https://github.com/w3c/html/commit/a66eb4f72165eb6101f9c7f09f3deccfa6133c18 00:09:13 13html/06feature/whatwg 14a66eb4f 15ianh: [ac] (3) Define a syntax for comments in WebVTT (doesn't affect parsers)... 00:09:13 gitbot has left #html-wg 00:23:04 Dashiva has joined #html-wg 00:40:11 tantek has joined #html-wg 01:00:20 sicking has joined #html-wg 01:12:21 nonge has joined #html-wg 02:09:12 gitbot has joined #html-wg 02:09:12 [13html] 15rubys pushed 1 new commit to 06feature/whatwg: 02https://github.com/w3c/html/commit/3c4747eae0785de87cc4626d37ab2526b81724e3 02:09:12 13html/06feature/whatwg 143c4747e 15ianh: [e] (0) Fix some typos or copypasta.... 02:09:12 gitbot has left #html-wg 02:12:06 Judy has joined #html-wg 02:19:00 karl has joined #html-wg 02:22:50 tantek has joined #html-wg 02:26:11 yoshiaki has joined #html-wg 04:30:24 yoshiaki has joined #html-wg 04:35:15 yoshiaki has joined #html-wg 06:00:52 tomoyuki has joined #html-wg 06:08:17 yamaday has joined #html-wg 06:32:28 glenn has joined #html-wg 06:35:25 r12a has joined #html-wg 06:38:14 tinkster has joined #html-wg 06:55:09 darobin has joined #html-wg 06:59:40 gavin_ has joined #html-wg 07:00:38 logbot has joined #html-wg 07:10:03 yoshiaki has joined #html-wg 07:16:49 cabanier has joined #html-wg 07:19:52 yoshiaki has joined #html-wg 07:21:12 adrianba has joined #html-wg 07:21:23 yoshiaki has joined #html-wg 07:22:16 naomi has joined #html-wg 07:25:24 gavin has joined #html-wg 07:27:27 kotakagi has joined #html-wg 07:29:25 kotakagi has joined #html-wg 07:30:10 glenn has joined #html-wg 07:34:00 dveditz has joined #html-wg 07:36:09 tomoyuki has joined #html-wg 07:38:46 r12a has joined #html-wg 07:42:46 Yoshiharu has joined #html-wg 07:43:08 Jirka has joined #html-wg 07:43:15 kotakagi has joined #html-wg 07:43:55 sakkuru has joined #html-wg 07:45:32 fsasaki has joined #html-wg 07:46:10 plh has joined #html-wg 07:46:25 Shinji has joined #html-wg 07:47:15 takuya has joined #html-wg 07:47:21 adrianba has joined #html-wg 07:47:46 darobin has joined #html-wg 07:50:23 a12u has joined #html-wg 07:52:19 rotsuya has joined #html-wg 07:52:23 plh has joined #html-wg 07:52:37 sgodard has joined #html-wg 07:53:58 mhellwig has joined #html-wg 07:54:10 MP has joined #html-wg 07:54:10 kfritsche has joined #html-wg 07:54:11 DomJones has joined #html-wg 07:54:21 mdelolmo has joined #html-wg 07:54:21 matthiasK has joined #html-wg 07:54:36 renatb has joined #html-wg 07:55:14 matthiasK_ has joined #html-wg 07:56:17 gilesg-b has joined #html-wg 07:56:22 Ruinan has joined #html-wg 07:56:47 sakkuru has joined #html-wg 07:57:37 pnietoca has joined #html-wg 07:57:50 paulc has joined #html-wg 07:58:00 Fredrik has joined #html-wg 07:58:03 daveL has joined #html-wg 07:58:23 MikeSmith has joined #html-wg 07:58:28 Magnus_Olsson has joined #html-wg 07:58:32 Present+ Paul Cotton 07:58:46 jens has joined #html-wg 07:58:54 rrsagent, make minutes 07:58:54 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html paulc 07:58:54 Zakim has joined #html-wg 07:58:55 present+ Magnus_Olsson 07:59:01 Ankit has joined #html-wg 07:59:12 present+ r12a 07:59:13 RRSAgent, make logs public 07:59:14 Present+ Adrian_Bateman 07:59:18 nkic has joined #html-wg 07:59:21 present+ felix_sasaki 07:59:22 Present+Jirka_Kosek 07:59:26 present+ glenn 07:59:27 present+ Moritz_Hellwig 07:59:29 acolwell has joined #html-wg 07:59:29 fumitakaW has joined #html-wg 07:59:32 Present+ sgodard 07:59:35 Present+ Karl_Fritsche 07:59:40 present+ Dominic_Jones 07:59:40 jyp has joined #html-wg 07:59:40 hbang has joined #html-wg 07:59:40 Present+Dave_Lewis 07:59:41 MP has left #html-wg 07:59:43 present+ hober 07:59:49 SebastianS has joined #html-wg 07:59:51 present+ pnietoca 07:59:57 present+ acolwell 08:00:00 present+ hyungjin_Bang 08:00:03 Present+ fumitakaW 08:00:07 Clemens has joined #html-wg 08:00:10 dF has joined #html-wg 08:00:11 zakim, who is on the phone? 08:00:11 sorry, paulc, I don't know what conference this is 08:00:12 On IRC I see dF, Clemens, SebastianS, hbang, jyp, fumitakaW, acolwell, nkic, Ankit, Zakim, jens, Magnus_Olsson, MikeSmith, daveL, Fredrik, paulc, pnietoca, sakkuru, Ruinan, 08:00:12 ... gilesg-b, matthiasK_, renatb, mdelolmo, DomJones, kfritsche, mhellwig 08:00:12 present+ Ankit_Srivastava 08:00:13 Marcis_Pinnis has joined #html-wg 08:00:15 Present+ Dave_Lewis 08:00:18 nsakai has joined #html-wg 08:00:19 present+ Mauricio_del_Olmo 08:00:30 mjs has joined #html-wg 08:00:41 title: HTML WG f2f 08:00:42 present+ dF 08:00:46 Arno has joined #html-wg 08:00:46 scribe: MikeSmith 08:00:55 present+ MikeSmith 08:00:55 present+ mjs 08:00:56 dromasca has joined #html-wg 08:00:57 Present+ Arnaud_Braud 08:01:01 edoyle has joined #html-wg 08:01:06 present+ Ruinan Sun 08:01:15 present+ Erika_Doyle_Navara 08:01:21 agenda: http://www.w3.org/html/wg/wiki/TPAC2012 08:01:37 kinji_ has joined #html-wg 08:01:39 dsinger has joined #html-wg 08:01:43 yamaday has joined #html-wg 08:02:01 Milan has joined #html-wg 08:02:09 Topic: MultilingualWeb-LT 08:02:25 RRSAgent, make minutes 08:02:25 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html MikeSmith 08:03:08 kotakagi has joined #html-wg 08:03:14 leroyfinn has joined #html-wg 08:03:21 Mark_Vickers has joined #html-wg 08:03:22 zakim, who is on the phone? 08:03:22 sorry, adrianba, I don't know what conference this is 08:03:24 On IRC I see Mark_Vickers, leroyfinn, kotakagi, Milan, yamaday, dsinger, kinji_, edoyle, dromasca, Arno, mjs, nsakai, Marcis_Pinnis, dF, Clemens, SebastianS, hbang, jyp, fumitakaW, 08:03:24 ... acolwell, nkic, Ankit, Zakim, jens, Magnus_Olsson, MikeSmith 08:03:25 zakim, who is on the phone? 08:03:27 sorry, paulc, I don't know what conference this is 08:03:27 On IRC I see Mark_Vickers, leroyfinn, kotakagi, Milan, yamaday, dsinger, kinji_, edoyle, dromasca, Arno, mjs, nsakai, Marcis_Pinnis, dF, Clemens, SebastianS, hbang, jyp, fumitakaW, 08:03:27 ... acolwell, nkic, Ankit, Zakim, jens, Magnus_Olsson, MikeSmith 08:03:32 zakim, this will be HTML_WG() 08:03:32 ok, adrianba; I see HTML_WG()4:00AM scheduled to start 3 minutes ago 08:03:35 present+ Mark_Vickers 08:03:35 zakim, call rhone_3 08:03:35 ok, paulc; the call is being made 08:03:36 HTML_WG()4:00AM has now started 08:03:37 +Rhone_3 08:03:48 zakim, who is on the phone? 08:03:48 On the phone I see Rhone_3 08:03:49 ddorwin has joined #html-wg 08:03:59 meeting: HTML WG f2f 08:04:01 RRSAgent, make minutes 08:04:01 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html MikeSmith 08:04:13 Paul reviews the agenda http://www.w3.org/html/wg/wiki/TPAC2012 08:04:36 markw has joined #html-wg 08:04:41 plan is to discuss MultilingualWeb-LT, i18n bugs in the morning 08:04:46 giuseppe has joined #html-wg 08:05:00 RRSAgent, make minutes 08:05:00 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html MikeSmith 08:05:01 Yoshihiro has joined #html-wg 08:05:22 Chair: Paul, Maciej 08:05:27 RRSAgent, make minutes 08:05:27 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html MikeSmith 08:05:58 Stevef has joined #html-wg 08:06:07 shoko has joined #html-wg 08:06:42 http://www.w3.org/International/multilingualweb/lt/wiki/File:Its20-html5-tpac2012.pdf 08:06:42 paulc: we have some friends here from the MultilingualWeb-LT WG 08:07:03 fsasaki steps up to the mic 08:07:15 richardschwerdtfeger has joined #html-wg 08:08:38 MLW-LT WG members stand up -- 10+ people here 08:08:38 fsasaki on slide 2 of his presentation 08:08:52 Takahiro has joined #html-wg 08:09:05 Kiyoshi has joined #html-wg 08:09:42 slide 3 shows example documents 08:10:27 More examples are in editor's draft at http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20.html 08:10:36 fsasaki: "translate" is now a native HTML attribute 08:10:49 slide 4 shows more examples 08:11:15 fsasaki: this shows one of the hyphenated its attributes 08:11:27 slide 5 has some links 08:11:32 SungOk_You has joined #html-wg 08:11:41 fsasaki: Frederick will show some demos 08:12:03 fsasaki: we want to go to LC in November 08:12:16 … and have validator support when we go to LC 08:12:46 … we want feedback on this section "How to use ITS metadata in HTML" by end of November 08:12:49 jcraig has joined #html-wg 08:12:54 … I wanted to make you aware of that plan 08:13:00 shige_ has joined #html-wg 08:13:01 RRSAgent, make minutes 08:13:01 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html MikeSmith 08:13:24 MichaelC has joined #html-wg 08:13:31 Fredrik at the decks now 08:13:36 speaker is frederik linden from enlaso 08:13:40 David_MacD_Lenovo has joined #html-wg 08:13:59 Frederik describing use cases 08:14:20 Present+ Tomoyuki_Shimizu 08:14:39 describing filters design, processing through "ITS engine" 08:14:53 JonathanJ1 has joined #html-wg 08:15:02 frederiks slides are at http://www.w3.org/International/multilingualweb/lt/wiki/File:Some_Use_Cases_with_the_Current_Okapi_Framework_Implementation_of_ITS_2.0%28Yves_Savourel-2012-09-25%29.pptx 08:15:18 now describing "Translation Package Creation" slide 08:15:18 (sorry, currently ppt only, pdf will come later) 08:16:11 robints has joined #html-wg 08:16:27 describing benefits 08:17:23 JonathanJ1 has joined #html-wg 08:17:35 here slides in pdf http://www.w3.org/International/multilingualweb/lt/wiki/File:Some_Use_Cases_with_the_Current_Okapi_Framework_Implementation_of_ITS_2.0%28Yves_Savourel-2012-09-25%29.pdf 08:17:37 fantasai has joined #html-wg 08:17:52 we enter the demonstration 08:18:03 showing "Rainbow" implementation 08:18:24 Bert has joined #html-wg 08:21:00 kawakami has joined #html-wg 08:21:35 fsasaki: there are other use cases described in our document but we just wanted to show you this one demo for now 08:21:45 … main thing we want is your feedback 08:21:46 q? 08:21:49 Lachy has joined #html-wg 08:22:11 paulc: let's go around the room and see if anybody has any questions 08:22:18 YoshiT has joined #html-wg 08:22:47 paulc: fsasaki you pointed us at your document 08:23:10 http://www.w3.org/International/multilingualweb/lt/wiki/File:Its20-html5-tpac2012.pdf 08:23:45 Present+ Jonathan_Jeon 08:24:19 paulc: fsasaki are there any particular parts that you yourself are concerned about? that you may or may not have got right? 08:24:57 paulc: the group is large and so it's been difficult to get consensus for comments on other group's specs 08:25:17 … so it's more likely that you'll get individual comments 08:25:19 q+ 08:25:21 http://www.w3.org/TR/its20/#html5-markup 08:25:46 Zakim, who's on the phone? 08:25:46 On the phone I see Rhone_3 08:25:52 jkiss has joined #html-wg 08:26:15 mjs: these ITS extensions to HTML, are they intended to be in actual HTML content that is published over the Web? 08:26:28 … or are they intended for internal use? 08:26:30 Yongrok has joined #html-wg 08:26:38 Jirka: content published over the Web? 08:26:52 mjs: so 3rd-party tools will consume this? 08:26:57 Jirka: yeah 08:27:06 shoko has joined #html-wg 08:27:06 Wonsuk has joined #html-wg 08:27:36 cameronjones: is this something that's going to be integrated with HTML itself? 08:28:16 Jirka: similar to say, style attribute in HTML. Can use CSS selectors or XPath 08:28:35 cameronjones: what's the default? 08:28:35 Jirka: XPath 08:28:46 Jirka: default is to apply to complete subtree 08:29:22 fsasaki: about CSS selectors, we would like to have that support 08:29:24 rubys has joined #html-wg 08:29:48 Fredrik has joined #html-wg 08:30:04 cjones: translation can be quite verbose, anything that can reduce that would be great 08:30:23 fsasaki: but it is a feature at risk, so if you are interestd i that, please contact us for aslo implementations - thanks 08:30:28 … looks like it will help to reduce that verbosity 08:30:34 q+ 08:30:54 rrsagent, generate minutes 08:30:54 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html hbang 08:31:19 - new dir values 08:31:20 - concerns with ruby 08:31:20 - https://www.w3.org/Bugs/Public/show_bug.cgi?id=15278 Adding Islamic calendar support in HTML5 08:31:20 paulc thanks the MLW-LT WG for joining us this morning 08:31:21 - https://www.w3.org/Bugs/Public/show_bug.cgi?id=16965 i18n-ISSUE-97: Allowing a page to request a given locale (4.10.7.2 normativity) 08:31:57 the W3C Nu validator and validator.nu now already have support for ITS attributes, btw 08:32:11 Topic: i18n bugs 08:32:11 Milan has joined #html-wg 08:32:14 q- 08:32:22 DomJones has joined #html-wg 08:32:23 q? 08:32:27 q- 08:32:30 DomJones has left #html-wg 08:32:36 RRSAgent, make minutes 08:32:36 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html MikeSmith 08:32:38 mdelolmo has left #html-wg 08:33:00 Norbert has joined #html-wg 08:33:10 cjones has joined #html-wg 08:33:16 darobin gives an overview 08:33:27 preent +cjones 08:33:34 present +cjones 08:33:35 r12a: want to set the scene first 08:33:42 present+ Norbert_Lindenberg 08:34:00 … I will take about bi-directional text aka BIDI 08:34:09 present+ cjones 08:34:12 JonathanJ3 has joined #html-wg 08:34:25 r12a: imagine you have a data feed that provides info about restaurants 08:34:41 Marcis_Pinnis has left #html-wg 08:34:49 … including the name of the restaurant and some stars to show a rating 08:35:36 pal has joined #html-wg 08:35:41 r12a: there are cases where you need to isolate a word from the surrounding text 08:36:16 r12a: the isolation issue is really important when you don't know the directionality of the surrounding text but it's *also* important even when you do know 08:36:41 r12a: the Unicode Consortium is going to introduce some new character codes to address this 08:36:55 … and the CSS specifications are going to be updated to address this 08:37:16 … and the Unicode Consortium is going to be saying that isolation should be use by default 08:37:56 r12a: there are some limitations with current solutions the authors have been using 08:38:35 r12a: so we arrive at the bdi element 08:38:51 … it creates problems for templating and other things 08:39:06 r12a: so it would be much simpler if we could just use the dir attribute 08:39:12 … with new values 08:39:14 q+ 08:39:23 … say "rli" and "lri" 08:39:32 s/other things/other things, because it splits information across two elements where not necessary/ 08:39:35 r12a: we are not asking for the bdi element to be replaced 08:39:55 … because the bdi element still has some other use cases 08:39:57 SungOk_You has joined #html-wg 08:40:14 r12a: what we're proposing would make it easier for authors 08:40:48 hsivonen: so considering adding values to the dir attribute, wouldn't that make the new values fall back to left-to-right in older attributes? 08:41:01 … what about adding a new attribute instead? 08:41:07 ack Hsi 08:41:16 r12a: we want people to stop using ltr and rtl actually 08:41:29 … we realize there will be a bit of a difficult transition peried 08:41:40 q+ 08:41:50 … but authors can address that by using some CSS to address older browsers vs newer browsers 08:41:57 hsivonen: yeah, makes sense 08:42:29 fsasaki has left #html-wg 08:42:35 mjs: if you want to deprecate use of the old values and have a combined thing, you can introduce a new attribute, say "isolation" (though maybe a shorter name) 08:42:53 … it's usually not a good idea to require people to jump through huge hoops to deal with fallback 08:43:06 ack mjs 08:43:14 mjs: I would strongly suggest that you consider a design for this that has good fallback 08:43:33 fantasai: the implementation in Mozilla for this would be one line of code, probably 08:43:48 r12a: people will need CSS anyway for bidi support 08:43:52 Judy has joined #html-wg 08:44:08 r12a: we want people to take this up, and use of the dir attribute makes that easier 08:44:17 q+ 08:44:22 q+ 08:44:24 r12a: about adding a new attribute, we would really like to get this in HTML5 08:44:29 ack hs 08:44:37 q+ 08:44:48 q+ to say adding new values to existing attributes should be considered the same as adding new attributes 08:45:28 hsivonen: I think the desire to get this into HTML5 is a terrible reason [for not using the best technical solution] 08:45:29 ack mjs 08:45:31 koji has joined #html-wg 08:45:51 q- 08:46:02 mjs: this would be considered a new feature whether you do it as a new attribute or new values on an existing attribute 08:46:02 mjs made my point 08:46:11 … as far as our CR exit criteria 08:46:18 ack mikes 08:46:18 MikeSmith, you wanted to say adding new values to existing attributes should be considered the same as adding new attributes 08:46:23 q+ 08:46:25 ack MichaelC 08:46:29 ack MikeSmith 08:46:50 MikeSmith: mjs made my point too 08:47:21 ack cj 08:47:28 r12a: what I am hearing is that we should develop an extension and that we should consider doing it some way other than adding new values to the dir attribute 08:48:08 cjones: deprecating ltr and rtl? good idea to do? 08:48:13 r12a: not sure yet 08:48:25 - concerns with ruby 08:48:31 Next item is - concerns with ruby 08:48:35 darobin: will require a few years time 08:48:42 Topic: Concerns with ruby markup 08:49:01 drublic has joined #html-wg 08:49:14 fantasai: ruby markup is used with Chinese and Japanese content, to annotate the characters with their pronunciations 08:49:21 RRSAgent, make minutes 08:49:21 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html MikeSmith 08:49:45 fantasai: there is "mono ruby" and "group ruby" and from a markup perspective, those are the same 08:49:51 Joshue108 has joined #html-wg 08:50:12 fantasai: we also have "jukugo ruby" which looks the same basically but is different for line breaking 08:50:18 … you have to know what the grouping is 08:50:45 … so that you don't break them in the wrong place (among other things) 08:50:58 fantasai: that XHTML WG came up with a bunch of elements 08:51:14 … the HTML WG came up with a simpler solution 08:51:38 fantasai: but aside from the number elements, the model for the two approaches are quite different 08:51:57 … it is a "column-based model" vs a "row-based model" 08:52:43 fantasai: is you are displaying the ruby text inline -- which has some use cases such as, say, display on a mobile phone 08:52:56 q+ 08:53:01 … Stuff like that is very easy if you have a row-based model 08:53:15 fantasai: that is a fallback issue, and important 08:53:30 fantasai: another case is double-sided ruby 08:53:51 … where you have annotations both above the character and below the character 08:54:19 george has joined #html-wg 08:54:19 fantasai: with HTML5 ruby markup you can deal with this by using two rt elements 08:55:14 fantasai: there are cases of double-sided ruby that you can't address just with multiple rt elements 08:55:28 … So the solution proposed for that has been to use "nested ruby" 08:55:40 … But there are problems with that 08:55:58 … One problem is that it amounts to having two different models 08:56:32 … And it requires different styling for nested ruby vs normal ruby 08:57:26 fantasai: so an additional thing that has not been considered is that there are cases where you have the possibility of running out of room for the annotations 08:57:37 … so that the annotations would end up overlapping 08:57:50 … these are things that have to be handled at the style layer 08:58:13 … so it's not a bunch of discrete boxes that don't know anything each other 08:58:26 pal has joined #html-wg 08:58:38 … you ideally need to know "what's in this box next to me" 08:59:07 fantasai: I think the solution to all these problems is to go to a wholly row-based approach 08:59:23 … which is the same approach that's used for the simple ruby case in HTML5 08:59:23 Milan has left #html-wg 08:59:38 fantasai: so you need an rb element 09:00:01 RRSAgent, make minutes 09:00:01 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html MikeSmith 09:00:19 q+ 09:00:39 fantasai: plus an rtc element 09:01:02 … which addresses the spanning use case 09:01:12 … which current model cannot be used for 09:01:19 r12a: is can actually 09:01:37 paulc: status of the related bugs? 09:02:51 fantasai: Hixie hijacked the bug we had which was just about parsing and [tried to made it into be about something else] 09:03:13 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13113 ( and https://www.w3.org/Bugs/Public/show_bug.cgi?id=17967 ) 09:03:16 ack hsi 09:03:27 cabanier has joined #html-wg 09:03:27 hsivonen: I have three points -- two of my own and one channeling Hixie 09:04:10 hsivonen: first, is there actual statistics on how often a Japanese print reader encounter these various types of ruby? Daily? Once a week? Yearly? 09:04:17 fantasai: depends on which case you mean? 09:04:36 fantasai: jukugo ruby is quite common 09:04:46 hsivonen: what does common mean in this case? 09:04:56 hsivonen: again, daily? weekly? 09:05:07 fantasai: Koji can answer that 09:05:51 koji: I don't have exact numbers 09:06:22 r12a: the jukugo ruby thing is not an issue -- you can achieve it by styling 09:06:42 r12a: the thing I think you were asking about more is double-sided ruby 09:06:48 hsivonen: I was asking about all of them 09:06:51 Present+ Odin_Hoerthe_Omdal 09:07:00 … that you can prioritize their importance 09:07:05 q? 09:07:08 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html odinho_ 09:08:00 rubys has joined #html-wg 09:08:05 r12a: I have had people come up to me from Amazon and others and tell me that they need double-sided ruby support 09:08:35 hsivonen: question two, was the case about fallback for legacy UAs or for the principle of semantics 09:08:54 Note we still have 2 more items to discuss in this session: 09:08:55 - https://www.w3.org/Bugs/Public/show_bug.cgi?id=15278 Adding Islamic calendar support in HTML5 09:09:08 … Leading me to ask, in the case where you'd want it rendered inline with parenthesis, why don't you just mark it up with parenthesis? 09:09:16 2nd item is: 09:09:17 - https://www.w3.org/Bugs/Public/show_bug.cgi?id=16965 i18n-ISSUE-97: Allowing a page to request a given locale (4.10.7.2 normativity) 09:09:23 fantasai: responsive design is one case 09:09:40 darobin: like the case where you want to make the case more compact 09:09:55 hsivonen: OK, last, I think Hixie's argument was about frequency of use 09:10:49 … and about implementor indifference. [The implementors should be focusing on implementing simple ruby before they implement complex ruby.] 09:11:19 fantasai: question is, why aren't we going with the model that enables extension more easily? 09:11:23 http://www.w3.org/TR/ruby-use-cases/ 09:12:01 r12a: the i18n WG did not yet get a lot of traction saying that we should be doing things differently 09:12:10 … Hixie has added double-sided support 09:12:26 darobin: we could the same thing that we are doing for other features 09:12:43 … we could flag the current model as "at risk" and publish an extension spec 09:13:06 paulc: is the double-sided support that Hixie came up with already in our CR draft? 09:13:06 http://fantasai.inkedblade.net/weblog/2011/ruby/ 09:13:10 darobin: yes 09:14:07 hsivonen: would the potential extension spec require a delta spec of the parser algorithm? 09:14:15 (discussion) 09:14:34 hsivonen: so the answer seems to be that it's unknown at this time 09:14:58 hsivonen: I am generally unhappy about the idea of multiple delta specs to the parser algorithm 09:15:26 … especially since we currently have the parsing algorithm implemented in all major browser engines 09:15:27 Norbert has joined #html-wg 09:15:34 RRSAgent, make minutes 09:15:34 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html MikeSmith 09:15:34 q+ 09:15:49 cjones: these two bugs are about the same thing 09:16:00 q+ 09:16:05 … Localization for this case is currently applied as a user setting 09:16:19 Judy has joined #html-wg 09:16:31 cjones: user's preferred locale is what always ends up being used 09:16:41 Arno has joined #html-wg 09:16:41 I agree with hsivonen's sentiment on the parser and would rather see the parser modified to not break potential extensions to ruby, and let the discussion on exactly how ruby is extended be independent of the parser 09:16:54 … this is a problem for multi-language documents. It provides no flexibility. 09:17:25 s/fallback for legacy UAs/fallback for legacy UAs, or responsive design,/ 09:17:27 cjones: this should be seen as a form of translation rather than localization 09:17:44 … so maybe this could be controlled through the translate attribute 09:17:57 SimonPieters has joined #html-wg 09:18:17 ack r12a 09:18:18 … [translate attribute] is something for document consumers and not so much for user agents 09:18:32 s/responsive design is one case/all three are valid points. Fallback is not just for legacy UAs, but also newer layout engines for which ruby is not a high priority -- at least they can render something sensible. Reponsive design, but also to have markup independent of styling--the author has the choice to decide on a different rendering without going back and changing the markup./ 09:18:43 ack norbert 09:19:01 Takahiro has joined #html-wg 09:19:04 q+ 09:19:18 Norbert: sometimes a page loads other components that are not in the same language 09:20:02 … So start from the element that you want to format, and check to see if it has inherited a language, and if not, then go back up to the user preference 09:20:08 divya has joined #html-wg 09:20:25 cjones: the reason browsers have taken the approach they have is that typically users want to see something in their own language 09:20:31 i/fantasai: question is/fantasai: I'm not suggesting we have a model that does everything now/ 09:20:45 … so they are in effect overriding the author preferences with the user preferences 09:21:02 ack hsi 09:21:16 … but the problem with that is we provide no way to break out of that 09:21:43 hsivonen: browsers don't do right now what is already in the spec 09:21:51 hsivonen: the spec already says what you want 09:22:11 q+ 09:22:14 hsivonen: we can't fix this by having the spec say, "UAs must must must must do this" 09:22:31 hsivonen: and adding new syntax is not going to make it any better 09:23:13 drublic_ has joined #html-wg 09:23:24 hsivonen: it is completely unhelpful to munge pieces of a page into the language of the reader 09:23:44 tmpsantos has joined #html-wg 09:24:11 hsivonen: this is an artifact of the browser just trying to do one thing for the whole page vs trying to be helpful 09:25:07 ack r12a 09:25:09 hsivonen: and issue of having the browser ship with support for all possible languages [that some piece of a page might be in] 09:25:30 r12a: I am wondering about whether the lang attribute is the right thing to use for locale 09:25:35 janina has joined #html-wg 09:26:01 r12a: Cameron, what do you want to have done with these bugs? Why are we discussing them here today? 09:26:03 s/for the simple ruby case in HTML5/for XHTML ruby/ 09:26:31 cjones: there are always some dates that are pre-formatted by the server 09:26:41 … the problem already exists 09:26:57 q? 09:26:59 ack norbert 09:27:01 hsivonen: the problem exists in implementations, it does not exist in the current spec text 09:27:16 Norbert: I don't agree that the problem does not exist in the spec 09:27:23 http://www.w3.org/TR/html5/states-of-the-type-attribute.html#input-impl-notes 09:27:28 janina has left #html-wg 09:27:35 i/fantasai: so you need an rb element/fantasai: You can have a create a model that is compatible with both the HTML5 simple ruby as well as a row-based approach for the other cases/ 09:27:35 … some of the relevant text is non-normative 09:28:10 hsivonen: so we can keep it non-normative for CR but make it normative after 09:29:03 hsivonen: I think it would make it normative, after CR, 09:29:27 s/it would make it normative/it would make sense to make it normative/ 09:29:34 Still pending - - https://www.w3.org/Bugs/Public/show_bug.cgi?id=15278 Adding Islamic calendar support in HTML5 09:29:54 darobin: It seems like a resolution for this is to agree to make it normative after CR 09:30:03 RRSAgent, make minutes 09:30:03 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html MikeSmith 09:31:26 r12a: come talk to me about bug 15278 later 09:31:55 darobin: a decent number of the remaining i18n bugs are editorial 09:31:56 q+ 09:32:16 paulc: so r12a please work with darobin and the editors to deal with these bugs 09:32:36 DanielAustin has joined #html-wg 09:33:03 ACTION: Robin to summarise I18N discussion and bugs, copy public-i18n 09:33:03 Sorry, couldn't find Robin. You can review and register nicknames at . 09:33:15 i/these two bugs are/Topic: i18n bugs/ 09:33:19 RRSAgent, make minutes 09:33:19 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html MikeSmith 09:33:37 https://www.w3.org/Bugs/Public/show_bug.cgi?id=16959 09:33:46 JonathanJ3 has joined #html-wg 09:34:13 Norbert: is there any chance of renaming the "global time" and "local time" in the spec 09:34:51 i18n-ISSUE-88 09:35:12 paulc: get together over coffee for that discussion 09:35:38 nonge_ has joined #html-wg 09:35:44 rrsagent, make minutes 09:35:44 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html hbang 09:37:44 rubys has joined #html-wg 09:40:07 ACTION: Robin to summarise I18N discussion and bugs, copy public-i18n 09:40:07 Sorry, couldn't find Robin. You can review and register nicknames at . 09:41:15 ACTION: darobin to summarise I18N discussion and bugs, copy public-i18n 09:41:15 Sorry, couldn't find darobin. You can review and register nicknames at . 09:42:42 trackbot, status 09:43:46 trackbot, reload 09:44:01 trackbot, bye 09:44:01 trackbot has left #html-wg 09:44:10 trackbot has joined #html-wg 09:44:15 ACTION: darobin to summarise I18N discussion and bugs, copy public-i18n 09:44:15 Created ACTION-224 - Summarise I18N discussion and bugs, copy public-i18n [on Robin Berjon - due 2012-11-09]. 09:47:31 tinkster has joined #html-wg 09:49:10 drublic has joined #html-wg 09:50:10 Judy has joined #html-wg 09:55:46 cjones has joined #html-wg 09:56:18 kawakami has joined #html-wg 09:59:14 Arno has joined #html-wg 09:59:45 hbang has joined #html-wg 09:59:46 pal has joined #html-wg 10:00:55 Milan has joined #html-wg 10:01:28 drublic_ has joined #html-wg 10:01:47 Stevef has joined #html-wg 10:01:59 +Cynthia_Shelly 10:02:12 jkiss has joined #html-wg 10:02:43 ddorwin has joined #html-wg 10:05:03 Takahiro has joined #html-wg 10:07:47 r12a has joined #html-wg 10:08:04 a12u has joined #html-wg 10:08:06 naomi has joined #html-wg 10:08:23 Norbert has joined #html-wg 10:08:27 koji has joined #html-wg 10:09:09 scribe: Matt 10:10:25 Topic: Preparing for CR and WG Status 10:10:50 paulc: We'll review objections, features at risk, CR exit criteria, status of CR drafts, and HTML 5.1 planning. 10:11:13 paulc: We'll reserve some time at the end for email organization discussion. 10:11:18 DanielAustin has joined #html-wg 10:11:30 paulc: We noticed during responsive images discussion that we didn't have a place for the discussion. 10:11:42 MikeSmith has joined #html-wg 10:11:56 kenji has joined #html-wg 10:12:02 http://www.w3.org/News/2012#entry-9619 10:12:03 paulc: Let's review the list of the recently published drafts 10:12:21 -> http://www.w3.org/News/2012#entry-9615 Recent Drafts 10:12:43 paulc: Coming out of this meeting I'd like to at least get a sentiment out of the people in this room about how we'll progress each of these docs. 10:12:51 sakkuru has joined #html-wg 10:12:52 cabanier has joined #html-wg 10:12:58 cabanier1 has joined #html-wg 10:13:07 jyp has joined #html-wg 10:13:11 paulc: We'll go back to that list and get agreement on how we're progressing those documents. 10:13:12 http://lists.w3.org/Archives/Public/public-html/2012Oct/0026.html 10:13:30 paulc: This email is what you agreed to do in the past from a CfC point of view. 10:13:47 paulc: There was an explicit list of things you weren't agreeing to in that CfC too. 10:13:53 Jirka has joined #html-wg 10:14:05 paulc: You were agreeing to go to CR, but weren't explicitly agreeing to the exact terms of that. 10:14:08 Mark_Vickers has joined #html-wg 10:14:33 present+ Mark_Vickers 10:14:37 jens has joined #html-wg 10:14:49 paulc: We still need to do the CR transition request, need to request FPWD of 5.1, FPWD of extension specs, and any other transitions for any other specs. 10:15:05 LeonieWatson has joined #html-wg 10:15:10 paulc: There were two other items: accessibility TF statement (which we won't touch on), and agreement on full list of features at risk. 10:15:20 SungOk_You_ has joined #html-wg 10:15:25 paulc: Given that summary, which drafts are being proposed to go to CR? 10:16:00 paulc: I believe we'll go to CR on four or five documents. 10:16:19 paulc: The HTML 5, Canvas 2D, Polyglot and Alt-Techniques documents. 10:16:36 s/5/5 Core/ 10:16:51 s/Polyglot/Microdata, Polyglot/ 10:16:51 krisk has joined #html-wg 10:16:53 rrsagent, draft minutes 10:16:53 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html matt 10:17:04 present+ kris_krueger 10:17:10 paulc: We need to ask ourselves about the other drafts as well. 10:17:13 Ruinan has joined #html-wg 10:17:16 q+ 10:17:31 q- 10:17:34 paulc: Robin has said three docs would be prepared. 10:17:38 3 cr frafts: http://htmlwg.org/cr/ 10:17:44 s/frafts/drafts/ 10:18:13 fumitakaW has joined #html-wg 10:18:13 takuya has joined #html-wg 10:18:47 q? 10:18:54 Wonsuk has joined #html-wg 10:19:04 darobin: Those are generated from the same source document, the others I'd have to sync up with the other editors. We'll have a short meeting with Steve about that today. Elliott wasn't here and I have to have a conversation with him about how he generates it in order to get it. 10:19:05 paulc: So those five, does anyone disagree that they go to CR? The 2 docs don't have features at risk. 10:19:31 Takahiro has joined #html-wg 10:19:31 hsivonen: Lachy formally objected to making micro data normative and I second that objection. 10:19:33 q+ 10:19:48 FOs: http://dev.w3.org/html5/status/formal-objection-status.html 10:19:58 s/micro data/polyglot/ 10:20:10 ack hsivonen 10:20:27 paulc: The Director asked us to confirm which of the FOs are still pertinent. I may have the number incorrect -- I seem to remember 11 at the time, but might have been higher -- it's now down to 5. 10:21:07 paulc: There are two examples of the case just mentioned by hsivonen, Lachlan's objection to the polyglot document being on the Rec track and obviously if that FO was upheld it'd hardly make sense to take that document into CR. 10:21:40 paulc: Then there's 2 objections to text alternatives. 10:22:00 paulc: These were from May of last year and the 2nd objection fell out of sync with what we now do with extension specs. 10:22:21 ddorwin has joined #html-wg 10:22:38 Lachy, it would be useful 10:22:41 paulc: These five were sent to the Director. We sent mail to him last week and let him know we'd done what he asked and pruned the list as much as possible. These five were confirmed as the objector wanted to maintain them. They'll be dealt with by the Director when we go to CR. 10:23:00 paulc: We'll go to the Director with these docs and these five FOs and we'll come out with 5 or less docs. 10:23:32 Judy has joined #html-wg 10:23:33 mjs: After Lachlan made his formal objection to those docs being Rec track (rather than note), we made up a process that doesn't involve the whole change proposal dance for getting WG decision on what should be normative or not. 10:23:59 mjs: The WG hasn't made a decision on these, the editors chose them being Rec track. No one chose to use that process, and it's unclear if it was because they didn't know the process or wanted FO. 10:24:08 hsivonen: I was unaware of the process. 10:24:41 mjs: It's not too late to do it now. Normativity of the document is a sort-of substantial change. If people didn't know about the process, we could do it now. The process is basically write a tracker issue and then have a preference poll. 10:24:43 trackbot: reload 10:24:54 mjs: I'd rather have a WG decision than throwing it in to the Director's corner. 10:24:56 trackbot, reload 10:25:05 glenn: I was wondering if anyone supports those being Rec track rather than notes. 10:25:07 Milan has left #html-wg 10:25:29 hsivonen, Lachy: process is here: http://dev.w3.org/html5/decision-policy/decision-policy-v3.html#note-vs-rec 10:25:33 Steve: Yes. The doc I edit on alt techniques is normative because the corresponding advice in the HTML 5 spec is normative. 10:25:46 Stevef: The reason I developed the document is because the HTML 5 spec wouldn't change. 10:25:59 glenn: If the HTML 5 spec changed to use non-normative prose would that change your spec? 10:26:02 Stevef: No. 10:26:12 hsivonen, Lachy: I believe that bugs already exist regarding normatively of both of these specs 10:26:34 paulc: Does anyone want the HTML/XHTML to be normative? The Director asked this to be produce that document. 10:26:53 paulc: It'd be ironic if the Director has to be the one to deal with the FO. 10:27:03 paulc: If we ask him if it's normative, I have a feeling we know the answer. 10:27:14 yes please can we get agreement to change the formal title of that document to Polygot 10:27:19 q+ 10:27:23 tomoyuki_ has joined #html-wg 10:27:26 ack mjs 10:27:27 Cameron: Programmatically vs hand authoring, XHTML is easier to author in an algorithmic fashion and it's still good to have techniques for producing XHTML. 10:27:36 q? 10:27:54 trackbot, reload my gin can 10:27:54 Sorry, MikeSmith, I don't understand 'trackbot, reload my gin can'. Please refer to http://www.w3.org/2005/06/tracker/irc for help. 10:28:00 rrsagent, make seconds 10:28:00 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html matt 10:28:04 http://dev.w3.org/html5/decision-policy/decision-policy-v3.html#note-vs-rec 10:29:04 paulc: Looking at this process, which is part of decision policy v3 -- though this text has been there unchanged for some time. We seem to only ever get into the first stage here, where editor's make up a draft and declare Rec or Note. 10:29:11 paulc: We don't seem to get to the stage where people object with the initial decision. 10:29:31 here's a bug on polyglot being normative: https://www.w3.org/Bugs/Public/show_bug.cgi?id=9969 10:29:56 paulc: I think mjs was saying it might be better to have a sense of the WG before going to the Director. Aren't we going to get that sense when we go to CfC on the documents? 10:30:13 paulc: You are suggesting we ask it so we don't get objections at CfC so we can ask it separately? 10:30:53 mjs: There might be people who are OK with it going to CfC either way and there may be people who object at the FO level until the end, even though the question has never gone to the full WG to decide. It's skipping a step to go from Editor's decision to Director without having the WG decide. 10:31:02 mjs: I think it'd be cleaner to do it that way. 10:31:17 q? 10:31:23 Norbert has joined #html-wg 10:31:30 glenn: Agree with mjs on that. Are the last two FO's the same? 10:31:35 paulc: No, there are two objections in one email. 10:31:44 rotsuya has joined #html-wg 10:32:19 paulc: What if we did two CfCs on those two documents? 10:32:24 sgodard has left #html-wg 10:33:22 mjs: You can't have a CfC without knowing what the consensus position might be. We usually do CfCs when we think we know the default position and make others argue for it to not be. We could have a CfC and then still have an FO and *scribe fail* 10:33:37 q+ 10:33:41 David_MacD_Lenovo has joined #html-wg 10:33:46 paulc: If we did a vote and get only 10 responses, vs a CfC where we get 40. What if the vote was 4 and 4 or 6 and 4. 10:34:05 mjs: The process clearly says it's a preference poll because it's a process not a tech decision, so it's by individual not by org. 10:34:16 mjs: It's really not much more complex than a CfC. 10:34:21 s/last two FO's the same/last two FO's the same document/ 10:35:12 and here's a bug on alt techniques being normative: https://www.w3.org/Bugs/Public/show_bug.cgi?id=12726 10:35:15 paulc: The suggestion on the floor then would be to do two separate preference polls immediately on whether the two drafts (XHTML guidelines and Alt techniques) whether both of those should be rec track. 10:35:41 ack hsivonen 10:35:48 hsivonen: So did the chairs decide that there's no reason to invoke the process button? 10:35:52 paulc: Yeah. 10:36:42 hsivonen: Cameron has said that it's easier to algorithmically produce XHTML, but I've got experience in this that shows that's not true. It's actually easier to put an HTML serializer at the end of the pipeline than try to teach a generic XML producer to learn polyglot. 10:37:07 hsivonen: A generic XML tool won't produce polyglot and polyglot makes it harder to serialize than to use a serializer that uses HTML. 10:37:30 Joshue108 has joined #html-wg 10:37:35 +q 10:37:43 ack Stevef 10:38:04 Stevef: Say the document gets changed to a Note that I edit, then we still have normative text in the HTML 5 spec, then when do I get to make a decision going forward? 10:38:22 paulc: That's one of the arguments going into it, and you could object to HTML 5 going to CR. 10:39:05 paulc: That's step one. mjs would it be useful for the co-chairs to follow-up with a note to the Director saying we're continuing to work on these items. He gave us homework and if we change our mind we should tell him. 10:39:07 mjs: Yes, we should probably tell him to hold off on those as the participants in those want to get a WG decision. 10:39:34 mjs: The process set up for this does require having supports for and against having these on Rec track each write a brief rationale. 10:39:38 mjs: Do we have that for each spec? 10:39:49 Cameron: I'll prepare a rationale on the pro side of polyglot. 10:39:54 hsivonen: I'll write one against since it's my objection. 10:40:11 paulc: Does anyone in the room want to write why Alt text shouldn't be on the rec track? 10:40:13 Lachy: Yes, I can do it. 10:40:21 Stevef: I'm willing to make a statement for it. 10:40:38 mjs: You can start writing those now, send them to public-html and the sooner we get that done the sooner we can get it done quickly. 10:40:38 q? 10:40:40 Cameron: I'll help if you'd like 10:40:56 mjs: Wednesday of next week say? They can be short, a paragraph. 10:41:18 Cameron: Can I have two weeks? 10:41:24 mjs: We'd need another volunteer then. 10:41:24 ack Joshue 10:41:29 Cameron: I'll see what I can do. 10:42:01 Joshue108: The alt techniques doc is a substantive document and I suggest the WG read it thoroughly before making a decision. I'm highly concerned that it gets drowned in the WG process. 10:42:41 matt: You can also FO for it to be Rec track, so you still have a way out. 10:42:54 paulc: The idea is to get some indication to give to the Director. 10:43:06 mjs: I'll write the Director with the current status. 10:43:22 paulc: I don't think the formal objections are going to go away, so I'll consider this item covered. 10:44:05 ch has joined #html-wg 10:44:39 paulc: So I think we have the five docs that will go to CR and decided the WG determined what to do on polyglot and alt-text. Now let's talk about Web authors, differences, Platform Accessibility APIs, and the Markup Language. 10:45:26 paulc: When the base core spec goes into CR, what should happen with the Web Authors and diffs doc. 10:45:45 MikeSmith: The diffs doc isn't rec track and can just be a WD, at some point we'll have to decide what to do with it. 10:46:09 paulc: It says it's on the Note track. When we publish this do we base i-- 10:46:31 MikeSmith: I'd say we need to republish the author doc. We don't have complete agreement that it should be a Rec track doc. I don't believe it should be personally, but others do. 10:46:53 MikeSmith: Simon is working on the diffs doc, it'd be a lot of work to do another version. I'm not sure it's worth the time to do it as there aren't going to be many differences that are just editorial. 10:47:20 paulc: The high bar would be to publish both as WDs as we go to CR, but I'm hearing it's not important for the diffs doc. 10:47:36 Simon: I don't mind redoing it for this publication. 10:47:45 cyns has joined #html-wg 10:47:47 paulc: So we should republish both as a WD? 10:47:51 SimonPieters: I believe that makes sense. 10:47:56 q+ 10:48:09 paulc: So that leaves us with HTML the Markup language, Mike? 10:48:12 MikeSmith: I'll do it. 10:48:21 paulc: So we'll publish the Markup Language as a WD. 10:48:28 q? 10:49:04 q? 10:49:04 ack next 10:49:07 sakkuru_ has joined #html-wg 10:49:09 paulc: The last one is the HTML Accessiblity API guide. This is a DW and hasn't gone to LC. 10:49:21 paulc: In some ways it's on a different timeline than other docs. What are the next steps? 10:49:44 cyns: It's not ready for LC. It was originally conceived as a Note, but we'd like it to go to Rec track. 10:49:52 sakkuru has joined #html-wg 10:50:11 paulc: I don't see why this would have to be co-published. 10:51:02 Judy has joined #html-wg 10:51:17 cyns: It's in active development so there are changes all the time. I don't see a reason not to when we go to CR on the other 3 that we would also publish the Accessiblity API as a draft as well. 10:51:39 cyns: We have a few big changes that we were holding off on for the heartbeat draft, but we can get those in. Late November? 10:52:02 paulc: We'll know better after this meeting. You said it isn't on the rec track, but you want it to be? There's nothing in the SotD to say it's not, which means by default it is. 10:52:14 cyns: That's fine, I know there was some discussion of it. 10:52:34 paulc: There is a procedure for someone to object. The situation is that the Editor's have proposed that it be on the Rec track and no one has objected. 10:52:39 cyns: Great. 10:52:50 daq? 10:52:50 paulc: So we have 9 documents, 5 CRs and the rest as WDs published at the same time. 10:52:54 q? 10:53:06 paulc: Objections to that? 10:53:10 paulc: OK. 10:53:27 rrsagent, draft seconds 10:53:27 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html matt 10:53:37 David_MacD_Lenovo has joined #html-wg 10:54:03 paulc: Given that we've talked about having a preference poll about alt-techniques and polyglot, I say darobin should hold off on working on them. 10:54:08 darobin: Happy to oblige. 10:54:23 paulc: We've done FOs. Now CR exit criteria. 10:55:01 paulc: The CR exit criteria were proposed for Plan 2014, if there are no objections I won't review this now. The docs will point at the CR exit criteria. darobin do the SotDs do that? 10:55:50 darobin: I don't believe it does. I don't know if we're allowed to point to them or if we have to include them. 10:56:37 paulc: The 3 CR drafts need to be amended to have the CR exit criteria. 10:56:42 exit criteria: http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html 10:58:30 +? 10:58:35 q? 10:58:36 q+ jgraham 10:58:45 q+ 10:58:53 q+ 10:58:54 q? 10:59:04 paulc: Features at Risk. Does anyone object to the items on the list of Features at Risk? Are there any items missing from the list? 10:59:04 -> http://www.w3.org/html/wg/wiki/index.php?title=HTML5.0AtRiskFeatures Features at Risk 10:59:15 q? 10:59:28 ack jg 11:00:12 jgraham: I have a general point and a specific point. I am wondering if we have some defined criteria by which we decide what can be on this list or can't be on this list? So far it seems like anything that people have suggested has gone on the list. That doesn't seem like great criteria. 11:00:52 paulc: I refer to this as a draft list and I believe your characterization is correct in that it's a wiki and that anyone who wanted to add something to the list did add it. Your second question is about procedure and we do need to get to consensus on what the features at risk are. 11:01:36 paulc: When we do go to CfC for CR, there will be two elements: documents you can look at, which include explicitly the list of features at risk, and it will also explicitly ask whether we have consensus on those features at risk. 11:01:46 LeonieWatson has joined #html-wg 11:02:16 paulc: What principles we use for what's on the Features at Risk is that it's not toxic to have things on the Features at Risk list because the criteria is if we had interop on those features. 11:02:34 paulc: Having the Features at Risk has actually caused people to implement those features so they don't get cut rather than the other way around. 11:03:16 jgraham: For several of the things on those lists I believe we already have multiple, largely interoperable implemented features. I don't think we should put anything on the list when they've already become part of the interoperable Web. 11:03:37 q+ to talk about registerProtocolHandler 11:03:43 jgraham: Specifically I'm looking at registerProtocolHandler. We've got implementations. I don't think it's appropriate to call it at risk from a spec point of view. 11:03:52 MikeSmith: I put it there. 11:04:12 gitbot has joined #html-wg 11:04:12 [13html] 15darobin pushed 3 new commits to 06CR: 02https://github.com/w3c/html/compare/77652fdd84fc...1cd972ab1a00 11:04:12 13html/06CR 149d6fa52 15Robin Berjon: bp conflict 11:04:12 13html/06CR 14b81e1be 15Robin Berjon: bp conflict 11:04:12 13html/06CR 141cd972a 15Robin Berjon: appcache at risk; CR exit criteria 11:04:12 gitbot has left #html-wg 11:04:13 rrsagent, make minutes 11:04:13 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html hbang 11:04:19 MikeSmith: I didn't add it because I felt strongly about it other than Larry Masinter brought it up. 11:04:26 MikeSmith: I'm willing to retract it. 11:05:00 plh: I would object to removing that from the list with my IETF hat on. The IETF do have concerns about that and I'd like it to remain on the list while we're working it over with IETF. 11:05:12 plh: Not because of technical issues. 11:05:21 darobin: It's about potential security risk? 11:05:36 plh: Yes. I don't want to have to worry about having to remove it without it being marked Feature at Risk. 11:05:57 jgraham: If it's such a serious concern that it'd have to be removed from implementations, even then it doesn't seem like it should be marked as a Feature at Risk. 11:06:29 darobin: The at risk process lacks granularity. We might have to change it substantially, but it'd still have to be marked a Feature at Risk if we do have to blow it up. 11:06:31 q? 11:06:51 hsivonen: Can someone explain to me what the purpose of at risk is? 11:07:12 hsivonen: jgraham said there are interoperable implementations, but it appears you can get on the list from vague IETF concerns. 11:07:37 hsivonen: It doesn't seem like there are reasons for Features at Risk. Why not put the whole spec under Features at Risk? 11:07:54 Bert has left #html-wg 11:08:27 Wonsuk has joined #html-wg 11:09:04 hsivonen: I believe all of the navigation stuff is potentially not interoperable exactly as written, so if we took the criteria of having stuff that might not be interoperably implemented or implementable, then it should be on that list. It'd be horrible to remove it. 11:09:43 darobin: I don't disagree with you. I'd like to get this done without too much process. To answer your question: if we have to make some changes because interoperability problem then we're good to go if they're not too radical. I'd rather not have registerProtocolHandler be on the list because of IETF, but this might just be a good thing to be friendly to them. 11:09:44 Wonsuk has left #html-wg 11:09:59 paulc: Is there somewhere on public-html where IETF have listed their concerns? 11:10:12 plh: We talked about it on our last coord call and someone took an action to do it and send it to us. 11:10:15 darobin: Timeframe? 11:10:17 plh: I don't recall. 11:10:24 paulc: So, no. 11:10:38 paulc: How are we going to evaluate anything without seeing it? 11:10:59 it would be editorially horrible to remove navigation, but substantively, I don't want a REC that requires Web-incompatible navigation 11:11:24 plh: I have shared all I know, and said to them write down what you don't like. And that the best course of action at the time was to mark it Feature at Risk in that section. 11:11:30 kenji has left #html-wg 11:11:43 q? 11:12:02 paulc: I said 15 minutes before the end we'd switch to the mailing list discussion, so I'm going to pop up a level and ask: is there anything on this list of Features at Risk that people object to? And are there anything missing from the list? 11:12:21 paulc: I answered the 2nd question myself with reference to CSS item and I believe scoped-stylesheets needs to be added. 11:12:23 plh: It's there. 11:12:47 paulc: We've had some discussion on objections to it, specifically registerProtocolHandler, was there any other? 11:12:55 jgraham: AppCache is interoperably implemented -- 11:13:23 darobin: The reason it's there is purely procedural: we want to have the option of removing it and putting it in WebApps. If WebApps did a delta on this it might become a complete mess. 11:13:26 jgraham: That makes sense. 11:13:33 q+ 11:14:24 paulc: We have three examples of principles of what goes on the list: AppCache because it might be done in an extension spec, non-interoperable items and the registerProtocolHandler is that we may get evidence from an external organization that there are significant security problems and that it might need to be removed even if there is interop. 11:14:32 paulc: Is there anything missing from the list? 11:14:33 q? 11:14:54 hsivonen: What's the consequence of something missing on the list and then not fulfilling the CR exit criteria. I believe navigation won't fulfill the CR exit criteria. 11:15:08 paulc: If you have something on the list that wasn't identified you'd have to go back to LC. 11:15:28 q+ 11:15:29 paulc: If you read Plan 2014, we're planning on doing that. We're not anticipating getting this list correct. We're going into CR for a long time on a large spec. 11:15:51 -> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18975 registerContentHanlder and registerProtocolHandler open huge security and privacy holes (bug raised by Larry Masinter) 11:16:26 paulc: The LC would be short, probably just a month. But any item we failed to get interoperable evidence we'd have to go back to LC. 11:16:29 q- 11:16:31 hsivonen: Why have the list? 11:16:41 paulc: It helps drive implementations. 11:16:51 gitbot has joined #html-wg 11:16:51 [13html] 15darobin pushed 1 new commit to 06html5_canvas_CR: 02https://github.com/w3c/html/commit/d46707fc59505c7155f6be90681451306716bbf8 11:16:51 13html/06html5_canvas_CR 14d46707f 15Robin Berjon: CR exit criteria 11:16:51 gitbot has left #html-wg 11:16:55 rrsagent, draft minutes 11:16:55 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html JonathanJ1 11:16:56 kawakami has joined #html-wg 11:16:58 plh: And it draws attention to the implementors. Having the entire spec be in Features at Risk won't do that. 11:17:46 cjones: ?? on the list doesn't meet the CR exit criteria. I'd like to put either a broad form submission algorithm or a method based switching with FTP and javascript means. 11:17:58 SimonPieters has joined #html-wg 11:18:06 cjones: I'll add it right now. 11:18:10 -> http://lists.w3.org/Archives/Public/public-ietf-w3c/2012Sep/thread.html#msg4 web+ and registerProtocolHandler 11:18:15 q? 11:18:39 a1zu has joined #html-wg 11:19:04 paulc: We're not going to make any decisions today, but we need it on the list as quickly as possible. 11:19:04 ack next 11:19:04 glenn: In the test suites I don't see any tests for ruby or the algorithm defined. I think that should be on this list as well for now. 11:19:33 Chris: There are parser tests which does the syntax and the semantics and layout are non-normative. 11:19:44 paulc: And if it's informative material you don't need tests. 11:19:47 q? 11:19:54 ack next 11:19:56 plh, you wanted to talk about registerProtocolHandler 11:20:00 ack next 11:20:26 SimonPieters: hsivonen asked before what's the purpose of this list, and you said to drive implementations. That suggests that this is to micromanage the priority of implementations in browsers. 11:20:28 kawakami_ has joined #html-wg 11:20:28 q+ 11:20:29 q+ jgraham 11:20:50 SimonPieters: I don't think it's appropriate to do that. If we want flexibility to take stuff out for various reasons then it makes more sense to put the whole spec on the list. 11:20:53 q+ 11:21:01 q+ to talk about putting the whole spec in the list 11:21:02 silvia has joined #html-wg 11:21:14 there is a rather long "segmentation and categorisation of content" algorithm specified for ruby at http://dev.w3.org/html5/spec/single-page.html#the-ruby-element 11:33:34 RRSAgent has joined #html-wg 11:33:34 logging to http://www.w3.org/2012/11/02-html-wg-irc 11:33:46 paulc: Then 15 minutes on public-html list and it's use. 11:33:57 paulc: Won't make decisions but get opinions on the table then do the testing session. 11:34:06 rrsagent, draft seconds 11:34:06 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html matt 11:34:18 DanielAustin has joined #html-wg 11:34:20 paulc: Scribe? 11:34:25 rick: I'll do it. 11:34:35 paulc: Recess. Please be back before 2pm. 11:34:59 http://www.w3.org/html/wg/wiki/TPAC2012 11:46:38 DomJones has joined #html-wg 11:53:36 r12a has joined #html-wg 11:56:37 DomJones has left #html-wg 12:15:05 Yoshiharu has joined #html-wg 12:16:18 tomoyuki has joined #html-wg 12:17:59 Shinji has joined #html-wg 12:19:26 Arno has joined #html-wg 12:20:00 a12u has joined #html-wg 12:22:56 naomi has joined #html-wg 12:27:17 yamaday has joined #html-wg 12:28:40 hbang has joined #html-wg 12:28:51 rrsagent, make minutes 12:28:51 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html hbang 12:34:09 kenji has joined #html-wg 12:35:25 naomi has joined #html-wg 12:36:23 Kiyoshi_ has joined #html-wg 12:38:07 MichaelC_ has joined #html-wg 12:39:53 Yoshihiro has joined #html-wg 12:41:23 kotakagi has joined #html-wg 12:41:29 Stevef has joined #html-wg 12:41:55 takuya has joined #html-wg 12:42:37 Wonsuk has joined #html-wg 12:45:14 glenn has joined #html-wg 12:47:36 yoh has joined #html-wg 12:50:06 pal has joined #html-wg 12:50:07 trackbot has joined #html-wg 12:50:21 giuseppe has joined #html-wg 12:50:26 giuseppe has left #html-wg 12:50:28 giuseppe has joined #html-wg 12:50:31 edoyle has joined #html-wg 12:50:43 r12a has joined #html-wg 12:51:27 dsinger has joined #html-wg 12:51:29 jcraig has joined #html-wg 12:52:38 Norbert has joined #html-wg 12:53:39 Stevef has joined #html-wg 12:54:01 richardschwerdtfeger has joined #html-wg 12:54:53 adrianba has joined #html-wg 12:55:14 robint_ has joined #html-wg 12:56:36 cabanier has joined #html-wg 12:56:43 cabanier1 has joined #html-wg 12:59:38 shoko has joined #html-wg 12:59:49 SimonPieters has joined #html-wg 13:00:02 MartinSoukup has joined #html-wg 13:01:51 Milan has joined #html-wg 13:01:52 mjs has joined #html-wg 13:02:08 takuya has joined #html-wg 13:02:34 markw has joined #html-wg 13:02:51 ddorwin has joined #html-wg 13:03:29 Magnus_Olsson has joined #html-wg 13:03:32 glenn has joined #html-wg 13:03:46 scribenick: cabanier 13:04:09 dsinger has joined #html-wg 13:04:18 krisk has joined #html-wg 13:04:23 we need to put in a call to implementation 13:04:35 change to the agenda to go over this 13:05:07 topic: minimum period for cr 13:05:08 fumitakaW has joined #html-wg 13:05:18 Present+ ddorwin 13:05:31 paulc: I will go over the notes 13:05:36 jens has joined #html-wg 13:05:36 DanielAustin has joined #html-wg 13:05:48 paulc: …we need a mimimum CR period 13:05:58 paulc: … first item is plan 2014 13:06:16 jkiss has joined #html-wg 13:06:30 paulc: … we go into cr 4q 2012 and LCF 2014 13:06:34 darobin has joined #html-wg 13:06:39 paul: … this is the maximum CR 13:07:12 paulc: …another option is the one year option. minimum length is 12 month CR 13:07:30 paul: …if we choose the maximum cr, we can't get out of CR sooner 13:07:54 paulc:… option c is some earilier date 13:08:07 paulc: … which is 2013 13:08:12 present+ kris_krueger 13:08:14 paulc:… for some drafts 13:08:25 paulc: … such as canvas and microdata 13:08:58 Jirka has joined #html-wg 13:08:58 q+ 13:09:05 MikeSmith has joined #html-wg 13:09:08 paulc: …we can debate if we want the same data for everyone or separate dates 13:10:11 mjs: for the HTML5 spec, we already committed implicitly ourselves to a specific date 13:10:24 mjs: … we can make if different for different spec 13:10:54 Mark_Vickers has joined #html-wg 13:11:22 jcraig has joined #html-wg 13:11:27 paulc: so we would pick the long option for the HTML core spec 13:11:28 q+ 13:11:43 ack mjs 13:11:50 ack krisk 13:11:51 chris: the canvas one is the one that we can finish earlier 13:12:00 chris: … we have a lot of tests 13:12:12 eh? 13:12:13 chris: … I have no opinion on microdata 13:12:25 have the microdata dom api tests not been checked into the repo? 13:12:25 s/chris:/krisk:/g 13:13:12 paulc: I hear sentiment for a earlier cr exit for canvas 13:13:23 q+ 13:13:24 Here is the Microdata tests from OPERA not tantek http://www.w3c-test.org/html/tests/submission/Opera/microdata/ 13:13:46 q+ 13:13:47 krisk, ah OK those are the ones I was thinking of 13:13:58 Takahiro has joined #html-wg 13:13:58 paulc: … so, the current proposal is that for HTML5 we will say the minimum period is june 2014 and for canvas/microdata it's 6 month period 13:13:59 r12a has joined #html-wg 13:14:18 mjs: I would like to give a counterpoint for canvas 13:14:25 Norbert has joined #html-wg 13:14:35 LeonieWatson has joined #html-wg 13:14:46 mjs: … there are several items on the at risk page 13:15:04 mjs: …especially hit regions 13:15:20 q? 13:15:26 ack mjs 13:15:26 ack mjs 13:15:53 q- 13:16:05 adrianba: I have one comment 13:16:40 adrianba: … the polyglot spec could make progress more quickly 13:17:06 ack adrianba 13:17:22 Philip: ... 13:17:35 q+ 13:17:42 q+ 13:18:01 i/Philip: .../adrianba: what happens when the spec gets to PR - does it wait for Rec?/ 13:18:27 ack cabanier 13:18:31 s/Philip: .../plh: the director has said that if you can show the features you depend on are stable then you can go to rec/ 13:19:17 cabanier: my fear is that the progress will be so long that by the time the spec is released it will be obsolete 13:19:27 cabanier1: …because the canvas specification is moving fast 13:19:37 ack mjs 13:19:58 annevk has joined #html-wg 13:20:00 Travis has joined #html-wg 13:20:02 q+ 13:20:20 mjs: polyglot has no user agent conformance. It just describes rules. I don't know how to write exit criteria for it 13:20:36 great reason for not having Polyglot on the REC track 13:20:51 a1zu has joined #html-wg 13:20:57 paulc: any other opions 13:21:05 ack adrianba 13:21:05 plh has joined #html-wg 13:21:15 adrianba: I didn't mean that polyglot requires parsing behavior 13:21:43 adrianba: … so this would be an argument for waiting 13:21:59 rubys has joined #html-wg 13:22:01 paulc: for HTML5, maciej wants for go for the long time of 2014 13:22:10 s/requires parsing behavior/requires parsing behavior in user agents/ 13:22:26 paulc: for the other items, it's unclear. 13:22:50 paul: I heard some sentiment to move early except Maciej 13:23:04 Travis has left #html-wg 13:23:04 Marcos has joined #html-wg 13:23:07 paulc: hit testing is the one he specifically identified 13:23:08 s/so this would be an argument for waiting/but writing a spec to map two parsers relies on those parser definitions being stable - if they were in flux then that would be an argument for not moving forward more quickly/ 13:24:53 maybe polyglot and alt techniques editors should first define their CR exit criteria 13:25:08 paulc: now we have to find the exit criteria with the editors 13:25:25 paulc: and they have to find a minimum period 13:25:25 Milan has left #html-wg 13:26:15 paulc: … we won't preclude to go fast on html5, canvas and microdata to CR if the other two are slower 13:26:25 paulc: … we can go CR with any spec 13:27:52 cabanier has joined #html-wg 13:28:15 topic: mailing lists 13:28:25 q? 13:28:28 q+ 13:28:38 mjs: one thing I've been hearing, is that people want to do work outside the working group 13:28:54 mjs: … and complaints that the list is too noisy 13:29:22 mjs: … my job is to fix this. If every spec has its own list, it makes it very hard to follow 13:29:43 mjs: … I would like to hear what is bad about public-html 13:29:52 +q 13:29:55 q+ 13:30:03 robin: bugzilla email 13:30:29 JohnS has joined #html-wg 13:30:41 mjs: poll -> 15 people 13:30:47 paulc has joined #html-wg 13:31:08 Marcos: too much email 13:31:20 q+ darobin 13:31:40 mjs: poll -> 2-3 people 13:31:42 kotakagi has joined #html-wg 13:31:54 koji has joined #html-wg 13:31:54 hsivonen: failure to ban people 13:32:09 hsivonen: people should be banned immediatly for one week 13:32:11 +1000 milion to what hsivonen just said 13:32:26 hsivonen: or people that keep going over the same thing 13:32:27 jcraig has joined #html-wg 13:32:38 drublic has joined #html-wg 13:32:51 mjs: failure eliminate trolls -> 10 people 13:33:15 mjs: failure to stop ratholes -> 10 people 13:33:20 ack hsivonen 13:33:21 q+ 13:33:52 dbaron has joined #html-wg 13:34:21 adrianba: the WG has a broad charter and diverse membership. it's hard for people to identify where they can contribute 13:34:42 Shinji has joined #html-wg 13:34:55 adrianba: … I agree we don't want to fragment discussion but there should be a way to group topics 13:34:58 q+ to say better subject tagging would help. {agenda}, [aapi] and [] are the few I see. ideally, emails are tagged with issues or actions, so they are associated with something 13:35:15 ack Marcos 13:35:23 ack adrianba 13:35:47 mjs: too hard to follow/small set of topics of interest -> 12 people 13:35:59 q- 13:36:10 mjs: … there are 2 other WGs that have this issue. 13:36:22 mjs: … and they are happy with their mailing list 13:36:46 robin: even though webapps is diverse, it's all about API's 13:36:57 q? 13:37:00 ack darobin 13:37:01 ack darobin 13:37:03 adrianba: perfectly happy is a bit over generalized 13:37:05 WebApps 1) www-dom 2) public-script-coord 3) public-webapps 4) good use of Bugzilla 5) too hard to follow for trolls 13:37:32 darobin: moving process related discussion to another list would help 13:37:35 www-style also does subject-tagging 13:38:02 paulc: can you give an example? 13:38:23 darobin: in dap we did that 13:38:26 +1 to darobin 13:38:50 q+ 13:38:59 mjs: some people have told me that they don't want to see process related email 13:39:15 mjs: mix of process and technical ->15 13:39:26 q+ 13:39:32 ack SimonPieters 13:39:33 JonathanJ1 has joined #html-wg 13:39:40 ack hsivonen 13:39:51 q+ jgraham 13:40:03 hsivonen: the decision process 13:40:17 shige__ has joined #html-wg 13:40:18 hsivonen: it should be about getting stuff done. 13:40:34 hsivonen: there should be no animosity between the chairs and the members 13:40:44 JonathanJ1 has joined #html-wg 13:40:50 s/the decision process/the decision process seems optimized to make the chairs seem impartial/ 13:40:54 hsivonen: chairs are trying to protect themselves from criticism 13:41:21 mjs: I think things have changed. there might still be some distrust. 13:41:22 q? 13:41:44 s/changed/changed; in first 2 years of WG, lots of traffic was wrt decisions being unfair/ 13:41:48 mjs: …is this relevant to the question? 13:41:52 kotakagi has joined #html-wg 13:42:10 hsivonen: if the chairs make more decisions, it would make the list less process heavy 13:42:10 +1 to hsivonen 13:42:42 mjs: so you suggest that the chairs should decide contentious issues? 13:42:45 Joshue108 has joined #html-wg 13:43:19 hsivonen: maybe no for contentious issues but for editorial ones. There is no reason to escalate those. 13:44:17 Kiyoshi_ has joined #html-wg 13:44:29 mjs: I agree for small issues. however it can become contentious if you decide an issue is small 13:44:39 giuseppe has joined #html-wg 13:44:40 q? 13:45:33 paulc: so you're looking for less process by making earlier decisions and using the decision policy for big issues? 13:45:42 paulc: … and you think that is important? 13:45:46 hsivonen: yes 13:45:58 paulc: because you believe this creates less process? 13:46:02 hsivonen: yes 13:46:21 q? 13:46:37 mjs: who believes that this decision process is important -> 10 people 13:46:45 glenn: how many people are satisfied with the list? 13:46:56 naomi has joined #html-wg 13:47:27 mjs: satifaction poll -> 2 people 13:47:29 ack Stevef 13:47:56 q+ 13:47:58 Travis has joined #html-wg 13:48:18 q+ 13:48:20 Stevef: maybe having a digest would be helpful. so you inbox is not filled up 13:48:45 David_MacD_Lenovo has joined #html-wg 13:49:04 tomoyuki_ has joined #html-wg 13:49:18 jgraham: we have to make sure to not fragment the knowledge 13:49:31 jgraham: …because things are moved to other lists 13:49:42 odinho: yes 13:49:42 ack jgraham 13:49:54 richardschwerdtfeger has left #html-wg 13:50:12 ack hsivonen 13:50:14 mjs: do people that this is a current/future problem -> 7 people 13:50:49 hsivonen: it could be that the solution is worse than the problem. (solution = multiple mailing list) 13:50:51 s/having a digest/having a digest for administrativa/ 13:51:00 ack paulc 13:51:34 paulc: I want to point out that you're autosubscribed to the announce, public and html list 13:51:46 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html plh 13:52:02 karl: talking about auto digest 13:52:22 paulc: it used to be that public-html got every update on bugs 13:52:25 s/karl:/karl,/ 13:52:41 paulc: …now it seems that people don't even want to see the new bugs 13:53:04 MyNickName has joined #html-wg 13:53:17 paulc: people want public-html to be heavily about technical discussion 13:53:36 paulc: we could move the CFC's to public-announce 13:53:58 paulc: … I prefer not to get digests because it's not helping 13:54:28 paulc: the chairs could do a better job of starting technical discussion 13:54:56 q? 13:55:31 glenn: there have been 9500 message on www-style. public-html it's 3500 13:55:57 glenn: …this year so far. there's far less traffic on this list 13:56:04 also good evidence that people are staying away from public-html 13:56:18 darobin: I think people are complaining about the content (process decisions etc) 13:56:37 mjs: is there another distinct problem? 13:56:51 Norm has joined #html-wg 13:56:54 *silence* 13:57:20 mjs: 13:57:48 mjs: I want it to be a great place for technical discussion. Thanks for the feedback. 13:58:48 Travis_ has joined #html-wg 13:59:03 Topic: Bug 14689 13:59:07 https://www.w3.org/Bugs/Public/show_bug.cgi?id=14689 13:59:09 nkic has joined #html-wg 13:59:23 Norm: https://www.w3.org/Bugs/Public/show_bug.cgi?id=14689 13:59:42 kinji_ has joined #html-wg 13:59:48 Norm: there is no expectation for a normative change 14:00:01 norm: look at comment 35. 14:00:12 -> https://www.w3.org/Bugs/Public/show_bug.cgi?id=14689#c35 Comment 35 14:00:22 norm: the second to last comment 14:00:31 https://www.w3.org/Bugs/Public/show_bug.cgi?id=17976#c2 seems relevant for what needs to be done 14:00:33 mjs: could you give an overview of the technical issue 14:00:59 RRSAgent, make minutes 14:00:59 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html MikeSmith 14:02:12 there we go http://w3cmemes.tumblr.com/post/33421267632/scumbag-steve-is-worried-browsers-will-stop 14:02:16 q? 14:02:22 (old meme) 14:02:23 norm: xml core would like a non-normative note that this issue exists 14:02:29 q? 14:02:30 q+ 14:03:08 q+ mjs 14:03:10 ...today browsers support text/xslt in the PI at the top of a xhtml document 14:03:24 Proposed solution is in: https://www.w3.org/Bugs/Public/show_bug.cgi?id=14689#c35 14:03:26 tomoyuki_ has joined #html-wg 14:03:29 s/xslt/xsl/ 14:03:34 q+ to suggest removing the mention of "or application/xslt+xml" 14:03:39 -> http://www.w3.org/TR/xml-stylesheet/ Associating Style Sheets with XML documents 1.0 14:03:40 again, the actual solution here is addressing https://www.w3.org/Bugs/Public/show_bug.cgi?id=17976#c2 ... 14:03:48 I mean, if you want to solve the problem 14:03:51 you know 14:03:54 q? 14:04:08 ack adrian 14:04:12 Judy has joined #html-wg 14:04:31 adrianba: could you not fix the document: http://www.w3.org/TR/xml-stylesheet/ 14:04:42 q+ to see if mentioning https://www.w3.org/Bugs/Public/show_bug.cgi?id=17976#c2 has any effect 14:05:04 -> https://www.w3.org/Bugs/Public/show_bug.cgi?id=17976#c2 14:05:08 darobin: I think it could start as an extension spec 14:05:18 darobin: can we agree to a non-normative note? 14:05:23 ack mjs 14:05:23 ack mjs 14:05:48 Bert has joined #html-wg 14:05:48 mjs: it's my recollection when we did xslt, this was the spec we looked at 14:05:59 q- later 14:06:18 mjs: …I don't know what problem we're solving with the non-normative note since we never needed it before 14:06:38 Norm: my recollection was that it was removed at one point 14:06:49 mjs: yes that was an earlier draft of html5 14:07:01 mjs: what problem are you solving: 14:07:14 Norm: since it's non-normative note, I'm not sure 14:07:31 r12a has joined #html-wg 14:08:04 Norm: the point of the HMTL5 spec. We would like to see some hint of this issue to be restored 14:08:34 q+ 14:08:40 mjs: I still don't understand the purpose of the note. why xslt style sheets 14:08:52 mjs: we can leave it up to the editors 14:08:52 q? 14:08:53 q- 14:09:20 q- 14:09:20 The request is to add this text to the following location in the HTML5 spec: http://dev.w3.org/html5/spec/history.html#read-xml 14:09:21 glenn: I support Norm's request and there is some language in the CSS spc 14:09:29 q? 14:09:56 annevk: there is bug 17976 14:10:11 annevk: that lists the solution to this problem 14:10:16 See https://www.w3.org/Bugs/Public/show_bug.cgi?id=17976 14:10:22 q+ 14:10:32 DanielAustin: my proposal is to make this an editorial choice 14:10:46 q? 14:10:59 ack next 14:11:06 ack Jirka 14:11:24 Jirka: there is a document that describes what it should do when it encounters xml 14:12:23 Takahiro has joined #html-wg 14:12:44 Joshue108 has joined #html-wg 14:13:18 q? 14:13:20 s/ it encounters xml/ it encounters xml and xml-stylesheets is not mentioned here although browsers honour it/ 14:13:23 ack hsivonen 14:13:24 hsivonen: I think we can just put the language in there to put the concern that this feature is going to removed at rest. 14:13:25 +1 14:13:27 s/there is a document that/HTML spec / 14:13:30 MartinSoukup has joined #html-wg 14:13:43 +1 to hsivonen 14:14:05 +1 to hsivonen 14:14:20 DanielAustin: I want to insert this note too. Since we use it in our systems 14:14:25 pal has joined #html-wg 14:14:38 DanielAustin: … leaving it out seems like an omission to me 14:15:15 mjs: maybe we should have discussed xslt style sheet processing 14:15:46 dbaron has joined #html-wg 14:15:47 mjs: no interest because lack of time 14:15:50 all: yes 14:16:11 main element spec https://dvcs.w3.org/hg/html-extensions/raw-file/tip/maincontent/index.html 14:16:13 main element rationale http://www.w3.org/html/wg/wiki/User:Sfaulkne/main-usecases#Introduction 14:16:14 data in support of the feature http://lists.w3.org/Archives/Public/public-html/2012Oct/0109.html 14:16:16 topic: the main element spec 14:16:16 examples of use of the main/content id value to identify the main content area of a page http://www.html5accessibility.com/tests/HTML5-main-content/ 14:16:18 data source http://www.paciellogroup.com/blog/2012/04/html5-accessibility-chops-data-for-the-masses/ 14:16:53 Stevef: (listing the specs and the data) 14:17:19 LeonieWatson has joined #html-wg 14:17:23 Stevef: … the idea is that the main element is a simple structure element 14:17:36 Stevef: … it identifies the main area of content of the web page 14:17:59 Stevef: … like article, side, section, etc 14:18:29 Stevef: … but we don't have a marker for the main area because the idea that what is not marked up is the main content 14:18:47 Stevef: … so everything else needs to be marked up correctly 14:19:10 Stevef: … this can tie in with ARIA roles. 14:19:39 Travis_ has joined #html-wg 14:19:41 Stevef: …since we don't have a main element that can map to this role 14:20:32 s/language in the CSS spc/language in the CSSOM spec/ 14:20:37 Stevef: …the main element is a tradition and people have been doing it for a long time 14:20:48 dveditz has joined #html-wg 14:21:08 Stevef: …people create this structure in their mind so why not add it to the structure 14:21:40 fyi, re: HTML vs CSS ML traffic in 2012, see http://lists.w3.org/Archives/Public/public-html/2012Nov/att-0011/mail-list-traffic.htm 14:21:43 Stevef: … Search engines could use it to optimize their algorithms 14:22:00 yoav_ has joined #html-wg 14:22:28 shige_ has joined #html-wg 14:22:29 Stevef: I would like to hear comments. I've had feedback from browser vendors that it's not hard to implement 14:22:39 Stevef: … but there has been not much excitement 14:22:52 Stevef: … however accessibility implementors are 14:23:11 Stevef: … also authors and users are keen on using this feature 14:23:38 fantasai: I believe
was meant for this. What is the problem with it? 14:24:07 q+ 14:24:10 Wonsuk has joined #html-wg 14:24:11 Stevef: you can have many articles on the page. It's a different semantical things 14:24:20 q- 14:24:37 mjs: the main content can't be an article at all. It's semantically wrong to use it for this? 14:24:56 hsivonen: the spec says so too. article is broader 14:25:08 hsivonen: e.g. it is also used for blog comments 14:25:08 mjs: does anyone here think it's a bad idea? 14:25:41 glenn: yes. (However I didn't read the spec) 14:25:48 glenn: it sounds too generic 14:26:12 kinji has joined #html-wg 14:26:23 q? 14:26:25 q+ 14:26:31 Stevef: it used to be called 'main content' but after feedback from people like Maciej we shortened it to
14:27:04 +1 to the main element extension. 14:27:16 SimonPieters: Hixie refuses this idea 14:27:22 q? 14:27:26 ack SimonPieters 14:27:48 cynthia: the main content area is not always an article 14:28:01 q+ DanielAustin 14:28:33 ack danielfilho 14:28:45 ack DanielAustin 14:28:52 q+ 14:28:58 DanielAustin: the majority of authors are doing this. There is a lot of demand for this to create this semantic difference 14:29:23 mjs: does anyone know why hixie doesn't want this? 14:29:49 jgraham: he believes there is no use case for having a separate algorithm. 14:30:02 aka process of elimination 14:30:03 q+ 14:30:04 jgraham: … subtract every element that has no semantic 14:30:18 jgraham: … also known as the scooby doo algorithm 14:30:20 q+ 14:30:33 sgodard has joined #html-wg 14:30:36 everyone: we believe so too 14:30:57 paulc: will that resolve to more than 1 element? 14:31:07 jgraham: yes 14:31:23 dsinger_ has joined #html-wg 14:31:24 Judy_clone has joined #html-wg 14:31:41 q? 14:31:41 q+ 14:31:42 q? 14:31:57 naive question: why not use class or role? 14:31:58 ack Jirka 14:33:03 jirka: Suppose I have a very simple web page with no navigation, etc., just content 14:33:09 Jirka: Does this mean I have to add a
element to it now? 14:33:48 ??: For a11y, need to be able to skip navigation etc. to the beginning of the main content. Currently use e.g. skip links for it 14:33:57 ??:: That's the main use case 14:33:59 q+ 14:34:07 ??: So in your example, you don't need a
14:34:34 s/??/Stevef/ 14:34:46 q- 14:34:53 ack Stevef 14:34:58 Stevef: It's easier to mark up just the
content than to rely on everythign else to be correctly marked up 14:35:17 ack odinho_ 14:35:30 tomoyuki_ has joined #html-wg 14:35:48 odinho: you could say that the main element is not needed by elemination 14:36:01 ack Stevef 14:36:22 odinho: BUT it's much easier for authors to use such a thing and you often find that they already do it 14:36:23 odinho_: You already need such an algorithm for pages that don't have a
14:36:54 odinho: I don't see a problem apart from introducing new HTML elements 14:37:05 odinho: … jumping to the main content would be easier 14:37:25 q+ 14:37:30 odinho: .. especially if different ally tools start implementing it 14:37:42 s/ally/a11y/ 14:38:03 Yoshihiro has joined #html-wg 14:38:09 ack fantasai 14:38:12 yoshiaki has joined #html-wg 14:38:25 ack hober 14:38:25 fantasai: I think these are good points. 14:38:55 hober: I don't have a strong feeling about this. Steve did a great job on researching this 14:39:26 DanielAustin: a really good use case is to strip off content for screen reader 14:39:30 s/??: For a11y/Stevef: For a11y/ 14:39:45 s/??:: That/Stevef: That/ 14:40:22 mjs has joined #html-wg 14:41:53 r12a has joined #html-wg 14:42:44 Norbert has joined #html-wg 14:46:33 Takahiro_ has joined #html-wg 14:46:41 Norm has joined #html-wg 14:47:32 tomoyuki has joined #html-wg 14:55:04 DanielAustin has joined #html-wg 14:58:37 kotakagi has joined #html-wg 15:00:06 jcraig has joined #html-wg 15:00:23 Wonsuk has left #html-wg 15:02:18 shoko has joined #html-wg 15:04:48 Kiyoshi_ has joined #html-wg 15:05:15 dsinger_ has joined #html-wg 15:08:01 scribe:ddorwin 15:08:30 Arno has joined #html-wg 15:08:31 topic: Update on testing TF 15:08:43 kris: presenting slide given to AC 15:09:01 kris: 11907 tests with consensus are correct and valid 15:09:02 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html odinho_ 15:09:26 kris: presents new contributors since TPAC 2011 15:10:16 kris: public-html-testsuite@w3.org list. It's pretty quiet. Feel free to participate. 15:10:36 kris: … new activity: http://testthewebforward.org 15:12:03 kris: Presents Testing Task Force Status showing test results. 17 tests only pass in one implementation. 11 do not pass in any 15:12:22 kris: We do not have enough tests. 15:12:30 kris: … everything at risk needs tests 15:12:46 kris: questions? 15:13:19 Zakim, who's on the phone? 15:13:19 sorry, MikeSmith, I don't know what conference this is 15:13:20 On IRC I see Arno, Kiyoshi_, shoko, jcraig, kotakagi, DanielAustin, tomoyuki, Takahiro_, Norbert, r12a, mjs, Yoshihiro, Judy_clone, sgodard, dveditz, dbaron, Bert, 15:13:20 ... David_MacD_Lenovo, naomi, JonathanJ1, Shinji, drublic, koji, paulc, cabanier 15:13:24 paulc: regarding the page showing test status - what is the correlation of acceptance of tests and pass rates 15:13:44 kris: WebIDL tests haven't been accepted. 15:13:48 q+ 15:14:01 q+ 15:14:21 paulc: If I saw this chart for the unapproved test, I would see more red. Would I see some green? 15:14:42 ??: Yes, some green. Authors of the test usually pass the tests. 15:15:06 ??: … A lot of the passing tests are parsing tests. We have 4 good parsers. 15:15:09 s/??/jgraham/ 15:15:21 ack jgraham 15:15:36 kris: A number of canvas(?) tests. 15:16:00 Mark_Vickers: Do you have a sense of the goal? What is enough? Do you have a sense of coverage? 15:16:03 jkiss has joined #html-wg 15:16:10 plh has joined #html-wg 15:16:26 kris: People have created tests as they add features to their browsers. 15:16:32 ack Mark_Vickers 15:16:36 kris: … What we don't have is tests across the specification. 15:17:11 Philip: Tried to determine what from the specification the tests are trying to cover. 15:17:29 Philip: 2400 files, but only 700 are covered 15:17:38 q+ 15:18:20 Philip: Some of the test files have many tests in them 15:19:35 On screen is a table showing the data. Includes caniuse data in column 3. 15:20:04 rrsagent, make minutes 15:20:04 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html adrianba 15:20:24 cyns has joined #html-wg 15:20:28 q? 15:20:34 ack jgraham 15:20:39 s/scribenick: cabanier/scribenick: cabanier1/ 15:20:41 q+ to ask about aria integration testing 15:20:43 rrsagent, make minutes 15:20:43 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html adrianba 15:20:47 jgraham: the goal of the W3C is to lead the way. One of the goals is to make sure the standards are interoperable. More than getting individual to standards, we want to make them interoperable. We want to get rid of bugs that make it difficult to write interoperable apps. 15:21:28 jgraham: If there are tests that show a problem with interop, we should have a way of accepting that test regardless of process. 15:21:59 jgraham: It's not necessarily clear how we balance those two concerns. We don't want to be dropping/refusing tests because we have an immediate goal to get to Rec. 15:22:14 q+ 15:22:20 kris: With the 2014 plan, we have a risk that we end up with tests that no one passes or only one passes 15:22:26 q? 15:22:33 ack Mark 15:22:45 q? 15:23:14 Mark_Vickers: I think we have to split off the goals of testing for the purpose of the publication process vs. testing for developer support (i.e. webplatform.org). I wouldn't want to have to burden publication by saying every possible test. I would like us to take on the non-spec goal. 15:23:41 jgraham: I agree, but we have to have a way of separating out the tests that everyone has to pass before we get to rec. 15:23:58 ack cyns 15:23:58 cyns, you wanted to ask about aria integration testing 15:23:59 ???: We have to have the discipline to continue doing that 15:24:16 sorry i jumped the queue 15:24:23 cyns: Asks about Aria. It's being tested against HTML4, not HTML5. We have a huge set of tests. 15:24:41 q? 15:25:03 kris: Currently all tests are in one big folder that spans multiple specs. we should separate them out. 15:25:14 kris: I'm not sure where the accessibility tests are. 15:25:23 kris: We really need to submit them to the repository. 15:25:50 cyns: They are a bit complicated 15:25:52 s/???/Doug_Schepers/ 15:25:59 cyns: Michael Cooper is the person to talk to. 15:26:09 kris: Polyglot has a similar problem. 15:26:31 kris: Problems with screen readers on browser/OS combinations 15:26:42 cyns: We're not using screen readers. 15:26:46 shepazu has joined #html-wg 15:27:11 s/Doug_Schepers/shepazu/ 15:27:17 kris: Could definitely use experts on this in the testing WG 15:27:28 q? 15:27:38 s/kris:/krisk:/ 15:27:55 s/kris: /krisk: / 15:28:22 paulc: I don't believe we have transparency about the table and is it available or when it will be available. Is there a plan for a plan? 15:28:53 krisk: It's tough to produce this table and took a lot of hours. 15:29:17 kris: Put metadata in the tests (?) 15:29:24 mgrdcm has joined #html-wg 15:29:51 gk has joined #html-wg 15:30:34 paulc: With our HTML5 public permissive CR exit criteria, identifying the places where we have some public evidence of interop is the best way to show where we need more tests to get out of CR. People may still want to provide more tests in that area. Going to testthewebforward and saying these are the places we need tests because we don't have any evidence would be curcial 15:31:41 jgraham: Unless we know which tests go with which sections, it's hard to tell which sections need more tests. Quantity of tests is not necessarily a good measure. 15:31:58 q? 15:31:58 jgraham: Doing this work is hard. There is no magical process or metadata. Writing tests is hard creative work. 15:32:23 q+ 15:32:25 kris: Agreement on changing directory structure 15:32:42 kris: Approved vs. submitted is important. 15:33:06 jgraham: Approved vs. submitted has caused problems, such as when you move files around. 15:33:16 q+ 15:33:25 jgraham: Preference to have directory structure based on where in the spec it is. 15:33:31 richardschwerdtfeger has joined #html-wg 15:33:38 jgraham: Have approved vs. submitted as metadata 15:34:00 jgraham: Use scratch folder or branches for stuff people want to check in 15:34:05 ack Mark_Vickers 15:34:26 Or separate repos entirely. 15:34:27 Mark_Vickers: Related to testing devices & the work on WebDriver - Is there a goal that all of these should work with WebDriver. 15:34:33 (Given we're using a DVCS) 15:34:39 krisk: There is not requirement that tests must work with WebDriver. 15:35:13 krisk: AppCache is an example of something that couldn't be done with WebDriver. Playing a video and listening for sound as well. 15:35:58 jgraham: You could write a harness to run the tests. For JS tests, it's easy to run them without WebDriver. There are hooks that enable this. 15:36:47 jgraham: We prefer ref tests. These can be implemented in WebDriver. 15:37:17 q? 15:37:45 MartinSoukup has joined #html-wg 15:37:57 krisk: Early our principle was that we wanted tests available to everyone and to support everyone. 15:38:07 ack SimonPieters 15:38:53 SimonPieter: Submitted and approved directories - the point is that things in Approved have been reviewed. But we don't have a good process for reviews and revising the tests after review. 15:39:13 s/SimonPieter/SimonPieters/ 15:39:43 SimonPieters: Proposes using branches and tests in the main branch are always reviewed. 15:39:51 q+ 15:39:55 (And the experience in general is we never actually review half the tests, they just get moved through by virtue of no objections) 15:39:56 ????: Do you have a review tool? 15:40:00 SimonPieters: Yes. 15:40:08 krisk: Would like to have a review tool. 15:41:09 jgraham: If we move the workflow to github then push to Mercurial, that gives us a review tool. Using the github review tool, however limited it is. 15:41:36 discussion of how this would work 15:41:44 I think we can host next F2F meeting in Seoul. 15:41:45 q? 15:42:22 Mark_Vickers: In terms of tackling the large problem, there are a few paths. You mentioned donation. Another is crowdsourcing through testthewebforward. 15:42:47 we were already hosted many W3C WG meeting. DAP WG, Media Annotation, MWBP WG ... 15:43:24 OMG 15:43:28 Mark_Vickers: Other ideas: 1) Break down the spec into sections and assign responsibility for testing a section to companies - to figure out a test plan, etc. 2) Outsourcing - pay for testing to be done. Might have to get additional funding, but it might be worth it. 15:43:48 krisk: I don't think anyone is opposed to getting companies to do things. 15:43:56 s/I think we can host next F2F meeting in Seoul.// 15:44:18 kirsk: Hasn't been a lot of stickniess with testthewebfordard. Usually a 1-day thing. 15:45:04 jgraham: Of course getting people to write tests is good, but from a browser POV, I don't think it would work. The priority is to write tests when they are implementing. It seems unlikely they would pull people off implementing to write tests. 15:45:50 jgraham: Regarding hiring people to write tests, the trick is to make it good people. There is a strong concentration in browser vendors and other places of people that are good at writing tests. That's not always the case. 15:46:05 q? 15:46:06 jgraham: The places where tests are missing are the complicated bits. 15:46:30 paulc: Describes previous expereience. 15:47:01 paulc: A majority of the 25,000 tests in that WG were written by NIST. Not an implementor, but they had test writers. 15:47:26 XML Schema 15:47:41 paulc: This is part of plan 2014 15:47:56 s/that WG/the XML Schema WG/ 15:48:11 s/XML Schema// 15:48:14 paulc: Do we have any sponsorship money left? 15:48:17 http://www.w3.org/Consortium/Recruitment/#qmgr 15:48:52 plh: I don't have the answer yet. Hoping by the end of the month. 15:49:15 ack Mark_Vickers 15:49:39 plh: The link from Mark_Vickers is not the right posting. 15:49:59 oops 15:50:03 krisk: I feel we have tapped all our resources, in terms of browsers participating. 15:50:28 krisk: Maybe there is something that could be done in terms of membership. 15:50:45 krisk: Find organizations that care about testsing 15:50:53 queue+ 15:51:20 jgraham: We have not tapped browser vendors. We could do better at getting browser vendors to write tests that others can use. 15:51:33 And release the ones they have. 15:51:56 q? 15:52:08 jgraham: We should have a conversation about whether there are things we can do to make it easier. 15:52:17 ack DanielAustin 15:52:40 DanielAustin: In previous incarnations, we reached out to the HTML Writers Guild. I don't know whether we've reached out to them. 15:52:56 jgraham & krisk: not aware 15:53:05 Judy has joined #html-wg 15:53:26 plh has joined #html-wg 15:53:27 http://hwg.org/ 15:53:56 mjs: Looking at agenda. 15:54:46 mjs: remaining items: issue 204, remaining issues, Alt Guidance, Other FPWDs. 15:54:57 mjs: Asks if there is interest in these. 15:55:44 skipping 204 15:55:52 topic: Tracker Requests 15:56:32 paulc: Tracker Requests are bugs that have been addressed by an editor but someone disagreed with and added the Tracker label. 15:57:17 paulc/Robin: None of the current tracker bugs were disposed of by a current editor 15:57:44 mjs: is anyone interested in each of these. 15:57:56 Arno has joined #html-wg 15:58:13 paulc: drag-and-drop processing model - could not find anyone in this meeting. We don't have the right people. 15:59:16 paulc: 18384 adaptive image mechanism. I think the chairs should deal with this. 15:59:26 q? 15:59:43 link to this tracker list? 15:59:58 paulc: 18384 - Chairs to investigate whether to deal with the tracker request 16:00:24 mjs: 13614 16:00:35 -> http://intertwingly.net/tmp/wgstatus.html#tracker-requests Tracker Requests 16:00:44 SimonPieters: That bug appears to be fixed. Should we remove Tracker 16:00:46 q+ fantasai 16:00:59 thx 16:01:21 -> http://w3.org/brief/Mjk3 Tracker Requests 16:01:35 concern about adding more text that is meant to be read out (related to i18n) 16:01:42 into an attribute 16:01:58 Chairs will determine the providence of the Tracker Request 13164. 16:02:10 s/13164/13614/ 16:02:36 mjs: 13409 - Defining Entity references for characters in XHTML 16:02:42 The room tries to figure out what it is about. 16:03:12 mjs: i believe Sam said he would comment on this, and that it's an interop issue. 16:03:44 Reviewing the comments in the issue. 16:04:01 q+ to suggest we talk with David directly about this 16:04:50 mjs: This is a feature request. 16:05:11 ack fantasai 16:05:15 kotakagi has joined #html-wg 16:05:16 mjs: Most of these are extension specs, so they will likely be rejected unless someone makes an extension spec. 16:05:21 [for https://www.w3.org/Bugs/Public/show_bug.cgi?id=13614 TrackerRequest was added two weeks ago http://lists.w3.org/Archives/Public/public-html-bugzilla/2012Oct/0350.html] 16:05:29 mjs: … or 5.1. 16:05:32 q- 16:05:53 tomoyuki has joined #html-wg 16:06:16 TOPIC: Alt Guidance and Alt text in the HTML5 Document Part 1: Analysis of Guidance 16:06:23 paulc: We don't have the right people 16:06:31 TOPIC: Other FPWDs 16:06:47 Takahiro has joined #html-wg 16:06:48 mjs: Anyone have such a document and want to propose it here? 16:07:12 kotakagi2 has joined #html-wg 16:07:23 q+ 16:07:24 paulc: What is the process for getting extension specs to FPWD? 16:07:41 paulc: It's not clear what the next step is after the WG gets a request. 16:07:56 paluc: Travis suggested doing a CfC. 16:09:26 mjs: How we have handled FPWDs in the past: First, we expect there to be some indication that the document is ready for FPWD. We have asked in a few cases to make it explicit to show some minimal number of independent contributors to the draft in order to show it is not just a 1-person project. Previously, we have required 3 independent contributors. A contributor can be someone who has filed a bug. We do a CfC. Usually the bar for objection is pretty high. 16:09:32 q+ 16:09:50 mjs: This is outside the scope is a valid objection, but I don't like this generally is not at the FPWD stage. 16:10:10 mjs: We haven't written down the process because we haven't expected a lot of them. But now we might with the new extension process. 16:10:24 mjs: We may need to step back and create a process. 16:10:37 q+ 16:10:37 mjs: Does anyone have comments on what should be the bar? 16:11:11 ack darobin 16:11:15 shige_ has joined #html-wg 16:11:20 darobin: I don't disagree that we might need a little bit of process, but we did discuss having less process this morning. It would be nice if process was minimal and maybe rough consensus. 16:11:21 ack SimonPieters 16:12:12 SimponPieters: I think we should ask the question what is the implementation interest for what the spec is trying to target. For example, if the feature is targeted at search engines, we should ask if there is search engine interest. 16:12:32 ack hsivonen 16:12:39 SimonPieters: If there isn't implementor interest, we should drop the draft even if there are 10 people involved. 16:13:28 queue+ 16:13:37 q? 16:13:41 hsivonen: The general public will think that things this group publishes will be part of HTML5. We should have a filter at the start of the process. For the conformance classes addressed by the spec…(?) 16:13:48 q ? 16:14:25 Travis: I want to see less process and us having lots of extension specs because it gives us the opportunity for us to pick and choose and for the most popular ones to succeed. CSS 3 as an example. 16:14:57 Travis: We're already there in the public eye and browsers are not willy nilly with what they pick. 16:15:18 ack DanielAustin 16:15:29 q+ 16:15:41 q? 16:15:44 q+ 16:15:46 DanielAustin: Want to offer a counter example to previous speaker saying we should wait for implementor interest. if we had done that, we wouldn't have iframe. 16:16:09 DainelAustin: I'd like to think of it as users driving implementors to what they need. 16:16:13 ack mjs 16:16:21 q+ 16:16:57 yoav_ has joined #html-wg 16:16:58 mjs: (implementor hat): It is annoying when specs are published that are very likely never going to be implemented by anyone but purport to provide conformance criteria. 16:17:23 mjs: … On the other hand, when someone is at the FPWD stage, I don't know whether it's something that we'll want to implemented. 16:17:49 +1 16:17:53 q? 16:17:59 mjs: … Apple doesn't speak about future plans and wouldn't want the process to involve explicitly saying I'm interested in implementing this. 16:18:49 hsivonen: I'm not expecting any implementor to commit to anything. Rather, I'm expecting implementors to say this is a good idea as a spec. But not looking for a commit. 16:19:40 hsivonen: As for iframe, I though that came about from IE4 being developed at the same time as HTML4 and emerged as a feedback cycle. 16:20:17 jgraham: I don't think that we should be putting things in FPWD just because we think that then the group might be able to force implementors to do things that certain members want. 16:20:30 jgraham: I don't think the HTML WG is a good proxy for what users want. 16:20:39 s/users/authors/ 16:20:58 q+ 16:21:05 ack hs 16:21:07 ack jg 16:21:09 jgraham: I don't want to have that type of forcing function just because it's in the group process. 16:21:30 jgraham: Specs should have to survive on their own merit and not via branding 16:21:40 historical note: iframe appeared in IE4, was repeatedly rejected as a proprietary extension, until members complained that they really wanted it 16:22:10 paulc: (Microsoft hat) The last thing we want is that FPWD means a majority of browser vendors have agreed to implement it. 16:22:28 DanielAustin: Those were also very very dark times... More or less everything is different today. 16:22:37 paulc: I think a majority of the extensions fall on the end of the requirements that mjs suggested. 16:22:48 paulc: MSE and EME are examples. 16:23:06 not as different as you may think :) 16:23:12 q+ 16:23:15 paulc: Gives example of extremely credible effort done by one person. 16:23:43 paulc: For those specs that don't meet the requirements, please start saying so on the list. 16:23:46 ack paulc 16:24:16 q+ 16:24:20 ack jg 16:24:21 paulc: Media TF is going overboard to make sure it doesn't ask for FPWD before it's too early. Making sure to get the design right and flatten as many bugs as possible before FPWD. 16:24:39 +1 to say that there has been lots of discussion of the main element in the a11y-tf and in pf. 16:24:56 ack mjs 16:24:56 ack jgraham 16:25:01 jgraham: One thing that made
more credible is that it appeared the author had obtained buy-in. 16:25:11 from implementors 16:25:25 mjs: This is a lot easier to consider concretely than in abstract case. 16:25:52 mjs: For anything we have published, do you think it would not have passed? 16:26:05 hsivonen: I think RDFa would not have passed. 16:26:10 mjs: Disagrees 16:26:42 r12a has joined #html-wg 16:27:18 discussion of whether HTML+RDFa is implemented 16:27:32 and whether it's use of syntax vs. the spec. 16:27:54 mjs: Main Content and media specs have traction 16:28:11 mjs: Unclear whether longdesc has implementation support but … 16:28:31 mjs: We probably don't need to create a process for a problem that doesn't exist. 16:28:43 q? 16:29:07 paulc: If you look at the report the chairs gave to the AC, there is a reference to a F2F meeting in April 2013. 16:29:24 paulc: We're expecting the new charter to say F2F meetings twice per year instead of once per year. 16:29:44 paulc: Looking for a place in Silicon Valley. Possibly paired with WebApps. 16:29:54 r12a has joined #html-wg 16:29:57 paulc: If you want to volunteer a host site, talk to plh. 16:30:05 paulc: Approximately April 22nd. 16:30:26 DanielAustin: We are looking at hosting (PayPal) 16:30:57 paulc: Thanks to WG members. Thanks to scribes. 16:31:07 paulc: We'll see you on public-html 16:31:38 s/Philip/plh/ 16:31:42 rrsagent, generate minutes 16:31:42 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html ddorwin 16:33:36 naomi has joined #html-wg 16:33:42 plh has joined #html-wg 16:35:46 nonge has joined #html-wg 16:37:52 s/Philip:/plh:/ 16:38:31 annevk has left #html-wg 16:38:57 r12a has joined #html-wg 16:45:56 Ralph has joined #html-wg 16:48:30 rrsagent, draft minutes 16:48:30 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html matt 16:48:31 \ 16:49:05 rrsagent, draft minutes 16:49:05 I have made the request to generate http://www.w3.org/2012/11/02-html-wg-minutes.html matt 16:49:43 Norbert has joined #html-wg 16:53:58 cabanier has joined #html-wg 17:00:13 ddorwin has joined #html-wg 17:25:37 rubys has joined #html-wg 17:46:40 naomi has joined #html-wg 18:29:09 mdahlstrand has joined #html-wg 18:43:02 rubys has left #html-wg 18:44:10 karl has joined #html-wg 19:43:20 icaaq has joined #html-wg 20:06:58 yoav_ has joined #html-wg 20:14:16 Joshue108 has joined #html-wg 21:09:49 koji has joined #html-wg 21:30:54 glenn has joined #html-wg 21:32:19 ddorwin has joined #html-wg 21:33:28 dveditz has joined #html-wg 21:35:25 plh has joined #html-wg 21:41:13 Judy has joined #html-wg 21:44:34 SimonPieters has joined #html-wg 21:50:45 ddorwin has joined #html-wg 21:54:04 r12a has joined #html-wg 21:58:11 Dashiva has joined #html-wg 22:09:21 silvia has joined #html-wg 22:12:56 yoav_ has joined #html-wg 22:14:18 MikeSmith has joined #html-wg 22:14:58 drublic has joined #html-wg 22:22:29 glenn_ has joined #html-wg 22:35:48 mjs has joined #html-wg 23:09:14 gitbot has joined #html-wg 23:09:14 [13html] 15rubys pushed 1 new commit to 06feature/whatwg: 02https://github.com/w3c/html/commit/be7f311abd383043c06ef2928bcf2fbe3c69ee41 23:09:14 13html/06feature/whatwg 14be7f311 15ianh: [giow] (0) Provide a way for authors to broadcast to many ports without memory leaks.... 23:09:14 gitbot has left #html-wg 23:32:06 Bert has left #html-wg 23:35:04 Judy has left #html-wg 23:39:14 Zakim has left #html-wg 23:46:21 mamund has joined #html-wg 23:47:04 heathjs has joined #html-wg