Open serich opened 3 years ago
AsyncAPI was mentioned during the OpenAPI special session we held as part of the December 2020 OGC Member Meeting.
A detailed overview of the landscape of async-related technologies is presented in the draft PubSub tech paper edited by @sarasaeedi.
@serich The Testbed 17 Moving Features task is also exploring async.
@ghobona The Pub-Sub Whitepaper has been released to the TC for an electronic vote. The final version of the paper is here
A short list of async techniques to consider:
Callbacks and Web Hooks are supported by OpenAPI 3.1.
Review whether we should include PubSub part in Common.
The Testbed-17 Aviation Task kickoff discussed the possibility of implementing some sort of asynchronous response capability (asynch messaging is important in frameworks such as SWIM).
A suggestion was made that the task should align with the asynch capability being discussed in API - Common, I presume referring to the extension described in #184 (Simple asynchronous extension proposal).
Question: does the API - Common SWG have any recommendation(s) on how the task should proceed? Is this simple asynch extension too immature, and the T17 task should ignore it until further notice? Or is it sufficiently far along that the task should go ahead and assume that it will become part of Common soon? Or somewhere in-between?
It's not currently blocking task progress. But if possible we'd like to avoid undertaking any work that might end up being throwaway later (unless testbed feedback would shed valuable light on the direction forward).
Any guidance would be appreciated.
Thanks.