Issue 16331: XMI composite opposite constraint overly restrictive (mof2xmi-rtf) Source: Oracle (Mr. Dave Hawkins, dave.hawkins(at)oracle.com) Nature: Clarification Severity: Minor Summary: Section 9.4.1 of the specification contains the following constraint: For Properties with isComposite=true, the opposite property is not serialized. While this is fine when objects are nested it doesn't make sense when an object is serialised as a root object. For example, stereotype extensions are mapped to composite associations. Stereotypes instances are serialised as root objects because the composite property is not owned by the extended class. To attach them to their extended object the 'base' property is serialised, but this is the opposite of a property with isComposite=true. Resolution: Revised Text: Actions taken: June 13, 2011: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 13 Jun 2011 11:34:11 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Dave Hawkins Employer: Oracle mailFrom: dave.hawkins@oracle.com Terms_Agreement: I agree Specification: XMI Section: 9.4.1 FormalNumber: ptc/2010-12-06 Version: 2.4 Doc_Year: 2010 Doc_Month: December Doc_Day: Day Page: 69 Title: XMI composite opposite constraint overly restrictive Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Description: Section 9.4.1 of the specification contains the following constraint: For Properties with isComposite=true, the opposite property is not serialized. While this is fine when objects are nested it doesn't make sense when an object is serialised as a root object. For example, stereotype extensions are mapped to composite associations. Stereotypes instances are serialised as root objects because the composite property is not owned by the extended class. To attach them to their extended object the 'base' property is serialised, but this is the opposite of a property with isComposite=true.