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

RE: Meaning of "enumeration" and "pattern" in xs:list

From: Jeff Lowery <Jeff.Lowery@creo.com>
Date: Mon, 2 Jun 2003 10:44:56 -0700
Message-ID: <4827EC373E03DB44AC2AB3900430896B672293@csiex01.scenicsoft.com>
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

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