Issue 18144: Key order should be defined using the @Key annotation (dds-xtypes-rtf)
Source: PrismTech (Dr. Angelo Corsaro, PhD., angelo.corsaro(at)prismtech.com)
Nature: Enhancement
Severity: Significant
Summary: The X-Types specification had left under-defined mechanism to be used for specifying the order of key attributes.


The solution adopted by the FTF was to simply use the member ID to define such an order, but this is not optimal.


We strongly suggest to define @Key annotation as follows:



@Annotation
local interface Key {
        attribute unsigned long value;
        attribute boolean value default true;
};


Where the value attribute is used to define a total order among the key attributes. 

Resolution: 
Revised Text: 
Actions taken:
October 8, 2012: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 08 Oct 2012 08:57:35 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Angelo Corsaro
Employer:        PrismTech
mailFrom:        angelo.corsaro@prismtech.com
Terms_Agreement: I agree
Specification:   Extensible and Dynamic Topic Types for DDS
Section:         7.3.1.3.3
FormalNumber:    ptc/2012-03-26
Version:         1.0
Doc_Year:        2012
Doc_Month:       March
Doc_Day:         26
Page:            70
Title:           Key order should be defined using the @Key annotation 
Nature:          Enhancement
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue


Description:

From: webmaster@omg.org
Date: 08 Oct 2012 08:57:35 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Angelo Corsaro
Employer:        PrismTech
mailFrom:        angelo.corsaro@prismtech.com
Terms_Agreement: I agree
Specification:   Extensible and Dynamic Topic Types for DDS
Section:         7.3.1.3.3
FormalNumber:    ptc/2012-03-26
Version:         1.0
Doc_Year:        2012
Doc_Month:       March
Doc_Day:         26
Page:            70
Title:           Key order should be defined using the @Key annotation 
Nature:          Enhancement
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue


Description:


The X-Types specification had left under-defined mechanism to be used for specifying the order of key attributes.


The solution adopted by the FTF was to simply use the member ID to define such an order, but this is not optimal.


We strongly suggest to define @Key annotation as follows:



@Annotation
local interface Key {
        attribute unsigned long value;
        attribute boolean value default true;
};


Where the value attribute is used to define a total order among the key attributes.