Hi Sébastien,
thanks for the feedback!
About Papyrus-IM, would it be possible:
- to include the Package Diagram Editor of Papyrus-UML?
Yes, that seems to be useful. I created a bug report for that [1].
- why not renaming the UML Class Diagram into something more specific to Information Modeling (i.e., Conceptual Modeling) vocabulary, at least without the trem UML inside? => e.g., “Information Structural Diagram” ?
I agree that this is something to discuss -- we had internal discussions on that a couple of months ago but back then decided against another term. However, especially with respect to composability and future extensions of P-IM, we probably should use a more specific name. Information structure diagram sounds not bad. I'm wondering though if it would fit together with "Package Diagram" (as mentioned above). I opened a bug on this topic as well [2] and invite everyone to give their opinion on a new name for this diagram type.
For collaborative modeling in the welcome page, I would suggest to point to the tuto denoting how to install and use the feature into Papyrus instead of linking to Egit directly.
And integrating generic table support may be useful also.
In the initial development, we decided against integrating it to keep things as clean and simple as possible for our target audience. I think it may be better to provide a dedicated table view for information modeling instead of integrating generic table support. What do you think?
Thanks again for your feedback and best wishes,
Philip