I don't know how many exemplars we may want to have of this kind of
data, so I don't want to sweat it too much.
If no one anticipates multiple exemplars of this kind of data, we
could just use ExpressionSet and live with the terminologic abuse.
If the only benefit of a new class is new names and if you will want
to apply the same computations, then you really are just making work.
Make a new class _if_ the existing methods (thinking machine learning,
etc) that operate on exprs() are not going to make sense and need
customization.