Arazzo-Specification
Arazzo-Specification copied to clipboard
OAI
The Arazzo Specification - A Tapestry for Deterministic API Workflows
The specification is changing name, so update the specification and various wording to cater for the changes: ` worflowsSpec`, `Workflows Document` etc.
As the Workflows spec emerges as the second kind of specification under the OpenAPI auspices, there may be some governance issues to address. 1. Whether it makes sense to move...
**Time:** 17:00 (Irish Summer Time) **Zoom Link:** https://zoom.us/j/91426197903?pwd=cjNGcjgzWmRqZ1YyRW9PM3FFNFVFUT09 **Agenda:** - PR reviews/merging: - #182 - #183 - #187 - AOB - Governance / ReadMe updates
Hi Everyone, I have a few questions about `sourceDescriptions` with the type `workflowsSpec`. It appears that the intention is to reuse workflows from other files or sources. Iām a bit...
Hey folks š ! I've noticed you added support for `operationPath` for ability to target operations without operationId using JSON Pointer. I have some feedback based on our experience working...
In conversations with Erik Wilde, we also think it sensible that there should be a link relation type for workflows, so that for example an OpenAPI document could link to...
Revisit the structure of the README. Move the charter etc. to a separate file
We should publish a JSON Schema to help tooling validate specifications, etc...
See #164