OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsdm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [wsdm][UPlat] Correlatable Names


Title: Message
What?
Meta-data attached to one or more properties of a class definition.  It indicates that the values of these "correlatable" properties can be compared across instances, and if they are equal, signifies that the same "real-world" entity is being described by those  instances. 
 
Why?
The general use case for correlatable names is that a single "real-world" entity may be managed through several endpoints, and/or managers.  For these endpoints and managers, the instances must be identifiable.  This does not, however, dictate that a single identification scheme must be adopted throughout the managed environment.  To support a single scheme, all endpoints and managers would need access to the complete information required by the "identification" algorithm, and it would be necessary that the algorithm be sufficient in all implementations.    
 
Since a globally unique identifier for all environments is not achievable, it is important to provide mechanisms to determine if data for one or more "real-world" entities is being reported.  For example, when performing discovery, it is necessary to accurately determine the resources in the environment (and not over-estimate).  Another example where "correlatable names" is required is where a partitioned system has multiple management infrastructures - one for each of the partitions and one for the host system.  It is likely that the partitions' hardware data will be sparsely populated.  But, the host system's data may be completely populated.  There is a need to correlate these "hardware" instances. 
 
Andrea
 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]