Linus suggested:

> Make and maintain a Diagram Interchange model for MOF 1.4 (or 
> as close to the real thing as possible). Load it into the 
> current version of MDR, the one we have installed. XMI and 
> load and save are generated from MDR with old versions.
> 
> This would solve the file compatibility and saving and 
> loading problems but we still haven't made the transition to 
> UML 2.0 and we're still non-standard.

I don't understand how this is any different from wedging PGML into XMI or
any other ArgoUML proprietary approach.  Swapping one proprietary approach
for another has no advantage that I can see.  It causes us to waste effort
on an evolutionary dead end throw away piece of code,  It doesn't improve
interchange with other tools.  It replaces a set of known problems with a
new set of unknown problems.

Our current proprietary approach, for all of its problems, is at least a
known quantity.  The only way I'd support replacing it with a different
proprietary approach of our own crafting would be if it was clear that it
was going to be at least two years before we could get to a standard UML 2.x
Diagram Interchange.

We've made due with PGML for 5+ years.  Why the sudden rush to replace it
with something that will have a lifetime measured in months?

Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to