Issue 3959: Improvement needed on Membership textual description.                                                                                                                                                   (negotiation-ftf)
Source: OSM (Mr. Stephen McConnell, mcconnell@osm.net)
Nature: Revision
Severity: Significant
Summary: The Member type represents an association of a User to a 
	Membership, as such it should be re-defined as a type 
	of Link.  The current specification is currently broken 
	and must be recast against an extendable Link model. 

Resoliution:

	Resolution of this issue is proposed under EC/2000-10-02, 
	Part 2, in conjunction with resolution of issues defined under 
	EC/2000-10-01.
Resolution: see below
Revised Text: Issue Resolution
Redefinition of Member as a type of Link based on a revised Link valuetype. An abstract
Link named Privilege is defined as the common relationship between a User and a
Membership. The Member link defines the association to a Membership that is held by an
instance of User. The Recognizes link held by a instance supporting Membership defines
an association of a User to that Membership. This revision brings the User to Membership
association in line with the general association model defined under the Task and Session
framework.The definition of Member has been replaced by the following IDL:
valuetype Member : Session::Privilege {
public Membership resource;
};
valuetype Recognizes : Session::Privilege {
public Session::User resource;
public Labels roles;
};
Operations supporting access to role information previously on Member are replaced by
exposure of business roles under the state field named roles on the link held by an instance of
Membership. Additional access operations dealing with disclosure of member roles and
membership aggregation has been relocated under the Membership interface.
// from Membership
boolean is_member(
in Session::User user
) raises (
PrivacyConflict
);
boolean has_role(
in Session::User user,
in Label role
) raises (
PrivacyConflict
);
Labels get_member_roles(
in Session::User user
) raises (
PrivacyConflict
);
Session::UserIterator list_members(
in long max_number,
out Session::Users list
) raises (
PrivacyConflict
);
Session::UserIterator list_members_using(
in Label role,
in long max_number,
out Session::Users list
) raises (
PrivacyConflict
);
};
Actions taken:
October 16, 2000: received issue
February 27, 2001: closed issue
Discussion: 

End of Annotations:=====
From: "Stephen McConnell" <mcconnell@osm.net>
To: "Juergen Boldt" <juergen@omg.org>
Cc: <issues@omg.org>, <negotiation-ftf@omg.org>,
   "Abdul Akram Ph. D." <abdul.akram@mail.sprint.com>,
   "Sanjeev Goyal" <sanjeev.k.goyal@ind.xerox.com>
Subject: Negotiation FTF Issues
Date: Mon, 16 Oct 2000 19:17:22 +0200
Message-ID: <004101c03794$f2064ac0$0a01a8c0@osm.net>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800
Importance: Normal
Content-Type: multipart/mixed;
	      boundary="----=_NextPart_000_0042_01C037A5.B58F1AC0"
X-UIDL: -HAe93@]!!J1(!!e=>!!


Issue DDDD: Improvement needed on Membership textual description.
-----------------------------------------------------------------

Nature:

	Member type should be redefined as a type of Link.

Severity:

	High.

Summary:


	The Member type represents an association of a User to a 
	Membership, as such it should be re-defined as a type 
	of Link.  The current specification is currently broken 
	and must be recast against an extendable Link model. 

Resoliution:

	Resolution of this issue is proposed under EC/2000-10-02, 
	Part 2, in conjunction with resolution of issues defined under 
	EC/2000-10-01.