ws-success

I have created a wiki, http://ws-success.pbwiki.com, for capturing and refining success stories about implementing distributed systems with technologies that follow ws-* standards (SOAP, WSDL, etc.)

Please feel encouraged to capture your success stories there or contribute to the stories that may already be there by adding your experience with an existing story, technology, or standard that may be part of that success.

Feel free to leave questions about the stories too, but please respect the content that may already be in place. Don't edit someone else's story unless you are contributing to a faithful rendering of a common experience.

Follow the changes with the RSS feed or the Atom feed.

Fun (and Learning) with SVG

Firefox 1.5 now supports SVG, if you've not heard the news. You can see this in action on a fun learning page about orbits and how our moon may have been created.

Next Move in Programming

Dave Thomas (the Smalltalk Dave Thomas) writes in JOT...

We need to move beyond the complexity, limitations and weaknesses of Smalltalk and Lisp but seek a language with at least as simple a syntax and more expressiveness.

Here's a programming leader who knows his stuff and I love the fact that he refers to Smalltalk and Lisp as being complex, and having limitations and weaknesses. These are not the be-all and end-all even though they are better than anything that's come along since their invention 35-45 years ago. Noodle on that: 35-45 years without a significant leap forward in programming languages.

Maybe we'll go another 100 years without that improvement. Maybe that is to be expected.

ws-success

I have created a wiki, http://ws-success.pbwiki.com, for capturing and refining success stories about implementing distributed systems with technologies that follow ws-* standards (SOAP, WSDL, etc.)

Please feel encouraged to capture your success stories there or contribute to the stories that may already be there by adding your experience with an existing story, technology, or standard that may be part of that success.

Feel free to leave questions about the stories too, but please respect the content that may already be in place. Don't edit someone else's story unless you are contributing to a faithful rendering of a common experience.

Follow the changes with the RSS feed or the Atom feed.

Get to the Point: Open Source Speech to Text

Update: Jon Udell happened to know where to find the information I was listening for. And created the excerpt.

Lisa describes how to use WebDAV to lock events, multiple events, access control, etc. Then she explains that a narrow number of features are needed specifically for calendering, e.g. how to query free/busy information on someone's calendar.

I sure wish I knew whether Lisa thinks we need a DAV extension for every kind of resource. Assuming not, why are calendars special? I think we need *conventions* for using HTTP per se to do versioning, locking, accessing, calendaring. I certainly hope we don't need extensions for every kind of resource. Oops. Isn't that like SOAP?

End Update

I am listening to a podcast, something I have done only a couple of times because I would much rather read than listen. In this case it is IT Conversations with Lisa Dusseault on calendering, CalDAV, and WebDAV.

What I most want is to know whether the question comes up as to why WebDAV and CalDAV are necessary. The logical conclusion of this approach is every resource on the web has its own application protocol... PurchaseOrderDAV, MovieDAV, ShinyObjectDAV, etc.

I don't have the time to listen to 30 minutes of conversation to see if this comes up. So I am on the lookout for a relatively easy to use and free or open source speech to text conversions.