Schema.org should say something about repeating events

[danbri]

http://schema.org/Event

Either a markup model, a blog/wiki post, ... anything!

Migrating this old issue in from https://www.w3.org/2011/webschema/track/issues/11

See also http://www.w3.org/wiki/WebSchemas/RepeatingEvents "Even if the conclusion is "describe each event individually", this should be documented."

[commadelimited]

This relates to my interests. I've been working through all Eventbrite's pages, adding Schema microformat data. Repeating events is a big thorn for us and I'd love to see what sort of solutions you can come up with.

[rvguha]

Hi Andy,

Do you have a proposal for repeating events?

guha

On Tue, Apr 21, 2015 at 9:35 AM, Andy Matthews notifications@github.com
wrote:

This relates to my interests. I've been working through all Eventbrite's
pages, adding Schema microformat data. Repeating events is a big thorn for
us and I'd love to see what sort of solutions you can come up with.

—
Reply to this email directly or view it on GitHub
#240 (comment).

[commadelimited]

@rvguha I have thoughts, but nothing concrete. It could be as simple as a master Event object, and a container for "repeatingEvents" similar to the way offers works. The master Event would have description, location, organizer, etc. while each child event would only have startDate and endDate (and perhaps a few other assorted properties). Thinking about it from an OO perspective, you define all options on a parent event, then override them as needed on each individual child.

But I feel that's such a simple approach that surely it's already been discussed and discarded?

[vickitardif]

I think in the past the discussion was derailed by examples with complicated event scheduling. For example, "every other Tuesday except when there are 5 Tuesdays in month and not in December" or some such.

It may be helpful to carve out the 90% of cases schema.org could handle and give guidance for more complicated use cases.