Hi Tom, thanks a lot for your comments. I put my answers inline.
> > 1. Tagged values for UML2: [...] also we restrict TVs to strings (this > restriction also didn't exists for UML 1.4, btw.). > > This is unfinished work from the UML 1.3 to 1.4 transition many years > ago. The relevant bug is > http://argouml.tigris.org/issues/show_bug.cgi?id=4936 which includes a > patch, but it needs work. Some of the AndroMDA profiles would benefit > from support for Boolean, etc types, as I remember. My hope was to decouple the UML2 transition from issue 4936, but the more I think about it, the more I see the risk that we keep the "restricion to string" even for UML2. So maybe it's best to solve it before switching to UML2, or at the same time. > > Currently I think that comments are the > > only way to store documentation in the model and make this tab functional > > again. > > This would also imply that all the other ArgoUML specific tagged > values (@author, @since, @version, @deprecated, etc) are going to get > dropped. I haven't looked closely at the spec, but it seems like > there should be a way to have an ArgoUML profile with any needed > properties. It has disadvantages to introduce mandatory profiles to maintain that functionality (and the documentation tab I talked about before). I love profiles, but if there is a way to use plain UML, then I'd prefer that way. Maybe put these attributes in a UML comment associated with the model instance? I'll think about it, your suggestions are welcome. > here: http://www.omgwiki.org/model-interchange/doku.php (I'm in the mailing > list and have an actual internal compatibility matrix for the listed vendors, > if someone is interested.) > > Is there a reason not to put the matrix on the wiki? As far as the > OMG goes, I tried to get ArgoEclipse included over a year ago and did > models which conformed to their original experiment. Kenn Hussey > checked with the OMG who said it was restricted to members only. The matrix is most probably confidential as long as it is under discussion among the vendors (which it is), and until all vendors agree to publish it. That's my impression about the discussions on the mailing list. Shall we collaborate in any way to get ArgoEclipse/ArgoUML included? My plan was to first get something to work from their use cases and then contact them on their mailing list. Cheers, Thomas -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2606700 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
