This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4003 - Restrict "empty" to "empty-only"?
Summary: Restrict "empty" to "empty-only"?
Status: NEW
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.0 only
Hardware: All Windows 3.1
: P2 normal
Target Milestone: ---
Assignee: David Ezell
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords:
Depends on: 3958
Blocks:
  Show dependency tree / graph
 
Reported: 2006-11-22 05:30 UTC by Sandy Gao
Modified: 2012-12-04 00:53 UTC (History)
0 users

See Also:

Attachments

Description Sandy Gao 2006-11-22 05:30:58 UTC 
In section 3.4.6, constraint "Derivation Valid (Restriction, Complex)", there
is note:

"Note: Attempts to derive complex type definitions whose {content type} is
element-only by restricting a {base type definition} whose {content type} is
empty are not ruled out by this clause."

Why isn't this ruled out? The derived type allows whitespaces as the content,
but the base type doesn't allow it.