The Object Management Group (or OMG) "has been an international, open membership, not-for-profit computer industry consortium since 1989. Any organization may join OMG and participate in our standards-setting process. Our one-organization-one-vote policy ensures that every organization, large and small, has a effective voice in our process. Our membership includes hundreds of organizations, with half being software end-users in over two dozen vertical markets, and the other half representing virtually every large organization in the computer industry and many smaller ones. Most of the organizations that shape enterprise and Internet computing today are represented on our Board of Directors.

OMG Task Forces develop enterprise integration standards for a wide range of technologies, including: Real-time, Embedded and Specialized Systems, Analysis & Design, Architecture-Driven Modernization and Middleware and an even wider range of industries, including: Business Modeling and Integration, C4I, Finance, Government, Healthcare, Legal Compliance, Life Sciences Research, Manufacturing Technology, Robotics, Software-Based Communications and Space.

OMG’s modeling standards, including the Unified Modeling Language™ (UML®) and Model Driven Architecture® (MDA®), enable powerful visual design, execution and maintenance of software and other processes, including IT Systems Modeling and Business Process Management. OMG’s middleware standards and profiles are based on the Common Object Request Broker Architecture (CORBA®) and support a wide variety of industries."

JBoss is involved in the following task forces:

Business Process Model and Notation (BPMN)

The BPMN standard originally started as purely a graphical notation to enable business users to outline the flow associated with processes and their collaborations.

With the latest version 2 specification, the specification has been extended to incorporate the following important areas:

1. Interoperability
   A common meta-model has now been defined to enable BPMN compliant tools to exchange models and diagrams.
   
   
2. Executability
   The original version of the standard was widely used as the graphical notation for designing processes that subsequently were executed as WS-BPEL. Therefore it was recognized that version 2 should support directly executable processes, rather than requiring the translation of a BPMN model into other executable representations.
3. Choreography
   Prior to BPMN version 2, the only choreography standard was WS-CDL (from W3C). However this recommendation did not have a graphical representation, or fit well with the graph based BPMN notation. Therefore the concept of choreography was added to the BPMN2 standard, to enable the behaviour between interacting parties (services/processes) to be described in a notation familiar and compatible with the more traditional process based BPMN notation.

Decision Model and Notation

DMN is set to define a Decision Model notation and metamodel and associated interchange format. Decision Models are developed to define how businesses make decisions, usually as a part of a business process model (BPMN).

The Request For Papers defines the following mandatory requirements:-

1. A Typology of Decision Models
   As there is no standard definition or typology of decision models, the DMN standard shall provide such a typology.
   
   
2. Decision Metamodel
   DMN shall provide a metamodel to support decision models, and specify the associated semantics.
   
   
3. Decision Model Notation
   DMN shall provide an intuitive diagrammatic representation of a decision model for the business user.
   
   
4. Decision Model Interchange
   DMN shall provide, or reference an existing, interchange format that allows the exchange of decision models between tools.

Full details can be found in the linked document (Section 6.5, page 30).

Cloud Working Group

(forming)