W3C home > Mailing lists > Public > www-validator-cvs@w3.org > April 2007

[Bug 68] provide a warning when an XHTML page lacks an xmlns declaration.

From: <bugzilla@wiggum.w3.org>
Date: Mon, 02 Apr 2007 10:47:56 +0000
CC:
To: www-validator-cvs@w3.org
Message-Id: <E1HYK4q-0000He-J3@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=68


ot@w3.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED




------- Comment #9 from ot@w3.org  2007-04-02 10:47 -------
Done in HEAD (soon to be 0.8.0), see:
http://qa-dev.w3.org/wmvs/HEAD/check?uri=http://qa-dev.w3.org/wmvs/HEAD/dev/tests/xhtml1-strict-missing-xmlns.html;ss

The problem is that DTDs can either set an attribute to FIXED or REQUIRED but
not both... So we had to deal with this issue differently.

Note that current CVS version shoots an error at such an issue, whether it
should be a warning is unclear, but comments in e.g
http://www.w3.org/QA/2007/03/validation_to_conformance.html#comments seem to
show that there is no strong opposition (yet?) to marking
not-validation-but-conformance issues as errors. 

Also see 
http://qa-dev.w3.org/wmvs/HEAD/dev/tests/smil20-profile-doctype.smi
for an example of document with bogus xmlns, and that is also marked as error
by the current cvs HEAD.

Resolving FIXED.
Received on Monday, 2 April 2007 10:48:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:54:56 GMT