1926 2005-08-31 20:48:39 +0000 EP-14: define 'literal' and use it more consistently 2008-03-05 13:52:52 +0000 1 1 1 Unclassified XML Schema Datatypes: XSD Part 2 1.1 only PC Linux CLOSED FIXED resolved P2 normal --- 1 cmsmcq w3c-xml-schema-wg www-xml-schema-comments oldest_to_newest 5618 0 cmsmcq 2005-08-31 20:48:39 +0000 The Datatypes spec talks about members of the lexical space of a given type as lexical representations of (values of) that type. In many sentences, however, a term is needed to denote the strings of characters which are validated. These may or may not actually be lexical representations of values in the value space, because they may or may not be valid. Some time ago, the editors agreed to propose to use the term 'literal' with this sense, but noted that a definition of the term was needed. EP-14 is a proposal to define 'literal' as A sequence of zero or more characters in the Universal Character Set (UCS) which may or may not prove upon inspection to be a member of the lexical space of a given datatype and thus a lexical representation of a given value in that datatype's value space, is referred to as a <term>literal</term>. and to add (as a way of avoiding the false assumption that 'literal' is used only of unvalidated strings of uncertain validity) the remark The term is used indifferently both for character sequences which are members of a particular lexical space and for those which are not. Also, some occurrences of 'character string' used in the sense given are changed to 'literal' in this proposal. 5875 1 cmsmcq 2005-09-07 22:29:25 +0000 A proposal to resolve this issue is included in the omnibus package at http://www.w3.org/XML/Group/2004/06/xmlschema-2/datatypes.omnibus.20050831.html 7354 2 cmsmcq 2005-12-09 01:00:47 +0000 The proposal to resolve this issue was approved as part of the omnibus package approved by the WG at its meeting in Edinburgh in September 2005. 7358 3 cmsmcq 2005-12-09 03:54:51 +0000 The text approved in Edinburgh was integrated into the status quo document on 8 December 2005. 19297 4 davep 2008-03-05 13:52:52 +0000 Although no formal request for closure was made, since the reporter also noted the resolution of this bug over two years ago, I'm marking it closed.