Hi Laurant/Mark To be honest I really don't have time to dig into the diagram interchange stuff for UML2 together with all the other stuff that we need to complete for UML2 diagram presentation and modelling. That will have to follow later. There is some doubt as to whether this format will survive anyway so maybe we save ourselves some effort.
For pgml vs .argo I would say to save in the pgml as this is diagram level data rather than project level. Bob On 5 August 2011 19:21, Laurent BRAUD <[email protected]> wrote: > Hi, > Bob you are true, if we do this, we need to do it first with PGML rather than > XMI. > > But, if some "standard" tag documentation exists (shortDescription, author, > date, ...), use the same and show them to user even if we store not in > "standard". > And When we will start UML DI, even if there is a long time, it will be > easier. > > However, I haven't find a such "standard" tag . > So which one can we add to have usefull tool. Of course, user can uses others. > > What I found: > a) http://www.omg.org/spec/UMLDI/1.0/PDF/ > > There is a class Diagram and a XSD for diagram > > In "8.5 Properties": Non-standard properties could be added but are not part > of any standardization. Properties provide an extension > mechanism for adding non-standardized elements to the diagram interchange > metamodel. > > > => If I have well understand, we can add all properties we want. But there > aren't standard. Could be a choice. > > > b)I try TopCased: > <diagrams xmi:id="_2PG_gK1HEeC3fKGlWAkmOg" position="0,0" size="100,100" > name="StateMachine" viewport="0,0"> > <eAnnotations xmi:id="_ssPV4L-BEeCUNbPIxj8eBQ" > source="http://www.topcased.org/documentation";> > <details xmi:id="_ssUOYL-BEeCUNbPIxj8eBQ" key="documentation" > value="HERE DIAGRAM COMMENT"/> > </eAnnotations> > <property xmi:id="_2PahgK1HEeC3fKGlWAkmOg" key="pageFormatName" > value="A4"/> > ... > => I don't see yet where "eAnnotations" is defined in UML-DI (in XSD). > > > Mark, you ask for paragraph (and I agree): If we find something (in norm), it > must be an XML element, not an attribute. So what I found isn't enought. I > keep your idea in my mind. > > I don't know if what you asked Bob is possible. > > Regards, > > ------------------------------------------------------ > http://argouml.tigris.org/ds/viewMessage.do?dsForumId=449&dsMessageId=2809762 > > To unsubscribe from this discussion, e-mail: > [[email protected]]. > ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=449&dsMessageId=2809768 To unsubscribe from this discussion, e-mail: [[email protected]].
