Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "STP/IM Component/Discussion on STP IM and JWT"
| Line 2: | Line 2: | ||
The [[STP Intermediate Metamodel]] (STP-IM) is a "bridge" between STP editors and its elements have the role of conceptual transport between different development spaces with the purpose of capturing as much common SOA design information as possible. | The [[STP Intermediate Metamodel]] (STP-IM) is a "bridge" between STP editors and its elements have the role of conceptual transport between different development spaces with the purpose of capturing as much common SOA design information as possible. | ||
| − | Similarly, the | + | Similarly, the [http://www.eclipse.org/jwt Java Workflow Tooling] project defines, as part of its mission to unify different workflow definition languages, a metamodel. This metamodel provides a consistent and complete set of elements to respond to the needs of a generic workflow editor and engine while at the same time covering most current workflow languages and standards. |
Given the similarities in the needs and purposes of STP-IM and JWT, discussions have been initiated with the aim to improve communication, sharing and collaboration between the two projects. This page is intended as a living space where information on the status of this collaboration is kept up to date. | Given the similarities in the needs and purposes of STP-IM and JWT, discussions have been initiated with the aim to improve communication, sharing and collaboration between the two projects. This page is intended as a living space where information on the status of this collaboration is kept up to date. | ||
Revision as of 11:46, 9 January 2008
Preliminary
The STP Intermediate Metamodel (STP-IM) is a "bridge" between STP editors and its elements have the role of conceptual transport between different development spaces with the purpose of capturing as much common SOA design information as possible.
Similarly, the Java Workflow Tooling project defines, as part of its mission to unify different workflow definition languages, a metamodel. This metamodel provides a consistent and complete set of elements to respond to the needs of a generic workflow editor and engine while at the same time covering most current workflow languages and standards.
Given the similarities in the needs and purposes of STP-IM and JWT, discussions have been initiated with the aim to improve communication, sharing and collaboration between the two projects. This page is intended as a living space where information on the status of this collaboration is kept up to date.