open-workflow-specification · ricardozanini · Aug 27, 2026
@@ -1,6 +1,6 @@
-[![contributions Welcome](https://img.shields.io/badge/Contributions-Welcome-green.svg?style=flat)](https://github.com/serverlessworkflow/specification/issues)
-[![license](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://github.com/serverlessworkflow/specification/blob/master/LICENSE)
-[<img alt="GitHub Release" src="https://img.shields.io/github/v/release/serverlessworkflow/specification?label=Release">](https://github.com/serverlessworkflow/specification/releases/latest)
+[![contributions Welcome](https://img.shields.io/badge/Contributions-Welcome-green.svg?style=flat)](https://github.com/open-workflow-specification/specification/issues)
+[![license](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://github.com/open-workflow-specification/specification/blob/master/LICENSE)
+[<img alt="GitHub Release" src="https://img.shields.io/github/v/release/open-workflow-specification/specification?label=Release">](https://github.com/open-workflow-specification/specification/releases/latest)
 <br>
 [<img src="https://img.shields.io/badge/Website-blue?style=flat&logo=google-chrome&logoColor=white">](https://open-workflow-specification.org/) 
 [<img src="https://img.shields.io/badge/Slack-4A154B?style=flat&logo=slack&logoColor=white">](https://cloud-native.slack.com/messages/open-workflow) 
@@ -73,13 +73,13 @@ These SDKs empower developers to seamlessly integrate workflows into their appli
 
 Explore our SDKs for different programming languages:
 
-- [.NET](https://github.com/serverlessworkflow/sdk-net)
-- [Go](https://github.com/serverlessworkflow/sdk-go)
-- [Java](https://github.com/serverlessworkflow/sdk-java)
-- [PHP](https://github.com/serverlessworkflow/sdk-php)
-- [Python](https://github.com/serverlessworkflow/sdk-python)
-- [Rust](https://github.com/serverlessworkflow/sdk-rust)
-- [TypeScript](https://github.com/serverlessworkflow/sdk-typescript)
+- [.NET](https://github.com/open-workflow-specification/sdk-net)
+- [Go](https://github.com/open-workflow-specification/sdk-go)
+- [Java](https://github.com/open-workflow-specification/sdk-java)
+- [PHP](https://github.com/open-workflow-specification/sdk-php)
+- [Python](https://github.com/open-workflow-specification/sdk-python)
+- [Rust](https://github.com/open-workflow-specification/sdk-rust)
+- [TypeScript](https://github.com/open-workflow-specification/sdk-typescript)
 
 Don't see your favorite implementation on the list? Shout out to the community about it or, even better, contribute to the ecosystem with a new SDK!
 
@@ -90,15 +90,15 @@ No matter your preferred language, our SDKs provide the tools you need to levera
 | Name | About |
 | --- | --- |
 | [Apache KIE SonataFlow](https://sonataflow.org) | Apache KIE SonataFlow is a tool for building cloud-native workflow applications. You can use it to do the services and events orchestration and choreography. |
-| [Java SDK reference implementation](https://github.com/serverlessworkflow/sdk-java/tree/main/impl) | Full compliant Java implementation of the specification |
+| [Java SDK reference implementation](https://github.com/open-workflow-specification/sdk-java/tree/main/impl) | Full compliant Java implementation of the specification |
 | [Lemline](https://github.com/lemline/lemline) | Lemline is a highly scalable runtime running on top of your existing messaging infrastructure. |
-| [Synapse](https://github.com/serverlessworkflow/synapse) | Synapse is a scalable, cross-platform, fully customizable platform for managing and running workflows defined with Open Workflow Specification. |
+| [Synapse](https://github.com/open-workflow-specification/synapse) | Synapse is a scalable, cross-platform, fully customizable platform for managing and running workflows defined with Open Workflow Specification. |
 
 ### Tooling
 
 In order to enhance developer experience with the Open Workflow DSL, we provide a [Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=serverlessworkflow.serverless-workflow-vscode-extension).
 
-The sources of the extension can be found [here](https://github.com/serverlessworkflow/vscode-extension).
+The sources of the extension can be found [here](https://github.com/open-workflow-specification/vscode-extension).
 
 ### CNCF Landscape
 

@@ -4,7 +4,7 @@
 
 The Open Workflow Specification team and community take security bugs very seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
 
-To report a security issue, please use the GitHub Security Advisory ["Report a Vulnerability"](https://github.com/serverlessworkflow/specification/security/advisories/new) tab.
+To report a security issue, please use the GitHub Security Advisory ["Report a Vulnerability"](https://github.com/open-workflow-specification/specification/security/advisories/new) tab.
 
 The Open Workflow Specification team will send a response indicating the next steps in handling your report. After the initial reply to your report, the security team will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.
 
@@ -18,7 +18,7 @@ To help ensure the security of your workflows, we recommend the following best p
 - **Monitor and Audit**: Continuously monitor and audit workflows to detect and respond to any suspicious activities.
 - **Secure External Resources**: Ensure that any resources external to a workflow definition are always secured using modern authentication policies as defined in the DSL.
 - **Use Trusted Containers and Scripts**: When relying on [run tasks](dsl-reference.md#run), only use trusted container images, scripts, commands and workflows.
-- **Custom Functions**: Only use custom functions from the [Open Workflow Catalog](https://github.com/serverlessworkflow/catalog) or from trusted sources to avoid introducing vulnerabilities.
+- **Custom Functions**: Only use custom functions from the [Open Workflow Catalog](https://github.com/open-workflow-specification/catalog) or from trusted sources to avoid introducing vulnerabilities.
 
 ---
 

@@ -6,7 +6,7 @@ Proposed
 
 ## Related Issue
 
-[#1149](https://github.com/serverlessworkflow/specification/issues/1149) - Proposal: Official Migration Tool for 0.8/0.9 to 1.0.0 Workflows
+[#1149](https://github.com/open-workflow-specification/specification/issues/1149) - Proposal: Official Migration Tool for 0.8/0.9 to 1.0.0 Workflows
 
 ## Context
 
@@ -408,8 +408,8 @@ swf-migrate workflow.json --strict
 
 ## References
 
-- [Open Workflow 0.8 Specification](https://github.com/serverlessworkflow/specification/tree/0.8.x)
-- [Open Workflow 0.9 Specification](https://github.com/serverlessworkflow/specification/tree/0.9.x)
-- [Open Workflow 1.0.0 Specification](https://github.com/serverlessworkflow/specification)
+- [Open Workflow 0.8 Specification](https://github.com/open-workflow-specification/specification/tree/0.8.x)
+- [Open Workflow 0.9 Specification](https://github.com/open-workflow-specification/specification/tree/0.9.x)
+- [Open Workflow 1.0.0 Specification](https://github.com/open-workflow-specification/specification)
 - [JsonPath Specification](https://goessner.net/articles/JsonPath/)
 - [jq Manual](https://jqlang.github.io/jq/manual/)
@@ -26,7 +26,7 @@ multiple vendors/maintainers to contribute and embed it.
 
 This ADR formalizes the decision to build a shared editor, with a strictly
 scoped MVP, aligned with the proposal outlined in
-[serverlessworkflow/specification#1131](https://github.com/serverlessworkflow/specification/issues/1131) and further refined through MVP
+[serverlessworkflow/specification#1131](https://github.com/open-workflow-specification/specification/issues/1131) and further refined through MVP
 scoping discussions.
 
 ## Decision

@@ -13,13 +13,13 @@ well as the guidelines we follow for how our documents are formatted.
 ## Reporting an Issue
 
 If you have a question, consider opening a
-[discussion](https://github.com/serverlessworkflow/specification/discussions).
+[discussion](https://github.com/open-workflow-specification/specification/discussions).
 
 To report an issue or to suggest an idea for a change that you haven't had time
 to write up yet, open an
-[issue](https://github.com/serverlessworkflow/specification/issues). It is best
+[issue](https://github.com/open-workflow-specification/specification/issues). It is best
 to check our existing
-[issues](https://github.com/serverlessworkflow/specification/issues) first to
+[issues](https://github.com/open-workflow-specification/specification/issues) first to
 see if a similar one has already been opened and discussed.
 
 ## Suggesting a Change
@@ -29,12 +29,12 @@ glance, requiring some discussions with other contributors before reaching a
 conclusion.
 
 Before opening a pull request, we kindly ask you to consider opening a
-[discussion](https://github.com/serverlessworkflow/specification/discussions)
-or an [issue](https://github.com/serverlessworkflow/specification/issues). The
+[discussion](https://github.com/open-workflow-specification/specification/discussions)
+or an [issue](https://github.com/open-workflow-specification/specification/issues). The
 community will be more than happy to discuss your proposals there.
 
 Having the discussion or issue settled, please submit a
-[pull request](https://github.com/serverlessworkflow/specification/pulls) (PR)
+[pull request](https://github.com/open-workflow-specification/specification/pulls) (PR)
 with the complete set of changes discussed with the community. See the
 [Spec Formatting Conventions](#spec-formatting-conventions) section for the
 guidelines we follow for how documents are formatted.
@@ -46,7 +46,7 @@ discussion.
 
 Due to the amount of text a specification can have, typos, spelling, and
 formatting issues are pretty common. In these cases, please submit a
-[pull request](https://github.com/serverlessworkflow/specification/pulls)
+[pull request](https://github.com/open-workflow-specification/specification/pulls)
 directly only with the fixes that you see fit.
 
 ### Assigning and Owning work

@@ -46,7 +46,7 @@ Conformance testing is the process of verifying that an implementation adheres t
 1. **Clone the Repository**: Start by cloning the Open Workflow CTK repository to your local machine.
 
 ```sh
-git clone https://github.com/serverlessworkflow/specification.git
+git clone https://github.com/open-workflow-specification/specification.git
 ```
 
 2. **Install Dependencies**: Ensure that you have all the necessary dependencies installed. This typically involves setting up a testing framework that can execute Gherkin tests.

@@ -1472,7 +1472,7 @@ The data carried by the cloud event that notifies that the status phase of a wor
 |:--|:---:|:---:|:---|
 | name | `string` | `yes` | The qualified name of the workflow which's status phase has changed. |
 | updatedAt | `dateTime` | `yes` | The date and time at which the workflow's status phase has changed. |
-| status | `string` | The workflow's current [status phase](https://github.com/serverlessworkflow/specification/blob/main/dsl.md#status-phases). |
+| status | `string` | The workflow's current [status phase](https://github.com/open-workflow-specification/specification/blob/main/dsl.md#status-phases). |
 
 ###### Examples
 
@@ -1662,7 +1662,7 @@ The data carried by the cloud event that notifies that the status phase of a tas
 | workflow | `string` | `yes` | The qualified name of the workflow the task which's status phase has changed belongs to. |
 | task | `uri` | `yes` | A JSON Pointer that references the task which's status phase has changed. |
 | updatedAt | `dateTime` | `yes` | The date and time at which the task's status phase has changed. |
-| status | `string` | The task's current [status phase](https://github.com/serverlessworkflow/specification/blob/main/dsl.md#status-phases). |
+| status | `string` | The task's current [status phase](https://github.com/open-workflow-specification/specification/blob/main/dsl.md#status-phases). |
 
 ###### Examples
 
@@ -1957,9 +1957,9 @@ do:
 
 A **resource catalog** is an external collection of reusable components, such as functions, that can be referenced and imported into workflows. Catalogs allow workflows to integrate with externally defined resources, making it easier to manage reuse and versioning across different workflows.
 
-Each catalog is defined by an `endpoint` property, specifying the root URL where the resources are hosted, enabling workflows to access external functions and services. For portability, catalogs must adhere to a specific file structure, as defined [here](https://github.com/serverlessworkflow/catalog?tab=readme-ov-file#structure).
+Each catalog is defined by an `endpoint` property, specifying the root URL where the resources are hosted, enabling workflows to access external functions and services. For portability, catalogs must adhere to a specific file structure, as defined [here](https://github.com/open-workflow-specification/catalog?tab=readme-ov-file#structure).
 
-For more information about catalogs, refer to the [Open Workflow DSL document](https://github.com/serverlessworkflow/specification/blob/main/dsl.md#catalogs).
+For more information about catalogs, refer to the [Open Workflow DSL document](https://github.com/open-workflow-specification/specification/blob/main/dsl.md#catalogs).
 
 #### Properties
 
@@ -1979,7 +1979,7 @@ use:
   catalogs:
     global:
       endpoint:
-        uri: https://github.com/serverlessworkflow/catalog
+        uri: https://github.com/open-workflow-specification/catalog
         authentication:
           basic:
             username: user
@@ -2766,7 +2766,7 @@ do:
                     event:
                       with:
                         source: https://open-workflow-specification.org/samples
-                        type: io.serverlessworkflow.samples.asyncapi.message.consumed.v1
+                        type: io.open-workflow-specification.samples.asyncapi.message.consumed.v1
                         data:
                           message: '${ $message }'
 ```