Lists Home |
Date Index |
"Dare Obasanjo" <firstname.lastname@example.org> writes:
> > -----Original Message-----
> > From: Chiusano Joseph [mailto:email@example.com]
> > Sent: Tuesday, February 18, 2003 11:40 AM
> > To: Jochen Wiedmann
> > Cc: Kohsuke Kawaguchi; firstname.lastname@example.org
> > <Excerpt3>
> > Why the nonsense with "final" and "block"?
> > </Excerpt3>
> > Not sure what "nonsense" you mean - these attributes have
> > well-defined and useful application. The "final" attribute
> > is used to prohibit complex datatype derivation, while the
> > "restriction" attribute is used to prohibit the use of
> > derived complex datatypes. There are distinct cases in which
> > these are needed.
> I'm sorry but the behavior of final & block attributes is nonesensical
> and rarely "needed" especially when one considers that few people even
> within the W3C XML Schema working group can clearly spell out tell the
> difference between final & block on element declarations vs. complex
> type definitions.
'final' vs. 'block' is
"Can I derive new elements decls/type defns from this"
"Will derived element decls/type defns be allowed in instances when this is
specified in the schema"
On element decls vs on type defns controls substitution groups vs type
Having said that, we're considering removing 'final' from W3C XML
Schema 1.1 -- any input on retaining/removing it would be useful.
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
Half-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: email@example.com
[mail really from me _always_ has this .sig -- mail without it is forged spam]