Re: Next YAML: drop equality definition

Oren,

> I'm not averse to tweaking the wording on a YAML1.3/2.0/whatever.
>For example, relaxing the equality detection requirement to happen
>only during construction, so a complete representation may still
>include equal keys. That is, we can apply a schema to assign tags
>to the nodes, but still not have any clue what these tags _mean_.
>That seems like a cleaner cut-off point between a complete
>representation and the native data. What the spec calls now a
>complete representation would be a canonical representation -
>something which is useful, but not required in many cases.

I totally concur.

Let me confirm one point. Does this allow identity-based
comparison of mapping nodes with some specific tags?


> But that issue doesn't seem to be the one raised here;
>the problem seems to be with the "early duplicates detection".
>Which, again, is explicitly not required by the spec.
>So I'm not certain what the actual problem is with the current
>rules. Is this a case of the perceived rules being different
>from the actual rules in the spec?

If you don't see any problem to relax the equality detection
as above, neither do I.

Thank you for your consideration!

Best,
Osamu Takeuchi


------------------------------------------------------------------------------