• From: "Rushforth, Peter" <Peter.Rushforth@N...>
• To: David Carlisle <davidc@n...>
• Date: Mon, 10 Sep 2012 12:49:45 +0000

> The media (MIME) type in this 
> case is, as usual, specified by the server.

Resources have no intrinsic type, but their representations do.  Either
you negotiate for a type or you accept the default provided by the server.

When there is a choice, the default is _normally_ text/html, not some flavour of
xml.  Normally, but not in this case, because the server serves this xml with
a stylesheet which converts the xml to html in the browser.  But not all clients
are browsers, especially if they are requesting XML. 

Sometimes by context the client can know to negotiate for a particular type.
But in general, the client needs a hint regarding what to negotiate for, and this
is what @rel and @type are for.

Peter

• Follow-Ups:
  • Re: RE: Why does my browser treat the XML Schema document at a URL as an XML document?
    • From: David Carlisle <davidc@n...>

• References:
  • Why does my browser treat the XML Schema document at a URL as anXML document?
    • From: "Costello, Roger L." <costello@m...>
  • RE: Why does my browser treat the XML Schema document at a URL asan XML document?
    • From: "Rushforth, Peter" <Peter.Rushforth@N...>
  • Re: RE: Why does my browser treat the XML Schema documentat a URL as an XML document?
    • From: David Carlisle <davidc@n...>