Lists Home |
Date Index |
- To: "Bjoern Hoehrmann" <firstname.lastname@example.org>,"Joshua Allen" <email@example.com>
- Subject: RE: [xml-dev] What is the rule for parsing XML in a namespace inside HTML?
- From: "Dare Obasanjo" <firstname.lastname@example.org>
- Date: Tue, 13 Jul 2004 21:30:30 -0700
- Cc: <email@example.com>
- Thread-index: AcRpWAAbx28W7uvjTTiqebYUfIBpDwAA0uzV
- Thread-topic: [xml-dev] What is the rule for parsing XML in a namespace inside HTML?
It seems terribly obvious to me. If you want to make your site truly machine friendly then just expose XML and style it for Web browsers with CSS or XSLT instead of the gross hack of munging everything into XHTML. For example, look at Mark Pilgrim's Atom feed at http://diveintomark.org/xml/atom.xml.
Again I repeat; Joshua is right, XHTML was a stopgap. You are confusing a means to an end with the end in itself.
PITHY WORDS OF WISDOM
There are always two solutions to the problem: yours and the boss's.
From: Bjoern Hoehrmann [mailto:firstname.lastname@example.org]
Sent: Tue 7/13/2004 9:05 PM
To: Joshua Allen
Subject: Re: [xml-dev] What is the rule for parsing XML in a namespace inside HTML
>Ugh; I'll repeat myself verbatim: "Users should either stick with HTML;
>or if they want to have a pure machine-processable architecture, move to
>How is that confusing?
Well, you still fail to explain how this XML+XSLT+CSS thing serves as a
replacement for HTML or is better than using XHTML which seems to be
your point. CSS is clearly relevant to such users, but your argument so
far is that XML is not relevant as otherwise XHTML would seem to be very
relevant spite your claim and how XSLT is relevant you still have to
explain. It seems to me you are just trying to distract from the
original discussion by introducing new use cases.
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription