Re: YAML 2.0: drop arbitrary nodes to be used as keys

Dear Osamu,
>In YAML 1.2, the spec says

Please be aware that YAML 1.2 does not really exist. It is completely
ignored by the industry.
Even though it was released many years ago there is still no parser which
implements it.

I only know 2 parsers which _partially_ implement YAML 1.2


>Could you point out the importance of inter-operability
>if I do not understand it correctly.

I will try to define what is inter-operability for me (as a developer of a
general purpose YAML parser)

If I have YAML document  I can give it to anybody else.
They apply their context, they parse it with their programming language.
And they do not come back to me saying that I must change my YAML because
they cannot do anything.
The above  is valid for XML or JSON, but completely invalid for YAML.

SnakeYAML issues are full with complains that users cannot work with YAML
produced by another parser.
Why a developer should explain to the community the deficiencies of the
specification ?

If you produce and consume YAML yourself then it works. Is it what we want ?

Cheers,
Andrey

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140

_______________________________________________
Yaml-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/yaml-core