MEP Task Force
9 Jun 2003

See also: IRC log

Attendees

Contents

• Topics
  1. Review of meps-vs-iops document
  2. Definition of IOP
• Summary of Action Items

Review of meps-vs-iops document

<dbooth> http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/meps-vs-iops/meps-vs-iops_clean.htm

David: Let's go through the doc looking for areas that need work.

<dbooth> "
... · This TF will describe pros and cons of various patterns, and make suggestions to the WG about which patterns to adopt.
... "· WG sought to decide on patterns from a larger set of patterns"
... "A WSDL service defines an interface that is potentially usable by multiple clients to interact with that Web service. "
... "The WSDL interface/portType portion of a WSD defines an abstract interface that is potentially usable by multiple clients to interact with multiple Web services. "
... [[
... 7. Blue-filled circles represent nodes.
... 8. A blue-filled double circle represents a Web service.
... ]]

Scribe: [Scribe is failing. We're walking through the document together, cleaning up editorial and terminological questions.
... ]

<dbooth> "Pattern: A template for an ordered sequence of messages between nodes. Each message has a direction relative to a node. Each message, relative to a node, can either be a input, output, ifault or ofault."

Definition of IOP

<dbooth> dbooth: I'm concerned that we are wasting time discussing the definition of "IOP" instead of discussing the properties of specific patterns, regardless of whether they are called "IOPs", "MEPs" or anything else. I'd like to delete the definitions of "IOP" and "MEP" and just have a single definition of "pattern", which could be any kind of pattern.
... (Others agreed)
... ACTION: dbooth to remove the definition of IOP

Scribe: I'll try and summarize later and post it as minutes :-)

Summary of Action Items