Category only takes values, so you have no means of knowing what data
those values represent. Alternatively, there is the "x-prop" mechanism,
which C24 could use to define a set of extension properties with the
required meaning.
Notwithstanding Trevor's dewy-eyed optimism about how this could
actually work (see separate response), I think there would be merit in
C24 publishing a set of iCalendar extension properties, together with
some realistically detailed examples. They could then encourage
institutions to embed this data in the web pages which advertise their
events.
Where these pages are generated by code, it would be a one-off
programming job to add this extra metadata for all future events. For
sites based on a popular CMS, it might just be a matter of someone
writing a plug-in and lots of institutions deploying it.
Richard
On 18/06/2012 23:59, Andy Mabbett wrote:
> iCalendar has a "category" property, which takes multiple values.
>
> On 18 June 2012 23:05, Richard Light<[log in to unmask]> wrote:
>> 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/
>> ****************************************************************
>
>
--
*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/
****************************************************************
|