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 1926 - EP-14: define 'literal' and use it more consistently
Summary: EP-14: define 'literal' and use it more consistently
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.1 only
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: XML Schema WG
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2005-08-31 20:48 UTC by C. M. Sperberg-McQueen
Modified: 2008-03-05 13:52 UTC (History)
0 users

See Also:


Attachments

Description C. M. Sperberg-McQueen 2005-08-31 20:48:39 UTC
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.
Comment 1 C. M. Sperberg-McQueen 2005-09-07 22:29:25 UTC
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

Comment 2 C. M. Sperberg-McQueen 2005-12-09 01:00:47 UTC
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.
Comment 3 C. M. Sperberg-McQueen 2005-12-09 03:54:51 UTC
The text approved in Edinburgh was integrated into the
status quo document on 8 December 2005.
Comment 4 Dave Peterson 2008-03-05 13:52:52 UTC
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.