Re: "Google calendar" use case

Yes you¹re right.

What I was referring to was the functionality on the ³share this calendar²
tab which either requires you to publish the calendar or only open it up to
certain people.

But doesn¹t the functionality you¹re referring to just create another public
URI to the same resource/content? That is, the only thing ³private² about
this URI is its name, right?

Dan


On 23/01/2010 16:26, "Jonathan Rees" <jar@creativecommons.org> wrote:

> (re ACTION-278)
> 
> Dan,
> 
>>   <DKA> After just trying to share a Google calendar I can confirm
>>   that that seems to be how it works. The URI does not allow automatic
>>   access to the calendar. It seems to encode expected access
>>   credentials but still requires a credentials check (authentication).
> 
> My experience contradicts yours. When I go to my google calendar UI
> and click on the little down-arrow next to one of my calendars, and
> select "Share this calendar", then select the "calendar details" tab
> and go down to "private address", then click on "html", I see the
> following:
> 
>    Please use the following address to access your calendar in any web
> browser.
> 
>    
> https://www.google.com/calendar/hosted/creativecommons.org/embed?src=jar%40cre
> ativecommons.org&ctz=America/New_York&pvttk=123487r879579879874239847
> 
>    You can embed Google Calendar in your website or blog. Use our
> configuration tool to generate the HTML you need.
> 
>    Warning: Anyone who sees this link will be able to view all event
> details of this calendar.
> 
> [URI changed so you can't see my dentist appointments.]
> 
> I can then go use this URI in a different browser that has no
> Google-related authorization, and I can see the calendar with no
> authentication dialog.
> 
> Jonathan
>