Issue 13333: SoaML Issue: Participant Architecture (soaml-rtf)
Source: Model Driven Solutions (Mr. Cory B. Casanave, cory-c(at)modeldriven.com)
Nature: Revision
Severity: Minor
Summary: Since a participant architecture must be the architecture of a participant the Participant Architecture stereotype should specialize the participant stereotype.  Currently both stereotypes must be applied independently.

Resolution: 
Revised Text: 
Actions taken:
January 24, 2009: received issue
Discussion: 

End of Annotations:=====
ubject: SoaML/UPMS Issue -  Participant Architecture
Date: Sat, 24 Jan 2009 08:30:32 -0500
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: SoaML/UPMS Issue -  Participant Architecture
thread-index: Acl+JjFSyPJVkhsgSTyG+M1D2GKOjwAAU9gQ
From: "Cory Casanave" <cory-c@modeldriven.com>
To: <issues@omg.org>
Cc: <modelpro@modeldriven.org>, <upms@modeldriven.org>


SoaML Issue: Participant Architecture

Source: Model Driven Solutions (Mr. Cory Casanave, cory-c@modeldriven.com)
Nature: Revision
Severity: Minor
Summary:

Since a participant architecture must be the architecture of a participant the Participant Architecture stereotype should specialize the participant stereotype.  Currently both stereotypes must be applied independently.