Break down AttributeDescriptor not to contain writers and scheme serializers about proxima-platform HOT 3 CLOSED

Another remark for this - currently attribute family contains specifications for both readers and writers that apply to it. That is fundamentally wrong, because the read settings might (and will) be dependent on the actual reader (type of processing involved). We need to break the whole specification to:

• descriptors (entities, attributes, transforms, views)
• attribute families - physical storage, not including any settings for neither write nor read
• accessors - settings for write (single) and customizable settings for read using particular attribute family - this might also include settings about what strategy to choose when multiple options exist for a attribute family select choice (e.g. multiple commit logs, multiple families that can serve given access, etc.)

@JozoVilcek would you have any feedback or thoughts on this?

from proxima-platform.

I have nothing to add. Breakdown of responsibilities sounds right to me.

from proxima-platform.

Done.

from proxima-platform.