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 3958 - Restrict "empty" to "empty-only"?
Summary: Restrict "empty" to "empty-only"?
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.1 only
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: resolved
Depends on:
Blocks: 4003
  Show dependency tree / graph
 
Reported: 2006-11-07 22:07 UTC by Sandy Gao
Modified: 2009-04-21 19:21 UTC (History)
0 users

See Also:

Attachments

Description Sandy Gao 2006-11-07 22:07:35 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.
Comment 1 Sandy Gao 2006-11-22 05:31:28 UTC 
Proposal: to disallow restriction "empty" to "element-only".

Resolution: adopted at 2006-10-17 telecon.