[uf-discuss] Handling hCalendar event updates on clients

[Ryan King]

On Oct 6, 2006, at 3:22 PM, Guillaume Lebleu wrote:

> Ryan King wrote:
>> I think it's good practice, not just for hCalendar, but for all  
>> web content to create permalinks which are independent of things  
>> like pagination. If you can do that, then pagination shouldn't be  
>> a problem.
> Maybe I'm missing something, but instead of a new UID element with  
> a namespace-like value, couldn't we use the id attribute of the  
> element of class vevent?
>
> The added advantage I see is that it is RESTful and I can refer to  
> an event as a URL, for instance:
>
> http://microformats.org/wiki/hcalendar-examples#someid

I suppose that you mean on a document at http://microformats.org/wiki/ 
hcalendar-examples , we'd see:

<div class="vevent" id ="someid">
...
</div>

?

If so, then, yes we could potentially use that. However, it would be  
nice to be able to declare that the same event or contact info is the  
same, across separate web resources. Eventful already does this with  
their venues.

Each event page has an hcard for the venue, each of these hcards has  
a UID property which is the permalink url for than venue on  
eventful.com. Seems pretty easy and works.

-ryan