Re: Next YAML: drop equality definition

Oren,

> The answer is that we have learned from XML that these
> lead to madness and _must_ be avoided.

After all, we went back to the start point.
But now, I see you really think it makes YAML better than XML.

I understand you want to make all valid YAML document to be
able to be processed by all YAML libraries on all platforms
with the proper schema given. To do so, the use of YAML nodes
must be restricted in some degree. I understood your dream
for some degree.


If we go that way, as you wrote, we must forbid the use
of collection nodes as mapping keys when they are only
different in identity.


I still do not see why each tag must apply to exactly one
kind. It forbid the use case of !complex in the previous
example. Does it provide any more portability?


Javascript library will not handle a valid YAML mapping
correctly if it maps !!map to the javascript's native object.
Then, the library _must_ provide its own data structure that
can distinguish !!str "1" from !!int 1 because YAML specification
allow users to assume that a !!map node distinguishes them.


I still think the portability is not very much reduced by
relaxing equality definition in the spec but I need some time
to make up the argument. I may come back to this point, later.

Best,
Osamu Takeuchi


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval