Re: [wsdm] First Face to Face

["M. Homayoun Pourheidari" <homayoun@hp.com>]

Title:

Hi,

Here are some thoughts on what the usability requirements for WSDM and
in the space of management could entail.  There are overlaps with other
areas that are listed in the requirements list.  But, this is a view of
those requirements that would apply to a pragmatic, adoptable
approach.  What is stated below is just a starter kit to get us in the
same frame of mind and I look forward to the TC to add more value here.

In the context of WSDM, I believe usability relates to how quickly the
different roles, that are important in the lifecyle of a WSDM based
deployment, can provide and make use of the management information.  I
start with the roles of a manager and a managed object.  There are of
course other roles that should be considered.

For example, from a management role perspective, it is important that
it gets to the allowed management information easily and quickly. This
relates to the parts of the:

• protocol that allow the manager to get to the management information (e.g. how many steps do I need to take to get to the information, how do I do bulk operations, how hard is it to get events, etc.)
• protocol that allow the manager to display the information in a user and domain friendly way (e.g. How easy is it for me to convert the data to my special format, can I display it in a non-english env., etc.)
• model that allows the manager to understand the capabilities and the relationships between the managed objects such that it can understand their interdependencies and the type of management information they're capable of providing without having to necessarily know the details of their specific modeling techniques
• etc.
  

from a managed object role perspective, it is important that its
developers and deployers be able to:

• easily adopt and develop WSDM based deployments
• gradually build their management information capabilities and yet be compliant with WSDM
• pragmatically use the framework/protocol -- meaning that it should be lightweight and extensible

Cheers,
H.