-----Original Message----- From: Tom Morris [mailto:[EMAIL PROTECTED] Sent: Thursday, August 10, 2006 2:30 AM To: '[email protected]' Subject: RE: [argouml-dev] Re: Save entire project in XMI
I've only done a cursory review since Tigris got taken down for an upgrade while I was reviewing the changes (I was using Eclipse's CVS synchronization view), but here are my thoughts so far: 1. Since we're (hopefully) looking at a UML 2.x upgrade in the not-too-distant future, I'd have thought we'd be minimizing any changes to persistance structure. 2. I think merging .argo and .todo info into the main project .xmi file is a good idea. Anything in an xmi.extension element is likely to be inaccessible to anyone else though, so things that we think are useful to other tools should be put somewhere accessible like a comment or a tagged value (author's name, date created, etc). 3. I thought the UML 2.x structure was to have the diagrams in their own XMI file(s) separate from the model. If I'm remembering this correctly, merging everything into a single file represents a detour from the long term direction that we'll have to undo later. 4. From an implementation point of view, I saw places where the Model API was changed in fashion which is not upwardly compatible which is something we definitely need to rectify. 5. Also on the implementation side, we need to try and merge this side channel into the output stream as high up the architecture as possible. Currently it's being done at the byte level which is way too low. I suspect the current implementation isn't multi-byte character set safe. The best would be to inject the private content at the MDR level if it supports it (I'm not sure it does). Alternatively we should try to handle things at the Sax level. To answer some of Bob's questions: > So what do we do now with .zargo or .zip? Do we need both? > They both just contain a single .xmi file now. I think we want to allow both extensions. > For what tool is it that we provide a .zip save? Is it > AndroMDA? If so could we request of them that they recognise .zargo? MagicDraw reads and writes .xml.zip files. AndroMDA has no problem reading .zargo files. I think we want to be as permissive as possible about the file types that we read and write. There's enough incompatibility between tools without ripping out support that is already implemented. > With the OMG creeping towards to interchange of XMI have they > come up with any recommended filename extensions for xmi or > zipped xmi? Not that I've seen. I suspect they consider it an external issue. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
