Re: User Supplied YAML Diagnostic Keys: Descriptive Version

* chromatic <[EMAIL PROTECTED]> [2008-04-17 18:45]: > IETF's "no standards without at least two implementations, and > one of them public" rule That’s the W3C, actually. Regards, -- Aristotle Pagaltzis //

Re: User Supplied YAML Diagnostic Keys: Descriptive Version

--- Aristotle Pagaltzis <[EMAIL PROTECTED]> wrote: > I agree with David on all counts. > > [a-z] seems perfectly sufficient to me, but saying “anything for > which POSIX `islower` returns true” is acceptably precise. I'll go along with this. Can we move forward now? :) Cheers, Ovid -- Buy

Re: User Supplied YAML Diagnostic Keys: Descriptive Version

* David E. Wheeler <[EMAIL PROTECTED]> [2008-04-13 21:00]: > On Apr 13, 2008, at 11:37, Michael G Schwern wrote: > >>> A) Just reserve ASCII [a-z]. This is very easy to check > >>> for but I'm worried it's carving out too small a space. > >> Why would it be too small? I mean, that's a *lot* of word

Re: User Supplied YAML Diagnostic Keys: Descriptive Version

On Apr 11, 2008, at 06:13, Ricardo SIGNES wrote: 1) We reserve every key which begins with a lower case letter 2) We say nothing about anything else 3) All keys are optional I thought this had been the resolution. I hope it *is* the formalized resolution. It is simple and easy and leaves

Re: User Supplied YAML Diagnostic Keys: Descriptive Version

* Michael G Schwern <[EMAIL PROTECTED]> [2008-04-11T07:01:19] > Here's the descriptive way to specify how the diagnostic keys work. > > 1) We reserve every key which begins with a lower case letter > 2) We say nothing about anything else > 3) All keys are optional I thought this had been the re