Lists Home |
Date Index |
- From: Didier PH Martin <email@example.com>
- To: "Hodder, Ed" <Ed.Hodder@Bowne.com>,'Ben Sarsgard' <BSarsgard@Versient.com>,"XML-Dev (E-mail)" <firstname.lastname@example.org>
- Date: Wed, 13 Dec 2000 14:18:12 -0500
Yeah, that's interesting. It's definitely not valid XHTML. But transformed
XML doesn't have to be valid anything, does it?
The pages are very different based on the browsers we're using, so at least
the concept of divorced content is being used. There's almost no way short
of asking to find out what's going on behing the scenes, is there?
> From: Ben Sarsgard [mailto:BSarsgard@Versient.com]
> What's going on there? It just looks like HTML to me.
> There's illegal
> Am I missing
> something, or did they just take an html document, and save
> it as .xml?
It is possible that the xml document is transformed on the server side. Even
if you refer to an XML document, this latter could be delivered as HTML.
What could be happening is:
a) the server detects the user agent making the request
b) the server associates an XSLT stylesheet to transform this xml document
into an appropriate format understood by the user agent.
c) the server sends the transformed document.
This is also why you see the URL ending with a ".xml". The HTTP request is
really for an XML document, but the server having detected that the user
agent does not support XSLT may have performed the transformation on the
server side and delivered an HTML document in response to the ".xml" URL
Several xml servers are precisely doing that.
Didier PH Martin
Conferences: xml devcon 2000 (http://www.xmldevcon2000.com)
Wireless Summit NY (http:www.pulver.com)
xml devcon 2001 London (http://www.xmldevcon2000.com)
Book: XML Professional (http://www.wrox.com)
column: xml.com (http://www.xml.com)