Re: Enum default not in canonical form

Hi everyone, Below is one opinion of the subject. The most robust way to determine if two schemata are the same is how they serialise datums to bytes. Schema evolution allows us to match schemata if they are not the same, but similar enough. Default values, both for fields and enums, are perfect

Re: Enum default not in canonical form

This is a bit weird, and it could be clarified. The "same" schema, of course, can be represented by different JSON text files: attribute order, ways to express the full name, inheriting full names, etc. The canonical form is always the "same" for the "same" schema and can be used to generate a fi

Enum default not in canonical form

The spec says one of the steps to get parsing canonical form is > [STRIP] Keep only attributes that are relevant to parsing data, which are: > type, name, fields, symbols, items, values, size. Strip all others (e.g., doc > and aliases). and indeed, we strip the default from an EnumSchema. But i