W3C home > Mailing lists > Public > public-webapi@w3.org > December 2006

RE: NSResolver Re: Selectors API naming

From: Chris Wilson <Chris.Wilson@microsoft.com>
Date: Thu, 21 Dec 2006 14:09:46 -0800
Message-ID: <44FAFFCDE516434D84E6B62121DB6A440413769A@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
To: Anne van Kesteren <annevk@opera.com>, Charles McCathieNevile <chaals@opera.com>, Dave Massy <dave.massy@microsoft.com>, "Web API WG (public)" <public-webapi@w3.org>
CC: Tina Duff <tinad@microsoft.com>
Sorry.  I should be saying "what namespace URI is an HTML document in?"

-----Original Message-----
From: Anne van Kesteren [mailto:annevk@opera.com] 
Sent: Thursday, December 21, 2006 2:07 PM
To: Chris Wilson; Charles McCathieNevile; Dave Massy; Web API WG (public)
Cc: Tina Duff
Subject: Re: NSResolver Re: Selectors API naming

On Thu, 21 Dec 2006 22:57:55 +0100, Chris Wilson  
<Chris.Wilson@microsoft.com> wrote:
> Whose job is it in the W3C?  (This isn't "how you transform HTML into a  
> DOM" - it's "what doctype do you presume when it's not there?")

DOCTYPEs? DOCTYPEs have two use cases on the web as far as I know:

   1. In HTML they provide a way for the author to pick between
      "quirks mode", "almost standards mode" (in some browsers)
      and "standards mode". What these modes imply varies among
      implementations at the moment. In general they affect
      rendering. In some implementations they affect parsing
      too.

   2. In XML some "known DOCTYPEs" tell the user agent to
      support a set of "named entities".

(Note that I said "the web" above.)


If something is HTML or not depends on the media type, mostly. text/html  
-> HTML (except when you're fetching something like a feed). I think Ian  
Hickson is doing some research on this.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Thursday, 21 December 2006 22:10:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:56 GMT