Issue 18379: XML Schema for Associations (mof2xmi-rtf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: Rule 7 in section 8.2.1 deals with serialization of association instances (links). At the moment it uses <xsd:choice minOccurs=”0” maxOccurs=”unbounded”> for the ends. Though MOF is constrained to binary Associations, this would allow no, one, or even many ends to be serialized – which would never be valid. It would be a lot cleaner and more sensible to use <xsd:all> which requires exactly 2 ends. NB Rule 7 does not allow the use of XML attributes for the association ends, which would be allowed if the same reference were on an Object. I’m not convinced it would be useful (and it would not be Canonical XMI) but we should confirm that. Resolution: Revised Text: Actions taken: January 18, 2013: received issue Discussion: End of Annotations:===== ubject: Issue on XMI 2.4.1 Date: Fri, 18 Jan 2013 12:13:36 -0800 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue on XMI 2.4.1 Thread-Index: Ac31uEY9QOvMylYfTyqfRfvkWsfVxg== From: "Pete Rivett" To: Cc: X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== XML Schema for Associations Rule 7 in section 8.2.1 deals with serialization of association instances (links). At the moment it uses for the ends. Though MOF is constrained to binary Associations, this would allow no, one, or even many ends to be serialized . which would never be valid. It would be a lot cleaner and more sensible to use which requires exactly 2 ends. NB Rule 7 does not allow the use of XML attributes for the association ends, which would be allowed if the same reference were on an Object. I.m not convinced it would be useful (and it would not be Canonical XMI) but we should confirm that. -- Pete Rivett (pete.rivett@adaptive.com) CTO, Adaptive Inc 9861 Irvine Center Drive Suite 200, Irvine, CA 92618 cell: +1 949 338 3794 Follow me on Twitter @rivettp or http://twitter.com/rivettp