W3C home > Mailing lists > Public > www-ws-desc@w3.org > November 2005

Minutes, 10-11 November 2005 WS Description FTF

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Mon, 14 Nov 2005 13:36:09 -0800
Message-ID: <37D0366A39A9044286B2783EB4C3C4E8B63BC6@RED-MSG-10.redmond.corp.microsoft.com>
To: <www-ws-desc@w3.org>
Enclosed with summary following:

Thursday 10 November

       ?  2005-07-21: pauld to write a proposal for a working group 
                      report for requirements for schema evolution 
                      following closure of LC124 
    DONE  2005-09-26: Arthur to look for simplification options for 
                      comment 12 of 344. (LC344#12), due 2005-10-06. 
    DONE  2005-09-26: Jonathan to point this out when it gets 
                      Implemented (LC344#13), due 2005-10-06. 
       ?  2005-10-20: Bijan to contact WG to ask for contribution to 
                      test suite, due 2005-10-27. 
    DONE  2005-10-27: Umit to look at SOAP 1.1 binding whether soap 
                      action on response is prohibited or ignored
                      be ignored), due 2005-11-03.
          ACTION: Hugo to fix language "Binding component assigns quoted

                  string" in SOAP 1.1 binding, due 2005-11-16.
    DONE  2005-11-03: Marsh to respond to SPARQL about WSDL 1.1, due 
    DONE  2005-11-03: Arthur to propose text for "What should be
                      as a Fault in WSDL", due 2005-11-10. 
    DONE  2005-11-03: Marsh to add this as an issue, due 2005-11-10.
       ?  2005-07-21: Arthur to add stable identifiers for each 
                      assertion, due 2005-09-26.
          ACTION: Hugo will start adding assertions to Part 2.

Announcement: RDF Mapping First Working Draft published!

Rechartering: No objection to asking for an extension to the charter.

Issue LC304: Definition of a IANA media type token
  RESOLUTION: Implement Hugo's simplified proposal at

Issue LC345: POST & application/x-www-form-urlencoded serialization
  RESOLUTION: Hugo's proposal + Charlton's proposal + add disabling 
              attribute for {/} capability.

Splitting out the HTTP binding.
  RESOLUTION: Little interest in splitting the doc at this point.

Issue LC344#5: LC ISSUE: Editorial points
  RESOLUTION: Implement proposal at 
    plus these amendments:
  - Proposed sentence: "This additional information in no way affects 
    the messages exchanged with the service and ..."
  - s/by the interface message reference components of the/in/
  - "If no Operation component can simultaneously satisfy all of the 
    styles, the document is invalid."
  - Update URI to IRI.
  - Section needs to be amended to include Faults and to not
    be applied to the {element declarations} but to the actual
    since the style MAY be dependent on direction or possibly sequence.

Issue LC353: What is a valid WSDL component model?
  RESOLUTION: Implement proposal at 

Issue LC357: Comments on WSDL 2.0 (Core, Adjuncts, Soap 1.1 Binding) 
             from the i18n core wg (3)
  RESOLUTION: Add "Note: The xs:anyURI type is defined so that xs:anyURI

              values are essentially IRIs [RFC 3987]. The conversion
              xs:anyURI values to an actual URI is via an escaping
              defined by [XLink 1.0], which is identical in most
              to IRI Section 3.1. For interoperability, WSDL authors are

              advised to avoid the characters "&lt;", "&gt;", '"',
              "{", "}", "|", "\", "^", and "`", which are allowed by the

              xs:anyURI type but disallowed in IRIs.
  ACTION: Marsh to take the IRI issue to the CG.

Issue LC360: describing a service that returns an image/jpg (for
  RESOLUTION: Close with no action.

Issue LC361: Proposed Text for What Should Be Declared as a Fault in
  RESOLUTION: Add text at

Issue LC362: Re: new section
  RESOULTION: Accepted.

Double binding of an operation issue in SPARQL Protocol
  RESOLUTION: The SPARQL example violates Section 2.11.1: For each
              Operation component in the {binding operations} property
              a Binding component, the {interface operation} property
              be unique. That is, one cannot define multiple bindings
              the same operation within a given Binding component. The 
              correct way to describe that service is with two bindings:

              one for GET and one for POST.
  ACTION: Glen to write a proposal toward LC362.
  ACTION: Paul write to the DAWG re: binding operation twice.

Friday 11 November

Issue LC333: WSDL 2: binding defaults not component model properties?
  RESOLUTION: Proposal at

Issue LC355: simple case of IRIs for Components in WSDL 2.0
  RESOLUTION: Uphold WG resolution to close with no action.

Mapping WSDL message to a SOAP message in SOAP binding
  RESOLUTION: Accepted proposal at
http://lists.w3.org/Archives/Public/www-ws-desc/2005Nov/0022.html, plus
sentence about extensions.
  ACTION: Jonathan to record the issue formally to the issues list with 
          the resolution recorded

Assertion markup
  ACTION: Arthur to construct instructions sheet, and assign sections
          each member of the group to insert assertion markup.

Candidate Recommendation
 - The editors will produce drafts by Wednesday. We will tentatively 
   (unless people need more time) vote to go to CR on Thursday.
 - Current implementations
   + Apache Woden
 - Planned implementations
   + Apache Woden
   + Probably another IBM (not sure)
 - Exit criteria:
   + Two interoperable implementations of each feature 
   + A test suite with an implementation report
   + These will apply to the SOAP 1.1 binding too.
 - Features at risk:
   + URIPath
   + MEPs: all but in-only and in-out may be removed unless evidence of
 - Length
   + 3 months

Received on Monday, 14 November 2005 21:36:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:54 UTC