- From: <jon.calladine@bt.com>
- Date: Mon, 6 Nov 2006 18:53:24 -0000
- 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 paul.downey@bt.com 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 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:53:44 UTC