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 6591 - [FO] id() "Parsed as if IDREFS"
Summary: [FO] id() "Parsed as if IDREFS"
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 1.0 (show other bugs)
Version: Recommendation
Hardware: PC Windows NT
: P2 minor
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-17 10:08 UTC by Michael Kay
Modified: 2009-06-30 09:05 UTC (History)
0 users

See Also:


Attachments

Description Michael Kay 2009-02-17 10:08:25 UTC
The description of the id() function, and of the new element-with-id() function, says that "Each xs:string in $arg is parsed as if it were of type IDREFS". If this were taken literally, an error condition would result if the string did not contain at least one token, since xs:IDREFS has a minLength of 1. The subsequent text of the paragraph makes it clear this is not the intent, but the phrase is nevertheless misleading. 

Proposal: change the sentence from

"Each xs:string in $arg is parsed as if it were of type IDREFS, that is, each xs:string in $arg is treated as a whitespace-separated sequence of tokens, each acting as an IDREF." 

to

"Each xs:string in $arg is treated as a whitespace-separated sequence of tokens, each acting as an IDREF."

Furthermore, later in the paragraph there is some confusing typography, where "IDREF" in small caps is followed by a lower-case "s" in normal font; it takes a keen eye to spot that this is the plural of IDREF rather than the word "IDREFS". I propose to change it to "IDREF values".
Comment 1 Michael Kay 2009-06-30 09:05:34 UTC
The proposal was accepted by the WG on 17 March 2009 and erratum E48 has been issued. The bug is therefore being marked as Fixed and Closed.