Re: e-props-correct.2

I think you're right, there's a redundancy/confusion here, and the
example should be considered in error.  Unfortunately there's no prose
to back this up -- the definition of {value constraint} or of ·actual
value· should include a discussion of the error case.  Usually it
doesn't arise, of course, but it will for facet values (which appeal
to ·actual value· and default values.

Paul/Ashok: I thought the Datatypes spec. said somewhere that the
'value' attribute of some facets (e.g. enumeration, minExclusive) was
constrained by the basetype -- where does it say this?  That is, the
following is certainly an error, but I'm not sure what clause of the
spec. to appeal to in saying so:

  <xs:simpleType name="xmpl">
   <xs:restriction base="xs:integer">
    <xs:minExclusive value="2002-01-01"/>
   </xs:restriction>
  </xs:simpleType>

The relevant facet component describes its {value} property as

  A value from the value space of the {base type definition}.

but it doesn't say what happens if there _is_ no such value.

Finally note that in specifying the mapping from 'value' attribute to
{value} property, no mention is made of the {base type definition},
which is an omission which should be corrected, I think:

  {value} The actual value of the value [attribute]

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
          W3C Fellow 1999--2002, 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/
 [mail really from me _always_ has this .sig -- mail without it is forged spam]

Received on Tuesday, 14 January 2003 05:17:59 UTC