W3C home > Mailing lists > Public > xmlschema-dev@w3.org > January 2002

RE: Attribute error - a bug or a feature?

From: Mark Feblowitz <mfeblowitz@frictionless.com>
Date: Thu, 10 Jan 2002 18:13:47 -0500
Message-ID: <4DBDB4044ABED31183C000508BA0E97F024D56D4@fcpostal.frictionless.com>
To: "'Eddie Robertsson'" <eddie@allette.com.au>
Cc: "Xmlschema-Dev (E-mail)" <xmlschema-dev@w3.org>
Yup - and Apache reports that they have fixed it in the CVS.

Thanks,

Mark


----------------------------------------------------------------------------
----
 
Mark Feblowitz                                   [t] 617.715.7231
Frictionless Commerce Incorporated     [f] 617.495.0188 
XML Architect                                     [e]
mfeblowitz@frictionless.com
400 Technology Square, 9th Floor 
Cambridge, MA 02139 
www.frictionless.com  
 

 -----Original Message-----
From: 	Eddie Robertsson [mailto:eddie@allette.com.au] 
Sent:	Thursday, January 10, 2002 5:47 PM
To:	Mark Feblowitz
Subject:	Re: Attribute error - a bug or a feature?

>         <xs:element name="AddressId" minOccurs="0" maxOccurs="unbounded">
>                 <xs:complexType>
>                         <xs:simpleContent>
>                                 <xs:extension base="AddressId"/>
>                         </xs:simpleContent>
>                 </xs:complexType>
>         </xs:element>
>
> but the error goes away when that type is merely referenced:
>
>         <xs:element name="AddressId" type="AddressId" minOccurs="0"
> maxOccurs="unbounded">
>
> Does this problem arise due to the attempt to derive by extension, or does
> it look legit?

I don't see a problem with this as I read [1] so my bet is on a bug in
Xerces.

Cheers,
/Eddie

http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#declare-type (in the
table
with heading Complex Type Definition with simple content Schema Component)
Received on Thursday, 10 January 2002 18:14:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:26 GMT