Re: ACTION-642: With help from Larry to propose plan to liaise with PLH to register HTML media type


The HTML specs (W3C and WHATWG) define a new Media Type registration for application/xhtml+xml, so there is going to be a new registration anyway, if not a new RFC. XHTML5 documents do not need to have an xmlns attribute pointing to the XHTML namespace -- that is defaulted -- though the draft registration [1] does mention that namespace and if you know where to look, the HTML5 spec does say that elements are in that namespace [2].

It may be that the existing namespace document is the best place for a registry (I can't see any reason to maintain two?) and just needs to be updated, or that it should point to a separate registry perhaps maintained in a more flexible method such as using a wiki. I think this is something we need to discuss.



On 18 Jan 2012, at 16:05, Jonathan A Rees wrote:

> This looks great. Nit: As I said in IRC at the F2F,
> application/xhtml+xml *already* has such a registry, i.e. the XHTML
> namespace document. The right place to reference a new registry would
> be there, and that's OK (right?). No need to issue a new RFC for
> xhtml.
> Jonathan
> On Tue, Jan 17, 2012 at 5:09 PM, Jeni Tennison <> wrote:
>> Hi,
>> To complete ACTION-642 (with many thanks to Larry):
>>  There is currently no direct path, following definitional specifications,
>>  from an HTML document to the specs for extensions such as microdata or RDFa.
>>  The goal is to ensure there is such a path to "applicable
>>  specifications".
>>  We will work with PLH, in consultation with the HTML WG, to create a
>>  W3C-sponsored registry of applicable HTML extensions and their
>>  specifications. The W3C-sponsored registry might also include references
>>  to other registries of applicable specifications maintained by other
>>  groups and organizations.
>>  Once the basics and location of the registry is settled, we will work to
>>  ensure that this registry is referenced within revised Internet Media Type
>>  registrations for text/html and application/html+xml.
>>  This will allow a direct chain ("follow-your-nose") from content-type labels
>>  to the set of specifications covering the expected behavior of applications
>>  attempting to interpret data with that label.
>> Cheers,
>> Jeni
>> --
>> Jeni Tennison

Jeni Tennison

Received on Wednesday, 18 January 2012 17:12:42 UTC