The containers could be defined in a generic way for standards-schemas within standards_schema_all.yaml, but that limits some of the point of having the schemas treated as different modules. The modules could still have their own container types, defined in each schema.
Container classes allow sets of data objects to be defined together, like in this example borrowed from the LinkML tests:
In that example, the schema defines the container like this:
It could also look like:
The containers could be defined in a generic way for
standards-schemas
withinstandards_schema_all.yaml
, but that limits some of the point of having the schemas treated as different modules. The modules could still have their own container types, defined in each schema.