[Yaml-core] More IRC

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

Clark and I were just on the IRC.

We have a new YAC, #7: Rename 'implicit' to 'simple'. Because not all simple
leafs are implicitly types; they may be explicitly typed. And other leafs
may be implicitly typed using a '!' transfer property.

We'll do a YAC-list HTML page to keep track of issues. Place it and the spec
under CVS control so we can do small changes easily (assuming changes from
now on will be small).

YAC#3.2 is what we agreed upon for URIs. It is just like the YAC#3.1 I
described in a previous post, with the change that we'll write:

    !type:lang/package|type

Instead of:

    !type:lang:package|type

For example:

    !type:java/tld.domain|Type
    !java/tld.domain|Type

This is tricky for Perl, because we don'y have a package. I guess we'll
write:

    !perl/|%Net::Ftp

Unless we want to write:

    !perl/cpan|%Net::Ftp

Or best of all (IMO):

    !perl/Net|%Ftp

Brian's call... Brian?

!seq is shorthand for !type:any/org.yaml|seq
and !tld.domain|type is !type:any/tld.domain|type
so everything is a URI and all we have is a
defaulting mechanism for URIs.

We'll look into registering 'type:' as a URI scheme. It isn't taken.

We'll be using ';' for format.

YAC#6.1 gained some favor:

- key1: value1
  key2: value2

Is equal to:

-
 key1: value1
 key2: value2

This is an error:

- key1: value1
 key2: value2

This is a sub list:

- top key:
   sub key: sub value

Typing is of a key:

- !key-type key: value
- !map-type
 key: value

The use case is "list of maps" (it looks even better with a single key/pair
value). The use case is common (our invoice example has an instance).

Clark will go with it, but he thinks its ugly (he likes the empty '-' lines,
believe it or not :-). I'd rather keep it in, but won't make too much of a
fuss about it. So, Brian, the ball is in your court...

Have fun,

	Oren Ben-Kiki