RE: [wsdm] [UPlat] Action items for next weeks meeting

["VAMBENEPE,WILLIAM (HP-Cupertino,ex1)" <vbp@hp.com>]

Based on ths discussion on the conf call today, here is an updated
definition for addressing that better highlights how it relates to identity.

Addressing is the ability to reference an identified entity so that it can
be accessed. In the case of a web service, "being accessed" means getting
hold of its WSDL description and any extra information that might be needed
to route messages to the service.

Regards,

William

> -----Original Message-----
> From: MURRAY,BRYAN (HP-Seattle,ex1) [mailto:bryan.murray@hp.com] 
> Sent: Friday, October 10, 2003 12:41 PM
> To: wsdm@lists.oasis-open.org
> Subject: RE: [wsdm] [UPlat] Action items for next weeks meeting
> 
> 
> Included is my homework. I did not find a glossary for MUWS, 
> but some of the
> terms I use come from the glossary for MOWS. I also recommend 
> that we add a
> definition for 'manager'.
> 
> 
> Addressing
> 
> 1) Addressing is the ability to reference another entity. One 
> examples of
> where a reference is required is in a relationship to refer 
> to the entities
> that have an association with each other. Another example is 
> to refer to the
> Web service where asynchronous notifications should be sent. 
> In general, the
> Web service exposing the manageability interfaces for a 
> resource may need a
> reference to the resource. Since not all resources are Web services, a
> reference must be defined such that non-Web service entities 
> can also be
> referred to. The special case of referring to a Web service 
> entity should
> refer to the WSDL for the Web service such that a manager can 
> choose which
> Web service endpoint it wants to send messages.
> 
> 2) Addressing is required to provide references to other 
> entities. Other
> entities may include resources, Web services, WSDL documents, policy
> descriptions, as well as other documents and services. 
> Addressing defines
> the mechanism used to specify the reference. Management using 
> Web services
> requires a standard mechanism for referring to other entities.
> 
> 
> 
> Collection
> 
> 1) A collection is an entity which acts as a proxy to zero or 
> more other
> entities. A manager can send a single request to a collection 
> where the
> result is that zero or more members of the collection are 
> acted upon as
> specified in the request. The members of a collection are 
> managed entities
> in their own right and have their own management interfaces. 
> The result of a
> manager sending a single request to a collection must be the same as a
> manager sending a separate message to each of the selected 
> members of the
> collection individually. It is not necessary that the 
> collection actually
> send separate messages to each of its members, only that the 
> result to the
> members is the same. A collection provides a mechanism to 
> perform the same
> action on many managed entities at once, and acts as one scalability
> mechanism in a management system.
> 
> 2) As the number of managed resources grows, it becomes more 
> important for a
> management system to provide a mechanism to allow a manager 
> to perform the
> same action on many resources at once. For instance, with a 
> collection a
> manager can query for the state of all resources in the 
> collection at once
> rather than one at a time. Also, it is possible for a 
> collection to reset
> the state of metrics for the resources in the collection 
> using a single
> request. A collection provides the ability for a management 
> system to scale
> much better than a system not supporting collections. Also, 
> there are cases
> where the exact membership of a group is better known by an 
> entity, such as
> a collection, that may be closer to the group than a manager. 
> This allows
> the manager to defer to the collection to determine the exact 
> entities to
> act upon.
> 
> 
> I will be out of the office for the next 2 weeks, but hope to 
> be able to
> discuss this when I return.
> 
> Bryan
> 
> -----Original Message-----
> From: ECKERT,ZULAH (HP-Cupertino,ex1) [mailto:zulah_eckert@hp.com] 
> Sent: Thursday, October 09, 2003 11:20 AM
> To: wsdm@lists.oasis-open.org
> Subject: [wsdm] [UPlat] Action items for next weeks meeting
> 
> 
> 
> Here is the action for next weeks meeting and the list of 
> item/things as
> assigned during todays meeting. Please try to have your item 
> done by COB on
> Monday 10/13 so that we can have some email discussion prior 
> to next weeks
> meeting.
> 
> Action: For each item/thing  
>   1) create appropriate definitions using glossary terms 
> where available.
> Ideally, your definition would become part of the glossary
>   2) describe why this is necessary for MUWS
> 
> At this point, we are at a fairly course grained level of 
> detail. Keeping
> your deliverable succinct and to the point will help everyone 
> come to an
> understanding about the 15+ items so that we can prioritize 
> at the next
> meeting.
> 
> Action assignments:
> 
> Identification - Unique Id for svcs - Igor
> Notification Mechanism - Igor
> Registration/discovery/location - Igor
> 
> Version - version of service, in URIs today, w3c tab? 
> sufficient? - Andrea
> transaction - Andrea
> 
> Attributes & Metadata - Heather
> Relation - Heather
> Relationship Service? - Heather
> 
> Addressing - being able to convey a reference - like ws-addressing and
> gsr/gsh - Bryan Collection - Bryan 
> 
> Security - +bootstrap security mode? - John DeCarlo
> 
> Work Flow, scripting (e.g., BPEL)- William
> 
> Policy - may not be reqd for vers 1 - Andreas
> Policy Decision Point/Policy Enforcement Point - Andreas
> 
> Negotiation - Zulah
> 
> Logging - Ellen
> Lifecycle Support (e.g., factory) - Ellen
> 
> Let me know if any clarification is necessary,
> Zulah
> 
> To unsubscribe from this mailing list (and be removed from 
> the roster of the
> OASIS TC), go to
> http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leav
> e_workgroup.ph
> p.
> 
> To unsubscribe from this mailing list (and be removed from 
> the roster of the OASIS TC), go to 
> http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leav
e_workgroup.php.