Consider moving the agent subclasses to a type object
From @pospi in response to the addition of EcologicalAgent: Why not just do away with Agent types valueflows/vf-schemas/vf-graphql#101 and make inserting the 3 default ones a matter of data input / system configuration; like we do for Action.
I think this is worth some serious thought. Some considerations: still keeping some mapping to the agent structures in various rdf vocabs even with Agent, Person, Organization being in vf now; it would be a lot easier for some of the api's to not have subclasses; we could diverge vf and the api's (same meaning); ???
Thoughts welcome!