XML Serving Solutions

[Chris Maden]

[Jeremie Miller]
> I'm wondering what everyone else thinks about this issue.  When a
> server-side solution is used to dynamically modify XML content into
> HTML so existing browsers can render it appropriately, what happens
> to a browser that _can_ deal with the XML or XML + XSL?  Or what
> happens to an intelligent spider that understands XML?  As far as I
> can tell, right now nothing happens, they get HTML just like anyone
> else.  But so much is lost and it nullifies much of the power of XML
> and the meta information it contains.
> 
> I guess I'd just like to see this discussed before it becomes a
> problem.  I suppose something simple like this in the head of the
> HTML page would work: <LINK REL="Alternate" TYPE="text/xml"
> HREF="realpage.xml">
> 
> But without any kind of consensus on this or official recommendation
> I doubt it would get used.
> 
> Am I missing something, or has this already been discussed?

I don't think it needs discussion, just clarification.  I would expect
the browser to send an Accept-Type header (I think that's the right
name) of text/xml;q=1.0,text/html;q=0.9 if it can handle XML.  The
server shouldn't transform the XML if the browser prefers it to HTML.

-Chris
-- 
<!NOTATION SGML.Geek PUBLIC "-//Anonymous//NOTATION SGML Geek//EN">
<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
"<URL>http://www.oreilly.com/people/staff/crism/ <TEL>+1.617.499.7487
<USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>

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/
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)