Wednesday, 31 March 2010
- Re: ISSUE-94 Change Proposal
 - Re: ISSUE-94 Change Proposal
 - Re: ISSUE-94 Change Proposal
 - [Bug 9122] Obsolete but Conforming
 - [Bug 9061] allow image maps on the canvas element.
 - [Bug 9061] allow image maps on the canvas element.
 - Re: ISSUE-94 Change Proposal
 - Change proposals uploaded to Wiki - URLs, suggestions on Issue 92 table
 - Re: ISSUE-94 Change Proposal
 - Re: AuthConfReq: Presentational Markup
 - Re: All change proposals should now be submitted
 - Re: All change proposals should now be submitted
 - Re: The next HTML+RDFa Heartbeat
 - Re: The next HTML+RDFa Heartbeat
 - All change proposals should now be submitted
 - ISSUE-100 Change Proposal
 - ISSUE-97 Change Proposal
 - ISSUE-96 Change Proposal
 - ISSUE-95 Change Proposal
 - ISSUE-94 Change Proposal
 - ISSUE-93 Change Proposal
 - ISSUE-92 Change Proposal
 - ISSUE-91 Change Proposal
 - ISSUE-90 Change Proposal
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: AuthConfReq: Presentational Markup
 - RE: FW: AuthConfReq: Presentational Markup
 - Re: creating issues for non-published documents?
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: The next HTML+RDFa Heartbeat
 - Re: AuthConfReq: Presentational Markup
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: The next HTML+RDFa Heartbeat
 - Re: The next HTML+RDFa Heartbeat
 - Re: AuthConfReq: Presentational Markup
 - Re: The next HTML+RDFa Heartbeat
 - RE: FW: AuthConfReq: Presentational Markup
 - Re: The next HTML+RDFa Heartbeat
 - Re: The next HTML+RDFa Heartbeat
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: The next HTML+RDFa Heartbeat
 
Tuesday, 30 March 2010
- Re: FW: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - FW: AuthConfReq: Presentational Markup
 - Re: creating issues for non-published documents?
 - Re: The next HTML+RDFa Heartbeat
 - Re: {agenda} HTML WG telcon 2010-04-01: action items, decision policy update, issue status
 - Re: The next HTML+RDFa Heartbeat
 - Re: The next HTML+RDFa Heartbeat
 - Re: The next HTML+RDFa Heartbeat
 - Re: The next HTML+RDFa Heartbeat
 - Re: The next HTML+RDFa Heartbeat
 - Re: creating issues for non-published documents?
 - {agenda} HTML WG telcon 2010-04-01: action items, decision policy update, issue status
 - Re: The next HTML+RDFa Heartbeat
 - [Bug 8321] change controller for HTML media type
 - [minutes] 20100325 HTML teleconference
 - Re: The next HTML+RDFa Heartbeat
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - Re: creating issues for non-published documents?
 - Re: AuthConfReq: Presentational Markup
 - creating issues for non-published documents?
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility; X3D
 - Re: ISSUE-88 / Re: what's the language of a document ?
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - Re: AuthConfReq: Presentational Markup
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - [Bug 8784] politics in <param> example
 - Re: AuthConfReq: Presentational Markup
 - RE: AuthConfReq: Presentational Markup
 - Re: Make reset button non-conforming
 - Re: document.load: History and a proposal
 - Re: AuthConfReq: Presentational Markup
 - Re: Make reset button non-conforming
 - Re: AuthConfReq: Presentational Markup
 - [Bug 8207] Change definition of URL to normative reference to IRIBIS
 - [Bug 7391] Reference to WEBADDRESS should be replaced with reference to IRIbis
 - [Bug 8246] what about IE parsing problems? http://html5doctor.com/dd-details-wrong-again/
 - Re: Default value of "preload" attribute
 - [Bug 6853] restore meta keywords, search engines use them
 - [Bug 9160] input['type=checkbox'].checkValidity ought to work like the radio type, testing the whole checkbox group, not each checkbox individually
 - Re: Default value of "preload" attribute
 
Monday, 29 March 2010
- Re: AuthConfReq: Presentational Markup
 - Re: document.load: History and a proposal
 - Re: AuthConfReq: Presentational Markup
 - [Bug 9081] Confusing alt text in the fourth The Lady of Shalott example
 - [Bug 9077] Lady of Shalott example doesn't really "enhance the themes or subject matter of the page content"
 - [Bug 9077] Lady of Shalott example doesn't really "enhance the themes or subject matter of the page content"
 - [Bug 9081] Confusing alt text in the fourth The Lady of Shalott example
 - Re: The next HTML+RDFa Heartbeat
 - Re: Bug 7034
 - ISSUE-90 and ISSUE-91 have changed focus of change proposals
 - Re: waiting and seeking events in media element seek algorithm
 - Re: waiting and seeking events in media element seek algorithm
 - Re: Default value of "preload" attribute
 - Re: waiting and seeking events in media element seek algorithm
 
