Is xsi:schemaLocation mandatory?
111693Oct 28 2004 — edited Oct 29 2004Hi all,
I'd like to ask a question concerning the use of xsi:schemaLocation.
From my own experience and from browsing the forum - particularly the thread "XMLSchema: xmlns:* and xsi:SchemaLocation usage" from somewhere in 2002 - I got the impression, that the use of xsi:schemaLocation in instance documents is mandatory in XMLDB. The same seems to be true for the schema definitions' xsd:import element.
As pointed out by the initiator of the thread, this "...is in conflict with the general notion of namespaces". I tend to agree with this opinion.
So my question is: Are my assumptions correct? Or is there a way to omit the xsi:schemaLocation attribute in recent releases? In the aforementioned thread, one of the forum members stated:
"We are considering an enhancement to allow a namespace to schemaLocation table to be configured.... This would allow us to process instance documents that did not include the schemaLocation tag etc.."
So, is this enhancement available today?
I think, the problem with using the xsi:schemaLocation is, that it points to something not only specific to a certain platform, but also to a certain host. A schemaLocation, which makes sense on host A is most likely useless on host B. This turns out to be a real pain when one transmits XML instances between various machines, particularly if you're not in control over both ends of the line.