Re: XML, namespaces, extensibility and validation

Hi Mark,

In a process to try to clarify.

Mark Nottingham (5 sept. 2007 - 10:15) :
>>> - give a list of extensions used the validator does not know  
>>> about.  This is a warning, not an error.
>>
>> Could you give an example of that?
>
> My thinking was that unrecognised elements/attributes in HTML (not  
> just XHTML) should raise a warning, rather than an error.

Fix if I misunderstood:

For HTML 4.01, HTML 3.2 (W3C specs), we have two choices.
    1. Rescinding them when HTML 5 has been published [1]
    2. Republish them with these processing rules (unlikely)



For HTML 5, does it mean
    unrecognised elements/attributes
    => which are not in the HTML 5 specification.

This is a conformant HTML 5 document.

<!DOCTYPE html>
<title>life is beautiful<title>
<p>


You would issue warnings for "bar" attribute and "foo" element.

<!DOCTYPE html>
<title>life is beautiful<title>
<p bar>
<foo>

You would issue error for "foo" element and warning for "bar" attribute
	(markup is forbidden inside title element, text only)

<!DOCTYPE html>
<title>life <foo bar>is beautiful<title>
<p>

In Camino (Firefox 2 engine), it closes the title and moves the "foo"  
element to the body.
In Safari 2.0, the text and the elements disappears aka no title, no  
foreign element.
http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE% 
20html%3E%0A%3Ctitle%3Elife%20%3Cfoo%20bar%3Eis%20beautiful%3Ctitle%3E 
%0A%3Cp%3E%0A




[1]: http://www.w3.org/2005/10/Process-20051014/tr.html#rec-rescind


-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
   QA Weblog - http://www.w3.org/QA/
      *** Be Strict To Be Cool ***

Received on Thursday, 6 September 2007 03:53:23 UTC