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

[Bug 6735] List simple types with whitespace != collapse

From: <bugzilla@wiggum.w3.org>
Date: Tue, 24 Mar 2009 21:50:23 +0000
To: www-xml-schema-comments@w3.org
Message-Id: <E1LmEVr-000878-Ft@wiggum.w3.org>

--- Comment #1 from Dave Peterson <davep@iit.edu>  2009-03-24 21:50:23 ---
(In reply to comment #0)

> But there is no requirement on the value of the "whiteSpace" facet. Can it be
> "preserve"?
> It's not possible to get whiteSpace=preserve if the list type comes from a
> schema document, but what if it's "born-binary"?

In Datatypes, section, List Datatypes, we assert:

"When a datatype is derived by ·restricting· a ·list· datatype, the following
·constraining facets· apply:
For each of ·length·, ·maxLength· and ·minLength·, the length is measured in
number of list items.  The value of ·whiteSpace· is fixed to the value

That last sentence should settle the matter.  Perhaps it should be duplicated
in Structures?

Note also another aspect of your quote:  " D.{facets} contains only the
whiteSpace facet component."  I vaguely recall there was some reason we
required that a construction of, say, a two-items-required list of integers
datatype would be disallowed and one would be required to first construct an
arbitrary-lists-of-integers datatype and then derive (using the length facet)
the desired one.  Presumably to avoid constructing and deriving-by-facet in the
same step.  Without looking, I suspect that our current derivation/construction
mechanisms, even without that explicit restriction, don't have that capability.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 24 March 2009 21:50:33 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:09 UTC