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 1736 - [FS] ambiguous use of "optional" in 8.1.9 "type expansion"
Summary: [FS] ambiguous use of "optional" in 8.1.9 "type expansion"
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows 2000
: P2 minor
Target Milestone: ---
Assignee: Jerome Simeon
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-18 22:19 UTC by Fred Zemke
Modified: 2007-01-16 17:39 UTC (History)
0 users

See Also:


Attachments

Description Fred Zemke 2005-07-18 22:19:01 UTC
8.1.9 Type expansion
The sentence prior to the first inference says "If the type is 
nillable, then its expansion is optional".  Normally, the word
"optional" means "you have a choice whether to do this 
(ie, the type expansion) or not".  But you do not mean that it
is implementation-defined or implementation-dependent whether to
expand a nillable type.  What you mean is that the result of the
expansion includes the "?" quantifier.  It would be better to 
reword this sentence, avoiding the word "optional". 
For example, "...then the quantifier of the type is zero-or-one".
Comment 1 Jerome Simeon 2006-04-10 18:20:50 UTC
Used the more precise "If the type is nillable, then it expands into an optional type", which is the terminology used in 2.4.3 Content models.
- Jerome