RE: [wsdm] F2F agenda item

["Zulah Eckert" <zeckert@bea.com>]

What I would like to understand about either choice is what purpose it
serves (i.e., the problem that it addresses) in terms of integration. As
I understand the specs today, their purpose is to provide integration
with a resource via a Web service for the purpose of management. I've
heard various discussions about what capabilities provide and I have to
say from recently reading the specs, I found it unclear. Is the purpose
to:

1) aid developers by logically grouping management properties and
operations? Isn't this a tutorial or tooling issue?

2) provide model structure to resource management? Then there is some
barrier to entry to adapt one's model to this structure in order to
adhere to the standard.

3) provide some form of semantic integration. Is the information being
provided such that no apriori knowledge is needed to semantically
integrate?

My question about all three of these is does the value that they bring
to the standard outweigh the complexity that each potentially brings to
actually adhering to the standard?

Zulah

-----Original Message-----
From: Homayoun Pourheidari [mailto:homayounp@gmail.com] 
Sent: Monday, June 27, 2005 1:12 AM
To: Murray, Bryan P.
Cc: wsdm@lists.oasis-open.org
Subject: Re: [wsdm] F2F agenda item

+1 for the second choice.

As I recall, there were many use cases where a property or an
operation can belong to different management capabilities that one may
define.  Of course, you can go out of your way to define "capability"
categories that are mutually exclusive.  But I believe that is not how
most people would relate to manageability information.

A wsdm capability should be considered a meta data that can be
attached to various components of manageability information to form a
category that provides a meaningful manageability semantic.

Cheers,
H.
--

On 6/25/05, Murray, Bryan P. <bryan.murray@hp.com> wrote:
> I had an internal discussion about WSDM capabilities today that makes
me
> wonder if all of the WSDM TC understand capabilities in the same way.
> Heather could you add an agenda item to talk briefly about
capabilities
> during the f2f.
> 
> As a teaser, the 2 ways of looking at capabilities are:
> 
> 1) A capability is a set of properties, operations, and notifications
> described by WSDL/schema. Once defined, the capability has a fixed set
> of properties, operations, and notifications - it is like a portType,
> forever constant.
> 
> 2) A capability is a means of categorization. Capabilities are defined
> independent of properties, operations, notifications. Any property,
> operation, notification can be assigned to zero or more capabilities
to
> show that they have something to do with that category of
functionality.
> A capability has nothing to do with a portType and new properties can
> claim they are associated with an existing capability.
> 
> Bryan
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in
OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
>

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php