[Ietf-caldav] Creating a calendar

[Bernard Desruisseaux]

Lisa,

Actually, I did look at WebDAV ACL today and I couldn't
find any report that would allow me to ask "Who am I?".

Which of the 4 WebDAV REPORTs do you have in mind exactly?

Cheers,
Bernard

Lisa Dusseault wrote:
> Could be provisioning, yes.  For example, a CalDAV server might create 
> the collections only when the user first logs in to an authorized 
> account (LDAP or other).  Or there might be a Web page for requesting a 
> calendar repository.  I think this is not a requirement for CalDAV to 
> cover but I may be wrong about the use cases.
> 
> I also like the idea of looking at the principal resource to find out 
> more information like where the user's calendar is homed, where the 
> user's other file sharing space can be found, etc.  CalDAV would only 
> have to define a property on the principal resource for this to work -- 
> the principal resources are locatable through special ACL REPORTs.  I 
> would expect the CalDAV server to manage this property value, rather 
> than have the client attempt to set it.
> 
> When a user logs in, the ACL standard defines a REPORT to ask "who am 
> I". With that report the client gets the mapping from the user's login 
> ID to a principal URL.
> 
> Lisa
> 
> 
> On Aug 26, 2004, at 1:05 PM, Bernard Desruisseaux wrote:
> 
>> I see calendar creation more as a provisioning issue, and
>> thus probably outside the scope of CalDAV.
>>
>> A user could find the location of his calendars by looking
>> at the "calendars" property (see section 11.2) of his own
>> principal resource (e.g., http://example.com/users/bernard)
>> assuming the user knows the URL of his own principal resource.
>> I don't actually know how he would though.
>>
>> Cheers,
>> Bernard
>>
>> Cyrus Daboo wrote:
>>
>>> Presumably the client uses MKCOL to create a new calendar container, 
>>> but it has to include a body in the http request with suitable data 
>>> to indicate which of the new collection resource types it wants to 
>>> create. Or can it change the resourcetype after creating the 
>>> collection? If the former we need to define the http request body for 
>>> creating new collection resource types. Would that be a blob of xml? 
>>> The WebDAV spec does not define what MKCOL request bodies are....
>>> Also, who gets to create the event, alarm, todo etc collections 
>>> within the calendar resource? Presumably the server should do that 
>>> when MKCOL + http body is executed? Or is the client expected to do 
>>> create the component containers the first time it needs to write a 
>>> component? Again the MKCOL + http body issue would arise.
>>
>>
>>
>> _______________________________________________
>> Ietf-caldav mailing list
>> Ietf-caldav at osafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/ietf-caldav
> 
>