Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Duplicate attribute uses (Xerces bug?)

From: Kasimier Buchcik <kbuchcik@---------.-->
To: George Cristian Bina <george@----.-->
Date: 9/12/2005 4:02:00 PM
On Mon, 2005-09-12 at 15:00 +0300, George Cristian Bina wrote:
> Hi,
> 
> See http://www.w3.org/TR/xmlschema-1/#ct-props-correct
> 4 Two distinct attribute declarations in the {attribute uses} must not 
> have identical {name}s and {target namespace}s.

Yes, but in
http://www.w3.org/TR/xmlschema-1/#Attribute_Declaration_details

we have
"if the <attribute> element information item has <complexType> or
<attributeGroup> as an ancestor and the ref [attribute] is absent, it
corresponds to an attribute use with properties as follows (unless
use='prohibited', in which case the item corresponds to nothing at
all):"

Prohibiting an attribute use does not create an attribute use, thus
we don't have duplicate attribute uses at the component level here.

But I'm not sure if it was intended to rule out duplicates at the
XML representation level as well.

Regards,

Kasimier

From K.Buchcik@4... Mon Sep 12 13:07:26 2005
Received: from ma


transparent
Print
Mail
Digg
delicious
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