why distinctions within XHTML?

[Mark Birbeck]

It's exactly on topic!! I am arguing that one of the main uses for XHTML
*today* is as an intermediary between old HTML and squeaky-clean new
XML. That's why we need three variants - because there's three (ish)
HTMLs. If you want to validate you have three DTDs to choose from, and
if you want to mix document types you have three namespaces to help you.
What you can't do is validate the mixed documents - but then who can ...
yet?

Mark

> -----Original Message-----
> From: Hunter, David [mailto:dhunter at Mobility.com]
> Sent: 01 September 1999 15:30
> To: XML-Dev Mailing list
> Subject: RE: why distinctions within XHTML?
> 
> 
> > From: Mark Birbeck [mailto:Mark.Birbeck at iedigital.net]
> > David Brownell wrote:
> > > Mark Birbeck wrote:
> > > > 
> > > >  6. There are three variants of HTML 4.0 so we need 
> three variants
> > > >     of 'HTML 4.0 as XML' (let's call it XHTML).
> > > 
> > > Isn't that assertion pretty core to this debate?  That is, it's
> > > not a generally accepted assumption.
> > 
> > If you want to write something that transforms current HTML 
> into XML,
> > you need to go via an XML version of HTML. Since there are three
> > versions of HTML, then you need three 'XML versions of HTML'. 
> > To me that
> > says nothing about the future direction of XHTML, or what future
> > browsers will do, etc. It just says if you want to 
> manipulate current
> > documents, you have to accept they are in one of three 
> dialects of the
> > same language.
> 
> <?email snip?>
> 
> > That's good - and I'm sure 'modular' XHTML will address all those
> > issues. But what about dealing with current problems? We need 
> > a mark-up
> > for transforming current HTML documents to XML. And when I 
> say this, I
> > don't mean converting:
> > 
> > <TD ALIGN=LEFT>The Thin Red Line <B>1998</td>
> > 
> > To:
> > 
> > <TD ALIGN="LEFT">The Thin Red Line <B>1998</B></TD>
> > 
> > That is converting it to an XML version of HTML, but there is no
> > meta-information. I mean converting it to:
> > 
> > <Film>
> >     <Title>The Thin Red Line</Title>
> >     <Year>1998</Year>
> > </Film>
> > 
> 
> <?email snip?>
> 
> I think this post is slightly off topic, for talking about XHTML.  The
> debate here is:
> 
> a)  Although there are currently three flavours of HTML 4, 
> *should* those
> three flavours also be mapped into three flavours of XHTML 1, 
> or *should* we
> strive for one flavour?
> 
> b)  *If* we *should* use three flavours of XHTML, is 
> namespaces the way to
> do it?
> 
> What you're describing above is not XHTML, but is some other 
> XML vocabulary.
> (That is, there is no <xhtml:Film/> tag.)  If you want to 
> convert the HTML
> above to some other XML vocabulary, go ahead.  There is 
> nothing stopping you
> from doing that today.  But if we want to convert that HTML 
> above to XHTML,
> with XHTML's defined set of tags, *then* you have to worry 
> about whether
> XHTML should be using three namespaces or not.
> 
> Even if you want to take your other XML vocabulary and 
> display it directly
> in a browser you can do that;  CSS can do that today.  But it 
> still isn't
> XHTML.
> 
> David Hunter
> david.hunter at mediaserv.com
> MediaServ Information Architects
> http://www.MediaServ.com
> 
> xml-dev: A list for W3C XML Developers. To post, 
mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on
CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following
message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)