AMSM 1.0 FTF Avatar
  1. OMG Issue

AMSMF2 — The construction of global names of an instance is unclear.

  • Key: AMSMF2-49
  • Legacy Issue Number: 13248
  • Status: closed  
  • Source: THALES ( Willy Boenink)
  • 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.

  • Reported: AMSM 1.0b2 — Tue, 13 Jan 2009 05:00 GMT
  • Disposition: Resolved — AMSM 1.0
  • Disposition Summary:

    Remove any reference to DMTF CIM in section 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.

  • Updated: Fri, 6 Mar 2015 20:57 GMT