W3C home > Mailing lists > Public > www-ws-desc@w3.org > June 2002

issue 38: Clarify the what kinds of extensibility elements go where

From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
Date: Thu, 20 Jun 2002 12:42:25 +0600
Message-ID: <022201c2184b$abd67e50$82a6a409@lankabook2>
To: "WS-Desc WG \(Public\)" <www-ws-desc@w3.org>

I would like to request that we close the following issue as
its redundant with another issue in the part1 spec (see below):

  <issue>
    <issue-num>38</issue-num>
    <title>Clarify the what kinds of extensibility elements go
where.</title>
    <locus>Spec</locus>
    <requirement>n/a</requirement>
    <priority>Editorial</priority>
    <topic></topic>
    <status>Active</status>
    <originator><a href="mailto:sanjiva@watson.ibm.com">Sanjiva
Weerawarana</a></originator>
    <responsible>Unassigned</responsible>
    <description>
    [<a
href="http://lists.w3.org/Archives/Member/w3c-ws-desc/2002Apr/0029.html">ema
il</a>]
    There is confusion in the user community about what should go in a
binding
    vs. a port vs. a service in terms of extensibility.
    An approach could be to that data marshalling type extensions go in
    a binding and transport stuff goes in to a port and anything else
    goes into a service.
    </description>
    <proposal>
    </proposal>
    <resolution>
    </resolution>
  </issue>

The issue in the part1 spec is:

<issue id="issue-clarify-elements">
  <head>Clarify the what kinds of extensibility elements go where.</head>
  There is confusion in the user community about what should go in a
  binding vs. a port vs. a service in terms of extensibility. An
  approach could be to that data marshalling type extensions go in
  a binding and transport stuff goes in to a port and anything else
  goes into a service.
  <source>Sanjiva Weerawarana</source>
</issue>

Sanjiva.
Received on Thursday, 20 June 2002 07:15:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:20 GMT