16:58:26 RRSAgent has joined #html-wg 16:58:26 logging to http://www.w3.org/2008/11/13-html-wg-irc 16:58:28 RRSAgent, make logs public 16:58:28 Zakim has joined #html-wg 16:58:30 Zakim, this will be HTML 16:58:30 ok, trackbot; I see HTML_WG()12:00PM scheduled to start in 2 minutes 16:58:31 Meeting: HTML Issue Tracking Teleconference 16:58:31 Date: 13 November 2008 16:58:33 Zakim, call Mike 16:58:33 ok, MikeSmith; the call is being made 16:58:34 HTML_WG()12:00PM has now started 16:58:34 +Mike 16:58:54 Zakim, code? 16:58:54 the conference code is 4865 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), MikeSmith 16:59:03 Chair: MikeSmith 16:59:17 +DanC 16:59:35 arne has joined #html-wg 16:59:45 +??P2 16:59:59 zakim, ??p2 is Joshue 16:59:59 +Joshue; got it 17:01:14 deane has joined #html-wg 17:02:24 +Cynthia_Shelly 17:02:41 Regrets+ ChrisWilson, LauraCarlson, Julian 17:02:56 agenda: http://lists.w3.org/Archives/Public/public-html-wg-announce/2008OctDec/0005.html 17:02:58 Title: HTML WG telcon 2008-11-13 - f2f summary, markup spec, authoring guide from Michael(tm) Smith on 2008-11-12 (public-html-wg-announce@w3.org from October to December 2008) (at lists.w3.org) 17:03:05 + +1.519.378.aaaa 17:03:06 Zakim, who's on the phone? 17:03:07 On the phone I see Mike, DanC, Joshue, Cynthia_Shelly, +1.519.378.aaaa 17:03:20 Zakim, aaaa is MurrayM 17:03:20 +MurrayM; got it 17:03:34 Present+ MikeSmith, DanC, Josh, Cynthia, MurrayMaloney 17:05:18 +[Microsoft] 17:05:41 Present+ AdrianBatemen 17:05:42 Zakim, [Microsoft] is Adrian 17:05:42 +Adrian; got it 17:06:50 scribenick:Joshue 17:06:53 scribenick: Joshue 17:07:01 scribe: Joshue 17:07:22 TOPIC: Markup Lanhuage Spec 17:07:33 s/Lanhuage/Language 17:08:06 MikeS: I posted a draft of the spec that I have been working on. It would be helpful as a starting point. 17:08:07 http://www.w3.org/html/wg/markup-spec/ 17:08:08 Title: HTML: The Markup Language (at www.w3.org) 17:08:25 Zakim, mute Joshue 17:08:25 Joshue should now be muted 17:09:03 MikeS: I realize very few have looked at it. Has anyone initial comments? 17:09:42 MikeS: Gives outline of abstract 17:10:26 MikeS: The doc defines authors, producers and consumers differently. 17:11:30 MikeS: Gives further details. No normative criteria, web browsers are not defined in terms of how they parse HTML, Is not intended to be an aurthoring guide. 17:12:35 MikeS: HTML Syntax is described. Various Mime Types are discussed. Its the same prose as defined in the current draft, prettty much. Optional BOM are mentioned etc. 17:13:15 MikeS: DOC Type, character encoding etc are defined. The remianing part of spec is a list of HTML elements and their content models, attributes and values etc. 17:13:33 I had a brief look, looked reasonable, but I would be worried people take it for normative 17:14:34 MikeS: In addition there is a section on common content models, phrase and prose content matches bloack and inline content. Then definitions of sets of common attributes. Similar to HTML 4 draft and other markup specs. 17:15:42 MikeS: Last part deals with ARIA markup, attribute sets, enumerated values for ARIA attributes. Semantics uundefined as they are in the ARIA spec. Then exahistive list of name character references. 17:16:40 MM: Test kit being build. 17:16:52 MikeS: Not a schema? 17:17:07 MM: Its a grammer to build a parser. 17:17:20 MikeS: Interesting 17:17:33 MM: I will ask him to join WG. 17:17:42 q? 17:17:43 MS: WIll you have more infor next week? 17:17:46 MM: Yes 17:17:59 s/infor/info 17:18:33 Adrian: Do you have a view as to how having this doc changes what the HTML 5 spec is/does? 17:20:10 MS: Right now as far as content models and syntax description. This matches what is in the HTML 5 draft. We want to keep things that way. We need to decide that the current part of semantics, content models etc should be kept there. We need to keep them in synch. As different docs have diff editors there may not always be agreement. 17:20:51 MS: We want this to be normative. There can only be one spec so this will superceed anything else. 17:22:11 Adrian: This looks like a good start. In terms of a descriptive doc that talks about the language and not its use. However, how practical is this? How much of the text has been taken from the HTML 5 draft? 17:22:52 MS: This spec should have a lot of non-normative content. 17:25:56 MS: It should not describe rendering behaviors normatively, or have too much description of rendering behavior etc. many say the current draft conflates authoring and rendering domains. These are seperate so there is confusion. I like to have the markup spec not do this anymore. Seperate some of the under the hood stuff from the user manual aspect. Want to see the spec defined as an abstract language without processing assumptions. 17:26:13 s/This spec should have/This spec should not have/ 17:26:19 Adrian: That is a good goal. 17:26:34 q? 17:26:36 (trying to construct a proof in my head that the language defined in Mike's draft is smaller than the language in Hixie's draft; hmm... don't think there is one... I think it's not actually a theorem. I think there are counter-examples) 17:26:40 Joshue things this may make it easier to uunderstand for all concerned. 17:26:50 ack me 17:26:51 s/things/thinks 17:27:13 DacC: Its not smaller than the language Hixie defines as conformant. 17:27:36 DanC: In that docs conforming to his spec is conforming to yours. 17:27:40 MS; It is. 17:27:46 DanC: I don't think so. 17:27:55 (other way around) 17:28:05 MS: You are right. 17:28:54 DanC: e.g. documents that misuse headings, cite, etc. are prohibited by the HTML 5 spec 17:29:59 MS: Discusses schemas, parsing of schemas, attribute model and pattern definitions. RelaxNG etc. 17:31:55 MS: Programmatic extracts/additions of certain content via Schematron. Josh unable to parse some statements. 17:32:09 Cythia: I am curious why this is done that way? 17:32:55 (I think having feedback between validation tools and the spec is good... though this is something of an extreme approach) 17:33:24 MS; It is circular. Not ideal. Changes to the spec will go other way, or not be one way from validator to the spec. If changes are made the assertions that vlidator.nu are making will have to be changed to match the spec. At his point they are one way. 17:33:40 Cynthia: It is reasonable to do this in order to get the spec out. 17:35:17 MS: Its about having a formal description of the language. Formalisims are currently prose desciptions in order to not lock people who write a conformance checker. High level language used in order to design a tool around it loosely. 17:35:53 (publishing the schema as a note is an interesting idea.) 17:36:54 MS: Hixie feels there should not a normative shema for the language. Other builders have a disincentive to build anything. All of these normative schemas for the language seemed to stop others from developeing their own. We want to avoid this, having only one tool. 17:37:16 Cythia: Yes, some need this behind a firewall. 17:37:29 MS: This can be done and works well. 17:37:31 q? 17:37:37 q+ murray 17:37:50 ack murray 17:37:54 Cythia: We dont want to give advantage to one set of schemas. 17:39:04 MM: When developing a formalism for HTML, we can build a grammer, define constraints etc. It depends on what you are trying to do. 17:41:14 MM: Grammer needs to be correct. Stuff taken from different namespaces can be dealt with. Others have more rigorous purposes, may not be public facing. The grammer needs to be examined to be a more liberal version that conformance checkers want to use, then good stuff. 17:41:41 -Cynthia_Shelly 17:42:03 MS: Existing validators, and HTML 4. ZHTML 1.0 and 1.1 (DTD based validation tools) 17:43:02 MM: When you procude a DTD, the doc that accompanies it is produced alongside it. There are better formalisms to do this etc 17:43:30 MS: I understand. Validator.nu is doing a lot more that just conformance checking. 17:43:51 MM: You claim that it does that is false. 17:44:01 you have to be very very careful that people don't start trying to consume HTML via a grammar rather than an implementation of the parsing algorithm 17:45:40 +[Microsoft] 17:45:45 q? 17:45:45 MS: I conceed that, however when a decent schema is availalbe, validation against a schema etc there are more sophistcated tools. But the problem is that many see that passing the validator is percieved as meaning their content is fit for purpose. Schema checking alone does not always mean your doc can be processed the way you want it to be. 17:45:51 MM: Again this is false. 17:46:02 MS: I hear what you are saying. Other comments? 17:46:13 Cynthia: This is a good idea. It will be helpful. 17:48:27 MS: I think to have the Authoring guide as a way to make it clear to help them have their docs work on the web. It also needs to cover the DOM interface for scripting purposes. Real world use cases etc. This will keep the spec minimal. remove informative stuff into the authoring guide etc 17:48:47 MM: Then call it something else. 17:48:50 MS: No 17:49:13 Cythia: It could have subtitle? 17:49:37 MS: We have talked to developers and they want this. 17:49:56 +q 17:50:03 zakim, unmute me 17:50:03 Joshue should no longer be muted 17:50:24 MM; How about a browsers guide, devlopers guide etc? 17:50:50 MS: We need a normative guide for browsers.. 17:50:54 s/MM;/MM: / 17:50:56 MM: You can't hve that. 17:51:29 MM: I am not understanding this. 17:51:59 DanC: You said this was a spec for how UAs behave. 17:52:14 MM: Strong objection 17:52:28 -q 17:52:49 CGI707 has joined #html-wg 17:53:18 Joshue: some document that is specifically for authors, that cuts out a lot of the under-the-hood stuff is in principle a good idea 17:53:18 MM: I am going to make this an issue. 17:53:24 zakim, mute me 17:53:24 Joshue should now be muted 17:53:38 issue-61? 17:53:38 ISSUE-61 -- Conformance depends on author's intent -- RAISED 17:53:38 http://www.w3.org/html/wg/tracker/issues/61 17:53:40 Title: ISSUE-61 - HTML Issue Tracking Tracker (at www.w3.org) 17:53:51 maybe that's not so close to what Murray wanted on the issues list after all 17:54:15 action-77? 17:54:15 ACTION-77 -- Michael(tm) Smith to lead HTML WG to response to TAG discussion and report back to TAG -- due 2008-10-30 -- OPEN 17:54:15 http://www.w3.org/html/wg/tracker/actions/77 17:54:17 Title: ACTION-77 - HTML Issue Tracking Tracker (at www.w3.org) 17:54:19 MS: I did want to talk to the TAG list about this. Let them know we have followed up on the discussion. I have an item to do this. This should take place on the public HTML list. 17:54:35 MM: I don't follow 17:55:13 MS: The action item is complete. 17:55:22 ISSUE-59? 17:55:23 ISSUE-59 -- Should the HTML WG produce a separate document that is a normative language reference and if so what are the requirements -- RAISED 17:55:23 http://www.w3.org/html/wg/tracker/issues/59 17:55:24 Title: ISSUE-59 - HTML Issue Tracking Tracker (at www.w3.org) 17:55:27 (maybe that's closer) 17:56:16 Topic: Any other business? 17:56:18 MS: Lets take the rest of the discussion to public HTML. 17:56:25 TOPIC: AOB 17:56:32 @headers? 17:56:33 Joshue: Huh? 17:56:42 zakiim, unmute me 17:56:48 (just briefly, who has the ball on headers?) 17:56:57 zakim, unmute me 17:56:57 Joshue should no longer be muted 17:57:04 CGI707 has joined #html-wg 17:57:21 (the actions listed in http://www.w3.org/html/wg/tracker/issues/20 seem stale. ) 17:57:22 Title: ISSUE-20 - HTML Issue Tracking Tracker (at www.w3.org) 17:57:35 Joshue: we are talking with PF about @headers and discussing how to move this along a little farther 17:58:07 (hm... so it sounds like anybody/somebody/nobody has the ball.) 17:58:49 action: Joshue to prepare status report on @headers discussion by next week 17:58:49 Created ACTION-84 - Prepare status report on @headers discussion by next week [on Joshue O Connor - due 2008-11-20]. 17:59:07 waves bye 17:59:25 -Joshue 17:59:45 Topic: Next meeting 18:00:00 we will have the telcon at the regular time next week, probably with ChrisWilson chairing 18:00:15 [adjourned] 18:00:19 -[Microsoft] 18:00:22 -Adrian 18:00:38 RRSAgent, make minutes 18:00:38 I have made the request to generate http://www.w3.org/2008/11/13-html-wg-minutes.html MikeSmith 18:00:55 Zakim, who's on the phone? 18:00:55 On the phone I see Mike, DanC, MurrayM 18:01:10 Zakim, drop me 18:01:10 sorry, MikeSmith, I do not see a party named 'MikeSmith' 18:01:15 Zakim, drop Mike 18:01:15 Mike is being disconnected 18:01:16 -Mike 18:01:26 -MurrayM 18:05:05 deane has left #html-wg 18:05:42 arne has left #html-wg 18:20:32 RRSAgent, make minutes 18:20:32 I have made the request to generate http://www.w3.org/2008/11/13-html-wg-minutes.html MikeSmith 18:20:35 Title: HTML Issue Tracking Teleconference -- 13 Nov 2008 (at www.w3.org) 18:21:09 s/;/:/g 18:21:11 RRSAgent, make minutes 18:21:11 I have made the request to generate http://www.w3.org/2008/11/13-html-wg-minutes.html MikeSmith 18:21:12 Title: HTML Issue Tracking Teleconference -- 13 Nov 2008 (at www.w3.org) 18:31:54 adele has joined #html-wg 18:35:01 disconnecting the lone participant, DanC, in HTML_WG()12:00PM 18:35:02 HTML_WG()12:00PM has ended 18:35:05 Attendees were Mike, DanC, Joshue, Cynthia_Shelly, +1.519.378.aaaa, MurrayM, Adrian, [Microsoft] 18:35:57 RRSAgent, bye 18:35:57 I see 1 open action item saved in http://www.w3.org/2008/11/13-html-wg-actions.rdf : 18:35:57 ACTION: Joshue to prepare status report on @headers discussion by next week [1] 18:35:57 recorded in http://www.w3.org/2008/11/13-html-wg-irc#T17-58-49