- From: Lars A. <lars.pm@chello.se>
- Date: Fri, 19 Jul 2002 08:40:07 -0400 (EDT)
- To: www-validator@w3.org
The validator seems to use an old DTD for ISO-HTML.
The one used <http://validator.w3.org/sgml-lib/ISO-HTML/15445.dtd> is
probably from the time before the technical corrigendum:
<http://purl.org/NET/ISO+IEC.15445/TC1.html>
I noticed the difference while trying to validate a block element image map.
For example this is the ATTLIST for A in the W3C validator:
<!ATTLIST A
--Case shall not be taken into account when determining a match
between an ID value and a NAME value, between an ID value and
an HREF value or between a NAME value and an HREF value.
Comparisons should be made with the values folded to upper case.
The NAME attribute value specification shall be processed as if the
declared value were NAME.
It is recommended that authors of HTML documents give
preference to the ID attribute over the NAME attribute.
--
%core; -- Element CLASS, ID and TITLE --
%i18n; -- Internationalization DIR and LANG --
ACCESSKEY CDATA #IMPLIED -- Accessibility key character --
CHARSET CDATA #IMPLIED -- Character encoding as per RFC2045 --
HREF %URI; #IMPLIED -- Source anchor is URI of target --
HREFLANG NAME #IMPLIED -- Language code of resource --
NAME CDATA #IMPLIED -- Target anchor --
REL CDATA #IMPLIED -- Forward link types --
REV CDATA #IMPLIED -- Reverse link types --
TABINDEX NUMBER #IMPLIED -- Position in tabbing order --
TYPE CDATA #IMPLIED -- Advisory content type -->
And this is the corresponding paragraph in the current specification at
<http://purl.org/NET/ISO+IEC.15445/15445.html>
<!ATTLIST A
--Case shall not be taken into account when determining a match
between an ID value and a NAME value, between an ID value and
an HREF value or between a NAME value and an HREF value.
Comparisons should be made with the values folded to upper case.
The NAME attribute value specification shall be processed as if the
declared value were NAME.
It is recommended that authors of HTML documents specify both ID and
NAME attributes. When both attributes are specified, they shall have
identical values.
COORDS shall not be specified if SHAPE has the value `default'.
--
%core; -- Element CLASS, ID and TITLE --
%i18n; -- Internationalization DIR and LANG --
ACCESSKEY CDATA #IMPLIED -- Accessibility key character --
CHARSET CDATA #IMPLIED -- Character encoding as per RFC2045 --
COORDS CDATA #IMPLIED -- Comma separated list of values --
HREF %URI; #IMPLIED -- Source anchor is URI of target --
HREFLANG NAME #IMPLIED -- Language code of resource --
NAME CDATA #IMPLIED -- Target anchor --
REL CDATA #IMPLIED -- Forward link types --
REV CDATA #IMPLIED -- Reverse link types --
SHAPE %shape; rect -- Control interpretation of coords --
TABINDEX NUMBER #IMPLIED -- Position in tabbing order --
TYPE CDATA #IMPLIED -- Advisory content type -->
--
/M.v.h. Lars A.
Received on Friday, 19 July 2002 10:49:01 UTC