How about this:
Web services workflow: the capability to describe a sequence of web services
interactions, where each interaction is fully or partially determined by the
sequence description and the result of previous interactions in that
sequence.
William
> -----Original Message-----
> From: ECKERT,ZULAH (HP-Cupertino,ex1) [mailto:]
> Sent: Thursday, October 16, 2003 8:40 AM
> To: 'Heather Kreger'; ECKERT,ZULAH (HP-Cupertino,ex1)
> Cc:
> Subject: RE: [wsdm] [UPlat] Action items for next weeks meeting
>
>
>
> We can do this. I'll provide a definition for negotiation. William can
> provide one for workflow.
>
> Zulah
>
> -----Original Message-----
> From: Heather Kreger [mailto:]
> Sent: Thursday, October 16, 2003 8:15 AM
> To: ECKERT,ZULAH (HP-Cupertino,ex1)
> Cc:
> Subject: RE: [wsdm] [UPlat] Action items for next weeks meeting
>
>
>
>
>
>
> I thought we were going to define them anyways, even if it
> was determined
> '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)" <> on 10/16/2003
> 10:41:09 AM
>
> To:
> cc:
> Subject: RE: [wsdm] [UPlat] Action items for next weeks meeting
>
>
>
>
> My action item was negotiation which in this case would
> include protocol
> negotiation and QoS negotiation. Both of these are IMO out of
> scope for the
> platform needs for manageability.
>
> Zulah
>
> > -----Original Message-----
> > From: ECKERT,ZULAH (HP-Cupertino,ex1) [mailto:]
> > Sent: Thursday, October 09, 2003 11:20 AM
> > To:
> > 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.php.
>
> 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.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.
