Saturday, April 14, 2001
|
I've been thinking about next steps in SOAP 1.1 interop. We seem to be getting through the wire level, so the next thing is to have a set of criteria for application-level interop. I understand that there are lots of potential uses for SOAP, but our interest is clearly in the Web as a writing environment. I also understand that the world revolves around Microsoft until we prove otherwise. So here's the benchmark I propose. First, deliver a multi-vendor SOAP-based writing-publishing system that uses no Microsoft software. Then switch out the non-Microsoft components with Microsoft pieces, one at a time, and have it still work. [Scripting News] 1:06:51 PM
|
|
|
Paolo Marcucci has a Visual Basic script that converts a Word document to OPML. He says "Next step is importing a OPML file in Word, rebuilding the document format, and using Simon's function to pack it into a SOAP message." [Scripting News] 8:03:26 AM
|
|
|
When you use a piece of software that isn't being updated, every time a new version of the OS comes out you wonder "Is this the one that won't run my favorite program?" MORE, which was last released ten years ago, back when dinosaurs roamed the earth, has become something of a Methuselah in this way. Takes a lickin, keeps on tickin. (Thanks to Lee Hinde for the screen shot.) [Scripting News] 8:02:57 AM
|
|
|
|
