SDO 144 - Clarification on relationship between a Type's characteristicsand those of its Base type

[Blaise Doughan <blaise.doughan@oracle.com>]

Hello All,

I have looked at issue 144 and have come up with the following:

Spec Section

This issue deals with the Core SDO spec, section 5.2 SDO Type and Property Constraints

Issue

The following point does not make sense:

• Type.dataType and sequenced have the same value as their base Types' dataType and sequenced.

Example

For the following schema is the parent type "sequenced" just because the child type is?  What happens if the parent type had been previously defined is child type not allowed, or restricted to be sequenced=false?

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">

    <xs:complexType name="parent">
        <xs:sequence>
            <xs:element name="property-1" type="xs:string"/>
        </xs:sequence>
    </xs:complexType>

    <xs:complexType name="child">
        <xs:complexContent>
            <xs:extension base="parent">
                <xs:sequence>
                    <xs:choice maxOccurs="unbounded">
                        <xs:element name="foo" type="xs:string"/>
                        <xs:element name="bar" type="xs:string"/>
                    </xs:choice>
                </xs:sequence>
            </xs:extension>
        </xs:complexContent>
    </xs:complexType>

</xs:schema>

Proposal

Change :

• Type.dataType and sequenced have the same value as their base Types' dataType and sequenced

To:

• Type.dataType has the same value as the base Type's dataType
• Type.sequenced =true if the base Type's sequenced=true
  

-Blaise