Hi Ian,
As of late yesterday what we do should be what you want. I've set things
up such that if either property is specified, a schemaLocation attribute in
an import may be overridden; that is, if the import's namespace matches one
of the elements in the external-schemalocation property, or if there's no
namespace then if the external-nonamespaceschemalocation property is set.
In either case, if the property resolves to a schema the schemaLocation of
the import is overridden; in all other cases we try and dereference the
schemaLocation attribute on the <import> (if it exists); if nothing
resolves, or the property or import's schemaLocation aren't set, then we
emit a warning and continue.
Hope that helps,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 416-448-3519, T/L 778-3519
E-mail: [EMAIL PROTECTED]
Ian Roberts <[EMAIL PROTECTED]> on 06/26/2001 10:19:52 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: [Bug 2326] New: - <import> with NO schemaLocation="..."
reports error
On 26 Jun 2001 [EMAIL PROTECTED] wrote:
> The namespace="..." and schemaLocation="..." attributes on an
> <import> item are both OPTIONAL. However, the parser throws an
> error:
>
> "Schema error: Could not get the doc root for imported Schema file:
> ,."
>
> when an <import> item is missing schemaLocation="...". Here's an
> example:
Just a thought, how does this interact with the new external schema
location property? It would be good if an import with no schemaLocation
could consult this and see if there is a mapping given for the namespace.
Ian
--
Ian Roberts, Software Engineer DecisionSoft Ltd.
Telephone: +44-1865-203192 http://www.decisionsoft.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
