Re: [drinks] SOAP document - Gen-ART comment regarding minorVer..

Hi Alex,

As far as I recall, framework document only specifies the data type "MinorVerType" - and defers to the implementation Protocol (SPP over SOAP being one) for using the this type in minor versions.

The following definition in section 7.2.9.1 of the latest SPP protocol over SOAP  document seems closer to accuracy:

   o  minorVer: Zero or one minor version identifier, indicating the
      minor version of the SPP Protocol over SOAP API that the client is
      attempting to use.  This is used in conjunction with the major
      version identifier in the XML namespace to identify the version of
      SPP Protocol over SOAP that the client is using.  If the element
      is not present, the server assumes that the client is using the
      latest minor version of SPP Protocol over SOAP supported by the
      SPPF server for the given major version.  The versions of SPP
      Protocol over SOAP supported by a given SPPF server can be
      retrieved by the client using this same spppServerStatusRequest
      without passing in the minorVer element.

I like the idea of moving the definition to a common place, the last sentence above "The versions of ..." would probably need to be reworded a little I guess.

Thanks,
Vikas

-----Original Message-----
From: drinks [mailto:drinks-bounces@ietf.org] On Behalf Of Alexander Mayrhofer
Sent: Wednesday, May 20, 2015 8:05 AM
To: drinks@ietf.org
Subject: [drinks] SOAP document - Gen-ART comment regarding minorVer..

Hello,

Roni Even performed the Gen-ART review of draft-ietf-drinks-spp-protocol-over-soap (see https://www.ietf.org/mail-archive/web/ietf/current/msg91403.html).

Specifically, he asked about the definition of the minorVer element:

"There are two schemas used, the sppf:base and sppf:soap each have a version number. When talking about supported version and about response codes on supported version, is it referring to the base or soap version? There is some text in the minorVer section but it is not clear enough."

Our definition in the document is:

             minorVer: Zero or one minor version identifier, indicating the minor
              version of the SPPF API that the client is attempting to use. This is
              used in conjunction with the major version identifier in
              the XML namespace to identify the version of SPPF that the client
              is using.  If the element is not present, the server assumes that
              the client is using the latest minor version supported by the SPPF
              server for the given major version. The versions supported by a
              given SPPF server can be retrieved by the client using the
              Get Server Details Operation described in <xref target="servermenuopn"/>.

I have to admit, I can't remember what the intention was. Could someone help me creating updated text that fixes Roni's feedback?

Also, the definition is repeated in the text several times. I would move the definition to a dedicated section, and then only refer to that section in the individual objects - I guess that would be fine with the other authors?

Thanks,
Alex

_______________________________________________
drinks mailing list
drinks@ietf.org
https://www.ietf.org/mailman/listinfo/drinks

________________________________

This e-mail message is for the sole use of the intended recipient(s)and may
contain confidential and privileged information of Transaction Network Services.
Any unauthorized review, use, disclosure or distribution is prohibited. If you
are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.