[I still haven't seen the original message -- either my personal copy or the one to the dev list -- strange!]
The UML 2.x structure isn't really very different from UML 1.4 where Model and Subsystem are subtypes of Package also. Relaxing the requirement on the root element so that it can be a Package instead of a Model sounds fine since it will allow people to model pieces of a model independently. Breaking the 1:1 correspondance between an ArgoUML project, a root element, and an XMI serialization is something I'm less sure about. I think we should investigate what other tools allow before heading down this path. The mental model that I had in my head was that we would keep the 1:1 correspondance, but allow multiple ArgoUML projects to be connected together (and allow multiple projects to be open at a time). I think normally users will have the submodels and profiles set to be readonly (so they don't modify them inadvertently), but there may also be times when it is useful to work on multiple linked models simultaneously. All of this is largely orthogonal to the UML 2.x work since the same capabilities exist in UML 1.4. I expect that the Profile project will, of necessity, be dealing with many of these linking issues (but I haven't had time to keep up with what's going on there). Coordinating with them and making sure that you don't do anything which makes their work harder would be good, but I wouldn't let it slow down your work on UML2. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
