Issues for Mailing list of the DDS for Light-Weight CCM 1.0 (DDS4CCM) CORBA Component Model (CCM) joint RTF
To comment on any of these issues, send email to dds4ccm2ccm-rtf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.
List of issues (green=resolved, yellow=pending Board vote, red=unresolved)
Issue 15964: Move generic interaction support (GIS) to the CCM specification
Issue 16092: The model file ptc/11-02-11 is not valid UML – it has eclipse namespace and extraneous elements
Issue 15964: Move generic interaction support (GIS) to the CCM specification (dds4ccm2ccm-rtf)
Click here for this issue's archive.
Source: THALES (Ms. Virginie Watine, virginie.watine(at)thalesgroup.com)
Nature: Uncategorized Issue
Severity: Minor
Summary:
The current DDS4CCM specification is made of two parts
1) Description of a generic interaction support (GIS) allowing to define extended ports and connectors
2) Use of this GIS to define extended ports and connectors dedicated to DDS.
The first part (GIS) has been designed in purpose of supporting all future CCM extensions and would be better placed in the CCM specification.
Proposal is therefore to move it from DDS4CCM to CCM.
––––-
Severity I guess is minor as it does not affect at all the ability to implement. Actually it could have been treated as éditorial apat the point of revisiting compliance...
Resolution: Move the GIS section as a sub-section in CORBA – Part 3 / Component Model
Rationale for the move: The GIS is not at all specific to DDS-related extended ports and connectors and will be used for other CCM extensions.
Rationale for keeping the addition in a single CCM sub-section: It is easier to understand the purpose of the extension and to set it as optional.
Revised Text: Revised Text in DDS4CCM specification:
Notes
1. All modifications are indicated with page and line numbers. Those
numbers are related to the new version of the specification with change
bars.
2. All modifications in the above-mentioned document are related to this
single issue. There is therefore no issue tags.
Document ptc/2011-01-12 10
Modifications are as follows:
Page 1 / line 2 and after
Change the whole section 1 with the following contents
1 Scope
This specification defines how CCM1 components may interact using DDS and
how related DDS entities may be configured using CCM configuration
mechanisms.
For that purpose, it uses the Generic Interaction Support recently added to CCM
to allow extending CCM with new interactions. This support is made of two
constructs: i) a new port type (namely extended port) to capture as a whole a set
of basic interactions that need to be kept consistent (a trivial example is e.g., how
to provide message passing with flow control) and ii) abstractions in between
components (namely connectors) to support new interaction mechanisms.
This specification thus defines DDS-dedicated extended ports and connectors. It
is made of two parts.
• Section 7 defines extended ports and connectors for DDS-DCPS
• Section 8 defines extended ports and connectors for DDS-DLRL
This specification assumes an a-priori knowledge of the Generic Interaction
Support. If it not the case, refer to the CCM documentation.
1 In this document, CCM implicitly refers also to LightWeight CCM.
Page 1 / line 35 down to page 2 / line 4
Remove the list item # 1, including all its sub-items.
Page 2 / line 5
Remove “, in addition,” at the end of the line.
Document ptc/2011-01-12 11
Page 2 / line 12
Replace
V3.1
with
V3.2
Page 2 / line 13
Replace
formal/08-01-05; formal/08-01-07; formal/08-01-06
with
ptc/11-02-03, ptc/11-02-05, ptc/11-01-16
Page 2 / line 14
Remove the list item
Page 2 / lines 15-17
Replace
v4.0 (formal/06-04-01); CORBA Component Model, v4.0 XML (formal/07-
02-02); CORBA Component Model, v4.0 IDL (formal/07-02-01);
with
refers to part 3 of the above-mentioned specification.
Page 2 / line 18-20
Remove the two list items
Page 3 / line 14 and after
Change the whole section 6.1 with the following contents:
Document ptc/2011-01-12 12
6.1 Changes to Adopted OMG Specifications
None in this document.
Page 4 / line 1 and after
Remove the whole chapter 7. All the subsequent chapters will be renumbered
according to this deletion.
Page 27 / line 8
Change the title of the chapter from:
DDS-DCPS Application
to
DDS-DCPS Extended Ports and Connectors
Page 27 / line 10
Replace
described in the previous section
with
of CCM
Page 27 / line 11
Insert after “knowledge of”
this CCM extension and of
Page 49 / line 1
Change the title of the chapter from:
DDS-DLRL Application
Document ptc/2011-01-12 13
to
DDS-DLRL Extended Ports and Connectors
Page 49 / line 3
Replace
described in the previous section
with
of CCM
Page 49 / line 5
Insert after “knowledge of”
this CCM extension and of
Revised text in the CORBA 3.2 Part 3 specification
Notes:
1. As there is no line number in this specification, modifications are indicated
only with a page number. This page number relates to the commented
version.
2. The main change consists in inserting a new Section 7 taken as a whole
from DDS4CCM specification. To improve readability, and let the
reviewers see the small changes performed on the inserted text, this initial
change has been made without tracking modifications. In return, the
inserted text is embedded between two issue tags (begin / end).
Page 1
Add to Section 1 (Scope) as second bullet
• Generic interaction support allowing to define new interactions in CCM
(see Clause 7, ’Generic Interaction Support’).
Document ptc/2011-01-12 14
Page 3
Add to Section 2 (Conformance) as last bullet:
9. A CCM framework claiming conformance with the “Generic Interaction
Support” part of this specification shall support extended ports and
connectors:
• Extensions of IDL3 to support porttype, mirrorport and port
declarations
• Extension of IDL3 to support parameterized interfaces (template)
• Extension of D&C PSM for CCM to describe extended ports
• Extension of IDL3 to support connector declaration
• Extension of D&C PSM for CCM to deploy and configure connector
fragments
Page 3:
In Section 3.1 (Normative References)
[D+C] update reference link to “http://www.omg.org/cgi-bin/doc?formal/06-
04-02”
Page 4
In same section, add reference to QoS4CCM (after reference to PSS)
[QOS4CCM] Quality of Service for CORBA Components
(formal/2008-10-02)
http://www.omg.org/spec/QOSCCM/1.1
Page 5
In Section 4.1 (Terms Defined in this International Standard) add the following
entry (after definition of Component)
Connector
Document ptc/2011-01-12 15
Interaction entity between components. A connector is seen at design
level as a connection between components and is composed of several
fragments (artifacts) at execution level, to realize the interaction.
Page 7
In same section, add the following entry as first in the page
Extended Port
Consists of zero or more provided as well as zero or more required
interfaces, i.e. closely resembling the UML2 specification of a port.
In same section, add the following entry (after Facet)
Fragment
Artifact, part of the connector implementation. A fragment corresponds to
one executor that can be deployed onto an execution node, co-localized
with one component for which it supports the interaction provided by the
connector.
Page 57
1. Insert the whole Chapter 7 (Generic Interaction Support) from DDS4CCM
as Section 7 of this document. Subsequently original Section 7 and later
are renumbered to take this new section into account.
2. Then apply the following changes:
Page 57 / GIS line 1
Remove “proposed”
Page 74, Section 7.5
Change D&C reference to Chapter 15
Actions taken:
January 17, 2011: received issue
July 11, 2011: closed issue
Issue 16092: The model file ptc/11-02-11 is not valid UML – it has eclipse namespace and extraneous elements (dds4ccm2ccm-rtf)
Click here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Uncategorized Issue
Severity:
Summary: The model file ptc/11-02-11 is not valid UML – it has eclipse namespace and extraneous elements
Resolution:
Revised Text:
Actions taken:
March 21, 2011: received issue