Re: 4.3.1: second scenario: should value constraint default to FIXED?

James Tauber <JTauber@bowstreet.com> writes:

> [back again :-)]
> 
> In 4.3.1, in the second scenario (where ref is absent and schema is not the
> parent) the value of {value constraint} is given as "fixed" if the "use"
> attribute is not "default".
> 
> In other words, if a value is given, but the use attribute is one of
> "optional", "fixed" or "required", the value constraint is taken to be
> "fixed".

There's a co-occurrence constraint missing, you're right.  There
should be something under _Attribute Declaration Representation OK_
which says "if 'value' is present, then 'use' must be "default",
"fixed" or "required".

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/