ISSUE-20: Extension of collections from Databinding Issue Tracker on 2006-02-21 (public-xsd-databinding@w3.org from February 2006)

From: Databinding Issue Tracker <dean+cgi@w3.org>
Date: Tue, 21 Feb 2006 14:05:31 +0000 (GMT)
To: public-xsd-databinding@w3.org
Message-Id: <20060221140531.3694E66364@dolph.w3.org>

ISSUE-20: Extension of collections

http://www.w3.org/2005/06/tracker/databinding/issues/20

Raised by: Paul Downey
On product: Basic

The input document offers the following pattern for a collection
which is open to extension, thereby being useful when evolving
or extending a schema during versioning:

"""
<xs:complexType name="CustomerType">
  <xs:sequence>
    <xs:element name="firstName" type="xs:string" />
    <xs:element name="lastName" type="xs:string" />
    <xs:element name="extension" type="tns:CustomerExtensionType" minOccurs="0" />
  </xs:sequence>
  <xs:anyAttribute/>
</xs:complexType>

<xs:complexType name="CustomerExtensionType">
  <xs:sequence>
    <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"
          namespace="##targetNamespace"/>
    </xs:sequence>
</xs:complexType>

"""

How well is this pattern supported by tools - does it belong in
the Basic patterns document?

Are there authoring issues with this pattern we should warn about?

Received on Tuesday, 21 February 2006 14:05:42 UTC