Bug description
Details about spec consistency - Provide a single source of truth and enforce parity between written spec, OpenAPI schemas, and examples; standardize naming/casing (enums) to avoid codegen drift and incompatible clients.
Proposed fix
There is early implementation on the usage of LinkML. With the inclusion of the OpenAPI specification, we should think through what is the single source of truth, and how that automatically updates the associated or referenced artifacts.
Anything else (optional)
High - this is an interop issue. We need to a) define what's the normative baseline (written spec vs. OpenAPI) and b) ensure that the OpenAPI spec matches the written spec (this is a credibility issue)
Bug description
Details about spec consistency - Provide a single source of truth and enforce parity between written spec, OpenAPI schemas, and examples; standardize naming/casing (enums) to avoid codegen drift and incompatible clients.
Proposed fix
There is early implementation on the usage of LinkML. With the inclusion of the OpenAPI specification, we should think through what is the single source of truth, and how that automatically updates the associated or referenced artifacts.
Anything else (optional)
High - this is an interop issue. We need to a) define what's the normative baseline (written spec vs. OpenAPI) and b) ensure that the OpenAPI spec matches the written spec (this is a credibility issue)