W3C home > Mailing lists > Public > public-html@w3.org > August 2008

Re: Extensibility strategies

From: Henri Sivonen <hsivonen@iki.fi>
Date: Tue, 5 Aug 2008 15:03:01 +0300
Cc: Ian Hickson <ian@hixie.ch>, "'HTML WG'" <public-html@w3.org>
Message-Id: <5CC953D2-86A5-4921-BA60-02934F42C944@iki.fi>
To: Sam Ruby <rubys@us.ibm.com>

On Aug 5, 2008, at 14:29, Sam Ruby wrote:
> Henri Sivonen <hsivonen@iki.fi> wrote on 08/05/2008 06:39:58 AM:
> > Or is this thread really about establishing a mechanism that  
> involves
> > binding a prefix to a URI using reserved attributes starting with
> > "xmlns:" and then using the prefix in front of local names separated
> > by a colon?
>
> There are some advantages to such an approach, and some  
> disadvantages.  Some of the advantages include working with the DOM  
> API.  Some of the disadvantages include usability issues that you  
> have referred to.  Other solutions which do not involve attributes  
> starting with "xmlns:" can be found which map onto the DOM API.   
> There may be ways to mitigate the usuability issus with solutions  
> which involve colons in element names.
>

I'd rather not recap the whole ARIA discussion, since I've had that  
discussion way too many times. However, compatibility with the DOM is  
the major *dis*advantage of *any* scheme that puts a colon in element  
or attribute names, since the colon is already special in XML and IE.

With a colon in names, you can't have DOM consistency with all of  
these at the same time:
  * text/html in existing shipped versions of Firefox, Safari and Opera.
  * text/html in existing shipped versions of IE.
  * text/html in future HTML5-supporting browsers.
  * application/xhtml+xml in existing shipped versions of Firefox,  
Safari and Opera.

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/
Received on Tuesday, 5 August 2008 12:03:42 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:57 UTC