[whatwg] Parsing RFC3339 constructs
ian at hixie.ch
Sat Aug 15 20:08:05 PDT 2009
On Tue, 11 Aug 2009, Nils Dagsson Moskopp wrote:
> Am Dienstag, den 11.08.2009, 07:27 +0000 schrieb Ian Hickson:
> > On Tue, 11 Aug 2009, Julian Reschke wrote:
> > > Ian Hickson wrote:
> > > > On Mon, 27 Apr 2009, Asbjørn Ulsberg wrote:
> > > > > On Mon, 27 Apr 2009 12:59:11 +0200, Julian Reschke <julian.reschke at gmx.de>
> > > > > wrote:
> > > > > > > - the literal letters T and Z must be uppercase
> > > > > > Any technical reason why they have to?
> > > > > Any reason why they don't?
> > > >
> > > > It simplifies processing a tiny amount.
> > >
> > > So for a tiny win, you change the format?
> > By a tiny amount, yes.
> It will be interesting to see if parsers choose to also "get" lowercase
> letters. I'd half-expect that to work, not at least because there may
> already be RFC-compliant libraries in the wild.
The spec explicitly points out that implementors shouldn't naively use
> So if they do by the time HTML n is the standard, will the uppercase
> restriction be removed in HTML n+1 ?
HTML5 itself will have to change if the implementations don't implement
what it says.
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg