| CARVIEW |
Select Language
HTTP/2 301
date: Sat, 11 Oct 2025 07:52:53 GMT
content-type: text/html; charset=ISO-8859-1
location: https://lists.w3.org/Archives/Public/public-xsd-databinding/2006Feb/0029.html
cf-ray: 98ccc7d0cba1b9d7-BLR
cache-control: max-age=21600
expires: Sat, 11 Oct 2025 12:55:55 GMT
x-backend: www-mirrors
x-request-id: 98cc74629f57eefa
strict-transport-security: max-age=15552000; includeSubdomains; preload
content-security-policy: frame-ancestors 'self' https://cms.w3.org/ https://cms-dev.w3.org/; upgrade-insecure-requests
cf-cache-status: HIT
set-cookie: __cf_bm=N6167hN4zaRlIyTfyezEPKmdLcaxfN7MZMG9elLt098-1760169173-1.0.1.1-HybKGEjHvVK6AQTO2cNZtR7vMNXLCjIZ7z79yKZ9HIg9D2ajWabE0p862PJs2IMXEU6lSvZAbqHADpGLsfNqbQaW.TAjUu5b_gpGJIn6s8k; path=/; expires=Sat, 11-Oct-25 08:22:53 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
vary: Accept-Encoding
server: cloudflare
alt-svc: h3=":443"; ma=86400
HTTP/2 200
date: Sat, 11 Oct 2025 07:52:54 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 18:33:33 GMT
cache-control: max-age=2592000, public
expires: Mon, 10 Nov 2025 07:52:54 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98ccc7d59ed9c1cc
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: MISS
server: cloudflare
cf-ray: 98ccc7d59ed9c1cc-BLR
alt-svc: h3=":443"; ma=86400
Re: ISSUE-20: Extension of collections from Ed Day on 2006-02-21 (public-xsd-databinding@w3.org from February 2006)
Re: ISSUE-20: Extension of collections
- From: Ed Day <edday@obj-sys.com>
- Date: Tue, 21 Feb 2006 14:18:42 -0500
- To: "Databinding WG" <public-xsd-databinding@w3.org>
- Message-ID: <052f01c6371b$a0c68fd0$4800000a@objsys1>
The problem with this approach is that it requires the user to embed the <extension> element within the instance being extended. This is not what happens in the real world. What happens is additional elements just show up. Also, what happens if the schema is extended a 2nd time? Do you have an extension in an extension? Or maybe the "extension" element should have some kind of version number on the end to track when an extension happened (<extension1>, <extension2>, etc.)? Regards, Ed Day Objective Systems, Inc. https://www.obj-sys.com ----- Original Message ----- From: "Databinding Issue Tracker" <dean+cgi@w3.org> To: <public-xsd-databinding@w3.org> Sent: Tuesday, February 21, 2006 9:05 AM Subject: ISSUE-20: Extension of collections > > > ISSUE-20: Extension of collections > > https://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 19:16:45 UTC