${taskforce.name} Avatar
  1. OMG Task Force

Diagram Definition FTF — All Issues

  • Key: DD
  • Issues Count: 21
Open Closed All
All Issues

Issues Descriptions

Simplify DI metamodel

  • Key: DD-1
  • Legacy Issue Number: 15902
  • Status: closed  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    The DI metamodel can be simplified by removing
    planes (diagrams can be nested) and leaving
    packaging out of scope (DiagramCollection, and
    the association between Diagram and Style).

  • Reported: DD 1.0b1 — Wed, 15 Dec 2010 05:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    The DI metamodel is simplified by merging planes and plane elements into diagrams and diagram elements, respectively, and removing labels and diagram collections
    Planes are removed. These were to support nested diagrams, but it was decided the additional layer of terminology wasn't necessary, especially when some communities simply call them "nested diagrams". In the revised text, diagrams can be nested. Top level diagrams are those diagrams that happen not to be nested. We discussed various possibilities for modeling this, and settled on treating everything as a nestable diagram element, including diagrams, which are taken as a kind of shape. This means diagrams can have model elements, for example, as in UML composite structure. Top level diagrams won't use bounds. Diagrams can be connected by edges, for diagrams of diagrams.
    Labels are removed. The only difference from shapes is they are rendered as strings, which would often be determined by the mapping to DG. Language-specific DI's can define these as kinds of shapes if needed.
    It was decided that packaging should be out of scope, because domain languages usually have their own packaging mechanisms, resulting in these changes:
    The existing association between Diagram and Style is removed, because it was only packaging styles, it didn't mean styles applied to the diagram, like the association between DiagramElement and Style, which Diagram now inherits.
    DiagramCollection is removed, and its packaging associations to Style.
    Packaging of styles is left in Diagram Graphics, because DG is not intended to extend a domain language that might have its own packaging mechanism.
    Updates to the Annexes for these changes will be addressed in separate issues.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Interchange extension

  • Key: DD-6
  • Legacy Issue Number: 16001
  • Status: closed  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    The last pagraph of the DiagramElement section says:

    Other properties of diagram elements that tools need to interchange
    but are not defined in the metamodel can be interchanged using the
    extensibility mechanism that is native to the used interchange
    format. For example, in an XMIbased interchange, extended data can be
    placed on diagram elements within <xmi:extension> tags.

    I'm not sure we should be mentioning interchange level extensions,
    especially without mentioning metamodel extensions, and domain-specific
    extensions like profiles. Can we remove this paragraph, or generalize
    it to include other kinds of extension mechanisms?

  • Reported: DD 1.0b1 — Mon, 31 Jan 2011 05:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    The specification should not suggest ways of interchanging non-standard information

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Diagram::resolution default

  • Key: DD-5
  • Legacy Issue Number: 15997
  • Status: closed  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    The default for Diagram::resolution should be shown in the metamodel figures.

  • Reported: DD 1.0b1 — Mon, 31 Jan 2011 05:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    It is shown in Figure 9.3 (Diagram).
    Revised Text:
    None

    Disposition: Closed, no change

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Bounds should be optional

  • Key: DD-4
  • Legacy Issue Number: 15996
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    For example, as in compartmented property strings

  • Reported: DD 1.0b1 — Mon, 31 Jan 2011 05:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    Agreed that Shape::bounds should be optional. This is addressed in the resolution to 15902.
    Revised Text:
    None

    Disposition: Duplicate

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Waypoints should be optional

  • Key: DD-3
  • Legacy Issue Number: 15995
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    Some tools might autoplace edge end points.

  • Reported: DD 1.0b1 — Mon, 31 Jan 2011 05:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    Agreed that Edge::waypoints should be optional. This is addressed in the resolution to 15902.
    Revised Text:
    None

    Disposition: Duplicate

  • Updated: Fri, 6 Mar 2015 20:58 GMT

The Diagram metaclass should be abstract

  • Key: DD-2
  • Legacy Issue Number: 15994
  • Status: closed  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    The other DI classes are abstract.

  • Reported: DD 1.0b1 — Mon, 31 Jan 2011 05:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    Agreed that it should be abstract. This is addressed in the resolution to 15902.
    Revised Text:
    None

    Disposition: Duplicate

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Update Annex A

  • Key: DD-11
  • Legacy Issue Number: 16372
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    Update Annex A (UML Diagram Definition Example) for the changes in FTF ballot 1 and complete the example.

  • Reported: DD 1.0b1 — Tue, 19 Jul 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    Add a small example defining a subset of the UML Class diagram with DD

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Merge DI diagrams

  • Key: DD-10
  • Legacy Issue Number: 16371
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    After the first FTF ballot, the DI diagrams are small enough to be merged into one

  • Reported: DD 1.0b1 — Tue, 19 Jul 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    The DI metamodel is indeed small enough after Ballot 1 that all concepts can fit in one diagram.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Cascade specification in DG isn't as specific as DI

  • Key: DD-9
  • Legacy Issue Number: 16252
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    Cascade specification in DG isn't as specific as DI. DG should align with DI (local overrides shared overrides inherited), so the mapping from DI to DG won't need to repeat the cascade algorithm. Multiple styles in DG can be ordered to resolve conflicts

  • Reported: DD 1.0b1 — Tue, 17 May 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    The algorithms only appear different because of a typographic error.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Rename DG::Canvas::style to packagedStyle

  • Key: DD-8
  • Legacy Issue Number: 16251
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    Rename DG::Canvas::style to packagedStyle (and fills and markers) to clarify it is not applied to the canvas, like the one inherited from GraphicalElement::localStyle.

  • Reported: DD 1.0b1 — Tue, 17 May 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    Rename all the composite associations on Canvas to have a “packaged” prefix

  • Updated: Fri, 6 Mar 2015 20:58 GMT

