:-(

what little public record there is of the original HTML WG charter discussions is in here.

"When an application uses MSXML to process XHTML, redundant retrieval requests for well-known DTD files from the W3C Web server cause XHTML parsing to fail on a Windows-based computer"

potentially useful.

"No, RDF asked XML for namespaces." Source of the infamous "RDF tax" line of thought I presume

I'm confused. Inequality amongst women & men in technology is something I'm _very_ concerned about... but I gathered no evidence of sexism in that thread. Maybe having met Maciej in person and having read Shelly's blog(s) for a long time helps me to get a better sense of the voices in that thread?

I wonder how they'll rebrand XHTML2... hrm.

Branched spec editing how-to. (Thanks heycam!)

0_o

...uh...

"This document and its associated tables apply to all versions of Opera 10x on FreeBSD, Mac, Linux, Solaris, Windows, plus Opera Mobile running on the Opera Presto 2.2 rendering engine. "

The existing accessibility vendor participation @w3c is depressing... would be nice to get these folks at a F2F meeting to at least understand why.

"This document presents the specification for a primitive datatype representing internationalized text that is used in both the RIF and OWL 2 languages."

Good example from Henri Sivonent of how gnarly forms parsing can get

"Don't cross the streams"

"The links below include tests for three W3C specifications in various stages of development. These include CSS 2.1, HTML5, and ARIA."

I think this is the first shipping browser with GeoLocation support... cool stuff.

"This page allows the user to test the effect of various string functions used in URI creation, processing, or interpretation. Its initial intention is to help debug the atomic pieces of what will become more elaborate processing routines, but it may also be helpful in exploring the consequences of various design decisions in URI-related specifications."

IETF draft for spec'ing out the about: URI scheme.

This FAQ was the only positive result from this rather insane thread on www-style: http://lists.w3.org/Archives/Public/www-style/2009Feb/0475.html

A little analysis of @summary usage on data tables found in the wild.

Mozilla Bug 478665 discussion was moved here... The short of it seems to be that Mozilla is preparing for the possibility that the HTML 5 spec becomes logjammed in the W3C process circus. Think of this as HTML 4.1: a ton of errata covering the error handling for rendering and parsing, DOM consistency, plus adoption of mature features like <canvas>. That audio and video is missing from this draft is odd given Mozilla's significant work on those new elements+apis. To be fair it seems to be more of an _idea_ than say a "working draft".

0_o

"On this point, I have to call B.S. again. That a document is served as text/html does not make it HTML. Much less does it make it not XML. If a document satisfies the BNF grammar and the various well-formedness constraints, it is XML, whatever you call it. It may also be HTML, and perhaps other things as well."

"Note that in XHTML 1.0, the name attribute of these elements is formally deprecated, and will be removed in a subsequent version of XHTML"

Ian Hickson's status summary of whatwg work

"This document defines an interface definition language, Web IDL, that can be used to describe interfaces that are intended to be implemented in web browsers. Web IDL is an IDL variant with a number of features that allow the behavior of common script objects in the web platform to be specified more readily. How interfaces described with Web IDL correspond to constructs within ECMAScript and Java execution environments is also detailed."

"This document describes the properties (the W3C) desire(s) of the Web and the design choices that have been made to achieve them. It promotes the reuse of existing standards when suitable, and gives guidance on how to innovate in a manner consistent with Web architecture."

Yay, test suites!

"As the web is becoming ubiquitous, interactive, and multimodal, technology needs to deal increasingly with human factors, including emotions. The present Final Report of the Emotion Markup Language Incubator Group provides elements for an Emotion Markup Language striking a balance between scientific well-foundedness and practical applicability. The language is conceived as a "plug-in" language suitable for use in three different areas: (1) manual annotation of data; (2) automatic recognition of emotion-related states from user behaviour; and (3) generation of emotion-related system behaviour."

Henri Sivonen provides an update on his Gecko/HTML5 work.

"I sincerely hope the HTML Working Group considers our work in CDF before they re-invent the wheel."

This approximates the types of standards I think a certain vocal group of folks are interested in making.

XML 1.0 5th Edition plans to make a "minor" change to allow any Unicode (version 5 and future versions) character in element and attribute names. Seems like an enough change to warrant an XML 1.2 but since XML 1.1 went down in flames... I guess this was a way to "force" existing implementations to improve. There's going to be a lot of XML 1.0 implementations that are never updated to support this feature though and I think that's just going to confuse the same user group who needs this support.

Ian Hickson reviews emails covering looping audio and video resources in HTML 5. Key take away - "1. Simplify the API where possible; in particular start/end/loopStart/loopEnd and so on...I've removed all those attributes and related APIs."

"This specification describes the fifth major version of the HTML vocabulary. It provides the details necessary for producers of HTML to create conformant HTML documents. By design, it does not describe related APIs nor attempt to describe how consumers of HTML are meant to process HTML documents."

Jeremy Keith's experimental social audio project uses the HTML 5 audio element where supported (Safari for instance and the upcoming Firefox 3.1)

Try to pin down conversations that led to the <bb type="makeapp"> syntax proposal in HTML 5

"Murray Maloney hosted a lunch BOF around the theme of W3C's HTML5 work, tooling and community. These are my notes from the discussion when I asked Ian Hickson what would help make his HTML5-editing life easier; photo by TimBL."

"This document illustrates how to write HTML 5 documents, focussing on simplicity and practical applications for beginners while also providing in depth information for more advanced web developers"

"State Chart XML (SCXML) is currently a Working Draft published by the World Wide Web Consortium (W3C). SCXML provides a generic state-machine based execution environment based on Harel State Tables"