I'll make an executive call and say that you should stick to the spec. The type repository is not kept up to date as well as the spec is.

You may want to provide compatibility options to change your implicit typing if problems come up in the wild. Otherwise I would not worry about it.

In my opinion, the default implicit typing should be even stricter, only happening on 'true' and 'false'. This is required for JSON compatibility and also gives us one simple way to express boolean values. Maybe in YAML 2.0 :)

I would *highly* suggest that you don't ever *emit* anything other than those lowercase versions.

Cheers, Ingy

On Thu, May 26, 2011 at 8:14 PM, Jean-Sébastien Pédron <> wrote:
Hash: SHA1


The Core Schema (as found in YAML 1.2 specifications) defines some
types. Those types are also defined in the Tag repository

For instance, considering the Core Schema, the ",2002:bool"
type can have the following values:
   o  true    o  false
   o  True    o  False
   o  TRUE    o  FALSE

But the same tag defined in the Tag repository defines more values (ie.
a combination of "yes/no/on/off").

Which definition one must follow? Or did I miss something with tag
resolution (quite possible)?

Thank you!

- --
__  __
\ \/ /  Jean-Sébastien Pédron
 \  /   Yakaz
Version: GnuPG v2.0.17 (FreeBSD)
Comment: Using GnuPG with Mozilla -


vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
Yaml-core mailing list