[Ietf-caldav] Going from browser to application
mike.shaver at gmail.com
Wed May 17 18:33:54 PDT 2006
On 5/18/06, Lisa Dusseault <lisa at osafoundation.org> wrote:
> I don't quite make sense of your scenario as an application of the davmount
> scheme. What I meant to convey, was that calendars might also usefully be
> advertised in Web pages and other content that contains links. That's where
> the HTML comes in.
But how is this related to "a browser might be able to display this,
but the user may wish to have another application handle it instead"?
I'm a little lost, I fear. You're not sending back something that you
expect a browser to display (other than via the default-XML
presentation it might provide), as I understand your example.
If the question is "should we have a descriptor format for
calendars?", then I think a MIME type makes a lot of sense for
indicating that that's what you're handing back, but that doesn't seem
like a strategic direction. (I have to say that I do sort of like
protocol schemes for some of these cases, because you're talking about
how to get a calendar resource -- "my free-busy for this month" -- and
not what the format of the resulting data is. If the http: scheme had
a standard way to encode method and request payload, that would be
even more nicely pure, but here we are.)
More information about the Ietf-caldav