Issues for Mailing list of the Diagram Definition 1.1 Revision Task Force

To comment on any of these issues, send email to dd-rtf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 16492: Constraints
Issue 16628: DiagramElements cannot represent multiple model Elements
Issue 16907: CMOF version
Issue 16908: Figure A.1 multiplicities
Issue 16909: DiagramElement ownership
Issue 16910: Z-order in DC -> DI and DG
Issue 16991: Multiple modelElements per diagram element
Issue 17099: DG library for string bounding
Issue 17147: DG library for BNF parsing
Issue 17453: Use MOF Primitive Types

Issue 16492: Constraints (dd-rtf)

Click here for this issue's archive.
Source: NIST (Mr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Uncategorized Issue
Severity:
Summary:

The spec currently has no constraint sections.  Should we add them?  For
example, we might require unowned diagram elements to be diagrams

Resolution:
Revised Text:
Actions taken:
January 31, 2011: received issue

Issue 16628: DiagramElements cannot represent multiple model Elements (dd-rtf)

Click here for this issue's archive.
Source: Northrop Grumman (Mr. Christopher McClure, christopher.mcclure(at)ngc.com)
Nature: Clarification
Severity: Significant
Summary:

The definition of DiagramElement has an association to the depicted MOF Element with a multiplicity of [0..1]; so, one DiagramElement can represent at most one model Element.  However, UML contains at least one notation in which a single symbol represents more than one Element: using a single State symbol to represent multiple similar States (see p.601 of the UML 2.4 Superstructure Specification).  Will DD be able to support this notation?

Resolution:
Revised Text:
Actions taken:
October 18, 2011: received issue

Issue 16907: CMOF version (dd-rtf)

Click here for this issue's archive.
Source: Microsoft (Mr. Steve Cook, stcook(at)microsoft.com)
Nature: Revision
Severity: Significant
Summary:

DD should use the latest formal version of CMOF

Resolution:
Revised Text:
Actions taken:
December 14, 2011: received issue

Issue 16908: Figure A.1 multiplicities (dd-rtf)

Click here for this issue's archive.
Source: NIST (Mr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Minor
Summary:

In Figure A.1 (UML DI Metamodel), the multiplicities opposite UMLLabel should be 0..1.

Resolution:
Revised Text:
Actions taken:
December 14, 2011: received issue

Issue 16909: DiagramElement ownership (dd-rtf)

Click here for this issue's archive.
Source: International Business Machines (Dr. Maged Elaasar, melaasar(at)ca.ibm.com)
Nature: Revision
Severity: Significant
Summary:

In Figure 9.2 (Diagram Element) DiagramElement ownership should be ordered and given occlusion semantics, per Section 8.1.3 (Z-Order).

Resolution:
Revised Text:
Actions taken:
December 14, 2011: received issue

Issue 16910: Z-order in DC -> DI and DG (dd-rtf)

Click here for this issue's archive.
Source: NIST (Mr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Significant
Summary:

Section 8.1.3 (Z-Order) should be specific to the ownership association on DiagramElement to itself, and should be moved to DI and DG.

Resolution:
Revised Text:
Actions taken:
December 14, 2011: received issue

Issue 16991: Multiple modelElements per diagram element (dd-rtf)

Click here for this issue's archive.
Source: NIST (Mr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Significant
Summary:

Diagram elements might have multiple modelElements (for example, state lists in UML state machines, combined merge/decision diamonds in UML activities).  Languages can specialize to 1 or order as needed.

Resolution:
Revised Text:
Actions taken:
January 11, 2012: received issue

Issue 17099: DG library for string bounding (dd-rtf)

Click here for this issue's archive.
Source: International Business Machines (Dr. Maged Elaasar, melaasar(at)ca.ibm.com)
Nature: Revision
Severity: Significant
Summary:

Is a DG library needed to calculate bounding boxes for strings in particular fonts?

Resolution:
Revised Text:
Actions taken:
February 8, 2012: received issue

Issue 17147: DG library for BNF parsing (dd-rtf)

Click here for this issue's archive.
Source: NIST (Mr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Significant
Summary:

A DG library for BNF parsing would enable language-specific DI's capture strings, instead of modeling BNF constraints.

Resolution:
Revised Text:
Actions taken:
February 22, 2012: received issue

Issue 17453: Use MOF Primitive Types (dd-rtf)

Click here for this issue's archive.
Source: NASA (Dr. Nicolas F. Rouquette, nicolas.f.rouquette(at)jpl.nasa.gov)
Nature: Revision
Severity: Significant
Summary:

Diagram Common should reuse MOF Primitive Types

Resolution:
Revised Text:
Actions taken:
June 21, 2012: received issue