[X3D-Ecosystem] OpenAPI to …

[John Carlson]

*From a single OpenAPI YAML/JSON file for your system, tools can generate:*


*“Key Items Generated from OpenAPI:*

   - *API Clients/SDKs:* Code for consuming APIs in languages like Python,
   Java, TypeScript, Go, Ruby, and more.
   - *Server Stubs:* Skeleton code to start building APIs (e.g.,
   Express.js, Spring Boot, Flask, ASP.NET).
   - *Documentation:* User-friendly documentation sites (HTML, Swagger UI).
   - *Data Models/Schemas:* Data transfer objects (DTOs) and models based
   on the API definition.
   - *Configuration Files:* Build configurations, such as Maven, Gradle, or
   Bazel plugins.
   - *Other Artifacts:* GraphQL schemas, MySQL schemas, or specialized
   configurations.”

=============
What’s the likelihood of converting X3DUOM to an OpenAPI YAML/JSON file?  I
did a zod schema last night.   How do we make it repeatable and enduring?
Generating the first version with AI may lead to something repeatable, as
long as we have something to target.

I tried to get a contractor to work a project like this for me, but AFAIK,
he built some CakePHP/Laravel thing with Composer.

Perhaps it’s time to do something with X3D.

Is there an OpenAPI registry?
https://apichangelog.substack.com/p/the-openapi-registry

I do recall a JSON schema repository on GitHub.   I’ll talk to the JSON
schema folks to find out more.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-ecosystem_web3d.org/attachments/20260219/0fdd9cd1/attachment.html>