[uf-discuss] Handling hCalendar event updates on clients

Ryan King ryan at technorati.com
Fri Oct 6 14:45:02 PDT 2006

On Oct 6, 2006, at 12:04 PM, David Arango wrote:
> On 10/6/06, Ryan King <ryan at technorati.com> wrote:
>> The closest thing to a UID that people publish is a HTTP URL
>> permalink for the event description. If you just add a class name of
>> 'uid' to that hyper link, it will all work.
> URLs are good unique identifiers (the problem about namespaces is also
> solved with them) I think that using an ID attribute in every vevent
> element (so the event has a permalink) and using that permalink as UID
> the problem could be solved. That way clients could update event data
> and hCalendar-powered lists could be used as subscription channels for
> event data (applying the suitable transformations), so I think UID
> should be mandatory
> Am I mistaken? What about paginated calendars?

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.


More information about the microformats-discuss mailing list