Issue 9160: RefCCMBaseObject and RefBaseObject                                                                                                                                                                      (mof2idl-ftf)
Source: Fraunhofer FOKUS (Mr. Michael Soden, soden@ikv.de soden@fokus.fraunhofer.de)
Nature: Uncategorized Issue
Severity: 
Summary: RefCCMBaseObject and RefBaseObject should contain a ref_get_label() operation.
Source:
Michael Soden, soden@ikv.de
Summary:
Unfortunately the MOF2.0 Core like MOF1.4 fails explicitly model a property as the label of an instance of a class. It provides the isID flag but this cannot always be used to display class instances reflectively. For example, when modeling a "Library", a "Book" would have a "bookID" and "title". While the "bookID" may be flagged with isID=true, this may not be user friendly for a reflective client displaying a book.
Therefore I suggest the introduction of a ref_label() operation in the RefCCMBaseObject and RefBaseObject interfaces as well as a standard optional Tag whose value should denote the property to use as a label. The modeler can attach such a tag to a class so that the ref_label() method can be implemented accordingly in the class' derived interface.

Resolution: closed no chage
Revised Text: Introduce the operation
string ref_label(); 
in the RefCCMBaseObject and RefBaseObject interfaces
Introduce a standard tag for identifying labels. 
No changes made.

Actions taken:
November 15, 2005: received issue
March 8, 2006: closed issue
Discussion: 
Discussion:
Since this is outside the scope of the MOF2.0 IDL mapping, we do not consider it in the IDL language binding. However, this is a possible extension to MOF2.0 and should be raised as an issue for the MOF2.0 Core specification.

End of Annotations:=====
MG Issue No: [Temp13]
Title:	RefCCMBaseObject and RefBaseObject should contain a ref_get_label() operation.
Source:
Michael Soden, soden@ikv.de
Summary:
Unfortunately the MOF2.0 Core like MOF1.4 fails explicitly model a property as the label of an instance of a class. It provides the isID flag but this cannot always be used to display class instances reflectively. For example, when modeling a .Library., a .Book. would have a .bookID. and .title.. While the .bookID. may be flagged with isID=true, this may not be user friendly for a reflective client displaying a book.
Therefore I suggest the introduction of a ref_label() operation in the RefCCMBaseObject and RefBaseObject interfaces as well as a standard optional Tag whose value should denote the property to use as a label. The modeler can attach such a tag to a class so that the ref_label() method can be implemented accordingly in the class. derived interface.
Discussion:

Resolution:
Introduce the operation
string ref_label(); 
in the RefCCMBaseObject and RefBaseObject interfaces
Introduce a standard tag for identifying labels. 
No changes made.