DG::GraphicalElement::local/sharedStyle should have unbounded upper multiplicity

  • Key: DD-7
  • Legacy Issue Number: 16250
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    DG::GraphicalElement::local/sharedStyle should have unbounded upper multiplicity, to enable DI and the mapping to DG to both introduce styles. The style properties from these two sources might overlap for properties with upper multiplicity greater than one. Use ordering to prioritize styles in case of conflict.

  • Reported: DD 1.0b1 — Tue, 17 May 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    Change the multiplicities as suggested above, and explain the use case.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Optional bounds

  • Key: DD-15
  • Legacy Issue Number: 16389
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    After 15996, bounds should not be required, for example, search on "with a given bounds". Explain that if DI does not specify bounds, then the mapping to DG does.

  • Reported: DD 1.0b1 — Fri, 22 Jul 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    The only text remaining after 15902 that implies the presence of bounds is examples were bounds is supposed to be specified.
    Revise the description of bounds to indicate it is optional.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Cascading called inheritance

  • Key: DD-14
  • Legacy Issue Number: 16388
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    The spec sometimes refers to style cascading incorrectly as inheritance. Inheritance applies to classes, cascading applies to instances. Search on "inherit" to find them.

  • Reported: DD 1.0b1 — Fri, 22 Jul 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    Revise as suggested

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Owning styles

  • Key: DD-13
  • Legacy Issue Number: 16387
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    After issue 15902, the spec should not refer to owning styles, for example, see DI, DiagramElement, fourth paragraph, next to last sentence, and DI, Style, second paragraph, first sentence.

  • Reported: DD 1.0b1 — Fri, 22 Jul 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    Revise as suggested

  • Updated: Fri, 6 Mar 2015 20:58 GMT

MOF Compliance

  • Key: DD-12
  • Legacy Issue Number: 16386
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    Update for compliance with MOF 2.4 (for example UML:Element instead of MOF:Element), and change text to not refer to MOF, just "metamodel extension".

  • Reported: DD 1.0b1 — Fri, 22 Jul 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    MOF 2.4 is not formalized yet. It is valid to leave the property typed by CMOF::Element as it is the super class of all metaclasses. We should add a package import from DI to CMOF to make the dependency explicit.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Spurious question marks

  • Key: DD-18
  • Legacy Issue Number: 16408
  • Status: closed  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Remove "?"s before attribute names

  • Reported: DD 1.0b1 — Sun, 31 Jul 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    The “•” (composition) symbols got replaced by “?” symbols by mistake during the editing process of the Beta 2 specification. The fix is to restore the “•” symbols

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Optional waypoints

  • Key: DD-17
  • Legacy Issue Number: 16392
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    After 15959, multiple waypoints should not be required, for example, see DI Edge, first paragraph, and in the attribute description.

  • Reported: DD 1.0b1 — Sun, 24 Jul 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    Revise and suggested.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Visibility markers not needed

  • Key: DD-19
  • Legacy Issue Number: 16409
  • Status: closed  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Would be easier to read the specification with the "+" visibilitiy markers in the figures and attribute/association sections.

  • Reported: DD 1.0b1 — Sun, 31 Jul 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    We agree with the proposal to remove the visibility symbol as it is not relevant for metamodels

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Diagram description

  • Key: DD-21
  • Legacy Issue Number: 16485
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    Some of the clause 9.3.1 description is redundant with 8.1.3, and it does not make sense after changes from ballot 1.

  • Reported: DD 1.0b1 — Thu, 4 Aug 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    Remove the redundant paragraph as suggested

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Collections => sets

  • Key: DD-20
  • Legacy Issue Number: 16410
  • Status: closed  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Collections should be called sets, except when they are non-unique

  • Reported: DD 1.0b1 — Sun, 31 Jul 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    The word collection is valid as it is a generic way of describing sets, lists, sequences...etc. All metamodel properties are already annotated with the specific kinds of collections.
    Disposition: Closed, No Change

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Annex B

  • Key: DD-16
  • Legacy Issue Number: 16390
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    Update or remove Annex B (DG to SBV Mapping).

  • Reported: DD 1.0b1 — Fri, 22 Jul 2011 04:00 GMT
  • Disposition: Resolved — DD 1.0
  • Disposition Summary:

    Remove the annex until we have content for it.

  • Updated: Fri, 6 Mar 2015 20:58 GMT