Issue 5529: Change owner association from Security to Contact  from 1..1 to 0..n (gene-expression-ftf)
Source: Rosetta Biosoftware Business Unit (Mr. Michael D Miller, nobody)
Nature: Uncategorized Issue
Severity: 
Summary: Recommend that the owner association from Security to Contact be 
changed from 1..1 to be 0..n.  It was brought up that there may be many
contacts with permission to change Security and, separately, that
there may be no ownership concept.


Resolution of the issue would change:
MAGE-OM and the generated MAGE.xmi
MAGE-ML.dtd
Section 3.1.3, "Description" of the documentation

Resolution: see below
Revised Text: Section 2.1.2, "AuditAndSecurity" of the documentation

Figure 2-3 will be updated

In the documentation for Security the first Association is changed.

Currently:

"\bowner\b : Contact (1..1)"

Becomes:

"\bowner\b : Contact (0..n)"

(where \b...\b indicates bold)
 
 
 MAGE-OM and the generated MAGE.xmi are updated for the Owner association
 
 
 MAGE-ML.dtd

Currently:

"<!ELEMENT Owner_assnref ((%Contact_ref;)) >"

Becomes:

"<!ELEMENT Owner_assnreflist ((%Contact_ref;)+) >"

Currently:

"<!ELEMENT Security ((%Identifiable_content;),

Owner_assnref,

ReadGroups_assnreflist?,

WriteGroups_assnreflist?) >"

Becomes:

"<!ELEMENT Security ((%Identifiable_content;),

Owner_assnreflist?,

ReadGroups_assnreflist?,

WriteGroups_assnreflist?) >"
 

Actions taken:
July 20, 2002: received issue
December 11, 2002: closed issue
Discussion: 
This will allow both no owner and shared ownership
End of Annotations:=====
Recommend that the owner association from Security to Contact be 
changed from 1..1 to be 0..n.  It was brought up that there may be
many
contacts with permission to change Security and, separately, that
there may be no ownership concept.


Resolution of the issue would change:
MAGE-OM and the generated MAGE.xmi
MAGE-ML.dtd
Section 3.1.3, "Description" of the documentation


(MAGE ISSUE 102)