- From: Jeff Lowery <Jeff.Lowery@creo.com>
- Date: Mon, 2 Jun 2003 10:44:56 -0700
- To: Jeff Lowery <Jeff.Lowery@creo.com>, "'ht@cogsci.ed.ac.uk'" <ht@cogsci.ed.ac.uk>, Jeni Tennison <jeni@jenitennison.com>
- Cc: "'xmlschema-dev@w3.org'" <xmlschema-dev@w3.org>
> > But if the first is the constraint, the second is _not_ a valid
> > value. Lists are ordered.
Okay, I might be misreading this, but here's what I dug up:
"4.2.2.1 The ordered Schema Component
Schema Component: ordered
{value}
One of {false, partial, total}.
{value} depends on {variety}, {facets} and {member type definitions} ...
[...]
When {variety} is .list., {value} is false. "
So lists, then, are unordered? Or can {facets} and {member type
definitions} override this fundamental nature of lists somehow?
Received on Monday, 2 June 2003 13:46:19 UTC