Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TRQP-4] Change OpenAPI specifications to be bound to specifically RESTful implementation #56

Open
andorsk opened this issue Jul 30, 2024 · 1 comment

Comments

@andorsk
Copy link
Contributor

andorsk commented Jul 30, 2024

This is related to #52.

According to the current specification, there are components which are specifically bound to OpenAPI yaml. For example, TRQP-4 and the error codes in TRQP-5.

#52 proposes to add RDAP and DNS, which may require updates to the data models to comply with the protocol. RDAP resolves over HTTP, but the response models and accessors would need to look different to comply.

If we want to support multiple protocols, then TRQP-4 and 5 should probably be bound to a specific context (i.e RESTful), and allows variations depending on the profile.

@darrellodonnell
Copy link
Collaborator

Good catch.

re: #52 We should determine who is willing to do the RDAP/DNS work and if they will commit resources to moving things forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants