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

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

From: <paul.downey@bt.com>
Date: Mon, 6 Nov 2006 18:09:09 -0000
Message-ID: <2A7793353757DB4392DF4DFBBC95225504BFF002@I2KM11-UKBR.domain1.systemhost.net>
To: <public-xsd-databinding@w3.org>, <public-xsd-databinding@w3.org>

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

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

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"

patterns:

  ./xs:element[@block='#all']/(@block)
  ./xs:element[@final='#all']/(@final)

local elements can also be blocked this way

  .//xs:element[@block='#all']/(@block)
Received on Monday, 6 November 2006 18:09:56 GMT

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