OK, and I'll assume that the UML2 team decided that it didn't make sense to expand the scope of UML2, because this seems to be fully enclosed WRT dependencies.
What I'd like to suggest is that the language of the proposal or resulting project page be sharpened up to say what you're saying here in direct language, e.g.
_Introduction_
The proposed project provides implementations of "standard" UML profiles and a repository in/from which to discover/install them.
:D
I'd also want to know a bit more about whether this is intended to be a hub for active development and outside contributor involvement or if it is instead a kind of clearing house for already created implementations, almost like Orbit or something. Either way is ok I guess, I just think that if it is the latter we might be a little more clear about the process and on-going maintenance so that consumers can rely on the profiles being created. Usually a project like this has a center of gravity, and it seems vague here, but perhaps that is unavoidable given the nature of the scope.
On 2012-05-14, at 10:11 AM, Kenn Hussey wrote: The scope of the MDT UML2 project is not designed to include profile implementations; rather, it is about (just) the UML metamodel. The proposed project is about providing implementations of "standard" UML profiles and a repository in/from which to discover/install them.
Kenn On Mon, May 14, 2012 at 1:07 PM, Miles Parker <miles.parker@xxxxxxxxxxx> wrote:
Is there some reason that this can't be managed under the existing UML2 project, esp. given that this seems to be a matter of collecting a repository rather than active development of functionality? To me the scope and intro seemed vague about what exactly the project's goals and provided technologies are, and as a naive Modeling project consumer, I'm left wondering what the point is. That is, what if anything is actually being engineered here?
______________________________ Miles T. Parker Senior Engineer and Product Manager, Tasktop
Committer, Eclipse Mylyn and Virgo Project Lead, Model Focussing Tools and AMP
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
_______________________________________________ modeling-pmc mailing list modeling-pmc@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/modeling-pmc
______________________________ Miles T. Parker Senior Engineer and Product Manager, Tasktop Committer, Eclipse Mylyn and Virgo Project Lead, Model Focussing Tools and AMP
|