Schema validation with xinclude

Subjects

•	Home
•	VOTE Move XML Commons to Xerces
•	Commented: (XERCESJ 589) Bug with pattern restriction on long strings
•	: Xerces J 2 8 1 Release on Wednesday, September 13th
•	: Xerces J 2 9 0 Release on Wednesday, November 22nd
•	Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
•	Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
•	Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
•	Some consideration about the xerces DOM implementation
•	Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
•	Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
•	retain exception stack traces
•	Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
•	Future of NekoHTML
•	Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
•	DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
•	: xml commons external 1 3 04 Release on Wednesday, November 22nd
•	Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
•	XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
•	First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
•	: xml commons resolver 1 2 Release on Wednesday, November 22nd
•	Typo in RangeToken java Please check
•	Validator features
•	java lang ClassCastException when adopting Node
•	using the org apache xerces impl xs identity package
•	Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
•	Problem with ref attributes and schema validation
•	Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
•	Performance problem under load Xerces with Weblogic 9 x
•	remove ignored memory allocation
•	Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
•	Commented: (XERCESJ 977) Null pointer exception during DOM parsing
•	Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
•	Commented: (XERCESJ 1201) Initial contribution for StAX Event API
•	Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
•	Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
•	Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
•	Updated: (XERCESJ 589) Bug with pattern restriction on long strings
•	StackOverflow
•	xerces Range unnecessarily not garbage collectable if not detached
•	Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
•	Bug in xs:redefine
•	Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
•	Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
•	Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
•	Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
•	Google Summer of Code 2007
•	Xerces J and XInclude relative path issue
•	Assigned: (XERCESJ 206) Stack overflow when using a schema validation
•	Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
•	Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
•	non overriding equals methoda
•	Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
•	Xerces AS3 port
•	Updated: (XERCESJ 325) Regular Expression; Pattern "\| " clause order de
•	Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
•	Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
•	Created: (XERCESJ 1124) Nonspecific schema error message
•	a bug in xerces
•	Updated: (XERCESJ 1201) Initial contribution for StAX Event API
•	Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report

Links

Home

Oracle database error code

Schema validation with xinclude

Schema validation with xinclude

2004-03-01 - By Stottlemyer, Carl

I am getting errors when I try to validate a document that uses XInclude
against a schema. The version of xerces being used is: 2.6.2.

The problem I am having is with the xml:base attribute. The XInclude
FAQ says that to solve this problem one must modify the schema elements
to allow the xml:base attribute. Unfortunately, I have been unable to
figure out how to modify my schema to allow the attribute.

Currently, I have three documents: contacts.xml, name.xml and
contacts.xsd. When I parse contacts.xml I get the following error
message:
[Error] contacts.xsd:25:49: src-resolve: Cannot resolve the name
'xml:base' to a(n) 'attribute declaration' component.
[Error] contacts.xsd:25:49: s4s-elt-invalid-content.1: The content of
'nameType' is invalid. Element 'attribute' is invalid, misplaced, or
occurs too often.
[Error] name.xml:2:6: Document is invalid: no grammar found.
[Error] name.xml:2:6: Document root element "name", must match DOCTYPE
root "null".

contacts.xml
-----------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<contact xmlns="http://test"
xmlns:xi="http://www.w3.org/2003/XInclude"
xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xml="http://www.w3.org/XML/1998/namespace"
xsd:schemaLocation="http://test
contacts.xsd">

<xi:include href="name.xml"/>
</contact>

name.xml
--------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<name
xmlns="http://test">
<first>Carl</first>
<last>Stottlemyer</last>
</name>

contacts.xsd
------------------------------------------------------------------------
-------------------------
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:test="http://test"
targetNamespace="http://test"
elementFormDefault="qualified"
attributeFormDefault="unqualified">


<xsd:import namespace="http://www.w3.org/XML/1998/namespace"/>

<xsd:element name="contact">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name"
type="test:nameType"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

