Xmlschema global/local issue(oracle10g)

Question

I've schema with globally declared elements,something like:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:element name="el3" xdb:defaultTable="el3">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="el3_1"/>
                    <xs:element name="el3_2">
                         <xs:complexType>
                              <xs:sequence>
                                   <xs:element ref="el1" xdb:SQLInline="false" xdb:defaultTable="el1"/>
                                   <xs:element ref="el2" xdb:SQLInline="false" xdb:defaultTable="el2"/>
                              </xs:sequence>
                         </xs:complexType>
                    </xs:element>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="el1" type="el1" xdb:defaultTable="el1"/>
     <xs:element name="el2" type="el2" xdb:defaultTable="el2"/>
</xs:schema>
as you can see local element "el3" references two global elements in declaration.
When I insert document corresponding to "el1" in "el1" table-all works as expected but when I try to insert conforming to "el3"(verified by xmlspy) document in "el3" document,oracle don't recognize "el1" and "el2" elements in context of "el3".By the way,how oracle handle situation with existent primary key in dependent table(SQLInline="false")?Will it try to reinsert element or use existent?
An at last, <xdb:tableProps="OBJECT IDENTIFIER IS PRIMARY KEY" construction> dosen't work at all though <xdb:columnProps="primary key"> seems work as expected.
Any thoughts?

Answer 1

Mark
Please can you confirm that I understand correctly your response which mentions a potential future enhancement.
I assume you are saying that it is currently not possible to override the default table name to place elements of the same type into a single table.
I used the following test XML schema:
<?xml version="1.0"?>
<!-- edited with XMLSPY v2004 rel. 4 U (http://www.xmlspy.com) by GARY GREGORY (TERADYNE DIAGNOSTIC SOLUTIONS) -->
<!--W3C Schema generated by XMLSPY v2004 rel. 4 U (http://www.xmlspy.com)-->
<xs:schema elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xdb="http://xmlns.oracle.com/xdb">
     <xs:import namespace="http://www.w3.org/1999/xlink" schemaLocation="xlink.xsd"/>
     <xs:element name="COMPONENT">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="Properties"/>
                    <xs:element ref="SCHEMATIC"/>
                    <xs:element ref="DOCUMENT"/>
                    <xs:element ref="DIAG-TREE"/>
                    <xs:element ref="SHORTCUT" minOccurs="0" maxOccurs="unbounded" xdb:SQLInline="false" xdb:defaultTable="SHORTCUT_TABLE"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="DIAG-TREE">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="Properties"/>
                    <xs:element ref="START"/>
                    <xs:element ref="TACTIC-NODE"/>
                    <xs:element ref="RETURN"/>
               </xs:sequence>
               <xs:attribute name="id" type="xs:string" use="required"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="DOCUMENT">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="Properties"/>
               </xs:sequence>
               <xs:attribute name="id" type="xs:string" use="required"/>
               <xs:attribute ref="xlink:href" use="required"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="PresenterTactic">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="actionItem"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="Properties">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="icon32" minOccurs="0"/>
                    <xs:element ref="name" minOccurs="0"/>
                    <xs:element ref="component" minOccurs="0"/>
                    <xs:element ref="SHORTCUT" minOccurs="0" maxOccurs="unbounded" xdb:SQLInline="false" xdb:defaultTable="SHORTCUT_TABLE"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="RESULT">
          <xs:complexType>
               <xs:attribute name="ref" type="xs:string" use="required"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="RETURN">
          <xs:complexType>
               <xs:attribute name="id" type="xs:string" use="required"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="SCHEMATIC">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="Properties"/>
                    <xs:element ref="SCHEMATIC-REF" maxOccurs="unbounded"/>
               </xs:sequence>
               <xs:attribute name="id" type="xs:string" use="required"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="SCHEMATIC-REF">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="Properties"/>
               </xs:sequence>
               <xs:attribute name="x">
                    <xs:simpleType>
                         <xs:restriction base="xs:NMTOKEN">
                              <xs:enumeration value="132"/>
                              <xs:enumeration value="252"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:attribute>
               <xs:attribute name="y" type="xs:short"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="SHORTCUT">
          <xs:complexType>
               <xs:attribute name="id" type="xs:string" use="required"/>
               <xs:attribute ref="xlink:href" use="required"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="START">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="RESULT"/>
               </xs:sequence>
               <xs:attribute name="id" type="xs:string" use="required"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="TACTIC-NODE">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="PresenterTactic"/>
                    <xs:element ref="RESULT"/>
               </xs:sequence>
               <xs:attribute name="id" type="xs:string" use="required"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="actionItem">
          <xs:complexType>
               <xs:simpleContent>
                    <xs:extension base="xs:string">
                         <xs:attribute name="id" type="xs:string" use="required"/>
                    </xs:extension>
               </xs:simpleContent>
          </xs:complexType>
     </xs:element>
     <xs:element name="component">
          <xs:complexType>
               <xs:attribute ref="xlink:href" use="required"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="icon32">
          <xs:complexType>
               <xs:attribute ref="xlink:href" use="required"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="name">
          <xs:complexType>
               <xs:attribute ref="xlink:href" use="required"/>
          </xs:complexType>
     </xs:element>
</xs:schema>
The only important bit in this XML schema is that the SHORTCUT element can have more than one parent element (two in this example).
10.1.0.2.0 allowed me to register the XML schema above, but at runtime an error occurred when I attempted to insert the XML document via WebDAV. The insert works when I defined an XML Schema which uses different table names.
Sorry for asking for confirmation - this was potentially an important implementation requirement for us.
Just in case there is an obvious alternative implementation method, I'll briefly mention our real requirement. We were looking for a way to store our "xlink" references so that we can provide "re-factoring" capabilities for our XML documents. Our xml documents refer to each other using xlink attributes that contain relative paths (folder and file names). Our customers eventually will have 100,000+ XML documents, and therefore they are likely to wish to re-organise them.