- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 09 Oct 2006 17:38:50 +0000
- To: www-xml-schema-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3813 Summary: Editorial: correct misuse of 'lexical mapping' Product: XML Schema Version: 1.1 only Platform: Macintosh OS/Version: All Status: NEW Keywords: unclassified Severity: normal Priority: P2 Component: Datatypes: XSD Part 2 AssignedTo: cmsmcq@w3.org ReportedBy: cmsmcq@w3.org QAContact: www-xml-schema-comments@w3.org When discussing float, double, and decimal, the Datatypes spec uses the term 'NaN' to denote the appropriately typed value notANumber. The descriptions of that usage for float and double, however, seem to misuse the term 'lexical mapping'; this should be corrected. Section 3.3.5.1 has Note: As explained below, the lexical mapping of the float value notANumber is 'NaN'. Accordingly, in English text we generally use 'NaN' to refer to that value. Section 3.3.6.1 similarly has Note: As explained below, the lexical mapping of the double value notANumber is 'NaN'. Accordingly, in English text we generally use 'NaN' to refer to that value. The lexical mapping of a type is a function from the lexical space to the value space; that term makes no sense in the sentences just given. What is meant is the pre-image of notANumber. Section 3.3.4.1 on decimal has a better wording: Note: As explained below, the lexical representation of the precisionDecimal value object whose numericalValue is notANumber is 'NaN'. Accordingly, in English text we use 'NaN' to refer to that value. Proposal: the editors should be instructed to align the sections on float and double with that on decimal, in this regard.
Received on Monday, 9 October 2006 17:39:02 UTC