Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: "redefine" attribute allowed when deriving by extension?

From: "Michael Kay" <mike@--------.--->
To: "'Gert Driesen'" <gert.driesen@-------.-->, <xmlschema-dev@--.--->
Date: 5/22/2009 8:20:00 AM
Saxon gives the error message:

Error on line 8 of test.xsd:
  Attribute @name appears more than once in attribute group
Schema processing failed: The schema is invalid

The property tableau for complex types says that {attribute uses} for the
extended type is the union of the attribute uses listed in the <attribute>
children and the {attribute uses} of the type definition identified by the
base attribute. So there are two attribute uses with the same name, which
violates clause 4 of Schema Component Constraint: Complex Type Definition
Properties Correct ("Two distinct attribute declarations in the {attribute
uses} must not have identical {name}s and {target namespace}s"). 

There's some wriggle room over the term "union". If two attribute uses are
the same in all respects, then one could argue that forming the union
eliminates the duplicates. The specification explicitly says that it doesn't
define what it means for two schema components to be identical, and some
people interpret it in terms of all the properties being the same. However,
one can't claim they are identical if one says "optional" and the other says
"required".

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay 
 

> -----Original Message-----
> From: xmlschema-dev-request@w... 
> [mailto:xmlschema-dev-request@w...] On Behalf Of Gert Driesen
> Sent: 21 May 2009 10:42
> To: xmlschema-dev@w...
> Subject: "redefine" attribute allowed when deriving by extension?
> 
> Hi,
> 
> I'm sorry if this has been answered before (or if the answer 
> should've been obvious), but can someone tell me if the 
> following XML Schema should be considered valid:
> 
> <xs:schema xmlns="foo" xmlns:xs="http://www.w3.org/2001/XMLSchema"
> targetNamespace="foo" id="foo">
> 	<xs:element name="Foo" type="FooType" />
> 	<xs:element name="Bar" type="BarType" />
> 	<xs:complexType name="FooType">
> 		<xs:attribute name="name" type="xs:string" 
> use="optional"/>
> 	</xs:complexType>
> 	<xs:complexType name="BarType">
> 		<xs:complexContent>
> 			<xs:extension base="FooType">
> 				<xs:attribute name="name" 
> type="xs:string"
> use="required"/>
> 			</xs:extension>
> 		</xs:complexContent>
> 	</xs:complexType>
> </xs:schema>
> 
> Is it allowed to override/redefine an attribute of a base 
> type when deriving by extension?
> 
> The reason I'm asking this is because I've noticed that 
> several implementations expose a different behavior here:
> 
> Altova XMLSpy">XMLSpy 2009:
> Does not allow attribute to be "redefined" in the derived type.
> 
> Mono:
> Allows attribute to be "redefined" if its use and type match 
> the attribute in the base type.
> 
> Microsoft .NET:
> Allows attribute to be "redefined".
> 
> Oracle Service Bus:
> Allows attribute to be "redefined".
> 
> Any feedback is appreciated.
> 
> Gert
> 
> 
> 




transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent