Skip to content

Commit 80d8c8e

Browse files
Update list of Special Interest Groups (OAI#3262)
Each Special Interest Group is listed along with a description of the group and a link to its Slack channel and Github repository where available.
1 parent bcb0c45 commit 80d8c8e

File tree

1 file changed

+42
-0
lines changed

1 file changed

+42
-0
lines changed

SPECIAL_INTEREST_GROUPS.md

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1 +1,43 @@
1+
## Codegen
2+
> code-gen vocabulary special interest (working) group
13
4+
* Slack channel: #sig-codegen
5+
6+
## Formats
7+
> Focusing on the Formats Registry efforts
8+
9+
* Slack channel: #sig-formats
10+
11+
## Lifecycle
12+
> A place to discuss how to represent how APIs change in time in the context of OpenAPI
13+
14+
* Slack channel: #sig-lifecycle
15+
16+
## Overlays
17+
> The Overlay specification defines a way of creating documents that contain information to be merged with an OpenAPI description at some later point in time, for the purpose of updating the OpenAPI description with additional information.
18+
19+
* Github: https://github.com/OAI/Overlay-Specification
20+
* Slack channel: #sig-overlays
21+
22+
## Security
23+
> Workgroup to shape security components of the OpenAPI Spec
24+
* Slack channel: #sig-security
25+
26+
## SLA (Service Level Agreement)
27+
> Service level agreements and APIs.
28+
29+
* Github: https://github.com/isa-group/SLA4OAI-TC
30+
* Slack channel: #sig-sla
31+
32+
## Travel
33+
> An OpenAPI Initiative workgroup to address industry specific connective/API concerns of the travel industry
34+
35+
* Slack channel: #sig-travel
36+
37+
## Workflows
38+
> This is a channel dedicated to discussing workflows, automations, and scenarios.
39+
40+
> The OpenAPI Specification provides a way to document individual API calls and how to use them, but it doesn't give insight into the common ways to sequence those operations. While all APIs can benefit from formally describing these workflows, this is particularly important when considering more complex or more secure APIs.
41+
> The OpenAPI Workflows Special Interest Group was created to address this common problem. The goal is to construct a formal way to describe these sequences and support documentation of flows, such as a multi-part OAuth flow with JSON signing and refresh token behavior.
42+
43+
* Slack channel: #sig-workflows

0 commit comments

Comments
 (0)