We have a workflow process at UserLand which calls for each team member to periodically report on their status, what they're working on and what the next steps are. Since Jake and I have largely been working for the SOAP and XML-RPC communities for the last few days, I thought it made sense to cc my status report to the lists as well.
Yesterday we spent most of the day drafting A Busy Developer's Guide [1]. The work was done openly, with a live link from Scripting News. We finished at about 2PM, and then took comments [2] and made changes. The doc is not final, we're awaiting guidance from the soapbuilders list re several minor issues and one major one, the question of whether or not it's ok per the SOAP spec to make parameter names not significant and to make parameter order significant.
Another potential deal-stopper, non-iso-8859 character encodings, has been addressed with an unambiguous statement [3] that BDG implementations are required to use 8859 encoding. Jake must add this to the spec itself, and address the other issues in the written spec.
Our deadline for closing off BDG is 48 hours after it started, which is 9AM tomorrow Pacific. We want to address people's concerns now, so we can move forward on determining interop on the basis of this spec through the weekend.
Early next week UserLand will issue a press release listing the names of the implementations that interop with BDG. We invite any participants in the SOAP interop process to join us in that statement.
I hope we can put our differences aside and move quickly. We've made the investment in putting a clear stake in the ground. We want the process to have a closure point. We want to interop with every vendor that makes a tool or runtime that supports XML-over-HTTP. Our message is Let's Go, it's the right time.
Dave
Send Email