RE: WIMS> Normative Ref to WSDL/2.0 would block WIMS as PWG CS

From: McDonald, Ira (imcdonald@sharplabs.com)
Date: Mon Oct 31 2005 - 15:53:59 EST

  • Next message: wamwagner@comcast.net: "WIMS> CIM - Next conference call 10 November."

    Hi,
     
    Sorry for the lack of context, Bill.
     
    The comment was a request for real SOAP examples of WIMS protocol requests
    and responses,
    such as the ones in the IETF NetConf over SOAP spec
    <draft-ietf-netconf-soap-06.txt> on pages
    12 and 13.
     
    To flesh out Option (d):
     
    * Specify SOAP/1.2 bindings as Normative - give examples of WIMS Message
    schema instances
       in SOAP/1.2 messages over HTTP/1.1 session layer (like NetConf);
     
    * Don't use SOAP Headers (like NetConf), for portability across non-SOAP
    protocol bindings;
     
    * Don't use SOAP Faults, for portability across non-SOAP protocol bindings
       (i.e., all WIMS requests ALWAYS receive exactly one corresponding WIMS
    response and
       the 'fault' is contained in the 'ResponseStatusString' and
    'ResponseUnsupportedElements');
       
    * Specify an informative WSDL appendix and state (like NetConf):
        
         "Note that WSDL declarations for WIMS/1.0 over SOAP/1.2 bindings are
    not yet standardized,
         pending the W3C adoption of WDSL/2.0, scheduled for early 2006."
     
    Cheers,
    - Ira

    Ira McDonald (Musician / Software Architect)
    Blue Roof Music / High North Inc
    PO Box 221 Grand Marais, MI 49839
    phone: +1-906-494-2434
    email: imcdonald@sharplabs.com

    -----Original Message-----
    From: wamwagner@comcast.net [mailto:wamwagner@comcast.net]
    Sent: Monday, October 31, 2005 2:24 PM
    To: Harry Lewis; McDonald, Ira
    Cc: 'wims@pwg.org'
    Subject: Re: WIMS> Normative Ref to WSDL/2.0 would block WIMS as PWG CS

    Option D would appear most best. But without minutes of meeting, it is
    unclear what the comment was, what the implications were, and what the WG
    beleives is necessary to address it.
     
    Bill Wagner
     

    -------------- Original message --------------

    After having the opportunity to speak with Ira regarding this, we think
    there may also be an "option D" which is to describe normative Soap v1.2 but
    supply NO WSDL example at this time.. rather indicate that WSDL 2.0 is in
    progress and it is our intent to supply normative WSDL following adoption of
    WSDL 2.0 as a W3C candidate recommendation.
    ----------------------------------------------
    Harry Lewis
    IBM STSM
    Chairman - IEEE-ISTO Printer Working Group
    http://www.pwg.org
    IBM Printing Systems
    http://www.ibm.com/printers
    303-924-5337
    ----------------------------------------------

    "McDonald, Ira" <imcdonald@sharplabs.com>
    Sent by: owner-wims@pwg.org

    10/31/2005 10:53 AM

    To
    "'wims@pwg.org'" <wims@pwg.org>

    cc

    Subject
    WIMS> Normative Ref to WSDL/2.0 would block WIMS as PWG CS

                    

    Hi,

    Per the WG last comment on WIMS Protocol spec last week (for examples
    of WSDL definitions and actual SOAP messages), I've been working on WSDL
    for the WIMS Protocol - following the excellent examples in the recent
    WS-Polling submission from IBM to W3C.

    Good News - conveniently, I recently released the WIMS Message schema,
    which is most of the work - the WSDL itself is very small by comparison.

    Bad news - we all repeatedly agreed to make the non-standards-track
    bindings (using WSDL/1.1 and SOAP/1.1) _optional_ for compatibility and
    make standards-track bindings (using WSDL/2.0 and SOAP/1.2) _mandatory_
    to implement.

    But, the W3C site now says (at http://www.w3.org/2002/ws/desc/):

    "Below are the targeted publication dates for the WSDL 2.0 drafts:

     Second Last Call
       June 2005
     Candidate Recommendati! on
       October 2005
     Proposed Recommendation
       Early 2006"

    PSI/1.0 fudged on this and standardized a SOAP/1.1 binding described in
    WSDL/1.1 (calling them 'defacto industry standards' - which is true, but
    they're still not interoperable).

    So the WIMS/1.0 Protocol spec will have to:

    (a) Use the above SOAP/1.1 fudge for normative bindings;
       <or>
    (b) Wait for the approval of WSDL/2.0 (now a working draft) by W3C;
       <or>
    (c) Use SOAP/1.2 for normative bindings
       and INFORMATIVE references to the WSDL/1.1 W3C Note
       and INFORMATIVE examples of WSDL/1.1 for the SOAP/1.1 binding.

    My apologies for not realizing this problem earlier.

    Cheers,
    - Ira

    Ira McDonald (Musician / Software Architect)
    Blue Roof Music / High North Inc
    PO Box 221 Grand Marais, MI 49839
    phone: +1-906-494-2434
    email: imcdonald@! sharplabs.com



    This archive was generated by hypermail 2.1.4 : Mon Oct 31 2005 - 15:52:36 EST