Re: [uf-discuss] Handling hCalendar event updates on clients
Ryan King wrote: I suppose that you mean on a document at http://microformats.org/wiki/hcalendar-examples , we'd see: ... ? Yes, this is what I meant. 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. I had missed this requirement. And with this one in mind, I think your solution is indeed pretty easy and works. And by the way, in case you had not checked, it is compatible with the original RFC2445. "The identifier is RECOMMENDED to be the identical syntax to the [RFC 822] addr-spec." something like [EMAIL PROTECTED] It is a RECOMMEND, not a MUST, and given the circumstances, I think permalink makes much more sense than a unique generated dummy address. Guillaume ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Handling hCalendar event updates on clients
On 10/6/06, Ryan King <[EMAIL PROTECTED]> 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. I agree, but I think that microformats should go forth with this, the specification should require every event to have a permalink, so it could have an unique identifier that could be used by clients to update event data. Thank you Ryan -- David Arango el único desarrollador con una orden de alejamiento de Jeffrey Zeldman Simplelogica.net, ahora con un 33,3% más de intromisión en listas de correo Cuando no hago otra cosa escribo en mildiez.net ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Handling hCalendar event updates on clients
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: ... ? 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 ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Handling hCalendar event updates on clients
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 Guillaume ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Handling hCalendar event updates on clients
On Oct 6, 2006, at 12:04 PM, David Arango wrote: On 10/6/06, Ryan King <[EMAIL PROTECTED]> 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. -ryan ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Handling hCalendar event updates on clients
On 10/6/06, Ryan King <[EMAIL PROTECTED]> wrote: For what it's worth, some people already do this. The biggest being eventful.com. Here's a list of hCalendar events with UIDs by domain: Wow, thank you for that information, Ryan -- David Arango el único desarrollador con una orden de alejamiento de Jeffrey Zeldman Simplelogica.net, ahora con un 33,3% más de intromisión en listas de correo Cuando no hago otra cosa escribo en mildiez.net ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Handling hCalendar event updates on clients
On 10/6/06, Ryan King <[EMAIL PROTECTED]> 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? -- David Arango el único desarrollador con una orden de alejamiento de Jeffrey Zeldman Simplelogica.net, ahora con un 33,3% más de intromisión en listas de correo Cuando no hago otra cosa escribo en mildiez.net ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Handling hCalendar event updates on clients
On Oct 6, 2006, at 11:30 AM, Ryan King 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. For what it's worth, some people already do this. The biggest being eventful.com. Here's a list of hCalendar events with UIDs by domain: www.royalpalmshotel.com3 www.jnrowe.ukfsn.org 39 eventful.com 117,989 www.vyre.com 1 www.visionesbizarras.com 1 guildcenter.net 14 skamania.com 49 www.thesession.org19 microformats.org 1 www.skamania.com 66 www.mikerumble.co.uk 3 beta.skamania.com 9 beta.royalpalmshotel.com 1 www.midgard-project.org6 thesession.org10 www.lsbu.ac.uk 9 guildbank.tirsen.com 13 -ryan ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Handling hCalendar event updates on clients
On Oct 6, 2006, at 9:04 AM, David Arango wrote: Hi, Yesterday I was on Molly Holzschlag's workshop on Fundamentos Web [1], she talked a bit about hCalendar, and I remembered that I used the fantastic X2V [2] to subscribe my google calendar to Fundamentos Web's hCalendar [3]. I went to google calendar to see my event subscription and it was outdated. Then, I tried to update my subscription, but I had to delete previous versions of the events (it did not update my events at all). I think there is an important issue with hCalendar and unique ids (UID) very few people are using UIDs on hCalendar markup ¿shouldn't it become mandatory? People don't commmonly publishing anything like a UID when they publish data on the web. There's been discussion before about requiring and/or synthesizing UIDs, but there's hasn't been much come out of those discussions. 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. -ryan ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
[uf-discuss] Handling hCalendar event updates on clients
Hi, Yesterday I was on Molly Holzschlag's workshop on Fundamentos Web [1], she talked a bit about hCalendar, and I remembered that I used the fantastic X2V [2] to subscribe my google calendar to Fundamentos Web's hCalendar [3]. I went to google calendar to see my event subscription and it was outdated. Then, I tried to update my subscription, but I had to delete previous versions of the events (it did not update my events at all). I think there is an important issue with hCalendar and unique ids (UID) very few people are using UIDs on hCalendar markup ¿shouldn't it become mandatory? I'm also worried about recurring events ¿how do I track recurring events if an event doesn't have an UID? (also, I did not found a recurring event thing on hCalendar specification). Onother thing I miss on hCalendar is a way to link different pages of events, in web format we usually paginate event pages ¿how may I link a calendar if it's distributed on 5 pages? ¿do I need 5 links? Thank you for your patience with my english. [1] http://www.fundamentosweb.org/2006/index.html.en [2] http://suda.co.uk/projects/X2V/ [3] http://www.fundamentosweb.org/2006/programa/index.html.en -- David Arango el único desarrollador con una orden de alejamiento de Jeffrey Zeldman Simplelogica.net, ahora con un 33,3% más de intromisión en listas de correo Cuando no hago otra cosa escribo en mildiez.net ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
