Ideas and requirements for schema redesign

[987Nabil]

Currently Schema mixes up too many concerns into one data structure, that makes it hard to fit different needs.
For example, there is Schema.Transform which can't be serialized.

Requirements

• Separate pure Schema data description from (de)construction of instances of the type
• Elevate meta information from annotations to first class values.
  • Case/Field name
  • Case/Field alias
  • Field being transient
  • Description
  • Optionality
  • Simple enum (only object subtypes)

Open Questions

Special Requirements for specific serialization format

for example protobuf needs field numbers. Users need to define them. Where to save them

Annotations?

Should we save all annotations? Where? Annotations are not serializable.