Issue 10741: There is a lot of redundancy in the XML file. (data-distribution-rtf)
Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com)
Nature: Revision
Severity: 
Summary: Problem:

Inheritance is redundantly modeled in both IDL and XML. What to do when there is inheritance according to IDL but not the XML or vice-versa? Also, it is not clear in case of multiple level inheritance (C extends B extends A) which topic should act as the main topic: for class C in this example, is the main topic the one corressponding to the highest parent (A), or the topic corresponding to the closest parent (B)?
Finally, also the place topic description is very redundant: for each attribute located in the same place topic, the placetopic definition needs to be repeated.

Solution:

Our proposal is to not mention the extension topics in the IDL: just use normal class mapping and deduce from the IDL that two classes have an inheritance relationship.
Furthermore we propose to define the topic definition (with  its keydescription outside the scope of the class mapping: each attribute can then just refer to a known topic definition without repeating it.

TBD.

Resolution: 
Revised Text: 
Actions taken:
February 14, 2007: received issue
Discussion: 

End of Annotations:=====
s is issue # 10741	From: "Erik Hendriks" <Erik.Hendriks@prismtech.com>


There is a lot of redundancy in the XML file.

Problem:

Inheritance is redundantly modeled in both IDL and XML. What to do when there is inheritance according to IDL but not the XML or vice-versa? Also, it is not clear in case of multiple level inheritance (C extends B extends A) which topic should act as the main topic: for class C in this example, is the main topic the one corressponding to the highest parent (A), or the topic corresponding to the closest parent (B)?
Finally, also the place topic description is very redundant: for each attribute located in the same place topic, the placetopic definition needs to be repeated.

Solution:

Our proposal is to not mention the extension topics in the IDL: just use normal class mapping and deduce from the IDL that two classes have an inheritance relationship.
Furthermore we propose to define the topic definition (with  its keydescription outside the scope of the class mapping: each attribute can then just refer to a known topic definition without repeating it.

TBD.