RE: Why does my browser treat the XML Schema document at a URL

Cart

XML Editor - Download a Free Trial >

See What's New >

Buy Now >

[Home] [By Thread] [By Date] [Recent Entries]

From: Richard Salz <rsalz@u...>
To: "Rushforth, Peter" <Peter.Rushforth@n...>
Date: Mon, 10 Sep 2012 09:03:42 -0400

> Because there are no typed links in XML so it is impossible for the > client to disambiguate except perhaps by context / hardcoding?

I don't understand what this means. For example, xsi:schemaLocation? If you fetch a document at that link, or you fetch an XSD document as Roger initially did, any properly-configured web server will return that with an XML content-type. The content-type of a resource is independant of any entity which links to it.

/r$

--
STSM, WebSphere Appliance Architect
https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/

Follow-Ups:
- RE: Why does my browser treat the XML Schema document ata URL as an XML document?
  - From: "Rushforth, Peter" <Peter.Rushforth@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: Richard Salz <rsalz@u...>
- RE: Why does my browser treat the XML Schema document ata URL as an XML document?
  - From: "Rushforth, Peter" <Peter.Rushforth@N...>

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

XML Editor - Download a 15 Day Free Trial Now >

See What's New in Stylus Studio >

Buy Stylus Studio - XML Editor - Now >