W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2006

[whatwg] The problems with namespaces in text/html

From: Henri Sivonen <hsivonen@iki.fi>
Date: Sun, 5 Nov 2006 21:24:57 +0200
Message-ID: <651149E0-E0CB-4563-969B-E6E82B107B89@iki.fi>
On Nov 5, 2006, at 16:35, Elliotte Harold wrote:

> Anne van Kesteren wrote:
>
>> Well, the problem is that they would mean different things.  
>> Consider the following fragment:
>
> Meaning is in the eye of the beholder. In point of the fact, there  
> are a lot more than two different things the fragment you propose  
> might mean. Meaning is determined locally by each recipient for its  
> own unique purposes, which may or may not be anything close to what  
> the document producer expects.

Well, the whole point of having a spec is to give a mutual  
understanding to the producer and consumer of what the bytes mean.

> The syntax matters. If you give me the right well-formed syntax, I  
> can do what I need to do with it, as can others. If you give me  
> malformed syntax, working with the document gets a lot more  
> complicated. My concern is not from browser vendors on agreeing on  
> one interpretation that's somehow useful to them. It's making sure  
> that they don't in the process break everything else anyone else  
> might want to do with these documents.

Everyone who wishes to process HTML5 with XML tools is going to need  
an HTML5 parser that exposes an interface that makes the HTML5 parser  
look like an XML parser to the rest of the tool chain. The part of  
the XML tool chain that you can't use with HTML5 is the XML parser  
itself.

-- 
Henri Sivonen
hsivonen at iki.fi
http://hsivonen.iki.fi/
Received on Sunday, 5 November 2006 11:24:57 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:49 UTC