[Design] - Core service and Foxx database changes #1830
Description
Description
Based on what we have seen in the discovery work, the easies way forward is to introduce a type system for the schemas, so adding a type member to each schema document. The core service when it sees the type information will know what to do with the schema. If the schema type is not defined the default will be to assume the existing JSON schema approach should be used.
The schema def can stay in the schema document and simply remain empty for the LinkML approach. This avoids a bunch of changes.
Changes in the core service will be more involved. We need a plugin like architecture, this means we need to abstract the Schema logic into a schema object, possibly use a factory, with both the default JSONSchema and the linkML schema class implementations.