PUBLIC MARKS with tag w3c

HTML5 is not a technical achievement, it’s a social movement.

Laissé dans le noir par Adobe, Doug Schepers (Mr SVG au W3C) voit de la lumière dans la pièce d'à côté.

The Web platform encompasses many tools that live outside of browsers, but the important part of calling a technology a piece of the Web platform is that it works with the public content of the Web. For instance, a web crawler like Google’s doesn’t run in a browser, but processes public Web content, so it and its underlying pieces are clearly built on the web platform.

Google’s role is not free from the perception of conflict of interest, and that coupled with Ian’s endorsed role as a dictator will affect the credibility of the outcome produced. In particular, it will give Microsoft all of the excuse it needs to avoid implementing the standards. (Not that eliminating that excuse will magically cause Microsoft to participate…)

On December 11th, 2008 the W3C WAI released the WCAG 2.0 This site pretends to show what they are and how to accomplish them.

The HTML 2.0 specification, RFC1866, defines an SGML application and an Internet media type. The specification notes that extensions are planned, but only the text/html; level=2 internet media type and the "-//IETF//DTD HTML 2.0//EN" document type are defined. This document suggests the use of URIs as system identifiers for document type definitions, allowing decentralized evolution of the language. The use of marked sections as a transition technique and the continued use of the level mechanism for standardized points in the evolution path are discussed.

The HTML 2.0 specification, RFC1866, defines an SGML application and an Internet media type. The specification notes that extensions are planned, but only the text/html; level=2 internet media type and the "-//IETF//DTD HTML 2.0//EN" document type are defined. This document suggests the use of URIs as system identifiers for document type definitions, allowing decentralized evolution of the language. The use of marked sections as a transition technique and the continued use of the level mechanism for standardized points in the evolution path are discussed.

In particular, you may be overstating how closely you represented the browser vendors.

Whether Henri ever writes a validator that handles HTML5 and RDFa, I am confident that somebody at the W3C will. Even if I have to do it myself.

Last but not least, last time I checked Mozilla Labs' name contained the word "Labs". In general, labs are here to make experiments, things that don't seem ordinary or even reasonable, labs are here to pave the future, not do what all others are doing too.

The Geolocation API defines a high-level interface to location information associated with the hosting device, such as latitude and longitude.

future or web mashups are geo localized

<video> and <audio> elements, the W3C Geolocation API, JavaScript query selectors, CSS 2.1 and 3 properties, SVG transforms and offline applications. More info on this is located here: http://developer.mozilla.org/En/Firefox_3.1_for_developers