Re: [Yaml-core] Breaking change between YAML 1.1 and 1.2 with multiple documents

[Ingy d. N. <in...@in...>]

Sorry, for the late reply. Just returned from OSCON.

Thank you Roy for weighing in. When I have talked about removing the TAG
directives on IRC, it has been the Java people who have said that they are
really needed.

I came up with almost the same solution that trans did: put the info in a
leading inline document. This is very extensible, and can be used for all
types of added functionality.

I had the idea that instead of !!directives document you would have !!tags,
!!schema, !!meta (version etc), !!formatting (how to dump), !!translation
(how to load; merge etc) etc. You could also merge these into one leading
sequence doc of type !!yaml (where each sequence entry is one of the above).

This would take directives right out of the language, making the YAML
format simpler overall, and allow new external ideas to be played with in a
safe way before being adopted as yaml.org types.

I've always thought that schema documents should sit relative to their
content docs, but didn't think of putting them inline into the stream. YAML
has this (multidoc) advantage over JSON. Let's use it.

...

Ingy




On Wed, Jul 23, 2014 at 2:47 PM, Trans <tra...@gm...> wrote:

> https://gist.github.com/trans/c28a41353d76a7b78bef
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Yaml-core mailing list
> Yam...@li...
> https://lists.sourceforge.net/lists/listinfo/yaml-core
>
>