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

Diagram Definition 1.2 RTF — All Issues

  • Key: DD12_
  • Issues Count: 6
Create Issue
Open Closed All
All Issues

Issues Summary

Key Issue Reported Fixed Disposition Status
DD12_-6 Consider possibility of adding Port concept to DI DD 1.0 open
DD12_-5 Constraints DD 1.0b1 open
DD12_-4 Why does A_style_canvas have no name? DD 1.1 open
DD12_-3 Small typo. DD 1.0 open
DD12_-2 Small typos. DD 1.0 open
DD12_-1 A_style_canvas Association is unnamed DD 1.1 open

Issues Descriptions

Consider possibility of adding Port concept to DI

  • Key: DD12_-6
  • Legacy Issue Number: 18680
  • Status: open  
  • Source: Fraunhofer FOKUS ( Mr. Max Bureck)
  • Summary:

    Hi, the concept of ports, attached to the outside bounds of an element allowing connections between elements is a widespread concept. Adding this concept would help generic layouting algorithms taking ports into account (such as KIELER) doing a much better job. Since DI defines abstract subclasses, meta models without ports can simply choose to not use the concept.
  • Reported: DD 1.0 — Mon, 22 Apr 2013 04:00 GMT
  • Updated: Tue, 8 Jan 2019 15:34 GMT

Constraints

  • Key: DD12_-5
  • Legacy Issue Number: 16492
  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    The spec currently has no constraint sections. Should we add them? For
    example, we might require unowned diagram elements to be diagrams
  • Reported: DD 1.0b1 — Mon, 31 Jan 2011 05:00 GMT
  • Updated: Tue, 8 Jan 2019 15:33 GMT

Why does A_style_canvas have no name?

  • Key: DD12_-4
  • Status: open  
  • Source: Model Driven Solutions ( Dr. Edward Willink)
  • Summary:

    All the Associations in DC/DG/DI have names except just one:

    <packagedElement xmi:type="uml:Association" xmi:id="A_style_canvas" memberEnd="Canvas-packagedStyle A_style_canvas-canvas">
    <ownedEnd xmi:type="uml:Property" xmi:id="A_style_canvas-canvas" name="canvas" type="Canvas" association="A_style_canvas"/>
    </packagedElement>

    Is this intended?
  • Reported: DD 1.1 — Thu, 14 Apr 2016 08:13 GMT
  • Updated: Tue, 8 Jan 2019 15:32 GMT

Small typo.

  • Key: DD12_-3
  • Legacy Issue Number: 19485
  • Status: open  
  • Source: yahoo.fr ( Lambert Clara)
  • Summary:

    There is a small typo in the DD specification document.
    On page 17 we can read:
    "namely the Diagram Graphics(DI) package (Clause 9) and the Diagram Interchange(DG) package"

    The acronyms in the parenthesis are reversed, it should be Diagram Graphics(DG) and Diagram Interchange(DI).
  • Reported: DD 1.0 — Mon, 23 Jun 2014 04:00 GMT
  • Updated: Tue, 8 Jan 2019 15:32 GMT

Small typos.

  • Key: DD12_-2
  • Legacy Issue Number: 19486
  • Status: open  
  • Source: yahoo.fr ( Lambert Clara)
  • Summary:

    There are some typos in the attributes description of Color data type, we can read:
    "Integer [1] - the red component of the color in the range (0..255)"
    for all three components, green and blue included.

    The description should reflect the correct color.
  • Reported: DD 1.0 — Mon, 23 Jun 2014 04:00 GMT
  • Updated: Tue, 8 Jan 2019 15:32 GMT

A_style_canvas Association is unnamed

  • Key: DD12_-1
  • Status: open  
  • Source: Model Driven Solutions ( Dr. Edward Willink)
  • Summary:

    The final Association in DG.xmi

    <packagedElement xmi:type="uml:Association" xmi:id="A_style_canvas" memberEnd="Canvas-packagedStyle A_style_canvas-canvas">
    <ownedEnd xmi:type="uml:Property" xmi:id="A_style_canvas-canvas" name="canvas" type="Canvas" association="A_style_canvas"/>
    </packagedElement>

    has no name. This is at best poor practice and contrary to the guidance at the end of UML 2.5 2.4.2.
  • Reported: DD 1.1 — Tue, 13 Dec 2016 11:18 GMT
  • Updated: Tue, 8 Jan 2019 15:30 GMT