RE: [Yaml-core] Open Issues

[Oren Ben-K. <or...@ri...>]

Clark C . Evans wrote:
> | I like the syntax & semantics of these 5 types *exactly* as you
> | posted. 
> 
> Agreed.

OK but consider my latest as well.

> | > - References. OK, Alias != Pointer. Fine. Now, how does YAML
> | > serialize
> | > "\$a->[0]"?
> |
> | I'll handle Perl with what we have. Enough said.
> 
> Ok. 

I'm curious (said the cat). How will you do that?

> | > - Info model. If Clark comes up with a reformulation of the info
> | > model that JAP can grok, I'd be happy to include it into the spec,
> | > and more than happy
> | > to re-work the simpler productions :-)
> | 
> | OK
>
> It'll take me a few days.. I have day job work to do.

No rush.

> | > - Pipelining. Let's leave it out for now - right?
> | 
> | I just want to know how to serialize:
> | 
> | print YAML->Emit(bless [], "Foo::Bar");

We keep underestimating the power the existing building blocks give us. The
answer is, of course, you serialize it as:

--- !!Foo::Bar
 =: !seq

:-)

Come to think of it, this means one can safely write:

--- !gif
 = : !binary \
  [= base64 =]

No pipelining syntax needed! What I hate about 'pipelining' is that it
messes up the info model. If YAML has to round trip the pipeline I think the
above syntax reflects it in a better way.

BTW, should we allow ':' in private types? Currently it is banned (you can
only use alnum, '-' and '.'). Should we just allow any printables? How about
DNS-based names: should the part after the DNS name be anything, or
restricted to (alnum '-' '.') as today?

> | Hey, final note. What's going to keep us from mucking around with it
> | when
> | it's finished? I think we should all agree on some kind of frozen
> | period,
> | where nobody is allow to suggest major changes until we get a few
> | implementations completed and though an alpha test phase.
> 
> Sounds good.

Agreed.

Have fun,

    Oren Ben-Kiki