W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > January to March 2001

Re: Default values for block and final

From: Henry S. Thompson <ht@cogsci.ed.ac.uk>
Date: 04 Jan 2001 14:49:54 +0000
To: "Arnold, Curt" <Curt.Arnold@hyprotech.com>
Cc: "'www-xml-schema-comments@w3.org'" <www-xml-schema-comments@w3.org>
Message-ID: <f5bae97id7x.fsf@cogsci.ed.ac.uk>
"Arnold, Curt" <Curt.Arnold@hyprotech.com> writes:

> The Schema and DTD for Schema specify a default value of "" for block and final (but not in all uses) which will interfere with appropriate processing of blockDefault and finalDefault.  No default
> should be provided so that not providing a block or final attribute can be distinguished from providing a value of "" which would indicate blocking nothing (anti #all)
> 
> <xsd:schema ... blockDefault="#all" finalDefault="#all">
> 	<!--  should be blocked and final  -->
> 	<xsd:complexType name="blockedAndFinal"/>
> 	<!--  should block nothing   -->
> 	<xsd:complexType name="unblockedAndNotFinal" block="" final=""/>
> </xsd:schema>
> 
> These two complex types should have substantially different behaviors, however with the current DTD for Schema, they are indistinguishable.

Right, thought I'd eliminated all of those, thanks, I'll fix it.  I
expect this will have knock-on effects on the schema for schemas,
which sets blockDefault.

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
          W3C Fellow 1999--2001, part-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/
Received on Thursday, 4 January 2001 09:50:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 6 December 2009 18:12:49 GMT