<xsd:complexType name="nameType">
<xsd:sequence>
<xsd:element name="first"/>
<xsd:element name="last"/>
</xsd:sequence>
<xsd:attribute ref="xml:base" use="optional"/>
</xsd:complexType>
</xsd:schema>

Carl Stottlemyer

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6487.1">
<TITLE>Schema validation with xinclude</TITLE>
</HEAD>
<BODY>


I am getting errors when I try to validate a
document that uses XInclude against a schema.  The version of xerces being
used is: 2.6.2.

The problem I am having is with the xml:base
attribute.  The XInclude FAQ says that to solve this problem one must
modify the schema elements to allow the xml:base attribute.  Unfortunately
, I have been unable to figure out how to modify my schema to allow the
attribute.

Currently, I have three documents: contacts.xml,
name.xml and contacts.xsd.  When I parse contacts.xml I get the following
error message: 

[Error] contacts.xsd:25:49:
src-resolve: Cannot resolve the name 'xml:base' to a(n) 'attribute declaration'
component.

 [Error] contacts.xsd:25:49:
s4s-elt-invalid-content.1: The content of 'nameType' is invalid.  Element
'attribute' is invalid, misplaced, or occurs too often.

[Error] name.xml:2:6:
Document is invalid: no grammar found.

 [Error] name.xml:2:6:
Document root element "name", must match DOCTYPE root "null&quot
;.


contacts.xml

 -------------------------------------------------
----------------

 <?xml version=
"1.0"
encoding="UTF-8"?>

 <contact xmlns="<A HREF="http://test">http://test</A>"

         xmlns:xi="<A HREF="http://www.w3.org/2003/XInclude">http://www.w3.org/2003
/XInclude</A>"

         xmlns:xsd="<A HREF="http://www.w3.org/2001/XMLSchema-instance">http://www.w3
.org/2001/XMLSchema-instance</A>"

         xmlns:xml="<A HREF="http://www.w3.org/XML/1998/namespace">http://www.w3.org/XML
/1998/namespace</A>"


         xsd:schemaLocation="<A HREF="http://test">http://test</A>

              
               
     
contacts.xsd">


        <xi:include href="name.xml"/>

 </contact>


name.xml

 -------------------------------------------------
-------------

 <?xml version=
"1.0"
encoding="UTF-8"?>

 <name

         xmlns="<A HREF="http://test">http://test</A>">

   <first>Carl</first>

   <last>Stottlemyer</last>

 </name>


contacts.xsd 

 -------------------------------------------------
------------------------------------------------

 <xsd:schema xmlns:xsd="<A HREF="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001
/XMLSchema</A>"

         xmlns:xml="<A HREF="http://www.w3.org/XML/1998/namespace">http://www.w3.org/XML
/1998/namespace</A>"


         xmlns:test="<A HREF="http://test">http://test</A>"

         targetNamespace="<A HREF="http://test">http://test</A>"

         elementFormDefault="qualified"

         attributeFormDefault="unqualified">

        

   
          

         <xsd:import namespace=
"<A HREF="http://www
.w3.org/XML/1998/namespace">http://www.w3.org/XML/1998/namespace</A>"/>

        

         <xsd:element name="contact"
>

              
   <xsd:complexType
>

              
           <xsd:sequence>

              
               
    <xsd
:element name="name" type
="test:nameType&quot
;

              
               
            maxOccurs="unbounded"/>

              
           </xsd:sequence>

              
   </xsd
:complexType>

         </xsd:element>

        

         <xsd:complexType name="nameType">

              
   <xsd:sequence&gt
;

              
           <xsd:element name
="first"
/>

              
           <xsd:element name
="last"
/>

              
   </xsd:sequence
>

              
   <xsd:attribute ref="xml:base" use="optional"
/>

         </xsd:complexType>

 </xsd:schema>


Carl Stottlemyer


</BODY>
</HTML>