W3C home > Mailing lists > Public > xmlschema-dev@w3.org > August 2003

Re: block, blockDefault

From: Henry S. Thompson <ht@cogsci.ed.ac.uk>
Date: Tue, 19 Aug 2003 09:53:28 +0100
To: "Alain Andrieux" <aa_vrac@hotmail.com>
Cc: <xmlschema-dev@w3.org>
Message-ID: <f5bisoum3jr.fsf@erasmus.inf.ed.ac.uk>

"Alain Andrieux" <aa_vrac@hotmail.com> writes:


> Let's say schema A states blockDefault="#all". In schema B , which
> imports schema A, I can create types derived from the complex types
> exposed by this schema.  I am wondering what is the use of these
> derived types if I cannot instanciate an element of those types...Is
> there a namespace subtlety I am missing here?  Can I have elements
> declared in a different namespace that use those derived types or
> not at all? What is the point of a block="#all" thena as opposed to
> final="#all"?

Basically, block controls what can occur in instances when a given
type defn is named in an element or attr decl.  If you derive your
own types from a block='#all' type defn, you are free to use those
derived types in your _own_ element and attr decls, you just can't use
them in an xsi:type on, or an element substituted for, an element
declared with the original type defn.

  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: ht@cogsci.ed.ac.uk
		     URL: http://www.ltg.ed.ac.uk/~ht/
 [mail really from me _always_ has this .sig -- mail without it is forged spam]
Received on Tuesday, 19 August 2003 04:53:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:15:12 UTC