You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: