Issue 17552: opposite properties need to be serialized (canonical-xmi-ftf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: In XMI generally it’s fine and valid to serialize either end of a pair of opposite properties: it’s not required to serialize both. However for Canonical XMI this must be predictable and consistent so I guess both would need to be serialized. This needs to be made clear in the spec Resolution: Revised Text: Add a new numbered rule to the end of section B2: For pairs of opposite properties that satisfy the rules for being serialized, values must be serialized for each (XMI generally would allow one of the pair to be omitted) . Actions taken: August 16, 2012: received issue December 23, 2013: closed issue Discussion: End of Annotations:===== ubject: Issue on Canonical XMI Date: Thu, 16 Aug 2012 07:37:41 -0700 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue on Canonical XMI Thread-Index: Ac17vLCgyv7LMr8gTAeSna2dDep/Pw== From: "Pete Rivett" To: In XMI generally it.s fine and valid to serialize either end of a pair of opposite properties: it.s not required to serialize both. However for Canonical XMI this must be predictable and consistent so I guess both would need to be serialized. This needs to be made clear in the spec. -- Pete Rivett (pete.rivett@adaptive.com) CTO, Adaptive Inc 65 Enterprise, Aliso Viejo, CA 92656 cell: +1 949 338 3794 Follow me on Twitter @rivettp or http://twitter.com/rivettp