Issue 13248: The construction of global names of an instance is unclear. (amsm-ftf) Source: THALES (Mr. Willy Boenink, willy.boenink(at)nl.thalesgroup.com) Nature: Clarification Severity: Significant Summary: The Naming Convention specifyies that it reuses the DMTF CIM naming convention which is based on so-called "weak" associations. However in the CIM specification a weak association results in the propagation of the key properties to the dependent class. In the AMSM specification this is not the case. For a association link from class A to class B the AMSM specification states that the global name of an instance B is constructed by concatenating the global name of an instance of A with the key values of B. However the AMSM specification does not specify the syntax for the construction of the global names. Further it should provide an example. Resolution: Remove any reference to DMTF CIM in section 7.1.2.1. Add an example. Specify more clearly how the global name have to be built. State that the value of a key attribute shall be unique for all the instance of a class. Add the class name and the attribute name in the global name in order to avoid the cases where classes have a key relation with themselves and another key relation with another class. These cases lead to mistake because key names are unique per class and not for the whole model. Revised Text: Replace the text of the section 7.1.2.1 with the following one: In order to give a normalized global name to instantiations of the classes of this model, the AMSM service uses a naming convention that is based on specific attributes and associations of the class of the considered element. In the models shown hereafter, an UML constraint ("key") have been used to mark these specific attributes and associations. As already stated, the owner classes of a class can be found by going backward on associations whose other end is constrained as "key". The global name of an instance I of a class B is thus given by the following rules: · If i has no owner, its global name is given by its only attribute marked as "{key}" with the following syntax: "<className>.<attributeName>=<Value>". The value of a key attribute shall be unique for all the instances of a given class. · Else, the global name of i is constructed by concatenating: o the global name of its owner, o the letter ":" (ASCII code 58), and o the only attribute of i marked as "{key}" with the following syntax: "<className>.<attributeName>=<Value>".. Example 1: Considering the following excerpt of the PIM and an Executable Software Element named "ESE" residing in an application named "App" which resides in a system named "System" with doesn't reside in any other system. Thus, the global name of the system is "AMS_SoftwareSystem.Name=System" (no "owner", key attribute "Name"), the global name of the application is "AMS_SoftwareSystem.Name=System:AMS_Application.Name=App" (Owner given by the key association "CIM_SystemComponent", key attribute "Name"), and the global name of the Executable Software Element is "AMS_SoftwareSystem.Name=System: AMS_Application.Name=App:AMS_ExecutableSoftwareElement=ESE" (Owner given by the key association "CIM_SystemComponent", key attribute "Name"). Example 2: In the same context, an Executable Software Element named "ESE" residing in an application named "test2" which resides in a second application name "test1" in a system named "test1" with doesn't reside in any other system. The global name of ESE is: "AMS_SoftwareSystem.Name=test1: AMS_Application.Name=test1: AMS_Application.Name=test2:AMS_ExecutableSoftwareElement=ESE". Actions taken: January 13, 2009: received issue July 23, 2009: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 13 Jan 2009 10:11:17 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Willy Boenink Company: Thales Nederland mailFrom: willy.boenink@nl.thalesgroup.com Notification: Yes Specification: AMSM Section: 7.1.2.1 FormalNumber: dtc/2008-02-02 Version: Beta 2 RevisionDate: 02-02-2008 Page: 16 Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9) Gecko/2008051206 Firefox/3.0 Description The construction of global names of an instance is unclear. The Naming Convention specifyies that it reuses the DMTF CIM naming convention which is based on so-called "weak" associations. However in the CIM specification a weak association results in the propagation of the key properties to the dependent class. In the AMSM specification this is not the case. For a association link from class A to class B the AMSM specification states that the global name of an instance B is constructed by concatenating the global name of an instance of A with the key values of B. However the AMSM specification does not specify the syntax for the construction of the global names. Further it should provide an example.