Issue 4483: Add 'semantics' attribute to Operation. (mof-rtf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Enhancement Severity: Significant Summary: At the moment MOF has no way to describe the behavior of an operation. A new attribute, 'semantics', String (0..1) should be added to Operation. A more sophisticated alternative would be to include a 'language' attribute also, as for Constraint. This would be somewhat restrictive in permitting only one coding of the semantics (e.g. not both OCL and Java). Better would be to use just one multivalued attribute of type StructuredDataType 'Expression'. This would be as in UML and have StructureFields 'language' (String 0..1) and 'body' (String 1..1). It begs the question as to whether this datatype should then be used in Constraint instead of the current 'language' and 'expression' attributes. Resolution: Revised Text: Actions taken: August 12, 2001: received issue Discussion: End of Annotations:===== From: webmaster@omg.org Message-Id: <200108121644.f7CGiHt11760@emerald.omg.org> Date: 12 Aug 2001 12:47:18 -0400 To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Issue/Bug Report Content-Type: Text/html; charset=windows-1252 X-UIDL: p~gd9G2hd9)Cod91Uc!! Name: Pete Rivett Company: Adaptive mailFrom: pete.rivett@adaptive.com Notification: Yes Specification: MOF Section: 3.4.14 FormalNumber: formal/00-04-03 Version: 1.3 RevisionDate: 03-2000 Page: 3-44 Nature: Enhancement Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98) Description Add 'semantics' attribute to Operation. At the moment MOF has no way to describe the behavior of an operation. A new attribute, 'semantics', String (0..1) should be added to Operation. A more sophisticated alternative would be to include a 'language' attribute also, as for Constraint. This would be somewhat restrictive in permitting only one coding of the semantics (e.g. not both OCL and Java). Better would be to use just one multivalued attribute of type StructuredDataType 'Expression'. This would be as in UML and have StructureFields 'language' (String 0..1) and 'body' (String 1..1). It begs the question as to whether this datatype should then be used in Constraint instead of the current 'language' and 'expression' attributes.