as you might already know, Kenn and I have submitted a talk about "The
20 Modeling Things" to upcoming EclipseCon
( http://www.eclipsecon.org/2010/sessions/?page=sessions&i d=1315) and got
accepted. In this talk we want to give a high level overview of the most
essential services required for building integrated modeling tool
applications. These services could later be implemented in the recently
announced Sphinx project - with a part of them coming from the
Backbone/Core from Papyrus and the ECL layer from Artop.

Kenn and I had the idea to base this talk not only on our own thoughts
but on feedback from all members of Papyrus and Artop development team.
We already have identified an initial version of the 20 Modeling Things
including some comments detailing them a little bit (see below). We
would like to ask you to have a look at this list and comment on it.
Just let us know what you intuitively think. Tell us which of the
proposed services you find important, what their mandatory
features/properties should be, additional services that should be added,
services which you don't find important and should be removed from the
list (if any), or anything else.

In order to have enough time for consolidating your feedback an create
the presentation slides, it would be great if you could provide us your
feedback until Feb 28, 2010. While this message has also been sent out
to Papyrus and Artop mailing lists for reaching all of you, I think that
it would make sense to route all feedback over a single communication
channel. So please use only the MDT forum/newsgroup for posting your
response.

- execution of commands (possibly complex) in a thread safe way
- allowing undo (rollback)
- integration with the undo/redo mechanisms in eclipse

5. validation

- all things validation (rules, execution, scope, problems view, markers)
- support for this in a scalable way!

6. compare & merge

- differences between different version of artifacts
- graphical merge (diagram support)

7. scoping (viewpoints)

- models typically spread over multiple files of multiple types
- relation of projects to models, also "working sets"?
- references between projects
- supports models from different versions of a metamodel at same time
- "model" vs. resources, subsetting of these

21.Collaborative work :
- control mode command (EMF control command to split a model resource
into several resources = model fragments)
- export mode command (control mode with all dependencies to father
model embbeded into a cache to get an autonomous sub model that can be
sent by e-mail) and dual import mode command
- integrate existing model into current model (with diagrams) at a given
position in the model
- lock management
- role management (identify who did what + authorizations)
- CDO/Teneo

22. Customization : editors, property view, model explorer,...
The final idea is to give the possibility to end users to configure the
platform to support THEIR process.

23 : model simulation/animation - see links to Eclipse MXF proposal.
- debug the behavior of a model when defined.

21.Collaborative work :
- control mode command (EMF control command to split a model resource
into several resources = model fragments)
- export mode command (control mode with all dependencies to father
model embbeded into a cache to get an autonomous sub model that can be
sent by e-mail) and dual import mode command
- integrate existing model into current model (with diagrams) at a given
position in the model
- lock management
- role management (identify who did what + authorizations)
- CDO/Teneo

22. Customization : editors, property view, model explorer,...
The final idea is to give the possibility to end users to configure the
platform to support THEIR process.

21.Collaborative work :
- control mode command (EMF control command to split a model resource
into several resources = model fragments)
- export mode command (control mode with all dependencies to father
model embbeded into a cache to get an autonomous sub model that can be
sent by e-mail) and dual import mode command
- integrate existing model into current model (with diagrams) at a given
position in the model
- lock management
- role management (identify who did what + authorizations)
- CDO/Teneo

22. Customization : editors, property view, model explorer,...
The final idea is to give the possibility to end users to configure the
platform to support THEIR process.