Helge Hess wrote:
On 30.11.2008, at 15:44, Julian Reschke wrote:Cyrus encouraged me to bring up this topic again.Its still my opinion that CardDAV itself should say nothing about that (neither MUST nor MUST NOT).
Well, if "server-picks-the-URI" is an allowed option, than the spec should state that and explain how to do it.
The rules of HTTP/WebDAV and potential extensions should apply. If a
Of course.
server supplies a POST based creation method, it should advertise that.
Yes.
A client might discover that additional option and use it (or receive a 405 or 403 or some other error if it attempts to create a resource using a regular WebDAV approach).
Yes.
I have no idea what would justify to put such a generic HTTP extension directly into CardDAV (or CalDAV BTW).
I didn't suggest to put it *into* the spec. My proposal is to make a decision (because it has led to confusion in CalDAV), and -- if the WG thinks it's a use case that should be dealt with -- to reference a document that explains how.
Furthermore, *if* the WG thinks my proposal is a good approach,we should discuss where to finish it, so that CardDAV can indeed reference it.
> Please preserve the proper protocol layering. Yes, exactly the same way we're doing it with ext-mkcol. Best regards, Julian _______________________________________________ VCARDDAV mailing list VCARDDAV at ietf.org https://www.ietf.org/mailman/listinfo/vcarddav