[whatwg] Parsing RFC3339 constructs
ian at hixie.ch
Sun Aug 30 13:09:58 PDT 2009
On Thu, 20 Aug 2009, Christoph Päper wrote:
> Ian Hickson:
> > 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:
> > > > > > > > > - the literal letters T and Z must be uppercase
> > > > > > 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
> > ISO8601 libraries.
> That is not naivity! It is a standard's duty to correctly integrate other
> standards. If HTML 5 uses a subset of ISO 8601 then content processors must be
> able to use generic ISO-conformant parsers.
No, sorry, ISO-8601 is too vague to make that possible. It doesn't define
error handling, for instance.
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg