- From: Robert Kost <rkost@thematix.com>
- Date: Tue, 20 Dec 2011 21:20:50 -0500
- To: <public-vocabs@w3.org>
Hi Sean, I'm no authority, but insofar as schema.org seems to want to piggyback on ISO 8601 for date/time, recurrence is taken care of in section 4.5 of that standard (http://dotat.at/tmp/ISO_8601-2004_E.pdf). Does this sound right to you? Rob On 12/20/11 10:20 AM, "Sean Carlos" <sean@antezeta.com> wrote: >Hi list, > >I have several cases of repeating / recurring events, such as a >monthly business networking lunch, where the only data elements which >change from event to event are the dates. > >It appears to me that schema.org doesn't yet address this particular use >case? > >The current solution appears to be to repeat each event, including the >duplication of each data element. I'm thinking of using the search >engine frowned-upon <meta> tags to hide the repeated data in >successive event dates. > >Insights and alternatives from the trenches would be welcome. > >In a similar vein, the schema.org documentation is silent on how to >markup multiple events which occur at the same venue. There is an >example specific to Google: >http://support.google.com/webmasters/bin/answer.py?hl=en&answer=164506 >but it would be nice to see this officially documented for schema.org >AND clarity provided regarding the order of the data - i.e. the >possibility to list each event occurrence then the venue, i.e. putting >the event where it belongs, before the venue. > >best, > >Sean Carlos >-- >__________________________________________________ >Antezeta Web Marketing - Search/Social/Email/Analytics >ITA Tel: +39 02 69 000 333 http://antezeta.it/ >USA Tel: +1 617 394 1100 http://antezeta.com/ >Skype: sean-carlos >News: http://antezeta.com/news/ > http://antezeta.it/news/ >Twitter: @sean_it (italiano) > @seancarlos (English) > > >
Received on Wednesday, 21 December 2011 02:22:16 UTC