Duplicate model names generated for FlowSegment, FlowSegmentPost and DeletionRequest

[Shaun-3adesign]

Describe the bug
When generating server stubs from TimeAddressableMediaStore.yaml using openapitools/openapi-generator-cli, three schemas produce duplicate model pairs: FlowSegment / FlowSegment1, FlowSegmentPost / FlowSegmentPost1, and DeletionRequest / DeletionRequest1. Both models in each pair are structurally identical. A developer implementing the server traits has no clear basis for choosing between them.

Expected behavior
Each schema should produce a single, consistently named model.

Suggested fix
Register each schema once in components/schemas in the root YAML and replace all direct $ref: schemas/<file>.json usage sites with $ref: '#/components/schemas/<Name>'. The generator deduplicates schemas keyed on their components/schemas path, so all references to the same entry resolve to one model.

Additional context
The root cause is that the same external schema file is referenced at multiple distinct YAML paths. The generator resolves each path independently and treats them as separate schemas. This is a spec convention issue rather than a generator bug — using components/schemas is the intended OpenAPI pattern for shared, reusable schemas.

[Shaun-3adesign]

Generating from the bundled spec (docs/TimeAddressableMediaStore_bundled.yaml, produced by make render) resolves all four duplicate pairs as a workaround, but is not a true fix — anyone generating directly from TimeAddressableMediaStore.yaml would still hit the same problem.

[j616]

Thank you for your report. Can I check that this is the same as #202 and is an issue with openapi-generator, rather than the TAMS spec?

[Shaun-3adesign]

This one can be fixed by adding the required models to the components section of the yaml file. #202 I closed because it was not as straight forward. so I've also not make changes to the openapi generator code and have pending pull requests that fixes that.

[samdbmg]

This is a spec convention issue rather than a generator bug - using components/schemas is the intended OpenAPI pattern for shared, reusable schemas.

I'm not sure I'd agree that this is a spec bug - especially given that the docs renderer, bundler, linter etc. are all happy with it and only the generator can't de-duplicate references (unless you have a citation for this assertion?)

Nevertheless this experience could be better - I've re-cast this as a Task as such. I'd gladly take a PR that implements that change, so long as it doesn't break the docs render in the process.