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] Action items for next weeks meeting

Here are mine ...

Attributes – schema to describe attributes of a Web service and portType
operations to access and set the attributes. Attributes should be
introspectable at design time and runtime. Attribute is synonomous with
property. For manageability, A property is a name, type, value triple that
is part of the advertised manageability interface for a resource. An
attribute can be used to represent configuration values, metrics,
identifiers, etc.

Attribute Metadata – schema that defines how to describe metadata about
attributes, operations, events, or interfaces of a Web service. This
metadata for attributes could include includes units, volitility,
modifiability. Metadata about operations may include idempotency, endState.
Metadata should be introspectable at design time and runtime.

Relationships – schema to describe relationships between resource types,
resources, interfaces, and endpoints including portType operations to get
and modify the current set of relationships from a participant in the
relationship. Static relationships and relationships between types and
interfaces should be introspectable at design time and runtime.  All
relationships should be introspectable at runtime.

Relationship  service – a relationship repository or registry which may be
responsible for creating, inventorying, tracking, and validating
relationships. This service is not a participant in the relationships. If
relationships are rule based, then it would also be responsible for
altering relationship members based on the rules. This would include
portType operations for querying, adding,  finding, and validating
relationships. This service would bild on the Relationships schema

I should have picked ones that were out of scope... :-)

Heather Kreger
STSM, Web Services Lead Architect for SWG Emerging Technologies
Author of "Java and JMX: Building Manageable Systems"
919-543-3211 (t/l 441)  cell:919-496-9572

"ECKERT,ZULAH (HP-Cupertino,ex1)" <zulah_eckert@hp.com> on 10/09/2003
02:19:57 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

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

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,

To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to


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