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

RE: ISSUE-89: block/final attributes on global elements

From: <jon.calladine@bt.com>
Date: Mon, 6 Nov 2006 18:53:24 -0000
Message-ID: <657E2B34242ACC46BDD6774A9728F9E3019367F7@E03MVZ3-UKDY.domain1.systemhost.net>
To: <paul.downey@bt.com>, <public-xsd-databinding@w3.org>, <public-xsd-databinding@w3.org>

we have an abstract complexType currently in basic patterns but not for
final/blocked. I shall rectify the situation forthwith

-----Original Message-----
From: public-xsd-databinding-request@w3.org
[mailto:public-xsd-databinding-request@w3.org] On Behalf Of
Sent: 06 November 2006 18:09
To: public-xsd-databinding@w3.org; public-xsd-databinding@w3.org
Subject: RE: ISSUE-89: block/final attributes on global elements

I guess I'd have to ask why not for complexType as well?

-----Original Message-----
From: public-xsd-databinding-request@w3.org on behalf of Databinding
Issue Tracker
Sent: Mon 11/6/2006 5:40 PM
To: public-xsd-databinding@w3.org
Subject: ISSUE-89: block/final attributes on global elements

ISSUE-89: block/final attributes on global elements


Raised by: Jonathan Calladine
On product: Basic

Proposed Basic Pattern:

  <xs:element name="foo" final="#all" block="#all"/>

following on from previous issues in this area I think the above stand a
good chance for inclusion in the basic patterns as they restrict the
advanced patterns exploiting substitition groups and at worst will just
be ignored by processors.

Question is do we extend this to the other valid values e.g.

block="restriction extension substitution"
final="restriction extension"



local elements can also be blocked this way

Received on Monday, 6 November 2006 18:53:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:57 UTC