Hi, The xmi file would contain just a set of "examples" of the type system, right?
And there would be nothing there that would indicate the type hierarchy, I think, although one might be able to heuristically guess at a possible hierarchy, if there were instances of types that were members of various levels of the hierarchy, for instance if there was a type foo with features foof1 (e.g. string) and foof2 (ref to type bar) superfoo with features just being foof1 (of same type as foof1 in foo) Then you might be able to conclude a guess about the hierarchy... You might mean, instead, to come up with some type system that would "fit" the types in the xmi, with no need to have those be the actual type system. Even that, it may be difficult, because an xmi instance doesn't describe the data type of its feature value, and the encoding of the feature value is ambiguous with respect to the type system, I think. For instance, a feature reference is encoded as an integer value. -Marshall On 5/12/2017 12:32 PM, Richard Eckart de Castilho wrote: > Hi all, > > do we have code somewhere that tries to reverse-engineer > a type system description given an XMI file? > > Cheers, > > -- Richard >
