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 1315 - Typed value property of an element node
Summary: Typed value property of an element node
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Data Model 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows XP
: P2 minor
Target Milestone: ---
Assignee: Norman Walsh
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2005-05-09 22:06 UTC by Don Chamberlin
Modified: 2007-02-25 23:12 UTC (History)
0 users

See Also:


Description Don Chamberlin 2005-05-09 22:06:50 UTC
In Data Model Section 6.2.4, Element Node--Construction from a PSVI, under the 
subheading "Typed Value", there is a bulleted list of cases. These cases are 
presumably meant to be mutually exclusive. All the bullets but #2 are phrased 
in terms of the element type (presumably referring to the "type-name" property 
defined earlier in the section.) But bullet #2 says "If the element is empty, 
its typed-value is the empty sequence", which refers to the content of the 
element rather than its type. This is inconsistent and incorrect. For example, 
if the type of the element is a complex type with element-only content, then 
its typed value is undefined, regardless of whether it is empty or not.

Proposal: Replace bullet #2 in the above-referenced section with the 
following: "If the element has a complex type with empty content, its typed-
value is the empty sequence."

This proposal will make the Data Model document consistent with the XQuery and 
XPath documents, Section 2.5.2 (Typed Value and String Value).
Comment 1 Norman Walsh 2005-05-17 15:30:41 UTC
Accepted at Raliegh f2f