Issue 9360: Issue for MOF 2 spec (ptc/04-10-15) (mof2core-rtf) Source: Adaptive (Mr. Gene Mutschler, gene.mutschler(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: There are some shortcomings in the discussion of the isSet() and unset() operations of the Element class. In particular, there is no mention of optional properties in the Semantics section of the Element description. Is is intended that optional properties be covered by the semantics inSingle-valued properties? If so, how, if at all, does the fact that a property is optional interact with the default for the property? For example, I assume that notwithstanding the spec language: If a single-valued property has a default: • It is set to that default value when the element is created. isSet=false that an optional property will NOT, in fact, be set, and that isSet would be false. Resolution: Disposition: See issue 8269 for disposition Revised Text: Actions taken: February 9, 2006: received issue April 25, 2011: closed issue Discussion: End of Annotations:===== ubject: Issue for MOF 2 spec (ptc/04-10-15) Date: Thu, 9 Feb 2006 11:16:52 -0800 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue for MOF 2 spec (ptc/04-10-15) Thread-Index: AcYtrWI+qOuzFcomR8qSrjjweEXmgA== From: "Mutschler, Gene O" To: X-OriginalArrivalTime: 09 Feb 2006 19:16:53.0307 (UTC) FILETIME=[629398B0:01C62DAD] There are some shortcomings in the discussion of the isSet() and unset() operations of the Element class. In particular, there is no mention of optional properties in the Semantics section of the Element description. Is is intended that optional properties be covered by the semantics inSingle-valued properties? If so, how, if at all, does the fact that a property is optional interact with the default for the property? For example, I assume that notwithstanding the spec language: If a single-valued property has a default: . It is set to that default value when the element is created. isSet=false that an optional property will NOT, in fact, be set, and that isSet would be false. Dr. Gene Mutschler Unisys Corporation. Mission Viejo CA 949 380 6617 THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. Learn it. Love it. Live it. To: juergen@omg.org Cc: issues@omg.org, mof2core-rtf@omg.org Subject: Re: issue 9360 -- MOF 2 Core RTF issue X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005 From: Jim Amsden Date: Tue, 14 Feb 2006 08:20:02 -0500 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Release 7.0HF124 | January 12, 2006) at 02/14/2006 06:20:04, Serialize complete at 02/14/2006 06:20:04 Juergen (and Gene), Optional properties are discussed in the isSet operation description: "If the Property has multiplicity upper bound of 1, isSet()...". This applies if the lower bound is 0 or 1. The semantics of isSet for single-valued properties are intended to cover multiplicity [0..1] or [1..1]. The intention is that a property with multiplicity [1..1] that has no default will have isSet==false on construction and that would be an error in the model. MOF does not specify how this error is handled or when, just what it is. Generally required properties should be given a default if possible. If not, then applications should ensure the are set to some value. Juergen Boldt 02/09/2006 02:26 PM To issues@omg.org, mof2core-rtf@omg.org cc Subject issue 9360 -- MOF 2 Core RTF issue This is issue # 9360 From: "Mutschler, Gene O" Issue for MOF 2 spec (ptc/04-10-15) There are some shortcomings in the discussion of the isSet() and unset() operations of the Element class. In particular, there is no mention of optional properties in the Semantics section of the Element description. Is is intended that optional properties be covered by the semantics inSingle-valued properties? If so, how, if at all, does the fact that a property is optional interact with the default for the property? For example, I assume that notwithstanding the spec language: If a single-valued property has a default: . It is set to that default value when the element is created. isSet=false that an optional property will NOT, in fact, be set, and that isSet would be false. Juergen Boldt Director, Member Services 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org Subject: RE: issue 9360 -- MOF 2 Core RTF issue Date: Tue, 14 Feb 2006 05:31:29 -0800 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: issue 9360 -- MOF 2 Core RTF issue Thread-Index: AcYxaQ7yak3fOZ6sSeS27w/UtAH2fAAAYFig From: "Pete Rivett" To: "Jim Amsden" , Cc: , > intention is that a property with multiplicity [1..1] that has no default will have isSet==false on construction Not if a value is passed in the constructor (which will tend to be language specific though CMOF Reflection has a constructor with arguments for initial values). > and that would be an error in the model this depends on when the constraints are checked. Typically this would not be enforced immediately after construction to allow a chance to try and set the properties: so it would be at the end f a transaction containing the constructor, depending on how much of the facility capabilities are used by the client. Pete -------------------------------------------------------------------------------- From: Jim Amsden [mailto:jamsden@us.ibm.com] Sent: Tuesday, February 14, 2006 8:20 AM To: juergen@omg.org Cc: issues@omg.org; mof2core-rtf@omg.org Subject: Re: issue 9360 -- MOF 2 Core RTF issue Juergen (and Gene), Optional properties are discussed in the isSet operation description: "If the Property has multiplicity upper bound of 1, isSet()...". This applies if the lower bound is 0 or 1. The semantics of isSet for single-valued properties are intended to cover multiplicity [0..1] or [1..1]. The intention is that a property with multiplicity [1..1] that has no default will have isSet==false on construction and that would be an error in the model. MOF does not specify how this error is handled or when, just what it is. Generally required properties should be given a default if possible. If not, then applications should ensure the are set to some value. Juergen Boldt 02/09/2006 02:26 PM To issues@omg.org, mof2core-rtf@omg.org cc Subject issue 9360 -- MOF 2 Core RTF issue This is issue # 9360 From: "Mutschler, Gene O" Issue for MOF 2 spec (ptc/04-10-15) There are some shortcomings in the discussion of the isSet() and unset() operations of the Element class. In particular, there is no mention of optional properties in the Semantics section of the Element description. Is is intended that optional properties be covered by the semantics inSingle-valued properties? If so, how, if at all, does the fact that a property is optional interact with the default for the property? For example, I assume that notwithstanding the spec language: If a single-valued property has a default: . It is set to that default value when the element is created. isSet=false that an optional property will NOT, in fact, be set, and that isSet would be false. Juergen Boldt Director, Member Services 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org