- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 17 Feb 2009 10:08:26 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6591 Summary: [FO] id() "Parsed as if IDREFS" Product: XPath / XQuery / XSLT Version: Recommendation Platform: PC OS/Version: Windows NT Status: NEW Severity: minor Priority: P2 Component: Functions and Operators AssignedTo: mike@saxonica.com ReportedBy: mike@saxonica.com QAContact: public-qt-comments@w3.org 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". -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 17 February 2009 10:08:34 UTC