W3C home > Mailing lists > Public > public-xsd-databinding@w3.org > May 2006

RE: ISSUE-51: attribute and element name clashes

From: <jon.calladine@bt.com>
Date: Fri, 12 May 2006 15:02:02 +0100
Message-ID: <657E2B34242ACC46BDD6774A9728F9E30B326D@E03MVZ3-UKDY.domain1.systemhost.net>
To: <public-xsd-databinding@w3.org>

I think this gotcha does need to be covered. This would be best
addressed by a design consideration in the pattern for the use of
attributes and also cross referenced in the pattern for the subsequent
extension of a Complex Type where a conflicting attribute name may be
added.

Has anyone else experienced this?

JonC

> -----Original Message-----
> From: public-xsd-databinding-request@w3.org 
> [mailto:public-xsd-databinding-request@w3.org] On Behalf Of 
> Databinding Issue Tracker
> Sent: 12 May 2006 14:33
> To: public-xsd-databinding@w3.org
> Subject: ISSUE-51: attribute and element name clashes
> 
> 
> 
> 
> ISSUE-51: attribute and element name clashes
> 
http://www.w3.org/2005/06/tracker/databinding/issues/51

Raised by: Paul Downey
On product: Basic

The following schema caused a name clash in a 
Java databinding tool:

<xs:complexType name="Product">
  <xs:sequence>
    <xs:element name="name" type="xs:string"/>
    <xs:element name="inStock" type="xs:int"/>
  </xs:sequence>
  <xs:attribute name="name" type="xs:string" /> </xs:complexType>

Should we advise against using the same names
for elements and attributes directly under the same element
in Basic patters?
Received on Friday, 12 May 2006 14:02:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:20:37 GMT