Sunday, 28 March 2010
- Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: Some bugs filed based on conformance error study
 - Re: document.load: History and a proposal
 - The next HTML+RDFa Heartbeat
 - [Bug 7682] link tag: rel: associate pages about the same organization across many sites
 - [Bug 7681] link tag: rel: associate pages about the same person across many sites
 - [Bug 6610] add a preventable forced-fragment method
 - [Bug 6609] negative keywords-not meta tags
 - Re: co-chairs: question about change proposals for Issues 90 and 91
 - Re: document.load: History and a proposal
 - co-chairs: question about change proposals for Issues 90 and 91
 - Re: AuthConfReq: Presentational Markup
 - Re: ISSUE-89 Change Proposal
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: Make reset button non-conforming
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Make reset button non-conforming
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: Some bugs filed based on conformance error study
 
Saturday, 27 March 2010
Sunday, 28 March 2010
Saturday, 27 March 2010
- Re: AuthConfReq: Presentational Markup
 - Some bugs filed based on conformance error study
 - Re: document.load: History and a proposal
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: document.load: History and a proposal
 - Re: document.load: History and a proposal
 - Re: ISSUE-89 Change Proposal
 - Re: document.load: History and a proposal
 - Re: document.load: History and a proposal
 - Re: AuthConfReq: Presentational Markup
 - Re: Request for Volunteers: Polyglot spec
 - Re: document.load: History and a proposal
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: Bug 7034
 - Re: HTML's table model vs @hidden & display:none
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - Re: AuthConfReq: Presentational Markup
 - AuthConfReq: Presentational Markup
 - Bug 7034 - Thanks!
 - Re: ISSUE-89 Change Proposal
 - document.load: History and a proposal
 
Friday, 26 March 2010
- Re: ISSUE-89 Change Proposal
 - Re: ISSUE-89 Change Proposal
 - Request for Volunteers: Polyglot spec
 - Re: ISSUE-89 Change Proposal
 - ISSUE-89 Change Proposal
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - elevate bug 7034 to issue
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - Revisions of Decision Policy document under way
 - RE: {agenda} HTML WG telcon 2010-03-25: decision policy, issue status, updates from meetings, task force reports
 
