Comments on STT Spec Implementation Details
Hi All - Last week our team published jointly with Visa the STT specification. Since then, we've received some comments that the wire formats and protocols section for STT have not been complete enough for developers to implement. We're very interested in feedback and specifics on this. We worked to keep _only_ the detail we felt required to implement STT -- the language is intentionally terse. However, it is in everyone's best interest that the STT spec is completely understood and implementable. We want your participation in this. We've set up an alias direct to our team to respond to your comments: stt@microsoft.com Non-technical flames direct to: Rick - aka - Rick Johnson rickj@microsoft.com
Rick Johnson writes:
We're very interested in feedback and specifics on this. We worked to keep _only_ the detail we felt required to implement STT -- the language is intentionally terse. However, it is in everyone's best interest that the STT spec is completely understood and implementable.
My suggestion, which I made when Microsoft made a presentation at the IETF meeting in Stockholm and then had the gall to say "oh, no, we don't intend to publish an internet draft" is that you publish this as an internet draft and try to shepard it through the IETF's standardization process. You will, of course, be savaged, but that is in the interests of everyone, including you. The belief that companies can make more money by following proprietary solutions and imposing them on the world as standards is falling away. It is in Microsoft's interest that the standard that is adopted for commerce be open, publically discussed at length, and brutally critiqued. Losing a bit of control in exchange for actually getting something that works out for you and your customers is in your interest. Perry
participants (2)
-
Perry E. Metzger -
Rick Johnson