Andy,
iCalendar would encode the basic "where and when" of an event, but Ruth
has come back with some additional information which C24 need
(free-to-attend; event type, etc.) How would that work with hCalendar?
Could it accommodate concepts from a different "namespace"? If not, I
guess we would be looking at RDFa as an implementation framework.
Richard
On 18/06/2012 17:39, Andy Mabbett wrote:
> On 18 June 2012 14:47, Ruth Harper<[log in to unmask]> wrote:
>
>> There isn't a standard way to collect and distribute events data
> Oh yes there is: the iCalendar standard:
>
> http://en.wikipedia.org/wiki/iCalendar
>
> If each institution marks up its events, on its own website, with the
> hCalendar microformat:
>
> http://en.wikipedia.org/wiki/hCalendar
>
> then they can be parsed as iCalendar events by freely available tools,
> and read into databases/ calendar apps, for reuse elsewhere.
>
> Events can also be published in RDFa/ microdata/ as Linked Data, using
> iCalendar parameters, or as separate iCalendar files, but hCalendar
> offers a low barrier-of-entry. It used by, for example, Upcoming, and
> is also recognised by Google for their search indexes.
>
> I'm happy to expand on this here, or to offer assistance to
> organisations wishing to implement it.
>
--
*Richard Light*
****************************************************************
website: http://museumscomputergroup.org.uk/
Twitter: http://www.twitter.com/ukmcg
Facebook: http://www.facebook.com/museumscomputergroup
[un]subscribe: http://museumscomputergroup.org.uk/email-list/
****************************************************************
|