Thursday, 25 March 2010
- Re: order of arguments in window.postMessage()
 - Re: Presentational markup
 - Re: Presentational markup
 - Re: waiting and seeking events in media element seek algorithm
 - Re: Presentational markup
 - Re: media element seek algorithm: don't throw
 - RE: Default value of "preload" attribute
 - Re: Change proposal template and conformance class changes
 - Change proposal template and conformance class changes
 - Re: HTML's table model vs @hidden & display:none
 - Re: {agenda} HTML WG telcon 2010-03-25: decision policy, issue status, updates from meetings, task force reports
 - Re: Presentational markup
 - Re: Presentational markup
 - Re: Presentational markup
 - Re: media element seek algorithm: don't throw
 - Re: media element seek algorithm: don't throw
 - Re: Default value of "preload" attribute
 - Re: Default value of "preload" attribute
 - Re: Default value of "preload" attribute
 - RE: Default value of "preload" attribute
 - Re: HTML's table model vs @hidden & display:none
 - Re: Bug 7034
 - Re: Default value of "preload" attribute
 - Re: Bug 7034
 - Re: HTML's table model vs @hidden & display:none
 - Re: TAG requests addition to section 3.2.1 of Part 3 [#155]
 - Re: Default value of "preload" attribute
 
Wednesday, 24 March 2010
- Re: Default value of "preload" attribute
 - Re: Presentational markup
 - Re: HTML's table model vs @hidden & display:none
 - Presentational markup (was: Re: Bug 7034)
 - Re: <strike>
 - Re: HTML's table model vs @hidden & display:none
 - Re: Bug 7034
 - Default value of "preload" attribute
 - Re: <strike>
 - <strike> (was: Re: Bug 7034)
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - RE: HTML's table model vs @hidden & display:none
 - Re: Null change proposals for ISSUE-31, ISSUE-41, ISSUE-80, and ISSUE-88
 - Re: ISSUE-31 and ISSUE-80 Change Proposals
 - Re: Possible Conservative Proposal : no prefixes, but allow xmlns on a root element
 - Voice on the Web - message from the Voice Browser/Multimodal Interaction WGs
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: HTML's table model vs @hidden & display:none
 - RE: HTML's table model vs @hidden & display:none
 - Re: HTML's table model vs @hidden & display:none
 - Re: Change Proposal for ISSUE-101 (us-ascii-ref)
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: ISSUE-31 and ISSUE-80 Change Proposals
 - Re: ISSUE-31 and ISSUE-80 Change Proposals
 - Re: priority of bugs changed...again
 - CORRECTION ISSUE-78 (urls-terminology): Chairs Solicit Proposals
 - Re: ISSUE-78 (meta-name-registry): Chairs Solicit Proposals
 - Re: Null change proposals for ISSUE-31, ISSUE-41, ISSUE-80, and ISSUE-88
 - Re: Null change proposals for ISSUE-31, ISSUE-41, ISSUE-80, and ISSUE-88
 - Re: priority of bugs changed...again
 - Re: Old resolved bugs
 - Re: Bug 7034
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: Bug 7034
 - RE: INVALID_STATE_ERR or INVALID_ACCESS_ERR when attempting to write into XML documents
 - RE: HTML's table model vs @hidden & display:none
 - Re: Bug 7034
 - ISSUE-78 (meta-name-registry): Chairs Solicit Proposals
 - Re: Proposal for ISSUE-41: Generalization of approach taken by SVG and MathML
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: Null change proposals for ISSUE-31, ISSUE-41, ISSUE-80, and ISSUE-88
 - ISSUE-31 and ISSUE-80 Change Proposals
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Null change proposals for ISSUE-31, ISSUE-41, ISSUE-80, and ISSUE-88
 - Null change proposals for ISSUE-31, ISSUE-41, ISSUE-80, and ISSUE-88
 - Re: Change Proposal for ISSUE-101 (us-ascii-ref)
 - Re: Change Proposal for ISSUE-101 (us-ascii-ref)
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: ISSUE 79 editorial changes
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 
Tuesday, 23 March 2010
- Re: HTML's table model vs @hidden & display:none
 - Re: HTML's table model vs @hidden & display:none
 - Re: ISSUE 79 editorial changes
 - Re: ISSUE 79 editorial changes
 - Re: ISSUE 79 editorial changes
 - Re: Bug 7034
 - Re: ISSUE 79 editorial changes
 - Re: Bug 7034
 - Re: ISSUE 79 editorial changes
 - Re: HTML's table model vs @hidden & display:none
 - Re: Bug 7034
 - Re: Bug 7034
 - Update on HTML 5 Document License (ACTION-29)
 - Re: HTML's table model vs @hidden & display:none
 - Re: HTML's table model vs @hidden & display:none
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - ISSUE 79 editorial changes
 - Re: Bug 7034
 - Re: priority of bugs changed...again
 - Re: HTML5 Authoring Conformance Study
 - [Bug 8872] split out and modify parts of Section 4.8.2.1 the img element
 - priority of bugs changed...again
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: HTML5 Authoring Conformance Study
 - Proposal for ISSUE-41: Generalization of approach taken by SVG and MathML
 - HTML's table model vs @hidden & display:none
 - Re: HTML5 Authoring Conformance Study
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 - Re: HTML5 Authoring Conformance Study
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 - Re: HTML5 Authoring Conformance Study
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 - Re: Bug 7034
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 
Monday, 22 March 2010
- Re: ISSUE-90 background documentation on allowing any flow content in figure
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 - RE: Possible Conservative Proposal : no prefixes, but allow xmlns on a root element
 - Re: Bug 7034
 - Re: Possible Conservative Proposal : no prefixes, but allow xmlns on a root element
 - Re: Bug 7034
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 - Re: Bug 7034
 - RE: Possible Conservative Proposal : no prefixes, but allow xmlns on a root element
 - Re: Possible Conservative Proposal : no prefixes, but allow xmlns on a root element
 - RE: Possible Conservative Proposal : no prefixes, but allow xmlns on a root element
 - Re: HTML5 Authoring Conformance Study
 - Re: Possible Conservative Proposal : no prefixes, but allow xmlns on a root element
 - Re: Possible Conservative Proposal : no prefixes, but allow xmlns on a root element
 - RE: Possible Conservative Proposal : no prefixes, but allow xmlns on a root element
 - Re: Bug 7034
 - Re: Possible Conservative Proposal : no prefixes, but allow xmlns on a root element
 - Re: Bug 7034
 - Possible Conservative Proposal : no prefixes, but allow xmlns on a root element
 - Re: restrictions on blocks inside inlines (was Re: HTML5 Authoring Conformance Study)
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: HTML5 Authoring Conformance Study
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: Bug 7034
 - Re: HTML5 Authoring Conformance Study
 - RE: HTML5 Authoring Conformance Study
 - Re: ISSUE-90 background documentation on allowing any flow content in figure
 - Re: HTML5 Authoring Conformance Study
 - Re: change proposal: Provide accessibility implementation information (in the Canvas 2d Context specification) for focus rectangle and caret
 - Re: change proposal: Provide accessibility implementation information (in the Canvas 2d Context specification) for focus rectangle and caret
 - Re: restrictions on blocks inside inlines (was Re: HTML5 Authoring Conformance Study)
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - Re: restrictions on blocks inside inlines (was Re: HTML5 Authoring Conformance Study)
 - Re: restrictions on blocks inside inlines (was Re: HTML5 Authoring Conformance Study)
 
Sunday, 21 March 2010
- ISSUE-90 background documentation on allowing any flow content in figure
 - i18n tests for HTML
 - Re: HTML5 Authoring Conformance Study
 - Re: restrictions on blocks inside inlines (was Re: HTML5 Authoring Conformance Study)
 - Re: TAG requests addition to section 3.2.1 of Part 3 [#155]
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - restrictions on blocks inside inlines (was Re: HTML5 Authoring Conformance Study)
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - Re: HTML5 Authoring Conformance Study
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - Re: Bug 7034
 - HTML5 Authoring Conformance Study
 - Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034
 
Saturday, 20 March 2010
- RE: ISSUE-88 / Re: what's the language of a document ?
 - Re: Bug 7034
 - Re: Bug 7034
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - FW: [EAI] EAI Agenda for IETF 77 in Anaheim: mailto: URI scheme
 
Friday, 19 March 2010
- Re: Bug 7034
 - Re: Bug 7034
 - Re: Bug 7034 (was: Possible *third* proposal)
 - Re: Bug 7034 (was: Possible *third* proposal)
 - Re: FPWD of Additional Requirements for Bidi in HTML (rename BDI by SCE)
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Bug 7034 (was: Possible *third* proposal)
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: Change Proposals for ISSUE-41 (D.E.) vs XHTML and IE9
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - [Bug 9280] Add default button option/attribute for forms
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: Possible *third* proposal for ISSUE-41 Distributed Extensibility
 
Thursday, 18 March 2010
- RE: ISSUE-88 / Re: what's the language of a document ?
 - Possible *third* proposal for ISSUE-41 Distributed Extensibility
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: Change Proposals for ISSUE-41 (D.E.) vs XHTML and IE9
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - ANN: IETF HTTPbis Working Group Meeting next monday
 - Patial Change request proposal for Issue 74 Canvas accessibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: Change proposal for issue 103, was: ISSUE-103 change proposal
 - Change proposal for issue 103, was: ISSUE-103 change proposal
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - RE: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - RE: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - RE: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - RE: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 
Wednesday, 17 March 2010
- Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - RE: Indeterministic progress bar
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: FPWD of Additional Requirements for Bidi in HTML (rename BDI by SCE)
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: Change Proposals for ISSUE-41 (D.E.) vs XHTML and IE9
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: Change Proposals for ISSUE-41 (D.E.) vs XHTML and IE9
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: Change Proposals for ISSUE-41 (D.E.) vs XHTML and IE9
 - Change Proposals for ISSUE-41 (D.E.) vs XHTML and IE9
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - RE: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: ISSUE-103 change proposal
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: ISSUE-66 Change Proposal: no change
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - RE: Indeterministic progress bar
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: Indeterministic progress bar
 
Tuesday, 16 March 2010
- RE: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: Indeterministic progress bar
 - Re: problem with bugzilla?
 - problem with bugzilla?
 - [Bug 7525] meta/@name=keywords should be specified (and made conforming)
 - Indeterministic progress bar
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: Change Proposal for ISSUE-79, was: ISSUE-79: meta-keywords - Chairs Solicit Proposals
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - [Bug 9239] specify a convention for preventing vendor-specific non-standard extensions from clashing with themselves and future standard development
 - Re: TWO Change proposals for ISSUE-41 : Distributed Extensibility
 - TWO Change proposals for ISSUE-41 : Distributed Extensibility
 
Monday, 15 March 2010
- Re: change proposal: Provide accessibility implementation information (in the Canvas 2d Context specification) for focus rectangle and caret
 - Re: change proposal: Provide accessibility implementation information (in the Canvas 2d Context specification) for focus rectangle and caret
 - Re: ISSUE-4: Basis of the appeal to "XML editing workflows"
 - Re: [Bug 5758] insufficient accessibility fallback for <audio> or <video>
 - Re: FPWD of Additional Requirements for Bidi in HTML (rename BDI by SCE)
 - Re: FPWD of Additional Requirements for Bidi in HTML (rename BDI by SCE)
 - Re: [Bug 5758] insufficient accessibility fallback for <audio> or <video>
 - Re: [Bug 5758] insufficient accessibility fallback for <audio> or <video>
 - [Bug 7539] Since @summary is an official part of the table element, it is no longer obsolete. Suffienct warning language exists in it's definition that this entry should be removed
 - Re: [Bug 5758] insufficient accessibility fallback for <audio> or <video>
 
Saturday, 13 March 2010
Monday, 15 March 2010
- Re: [Bug 5758] insufficient accessibility fallback for <audio> or <video>
 - Re: [Bug 5758] insufficient accessibility fallback for <audio> or <video>
 - [Bug 7076] Client-side image maps attributes missing on the a element
 - Re: [Bug 5758] insufficient accessibility fallback for <audio> or <video>
 
Sunday, 14 March 2010
- Re: [Bug 5758] insufficient accessibility fallback for <audio> or <video>
 - [Bug 7391] Reference to WEBADDRESS should be replaced with reference to IRIbis
 - Re: [Bug 5758] insufficient accessibility fallback for <audio> or <video>
 - [Bug 7386] SharedWorkerGlobalScope
 - Re: Re-registration of text/html
 - Re: Old resolved bugs
 - [Bug 7056] <caption> and <figure><legend> elements should allow flow content children
 - Re: [Bug 5758] insufficient accessibility fallback for <audio> or <video>
 - [Bug 7056] <caption> and <figure><legend> elements should allow flow content children
 - Re: [Bug 5758] insufficient accessibility fallback for <audio> or <video>
 - [Bug 5758] insufficient accessibility fallback for <audio> or <video>
 
Saturday, 13 March 2010
- RE: ISSUE-88 / Re: what's the language of a document ?
 - Re: change proposal: Provide accessibility implementation information (in the Canvas 2d Context specification) for focus rectangle and caret
 - Re: ISSUE-103 change proposal
 - Re: change proposal: Provide accessibility implementation information (in the Canvas 2d Context specification) for focus rectangle and caret
 - Re: ISSUE-103 change proposal
 - Re: ISSUE-103 change proposal
 - ISSUE-103 change proposal
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - RE: Re-registration of text/html
 - RE: new dates for issue items based on today's HTML WG teleconference
 - Re: ISSUE-95 hidden - Chairs Solicit Proposals
 - Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 
Friday, 12 March 2010
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - [Bug 9098] Correct the img element definition. Replace with suggested text.
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - [Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections
 - Re: new dates for issue items based on today's HTML WG teleconference
 - Re: Breakdown of issues
 - Breakdown of issues
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Setting IDL attributes that map enumerated content attributes
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: ISSUE-88 / Re: what's the language of a document ?
 - RE: *Disregard* W3C Account and HTMLWG Participation "Unlinked"
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - W3C Account and HTMLWG Participation "Unlinked"
 - Re: ISSUE-88 / Re: what's the language of a document ?
 - Re: ISSUE-88 / Re: what's the language of a document ?
 - Re: new dates for issue items based on today's HTML WG teleconference
 - Re: new dates for issue items based on today's HTML WG teleconference
 
Thursday, 11 March 2010
- Re: new dates for issue items based on today's HTML WG teleconference
 - new dates for issue items based on today's HTML WG teleconference
 - Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - Re: ISSUE-88 / Re: what's the language of a document ?
 - Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - Re: ISSUE-79 (meta-keywords): Call for Consensus
 - Re: Setting IDL attributes that map enumerated content attributes
 - Re: change proposal: Provide accessibility implementation information (in the Canvas 2d Context specification) for focus rectangle and caret
 - Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - Re: Setting IDL attributes that map enumerated content attributes
 - Re: Setting IDL attributes that map enumerated content attributes
 - Setting IDL attributes that map enumerated content attributes
 - Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - Re: change proposal: Provide accessibility implementation information (in the Canvas 2d Context specification) for focus rectangle and caret
 - Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - Re: Re-registration of text/html
 - RE: Re-registration of text/html
 - Re: Re-registration of text/html
 - RE: Re-registration of text/html
 - Re: ISSUE-88 / Re: what's the language of a document ?
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: ISSUE-88 / Re: what's the language of a document ?
 - Re: ISSUE-88 / Re: what's the language of a document ?
 - Re: ISSUE-88 / Re: what's the language of a document ?
 - Re: ISSUE-88 / Re: what's the language of a document ?
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - Re: ISSUE-88 / Re: what's the language of a document ?
 - Re: ISSUE-88 / Re: what's the language of a document ?
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - RE: ISSUE-88 / Re: what's the language of a document ?
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - RE: ISSUE-88 / Re: what's the language of a document ?
 
Wednesday, 10 March 2010
- RE: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: Re-registration of text/html
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: ISSUE-4: Basis of the appeal to "XML editing workflows"
 - Re: Re-registration of text/html
 - warning: redirect test cases broken, was: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - Re: Re-registration of text/html
 - Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - Re: Re-registration of text/html
 - Re: The cite element in H:TML draft and Differences draft
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: Re-registration of text/html
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
 - [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives
 - [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives
 - [Bug 8646] Private communication exception
 - [Bug 6496] Allow <img aria-labelledby> to act as a text alternative
 - Re: DRAFT Anaheim agenda
 - ISSUE-4: Basis of the appeal to "XML editing workflows"
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - RE: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 
Tuesday, 9 March 2010
- Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: <video> attributes and children
 - Re: ISSUE-66 Change Proposal: no change
 - Re: a suggestion and a request on bugs and change proposals
 - Re: a suggestion and a request on bugs and change proposals
 - a suggestion and a request on bugs and change proposals
 - Re: ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - Re: ISSUE-66 Change Proposal: no change
 - ISSUE-66 Change Proposal: be more explicit about potential repair techniques
 - ISSUE-66 Change Proposal: no change
 - Old resolved bugs
 - Bug stats update
 
Monday, 8 March 2010
- Re: CfC: Adopt Change Proposal for Issue-27 (rel-ownership)
 - Re: Change Proposal for ISSUE-101 (us-ascii-ref)
 - Re: ISSUE-41: decentralized-extensibility - Chairs Solicit Proposals
 - Re: ISSUE-41: decentralized-extensibility - Chairs Solicit Proposals
 - Re: change proposal: Provide accessibility implementation information (in the Canvas 2d Context specification) for focus rectangle and caret
 - Re: ISSUE-41: decentralized-extensibility - Chairs Solicit Proposals
 - Re: change proposal: Provide accessibility implementation information (in the Canvas 2d Context specification) for focus rectangle and caret
 - Re: ISSUE-104 (sniffing-optional): Chairs Solicit Proposals
 - Re: ISSUE-41: decentralized-extensibility - Chairs Solicit Proposals
 - Re: FPWD of Additional Requirements for Bidi in HTML
 - Re: The cite element in H:TML draft and Differences draft
 - The cite element in H:TML draft and Differences draft
 - Re: FPWD of Additional Requirements for Bidi in HTML
 - FW: Daylight Saving Time start for 2010
 - RE: FPWD of Additional Requirements for Bidi in HTML
 - RE: FPWD of Additional Requirements for Bidi in HTML
 - Re: FPWD of Additional Requirements for Bidi in HTML
 
Sunday, 7 March 2010
- RE: FPWD of Additional Requirements for Bidi in HTML
 - Re: FPWD of Additional Requirements for Bidi in HTML
 - Re: <video> attributes and children
 - Re: H:TML draft for FPWD consideration
 - Re: H:TML Feedback (Re: H:TML draft for FPWD consideration)
 - Re: H:TML draft for FPWD consideration - object
 - Re: <video> attributes and children
 - Re: <video> attributes and children
 - Re: <video> attributes and children
 - Re: FPWD of Additional Requirements for Bidi in HTML
 - Re: Color Management in HTML5?
 - RE: Color Management in HTML5?
 - Re: Color Management in HTML5?
 - RE: Color Management in HTML5?
 
Saturday, 6 March 2010
- RE: Color Management in HTML5?
 - Re: Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)
 - Re: <video> attributes and children
 - <video> attributes and children
 
Friday, 5 March 2010
- Re: Color Management in HTML5?
 - Re: FW: Request that "conforming document" be better defined and more carefully referenced
 - Re: Color Management in HTML5?
 - Re: Color Management in HTML5?
 - Re: Color Management in HTML5?
 - Re: Color Management in HTML5?
 - Re: FPWD of Additional Requirements for Bidi in HTML
 - [Bug 9197] Remove unnecessary editorialization in acknowledgement section
 - RE: Color Management in HTML5?
 - ISSUE-94 and significant editing changes to specification since issue was created
 - FPWD of Additional Requirements for Bidi in HTML
 - Re: Color Management in HTML5?
 - Color Management in HTML5?
 
Thursday, 4 March 2010
- RE: ISSUE-41: decentralized-extensibility - Chairs Solicit Proposals
 - Re: ISSUE-41: decentralized-extensibility - Chairs Solicit Proposals
 - Re: Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)
 - Re: Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)
 - Call for Exclusions - HTML: The Markup Language
 - Re: Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)
 - HTML WG Working Drafts have been published
 - Re: CfC: Adopt ISSUE-1 PINGUI / ISSUE-2 PINGPOST Change Proposal to remove @ping from HTML5
 - Re: Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)
 - [minutes] HTML WG 2010004
 - Re: CfC: Close ISSUE-55 profile by amicable resolution
 - Re: CfC: Adopt ISSUE-1 PINGUI / ISSUE-2 PINGPOST Change Proposal to remove @ping from HTML5
 - Re: Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)
 - Re: Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)
 - Re: Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)
 - RE: Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)
 - Re: Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)
 - RE: Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)
 - Re: links with the HTML5 spec are messed up
 - Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)
 - change proposal: Provide accessibility implementation information (in the Canvas 2d Context specification) for focus rectangle and caret
 - Re: ISSUE-56 (urls-webarch) - Chairs Solicit Alternate Proposals or Counter-Proposals
 - Re: Issue-9 (video-accessibility): Chairs Solicit Proposals
 - Re: Issue-9 (video-accessibility): Chairs Solicit Proposals
 - Re: ISSUE-56 (urls-webarch) - Chairs Solicit Alternate Proposals or Counter-Proposals
 - Re: ISSUE-104 (sniffing-optional): Chairs Solicit Proposals
 - Re: ISSUE-56 (urls-webarch) - Chairs Solicit Alternate Proposals or Counter-Proposals
 - Re: ISSUE-56 (urls-webarch) - Chairs Solicit Alternate Proposals or Counter-Proposals
 - Re: links with the HTML5 spec are messed up
 - Re: links with the HTML5 spec are messed up
 - Re: ISSUE-104 (sniffing-optional): Chairs Solicit Proposals
 - Re: ISSUE-104 (sniffing-optional): Chairs Solicit Proposals
 - Re: ISSUE-104 (sniffing-optional): Chairs Solicit Proposals
 - links with the HTML5 spec are messed up
 - Re: ISSUE-56 (urls-webarch) - Chairs Solicit Alternate Proposals or Counter-Proposals
 - RE: Change Proposal for ISSUE-101 (us-ascii-ref)
 
