Issue 8684: Add a Constraint (uml2-rtf)
Source:  (, )
Nature: Clarification
Severity: Minor
Summary: No consistency condition is put between predecessor clauses, for instance two clauses can be the predecessor of each other. Add a Constraint: The transitive closure of predecessorClause must be a strict partial order. 

Resolution: agreed
Revised Text: In Section 12.3.18 (ConditionalNode) under Constraints (Package StructuredActivities), add the constraint (numbered appropriately):
[x] No two clauses within a ConditionalNode maybe predecessor clauses of each other, either directly or indirectly.

Actions taken:
April 5, 2005: received issue
Discussion: 
Disposition:	Deferred to UML 2.4 RTF
End of Annotations:=====

m: webmaster@omg.org 
Date: 05 Apr 2005 15:31:52 -0400 
To: <issues@omg.org> 
Subject: Issue/Bug Report 



--------------------------------------------------------------------------------

Name: Pierre Yves Schobbens
Company: FUNDP
mailFrom: pys@info.fundp.ac.be
Notification: Yes
Specification: Pierre Yves Schobbens
Section: 12
FormalNumber: 04-10-02
Version: 2.0
RevisionDate: 10/08/2004
Page: 313
Nature: Clarification
Severity: Minor
HTTP User Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/125.5.6 (KHTML, like Gecko) Safari/125.12
Description
No consistency condition is put between predecessor clauses, for instance two clauses can be the predecessor of each other. Add a Constraint: The transitive closure of predecessorClause must be a strict partial order. 
Subject: Proposed issue resolutions, Set 2: Activities -- Low and trivial effort changes
Date: Sun, 1 Feb 2009 23:25:51 -0500
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Proposed issue resolutions, Set 2: Activities -- Low and trivial effort changes
thread-index: AcmE7lQ9kq9LsV5zRgKwNovhcAlo8A==
From: "Ed Seidewitz" <ed-s@modeldriven.com>
To: <uml2-rtf@omg.org>


Attached are proposed resolutions to 21 additional Activity issues that only required low or trivial effort changes (though there are a few that, on further analysis, I decided to propose to close or identified as duplicate).

 

-- Ed



OMG Issue No:  8684
Title:	Add a Constraint
Source:
FUNDP (Pierre Yves Schobbens, pys@info.fundp.ac.be)
Summary:
No consistency condition is put between predecessor clauses, for instance two clauses can be the predecessor of each other. Add a Constraint: The transitive closure of predecessorClause must be a strict partial order. 
Resolution:
Agreed.
Revised Text:
In Section 12.3.18 (ConditionalNode) under Constraints (Package StructuredActivities), add the constraint (numbered appropriately):
[x] No two clauses within a ConditionalNode maybe predecessor clauses of each other, either directly or indirectly.
Disposition:	Resolved