DDS11 — (R#145,146) Inconsistent description of Topic module in PIM

Several members in the Topic module are described as attributes in the UML diagram in 2.1.2.3 but as operations in the following tables and in the IDL PSM. These include:
· TopicDescription::type_name
· TopicDescription::name
· ContentFilteredTopic::filter_expression
· ContentFilteredTopic::expression_parameters
· MultiTopic::subscription_expression
· MultiTopic::expression_parameters
Also, the topic name and type name members are needlessly repeated in the tables of all of the TopicDescription subclasses. They are non-abstract; they need only appear in the TopicDescription table.

Proposed Resolution:
The read-only attributes should appear as such in the PIM tables. "Attributes" that can be changed return ReturnCode_t from the corresponding "set" methods; for clarity, they should consistently appear as operations in both the tables and the UML diagram. The duplicate descriptions of the topic name and type name attributes should be removed.
The IDL PSM should continue to express all of the members as methods to preserve the consistency of the naming conventions used in all programming languages that may be generated from the IDL.

Proposed Revised Text:

In figure 2-7, replace the ContentFilteredTopic attribute expression_parameters with two operations: get_expression_parameters and set_expression_parameters. Replace the MultiTopic attribute expression_parameters with two operations: get_expression_parameters and set_expression_parameters.

Revise the TopicDescription Class table in 2.1.2.3.1 as follows:
TopicDescription
attributes
readonly name string
readonly type_name string
operations
get_participant DomainParticipant

Rewrite section 2.1.2.3.1.2 as follows:
2.1.2.3.1.2 type_name
The type name used to create the TopicDescription.

Rewrite section 2.1.2.3.1.3 as follows:
2.1.2.3.1.3 name
The name used to create the TopicDescription.
Remove the get_type_name and get_name operations from the Topic Class table in 2.1.2.3.2.
Remove the get_type_name, get_name, and get_filter_expression operations from the ContentFilteredTopic Class table in 2.1.2.3.3. Add the following attributes to that table:
attributes
readonly filter_expression string

Rewrite section 2.1.2.3.3.2 as follows:
2.1.2.3.3.2 filter_expression
The filter_expression associated with the ContentFilteredTopic. That is, the expression specified when the ContentFilteredTopic was created.

Remove the get_type_name, get_name, and get_subscription_expression operations from the MultiTopic Class table in 2.1.2.3.4. Add the following attributes to that table:
attributes
readonly subscription_expression string

Rewrite section 2.1.2.3.3.2 as follows:
2.1.2.3.4.1 get_subscription_expression
The subscription_expression associated with the MultiTopic. That is, the expression specified when the MultiTopic was created.

No Data Available