Re: [Yaml-core] Fix to YAML 1.1 Supports JSON as valid YAML

[Clark C. E. <cc...@cl...>]

On Wed, May 24, 2006 at 01:58:08PM -0700, Ingy dot Net wrote:
| We agreed that (as Oren had pointed out here earlier) we could achieve
| JSON compatability (meaning that any valid JSON stream is a valid YAML
| stream) by making two relaxations to the spec:
| 
| > 1. Relaxation: Allow tabs in separation spaces.
| > 
| > 2. Relaxation: Do not require a space after the colon if (and only if) 
| > the key is quoted.

Correct.  The decision today reflected a concensus: JSON 
compatibility sooner rather than later is important.  It 
would be great if implementations updated to handle these 
two relaxations as soon as they can.

| We also decided that on the related but separate issues about 
| the colon, we:
| 
|   1) Could not agree on what was best.
|   2) Did agree that the change would not be backwards compatible,
|      thus forcing us to YAML 1.2.

Yes, we agreed to disagree -- for now.  That said, we will have to come
to a resolution soon on this particular issue, 6-12 months is a resonable 
timeframe.  I would encourage emitters to *not* produce the following
syntax form since it could quite possibly be an error in the future:

| Therefore:
|     {a:12}
| Is currently valid YAML (1.1 and 1.0) and it means:
|     {"a:12": ""}

This is certainly and edge case, and if you get it wrong, as ingy says
"the bite will teach you".  I would also like to put a warning in the
1.1 specification about this particularly un-intuitive case; and I think
implementations should be free to pass along a potentially fatal-warning
onto the user as long as this warning can be disabled.

Best,

Clark