Arazzo-Specification
Arazzo-Specification copied to clipboard
OAI
The Arazzo Specification - A Tapestry for Deterministic API Workflows
Add more examples into the specification (or example documents) that show case having multiple success/failure objects with different criteria. This will draw better attention to the possibilities of branching.
Having the following event handlers could be advantageous for steps and workflows - onNext - onCompletion The addition would likely negate the creation of vendor specific extensions to cover similar...
As a working group we've discussed the potential need for having _aliases_ to facilitate _codegen_ use-cases. Currently, when referencing an `operationId` within a source specification document, you MUST prefix it...
The current specification is arguably Turing complete in so far as it supports conditional branching with the ability to _go to_ other steps or workflows depending on those conditions. Recursively...
We should define tags for implementors to use within their public repos that eventually will ensure their tools appear on https://tools.openapis.org/
**Time:** 17:00 (Irish Summer Time) **Zoom Link:** https://zoom.us/j/91426197903?pwd=cjNGcjgzWmRqZ1YyRW9PM3FFNFVFUT09 **Agenda:** - PR reviews/merging: - #189 - AOB - Governance / ReadMe updates
It seems a little odd that one identifier for XPath is `xpath-30` and the intention seems to be that it identifies XPath 3.1. There is an existing XPath 3.0 specification...
I believe this should say `...named location...`
closes #176 There are four pending issues related to finalizing this draft #223 #222 #221 #220