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 3262 - base64 constraints
Summary: base64 constraints
Status: RESOLVED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.1 only
Hardware: PC Windows XP
: P4 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard: cluster: clarification
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2006-05-09 11:26 UTC by Michael Kay
Modified: 2008-05-16 21:22 UTC (History)
0 users

See Also:


Attachments

Description Michael Kay 2006-05-09 11:26:14 UTC
QT approved comment

In 3.3.17.2 the phrase "because they cannot successfully be decoded by Base64 decoders." is unnecessary and somewhat disingenuous: most Base64 decoders in the big bad world are actually far more liberal than this specification.
Comment 1 C. M. Sperberg-McQueen 2008-05-05 18:43:44 UTC
I propose (this does not necessarily represent editorial consensus) that
we accept this comment and delete the offending clause without replacement.
If this change is accepted, the paragraph which currently reads:

    Note that this grammar requires the number of non-whitespace 
    characters in the ·lexical representation· to be a multiple of 
    four, and for equals signs to appear only at the end of the 
    ·lexical representation·; literals which do not meet these 
    constraints are not legal ·lexical representations· of 
    base64Binary because they cannot successfully be decoded 
    by Base64 decoders.

will read:

    Note that this grammar requires the number of non-whitespace 
    characters in the ·lexical representation· to be a multiple of 
    four, and for equals signs to appear only at the end of the 
    ·lexical representation·; literals which do not meet these 
    constraints are not legal ·lexical representations· of 
    base64Binary.

Comment 2 Noah Mendelsohn 2008-05-06 00:38:52 UTC
+1.  The proposed change looks good to me.

Noah
Comment 3 Dave Peterson 2008-05-09 12:21:14 UTC
(In reply to comment #2)
> +1.  The proposed change looks good to me.

Ditto.

 "Equals sign" (vs "equal sign") jars me, but I see that that's what Unicode documentation calls it.  
Comment 4 C. M. Sperberg-McQueen 2008-05-16 17:18:58 UTC
On today's WG call, the XML Schema Working Group agreed to the proposal
in comment #1; I am marking this issue resolved to reflect that.

Michael Kay, as the originator of the issue, would you report back to QT
on this resolution and let us know whether they accept this resolution of
the issue?  If they agree, please so indicate by changing the record's
status to CLOSED; if they disagree, REOPEN it.  If we don't hear from you
in a reasonable amound of time (say, two weeks), we will assume that silence
implies consent.