Re: Deprecated stuff in XHTML1.1 (was: Re: usemap in XHTML 1.1 no longer a URI?!)

> On 3/4/02 8:18 PM, Peter Sheerin wrote:
> >>So if there's a _serious error_ in the 1.1 DTD, why doesn't it get
> >>fixed? Is it so hard to write an errata page? I got confused by this and
> >>I'm sure I'm not the first, nor the last one...
> >>
> >
> > The error is the change in the chartype for usemap to IDREF. That change
> > broke all existing browsers, and that was not the intent of 1.1. I've
not
> > written an errata page before, but if you point me to any docs for the
> > procedures of making it official, I'd be happy to put it together.
> >
> Well, not only that. There's a discrepancy between
> http://www.w3.org/TR/xhtml11/doctype.html and
> http://www.w3.org/TR/xhtml-modularization/dtd_module_defs.html
>
> xhtml1.1 doesn't have a module for frames and targets while xhtml-mod
> has. That's what I'm not understanding...

I don't think those are in conflict, though the differences are not
well-described by those documents.  The second link above contains the
definitions of all the "XHTML Abstract Modules", including deprecated ones
such as applet, frames, name identification, and legacy. XHTML 1.1 is based
on this abstraction framework, but doesn't use all of them--it's closer to
XHTML 1.0 Strict in which portions it includes.

If one doesn't like the limitations of XHTML 1.1, then he can use the same
structure that was used to build 1.1 and build one based on a different set
of modules. For instance, the table module could be left out to create a DTD
for phone browsers. I wish the w3c docs provided some clear examples on how
to do this--I had to spend a lot of time fiddling and getting help on the
#validator IRC chat to figure out how to piece everything together.

Received on Monday, 4 March 2002 19:26:57 UTC