8 Dec
2007
8 Dec
'07
1:46 p.m.
;)
I got the same with XMI spec... :)
Stef
On 8 déc. 07, at 11:17, Adrian Kuhn wrote:
I attended a tutorial on that at WCRE in Pittsburgh,
and after my
experience with MOF/EMOF I will never again adopt an OMG standard,
they are usually incomplete and obfuscated snapshots of Rational's
current implementation mess... we better stick to properly
documenting our implementation mess :)
:)
But we have better data to store :)
It was fun to see that they want to represent control flow constructs.
stef
<model xmi:id="id.156"
xmi:type="conceptual:ConceptualModel"
name="Customer Information">
<conceptualElement xmi:id="id.157"
xmi:type="conceptual:TermUnit" name="AccountBalance"
implementation="id.15 id.12 id.17 id.153"/>
<conceptualElement xmi:id="id.158"
xmi:type="conceptual:TermUnit" name="MaxAdjustedBalance"
implementation="id.106"/>
<conceptualElement xmi:id="id.159"
xmi:type="conceptual:TermUnit" name="AllowanceAmount"
implementation="id.71"/>
<conceptualElement xmi:id="id.160"
xmi:type="conceptual:TermUnit" name="Allowance"
implementation="id.20"/>
<conceptualElement xmi:id="id.161"
xmi:type="conceptual:TermUnit" name="AdjustedBalance"
implementation="id.18"/>
<conceptualElement xmi:id="id.162"
xmi:type="conceptual:TermUnit" name="AccountBalanceField"
implementation="id.153"/>
Can we order new harddisks to store those models? ^^