Wednesday, 3 March 2010
- Re: CfC: Adopt Change Proposal for Issue-27 (rel-ownership)
 - Re: Change Proposal for ISSUE-101 (us-ascii-ref)
 - Re: Change Proposal for ISSUE-101 (us-ascii-ref)
 - Re: CfC: Adopt Change Proposal for Issue-27 (rel-ownership)
 - Re: Change Proposal for ISSUE-101 (us-ascii-ref)
 - Re: Change Proposal for ISSUE-101 (us-ascii-ref)
 - Re: CfC: Adopt Change Proposal for Issue-27 (rel-ownership)
 - Re: CfC: Adopt Change Proposal for Issue-27 (rel-ownership)
 - Re: Issue-9 (video-accessibility): Chairs Solicit Proposals
 - Re: Change Proposal for ISSUE-101 (us-ascii-ref)
 - Re: ISSUE-56 (urls-webarch) - Chairs Solicit Alternate Proposals or Counter-Proposals
 - Re: Issue-9 (video-accessibility): Chairs Solicit Proposals
 - Re: Issue-9 (video-accessibility): Chairs Solicit Proposals
 - Re: ISSUE-56 (urls-webarch) - Chairs Solicit Alternate Proposals or Counter-Proposals
 - Re: Issue-9 (video-accessibility): Chairs Solicit Proposals
 - apologies for test <eom>
 - RE: Issue-9 (video-accessibility): Chairs Solicit Proposals
 - Re: Issue-9 (video-accessibility): Chairs Solicit Proposals
 - {agenda} HTML WG telcon 2010-03-04: actions, publications, decision policy, issues
 - RE: Issue-9 (video-accessibility): Chairs Solicit Proposals
 - Re: Change Proposal for ISSUE-101 (us-ascii-ref)
 - Re: Issue-9 (video-accessibility): Chairs Solicit Proposals
 - Re: Change Proposal for ISSUE-101 (us-ascii-ref)
 - Change Proposal for ISSUE-101 (us-ascii-ref)
 - Re: Issue-9 (video-accessibility): Chairs Solicit Proposals
 - Re: Issue-9 (video-accessibility): Chairs Solicit Proposals
 - Re: Re-registration of text/html
 - Re: ISSUE-104 (sniffing-optional): Chairs Solicit Proposals
 - Re: CfC: Adopt Change Proposal for Issue-27 (rel-ownership)
 - Re: Schemas and validation
 - ISSUE-101 (us-ascii-ref): Chairs Solicit Proposals
 - ISSUE-104 (sniffing-optional): Chairs Solicit Proposals
 - ISSUE-102 (meta-name-registry): Chairs Solicit Proposals
 - ISSUE-99 (meta-scheme): Chairs Solicit Proposals
 - Re: CfC: Adopt Change Proposal for Issue-27 (rel-ownership)
 - Issue-9 (video-accessibility): Chairs Solicit Proposals
 - ISSUE-79 (meta-keywords): Call for Consensus
 - ISSUE-56 (urls-webarch) - Chairs Solicit Alternate Proposals or Counter-Proposals
 - Re: CfC: Adopt Change Proposal for Issue-27 (rel-ownership)
 - Re: Re-registration of text/html
 - CfC: Adopt Change Proposal for Issue-27 (rel-ownership)
 - Re: Schemas and validation
 - Re: H:TML draft for FPWD consideration - object
 
