Hi Jeff.  Thanks for pointing this out!  1.4.0 was indeed a touch lax in
this regard; and now that we've tightened things up personal-schema no
longer validates!  :-(  So I'm glad you pointed this out so we can fix it
before 1.4.1 comes out.

I'll get this done shortly.

Thanks again,
Neil

Neil Graham
XML Parser Development
IBM Toronto Lab
Phone:  416-448-3519, T/L 778-3519
E-mail:  [EMAIL PROTECTED]



"Jeff Rafter" <[EMAIL PROTECTED]> on 06/19/2001 01:58:37 AM

Please respond to [EMAIL PROTECTED]

To:   <[EMAIL PROTECTED]>
cc:
Subject:  XML Schemas - QName resolution of ref attributes


Is Xerces-J 1.4 enforcing the QName resolution constraint? [1]  In the
sample personal.xsd I believe there is an error that is not reported.  I
don't think the ref's to the schema components should be resolved as they
should be in the no-namespace (because there is no targetNamespace) and
they
are actually in th schema namespace because they are qualified.  I could be
wrong about that.  Nevertheless, I added a targetNamespace to personal.xsd
and referred to it in personal-schema.xml to ensure that there is very
clearly an error-- but Xerces didn't catch it:

<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns='http://www.w3.org/2001/XMLSchema'
targetNamespace="http://foo";>

 <element name="personnel">
  <complexType>
   <sequence>
     <element ref="person" minOccurs='1' maxOccurs='unbounded'/>
   </sequence>
  </complexType>

...

 <element name="person">
...
 </element>


Above the peronal element contains a person element which is declared by
reference.  The ref to the person element should raise an error as it
cannot
be resolved because the ref is unqualified. I can give a more full sample
if
needed.

[1] http://www.w3.org/TR/xmlschema-1/#src-resolve

Thanks
Jeff Rafter
Defined Systems
http://www.defined.net
XML Development and Developer Web Hosting


---------------------------------------------------------------------
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]

Reply via email to