Legacy Issue Number: 9663
Source: Adaptive ( Pete Rivett)
4.8.l7, 184.108.40.206: the syntax proposed for stringifying structured datatypes is ambiguous and not usable. It's ambiguous since there is no way to tell when the list of values for one multivalued property ends and another starts (the examples all have single-valued properties). If we have a DataType TwoShapes with properties s1: Point[2..*] and s2: Point[2..*] then with the proposed serialization a value such as (1,2,3,4,5,6,7,8,9,10,11,12) is not separable into s1 and s2 values.
Furthermore it ignores the names of the properties. And has no value for EMOF as claimed: a more natural representation of a structured DataType would be as a class in EMOF. Therefore there should at least be the option to serialize the values using a class-like approach. In fact section 4.14 does state that "MOF complex data types are treated as MOF classes with each field treated as a MOF attribute with a primitive type mapped to XML schema." So for the Point example this would be:
<point1 x="0" y="0"/>
<point1 x="1" y="5"/>
and for the Area example would be:
<point1 x="0" y="5"/>
<point1 x="4" y="0"/>
Reported: XMI 2.1 — Sat, 29 Apr 2006 04:00 GMT
Disposition: Resolved — XMI 2.4
Resolved by the resolution to issue 8884.
(see resolution to issue 8884)
Disposition: Closed Duplicate to issue 8884
Updated: Fri, 6 Mar 2015 20:59 GMT