Issue 6655: The descriptions about get/setMembers() are not correct (sdo-pim-psm-ftf)
Source: Fraunhofer FOKUS (Mr. Raju Nanda Vaidya, nobody)
Nature: Enhancement
Severity: Minor
Summary: The descriptions about get/setMembers() are not correct. See Sections 2.3.7 (4) and (5). Semantics of setMembers() should be described clearly. See Sections 2.3.7 (5). Need to make it clear how these operation behaves if it is called when an Organization has already had some SDOs in the members attribute. The name of setMembers() implies that the operation replaces the existing SDOs (members) with new ones (i.e. removes the existing ones). However, the table description in Sections 2.3.7 (5) says “SDOs to be added”. This implies that existing ones are preserved and new ones are added. Which semantics do we take? (1) replacing SDOs or (2) adding SDOs? The option (1) is simpler, and (2) is semantically richer. If we go for (2), we need to think if we need to define removeMember() or removeMembers() (this is a technical revision issue, though). Proposed resolution is: replacing SDOs

Resolution: 
Revised Text: 
Actions taken:
December 1, 2003: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org 
Date: 01 Dec 2003 06:05:00 -0500 
To: <issues@omg.org> 
Subject: Issue/Bug Report 


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

Name: Raju N. Vaidya 
Company: Fraunhofer FOKUS 
mailFrom: vaidya@fokus.fraunhofer.de 
Notification: Yes 
Specification: PIM and PSM for SDO 
Section: 2.3.7 
FormalNumber: dtc/03-09-01 
Version: 03-09-01 
RevisionDate: 03-09-03 
Page: 2-44. 2-45 
Nature: Enhancement 
Severity: Minor 
HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 
Description
The descriptions about get/setMembers() are not correct. See Sections 2.3.7 (4) and (5). Semantics of setMembers() should be described clearly. See Sections 2.3.7 (5). Need to make it clear how these operation behaves if it is called when an Organization has already had some SDOs in the members attribute. The name of setMembers() implies that the operation replaces the existing SDOs (members) with new ones (i.e. removes the existing ones). However, the table description in Sections 2.3.7 (5) says “SDOs to be added”. This implies that existing ones are preserved and new ones are added. Which semantics do we take? (1) replacing SDOs or (2) adding SDOs? The option (1) is simpler, and (2) is semantically richer. If we go for (2), we need to think if we need to define removeMember() or removeMembers() (this is a technical revision issue, though). Proposed resolution is: replacing SDOs