Note: assumes knowledge gleanable from Data::Record's README and wiki.
I want to do a revision of record types in Data::Record as the user interacts with them from top to bottom, similarly to what v1.x's annotations-based API did for its internals. This would primarily involve the abandonment of the structural, structured, and unstructured keywords in favour of fixed and freeform, which would apply to all core record types. The notion of structured and unstructured data doesn't fit for this module in my view, which I tried to express poorly by naming unstructured data structural, because "structured" only applies to the strictest available wrap, and "unstructured" only applies to the loosest available coercion; the presence of semi-structured data is t