Issue 18307: Multiplicity mismatch between TypeName and TypeObject (dds-xtypes-rtf) Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com) Nature: Clarification Severity: Minor Summary: The builtin topics have 2 ways to identify the type to which they apply: a string called type_name and a TypeObject alled type. The string can only relate to 1 type, while the TypeObject could refer to more than 1 type. If the type_name is not uniquely identifying a type, then what is the use of having a type_name in the builtin topics for Reader and Writer? The topic_name already refers to a DCPSTopic sample that has a similar type_name. Furthermore, in the spec it is assumed that Readers/Writers just make the TypeObject refer to just 1 type, while the Topic could make it refer to more than one. This is not orthogonal, so wouldn't it be better to make a TypeObject refer to 1 type and give the DCPSTopic a sequence of TypeObjects instead? Resolution: Revised Text: Actions taken: December 12, 2012: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 12 Dec 2012 08:49:36 -0500 To: Subject: Issue/Bug Report X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== ******************************************************************************* Name: Erik Hendriks Employer: PrismTech mailFrom: erik.hendriks@prismtech,com Terms_Agreement: I agree Specification: Extensible and Dynamic Topic Types for DDS Section: 7.6.2.2 FormalNumber: ptc/2012-03-26 Version: 1.0 Doc_Year: 2012 Doc_Month: February Doc_Day: Day Page: 152 Title: Multiplicity mismatch between TypeName and TypeObject Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Description: The builtin topics have 2 ways to identify the type to which they apply: a string called type_name and a TypeObject alled type. The string can only relate to 1 type, while the TypeObject could refer to more than 1 type. If the type_name is not uniquely identifying a type, then what is the use of having a type_name in the builtin topics for Reader and Writer? The topic_name already refers to a DCPSTopic sample that has a similar type_name. Furthermore, in the spec it is assumed that Readers/Writers just make the TypeObject refer to just 1 type, while the Topic could make it refer to more than one. This is not orthogonal, so wouldn't it be better to make a TypeObject refer to 1 type and give the DCPSTopic a sequence of TypeObjects instead?