It's certainly one option to provide a separate Avro schema for each feature format.  But the problem is that then you would lose any type relations between them.  I think having them rooted at a `BaseFeature` type will probably simplify some implementation in the future.

That said, I'm not against doing that if the group is on board with it.  It's probably the simplest way to go...