Re: Draft 2008-04-12, YamlReference 0.9.1

On Tue, 2008-04-15 at 10:04 -0400, Brad Baxter wrote:
> Then perhaps this is just a doc patch to change
> 
> Protective: { "\\": '\', "\"": '"', "\ ": ' ', "\<TAB>": TAB }
> 
> in the refcard to something that is valid YAML.  I'm not sure how,
> because
> of the restrictions--maybe an actual tab.  Of course, the refcard
> doesn't
> necessarily have to parse, but I think it's odd if it doesn't.
> 
> -- Brad

Sounds reasonable... However I can't think of the top of my head what to
replace the <TAB> with. In the spec example I used a right arrow, but
this is too obscure for the refcard. Maybe there should be a comment...
though <TAB> is pretty self-explanatory...

"In other news...":

I did a review of the spec as it is now, and there are a few very minor
wording glitches to be fixed, and one minor miss-specification (locating
it is left as an exercise to the reader :-). I'm holding off creating a
new draft in case someone else has more comments.

I think we should move forward towards formally declaring the final 1.1
spec. We need a stable spec so we can shift our attention to bringing
the implementations to compliance with it, and promote it in various
places - both are difficult to do until we formally finalize the spec.

Of course, we wouldn't want to finalize the spec until Clark, Ingy,
Xitology and other implementers had a chance to review it properly. This
could take a while...

So, in the meanwhile, if nothing new comes up in, say, the next two
weeks or so, and nobody raises any objections, I'll upload a new version
whose status would be "release candidate" with wording to the effect of
"we do not expect any additional changes other than ``bug'' fixes,
implementers are encouraged to make their implementations compliant and
submit any last moment bugs/comments if any, the next version is
expected to be the final spec".

Makes sense?

	Oren Ben-Kiki


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone