Update list of Special Interest Groups

SPECIAL_INTEREST_GROUPS.md

@@ -1 +1,43 @@
+## Codegen
+> code-gen vocabulary special interest (working) group
 
+* Slack channel: #sig-codegen
+
+## Formats
+> Focusing on the Formats Registry efforts
+
+* Slack channel: #sig-formats
+
+## Lifecycle
+> A place to discuss how to represent how APIs change in time in the context of OpenAPI
+
+* Slack channel: #sig-lifecycle
+
+## Overlays
+> 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.
+
+* Github: https://github.com/OAI/Overlay-Specification
+* Slack channel: #sig-overlays
+
+## Security
+> Workgroup to shape security components of the OpenAPI Spec
+* Slack channel: #sig-security
+
+## SLA (Service Level Agreement)
+> Service level agreements and APIs.
+
+* Github: https://github.com/isa-group/SLA4OAI-TC
+* Slack channel: #sig-sla
+
+## Travel
+> An OpenAPI Initiative workgroup to address industry specific connective/API concerns of the travel industry
+
+* Slack channel: #sig-travel
+
+## Workflows
+> This is a channel dedicated to discussing workflows, automations, and scenarios.
+
+> 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. 
+> 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. 
+
+* Slack channel: #sig-workflows