Cart
[Home] [By Thread] [By Date] [Recent Entries]
> That's how I understand the process, if that's not right > someone will correct me :) No you're quite correct (although I don't know, is it really an SGML parser?), but I still will call that sleight of hand from a web POV. Why should the http://www.w3.org/2001/xml resource provide an XML representation of this resource http://www.w3.org/XML/1998/namespace, when the latter could represent itself via the standard web means (content negotiation). Would we have to provide a third resource if we wanted to represent http://www.w3.org/XML/1998/namespace as RNG? And a fourth for text? Peter > -----Original Message----- > From: Andrew Welch [mailto:andrew.j.welch@g...] > Sent: September 10, 2012 11:02 > To: Rushforth, Peter > Cc: Richard Salz; xml-dev@l... > Subject: Re: Why does my browser treat the XML > Schema document at a URL as an XML document? > > > The W3C web server serves it as xml, and through sleight of hand > > (xml-stylesheet), as html too. > > No sleight of hand... the server serves it as xml, so the > browser parses it using it's xml parser instead of its sgml > parser... by default it will then transform the xml using an > internal xslt 1.0 to create the pretty printed view you get > when view xml in the browser, or as in this case there is the > stylesheet PI so the browser also fetches the xslt and then > applies that to the xml, presenting the result. > > As far as the server is concerned it just served 2 xml files. > > That's how I understand the process, if that's not right > someone will correct me :) > > > -- > Andrew Welch > http://andrewjwelch.com >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
