Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date: July 2014

  • This is the OMG submission template in Word and ODT. The OMG document number is pas/2012-04-08. The template was updated with a new Cover and Preface and supersedes OMG document pas/2008-10-01.

...

  • CORBA/IIOP
  • Data Distribution Services
  • Specialized CORBA

IDL/Language Mapping Specifications
Modeling and Metadata Specifications

  • UML, MOF, CWM, XMI
  • UML Profile

Modernization Specifications
Platform Independent Model (PIM), Platform Specific Model (PSM), Interface Specifications

  • CORBAServices
  • CORBAFacilities

...

The Scope clause shall appear at the beginning of each specification and define, without ambiguity, the subject of the specification and the aspect(s) covered. It indicates the limits of applicability of the specification or particular parts of it. It shall not contain requirements.
The scope shall be succinct so that it can be used as a summary for bibliographic purposes.
It shall be worded as a series of statements of fact.

...

The Conformance clause identifies which clauses of the specification are mandatory (or conditionally mandatory) and which are optional in order for an implementation to claim conformance to the specification.
Note: For conditionally mandatory clauses, the conditions must, of course, be specified.

...

3.1 Normative References
The following normative documents contain provisions which, through reference in this text, constitute provisions of this specification. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply.
List of normative references.
3.2 Non-normative References
List of non-normative references.

...

For the purposes of this specification, the following terms and definitions apply.
Term
Definition

...

List of symbols/abbreviations.

...

The following companies submitted this specification:

  • xxxxx
  • xxxxx
  • xxxxx

...

  • xxxxx
  • xxxxx
  • xxxxx

...

Text

...

  • true - Text
  • false - Text

 

...

body: String [0..1]

Specifies a string that is the comment.

...

annotatedElement : Element [*]

References the Element(s) being commented.

 

...

ownedComment : Comment [*]

The Comments owned by this element.
Subsets ownedElement

The Relationships subpackage of the Abstractions package adds support for directed relationships.

...

Text.

...

  1. Text
  2. Text
  3. Text

...

  • Text
  • Text

...

Package

Comment

Business Process Definition MetaModel

The Business Process Definition MetaModel package contains the models for orchestration (including BPMN) and choreography, and their performance, enactment, and execution. It has six subpackages grouped into two categories:
Common Behavior Model for the aspects of dynamics in common between orchestrations and choreography (Behavior Model, and Interactive Behavior Model).
Activity Model (including BPMN Extensions) for orchestration and Interaction Protocol Model for choreography.
The Business Process Definition MetaModel package imports the Common Infrastructure package which provides the framework that ties the other models to performance, enactment, and execution (Abstractions, Composition Model, Course Model, and Condition Model).

Common Infrastructure

The Common Abstractions package is the framework that ties the other models to performance, enactment, and execution (Composition Model, Course Model and Condition Model).

Annex A: Title
(normative)
Anchor_Toc443461104_Toc443461104A.1  Clause heading
Text
Normative annexes are integral parts of the standard. Their presence is optional. An annex's normative status (as opposed to informative) shall be made clear by the way in which it is referred to in the text and under the heading of the annex.
Informative annexes give additional information intended to assist the understanding or use of the standard and shall not contain provisions to which it is necessary to conform in order to be able to claim compliance with the standard. Their presence is optional. An annex's informative status (as opposed to normative) shall be made clear by the way in which it is referred to in the text and under the heading of the annex.
Anchor_Toc4434611041_Toc4434611041A.2  Clause heading
Text
Annex B: Title
(normative)
B.1 Sample IDL
#pragma prefix "http_//example.com"
module stockquote_wsdl {
interface StockQuotePortType {
typedef sequence<float> ArrayOfFloat;
typedef struct TimePeriod {
wstring startTime;
wstring endTime;
};
ArrayOfFloat GetTradePrices(
in wstring tickerSymbol,
in TimePeriod timePeriod,
out float frequency);
};
};
B.2 Sample Code
<?xml version="1.0"?>
<definitions name="StockQuote"
targetNamespace="http://example.com/stockquote.wsdl"
xmlns:tns="http://example.com/stockquote.wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsd1="http://example.com/stockquote/schema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<schema targetNamespace="http://example.com/stockquote/schema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="TimePeriod">
<all>
<element name="startTime" type="xsd:string"/>
<element name="endTime" type="xsd:string"/>
</all>
</complexType>
<complexType name="ArrayOfFloat">
<complexContent>
<restriction base="soapenc:Array"> The base template for the order service response can be found here.

 

The actual response is maintained at https://bitbucket.org/account/user/cogmedsys/projects/ORR.