New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schema.org support for recurring events #2

Open
ldodds opened this Issue Dec 14, 2016 · 6 comments

Comments

3 participants
@ldodds
Contributor

ldodds commented Dec 14, 2016

Schema.org doesn't currently handle recurring or scheduled events. There has been a number of discussion and proposals but not have yet been finalised.

For our use cases we need to publish and share the schedule and not just the individual sessions.

The proposal is to document a general purpose schedule property as suggested here.

@ldodds

This comment has been minimized.

Contributor

ldodds commented Dec 14, 2016

Submitted a proposal for further discussion here: schemaorg/schemaorg#1457

@ldodds ldodds self-assigned this Jan 18, 2017

ldodds added a commit that referenced this issue Feb 10, 2017

ldodds added a commit that referenced this issue Feb 10, 2017

ldodds added a commit that referenced this issue Feb 10, 2017

Merge pull request #12 from openactive/update-key-concepts
Redrafted Key Concepts based on feedback in hangout #2

@ldodds ldodds changed the title from Schema.org doesn't handle recurring events to Schema.org support for recurring events Feb 24, 2017

@ldodds

This comment has been minimized.

Contributor

ldodds commented Aug 9, 2017

After discussion this proposal turned into a pull request which has been moved into Schema.org.

schemaorg/schemaorg#1693

The terms will initially appear in the "pending" section of Schema.org and will be merged in after further testing.

@ldodds

This comment has been minimized.

Contributor

ldodds commented Aug 9, 2017

Leaving this issue open to cover any further work/revisions required before the schedule support formally becomes part of Schema.org schema.

@nickevansuk

This comment has been minimized.

Contributor

nickevansuk commented Mar 8, 2018

Referencing recent conversations for visibility: openactive/activation#107 (comment) and openactive/activation#6 (comment)

Summary: "byDay": "2TH" should be allowed; byDay should accept string as well day enum

@civsiv

This comment has been minimized.

civsiv commented Mar 23, 2018

Hi @ldodds ,
At imin, we break event schedules up into their respective individual occurrences (A event that occurs daily has 5 occurrences for example). Because of this, having schedules without an endDate is a problem for us as they go ad infinitum, and it feels a bit lazy on the provider's part. Any way we could make endDate mandatory along with the other mandatory fields such as startDate, startTime, and frequency?

@nickevansuk

This comment has been minimized.

Contributor

nickevansuk commented Jun 18, 2018

Note issues raised in #80 also

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment