Hi,
I think that the discussion regarding UML-RT vs. UML and whether we shall talk about only *one* language (UML-RT) in Papyrus-RT or not is multi-faceted.
Yes, for a basic configuration of Papyrus-RT were we only want to user UML-RT, very much as it once was in ObjecTime, we should skip the label "UML" as you say. But keep in mind that we also want to have configurations of "Papyrus-RT" (I put it in quotes to indicate the slight distinction) which is used in combination with UML, or even possibly any user-defined DSML on top of UML-RT and/or UML. I know that Charles brings up the "composability" aspect of Papyrus (as a product line) and that you shall be able to make lots of different configurations of Papyrus (inclduing Papyrus-RT). I can just refer to my own experience for the last decade working with systems modeling with UML-RT (the structure modeling part) and "plain" UML (use case modeling, activity modeling, and so on).
What I think is important is that when doing such a "composability" of different languages (UML-RT; UML, DSMLs) that the names of menus, tabs in properties view, of course needs to use the same labels, both when being used "standalone", or when being used in a "composability" scenario, so that users that use for example UML-RT both in a plain UML-RT configuration of Papyrus-RT finds its way around also in a configuration of "Papyus-RT" that also brings in other languages (UML, SysML, other DSMLs).
This aspect makes things a little bit more tricky to get right. I hope that the new architecture and view point framework that we get on the Oxygen track in Papyrus will help us achieve this. Probably we also need to iterate an learn a bit more about what can be done and what cannot with it...
Yes, in ObjecTime all this was very straight forward and could be kept crisp and clean. But on the other hand ObjecTime truly only had ROOM and was very limited when you wanted to go outside of ROOM. This with using ROOM/UML-RT in the context of system modeling would never have happened in ObjecTime, but it did happen with RoseRT since we then also got UML, e.g. use case modeling and activity modeling.
The trick here is to both get back to simple and "plain" user experience of ObjecTime, but at the same time get the benefit of what you had in RoseRT and RSARTE with also being able to bring the rest of UML if and when you want, by having a slightly different configuration of "Papyrus-RT".
/Peter Cigéhn