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?
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.