Lists Home |
Date Index |
- To: "Michael Champion" <email@example.com>,"XML Developers List" <firstname.lastname@example.org>
- Subject: RE: [xml-dev] What is the rule for parsing XML in a namespace inside HTML?
- From: "Dare Obasanjo" <email@example.com>
- Date: Tue, 13 Jul 2004 12:05:43 -0700
- Thread-index: AcRpBBgC7FN5Te23T+OOgJt1hT9BJQAB8Q/Q
- Thread-topic: [xml-dev] What is the rule for parsing XML in a namespace inside HTML?
> -----Original Message-----
> From: Michael Champion [mailto:firstname.lastname@example.org]
> Sent: Tuesday, July 13, 2004 10:50 AM
> To: XML Developers List
> Subject: Re: [xml-dev] What is the rule for parsing XML in a
> namespace inside HTML?
> Still, the point of XHTML is not so much to be a stopgap but
> to bring some rigor to content so that ALL SORTS of XML
> technology can be thrown at it. Screenscraping is just one
> use case, there's also querying, transformation, syndication,
> content re-use (without worrying about the HTML escaping
> hassles), web-services enablement
All of these are screen scraping. You are just describing different
things you could do with the scraped data. Bottom line, the only
justification the XHTML folks like ERH can give for Google, Amazon or my
weblog going to XHTML from HTML is that they can use XSLT, XQuery and
XOM to screen scrape the website. Of course, in all 3 cases the website
owner has given alternate XML sources for data the user would like to
screen scrape (Google Web Services, Amazon Web Services, my RSS feed). I
personally think using HTML for presenation and specific XML sources for
extracting content makes a lot more sense than trying to munge it all
into one interface via XHTML.
Joshua is right, XHTML was a stopgap. Many have confused the means to an
end to the end itself.
PITHY WORDS OF WISDOM
The information you have is not the information you need.
This posting is provided "AS IS" with no warranties, and confers no