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 1433 - [FO] Editorial: value vs atomic value and xdt:anyAtomicType
Summary: [FO] Editorial: value vs atomic value and xdt:anyAtomicType
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Ashok Malhotra
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-13 23:07 UTC by Michael Rys
Modified: 2005-09-29 11:14 UTC (History)
0 users

See Also:

Attachments

Description Michael Rys 2005-05-13 23:07:37 UTC 
The FO spec currently says:

"There are no values with the type annotation xs:anySimpleType at runtime."

This is one of the places where using "value" is incorrect! "value" is 
(unfortunately) not a synonym for atomic value but for sequence of items. So 
there are values (element or attribute nodes) that can have the above type 
annotation. Please use the term "atomic value" instead.

You may want to also make it clear that you cannot have xdt:anyAtomicType as a 
dynamic type annotation (only as a statically inferred type).