Tuesday, 2 March 2010
- RE: Editors, please prepare drafts for publication on Thursday, March 4
 - Re: Editors, please prepare drafts for publication on Thursday, March 4
 - RE: Editors, please prepare drafts for publication on Thursday, March 4
 - RE: Editors, please prepare drafts for publication on Thursday, March 4
 - RE: Editors, please prepare drafts for publication on Thursday, March 4
 - RE: Editors, please prepare drafts for publication on Thursday, March 4
 - RE: Editors, please prepare drafts for publication on Thursday, March 4
 - RE: Editors, please prepare drafts for publication on Thursday, March 4
 - Re: New Version Notification - draft-nottingham-http-link-header-08.txt
 - Re: Schemas and validation
 - Re: Schemas and validation
 - Re: Schemas and validation
 - Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
 - Re: Schemas and validation
 - Re: Schemas and validation
 - Re: Schemas and validation
 - Re: New Version Notification - draft-nottingham-http-link-header-08.txt
 - Re: use of title attributes in HTML5 spec.
 - Re: use of title attributes in HTML5 spec.
 - Re: use of title attributes in HTML5 spec.
 - Re: use of title attributes in HTML5 spec.
 - Re: H:TML draft for FPWD consideration - object
 - Re: use of title attributes in HTML5 spec.
 - use of title attributes in HTML5 spec.
 - Re: Counter change-proposal for ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - Re: change proposal: Allow the a element to have ARIA role attribute values other than link
 - Re: FW: Request that "conforming document" be better defined and more carefully referenced
 - Re: change proposal: Allow the a element to have ARIA role attribute values other than link
 - Re: Schemas and validation
 - Re: Schemas and validation
 - Re: New Version Notification - draft-nottingham-http-link-header-08.txt
 - Re: Schemas and validation
 - Re: Editors, please prepare drafts for publication on Thursday, March 4
 - Re: Schemas and validation
 - Re: New Version Notification - draft-nottingham-http-link-header-08.txt
 - Re: Schemas and validation
 
Monday, 1 March 2010
- Fwd: New Version Notification - draft-nottingham-http-link-header-08.txt
 - Re: Schemas and validation
 - Re: Editors, please prepare drafts for publication on Thursday, March 4
 - Editors, please prepare drafts for publication on Thursday, March 4
 - Re: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
 - Re: change proposal: Allow the a element to have ARIA role attribute values other than link
 - Re: Schemas and validation
 - Schemas and validation
 - Re: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - Re: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - RE: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - Re: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - Re: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - Re: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - RE: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - Re: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - Re: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - Re: Please vote on the canvas accessibility proposal
 - Re: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - RE: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - Re: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - Re: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - RE: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - RE: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - RE: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - Re: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - Re: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - RE: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)
 - RE: ISSUE-4 (html-versioning) (vs. ISSUE-30 longdesc)