Lists Home |
Date Index |
Although XML processors are free to ignore all xsi:schemaLocation and
xsi:noNamespaceSchemaLocation attributes (because the application may wish
to force use of a particular Schema regardless of what the document states
) it seems like merely a bug if a processor by rule reads only the first
Here is an argument you can use with implementers of such processors,
without resorting to quoting the XML Schema recommendations:
What is the outcome of xsi:schemaLocation with one namespace/schemaLocation
pair and xsi:noNamespaceSchemaLocation with one schemeLocation?
Does it ignore one or the other, or apply both Schemas?
If it ignores one, why?
If it applies both, then why does it allow two Schemas for two different
namespaces, but not three?
 In a math class once, a wily fellow advised me to learn a proof by
heart. If a test then required a proof and I couldn't do it, I was to write
down the memorized (different, but correct) proof. The TA would then likely
only validate the correctness of the proof. XML Schema avoids this problem
by now requiring that you believe the instance's internal Schema location
From: email@example.com [mailto:firstname.lastname@example.org]
Sent: Thursday, November 04, 2004 1:45 PM
To: Alessandro Triglia
Cc: 'Chiusano Joseph'; 'pat'; 'XML :: dev'
Subject: RE: [xml-dev] using more then one schema within one XML
Quoting Alessandro Triglia <email@example.com>:
I believe he's saying that an xsi:schemaLocation attribute can have
xsi:schemaLocation="ns1 schemalocation1 ns2 schemalocation2 ..."
but taht some processors only see the first pair, and ignore 2, 3 ....