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: RE: [wsdm] [UPlat] definitions


Identification is a way to represent that one element is same or different than the other without necessarily looking at the contents or definition of the element. Applied to Web resources in general, as defined by W3C, a Uniform Resource Identifier (URI) can be used to represent the identity of a Web resource. Applied to Web services, every element which Web service description is composed of (service, interface, endpoint, location, etc.), is required to be identifiable by a URI. Such URI must be unique by definition. Identity is not required to be an addressable location, so a dereferencing mechanism may be required to actually locate the corresponding resource.

Manageable resources need to be uniquely identified for the manager to tell one from the other and also to consistently refer to. Therefore a standard representation of a unique identity is required.


Registration is a method of advertising an existence of an element so that it can be discovered. Discovery is a method of locating an existing element so that it can be used or operated. Discovery can be based on a selection criteria or simply a name or identity of an element. Location is a method of obtaining an address of an element. For example, location may mean translating an identity of an element into an address of an existing useable element. In the Web services sense, registration, discovery and location can be represented by a set of operations and schema which may be implemented by a Registry. A Web service can register itself or can be registered by a third party by sending a request to the Registry. A Web service can be discovered by sending a request to the Registry. The Registry can return the description of a Web service with location address included in a description or it may return the location address directly.

Manageable resources have to be discoverable by the managers. Manageable resources exposed via Web services can be registered, discovered and located via a Registry.

Notification Mechanism

Notification is a method of conveying information from a source to recipients that expressed interest in that information. In terms of Web services it means delivering an XML message from the source to addressable recipients. An interest in receiving those messages must be established by the recipients, or by third parties on behalf of the recipients. When registering interest, address(es) of recipient(s) must be provided (see Addressing).

Manageable resources need to convey information to the managers. In certain cases, it is unreasonable for the manager to explicitly poll (request) the information, and it has to be sent to the manager by the resource. For example, a manager may be interested when a service receives a new message. The resource representing the service has to notify the manager when it happens (event). The resource needs to know which managers are interested in which information and what are the deliverable addresses of the managers to send the notification message when an event occurs.

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788

-----Original Message-----
From: ECKERT,ZULAH (HP-Cupertino,ex1) [mailto:zulah_eckert@hp.com] 
Sent: Thursday, October 09, 2003 2:20 PM
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/leave_workgroup.php.

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