Issue 18293: Applicable key types not clearly specified (dds-xtypes-rtf) Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com) Nature: Clarification Severity: Minor Summary: In section 7.2.2.3.5.6 it is stated that every member of a struct can act as key. If that is indeed the case, then keys could be set on attributes of type sequence or union for which the resulting behaviour is not clearly specified. (For example, how to compare a key from a sequence of length 1 to a key of a sequence of length 2? How to compare unions that have the same discriminator but different branch values? How to compare unions that have different discriminator values that map onto the same branch?) Either setting keys on sequence and union attributes should be prohibited, or the resulting behaviour should clearly be specified. Resolution: Revised Text: Actions taken: December 12, 2012: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 12 Dec 2012 07:02:11 -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.2.2.3.5.6 FormalNumber: ptc/2012-03-26 Version: 1.0 Doc_Year: 2012 Doc_Month: February Doc_Day: Day Page: 46 Title: Applicable key types not clearly specified Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Description: In section 7.2.2.3.5.6 it is stated that every member of a struct can act as key. If that is indeed the case, then keys could be set on attributes of type sequence or union for which the resulting behaviour is not clearly specified. (For example, how to compare a key from a sequence of length 1 to a key of a sequence of length 2? How to compare unions that have the same discriminator but different branch values? How to compare unions that have different discriminator values that map onto the same branch?) Either setting keys on sequence and union attributes should be prohibited, or the resulting behaviour should clearly be specified.