Skip to content
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

Clarify Event's applicability for non-commercial and historical events #1931

Closed
RichardWallis opened this issue Jun 3, 2018 · 1 comment
Closed
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).

Comments

@RichardWallis
Copy link
Contributor

As part of an in-depth thread on the schema.org mailing list Historical Events it is clear that, although Event is equally applicable to all types of event current, historical, commercial, etc., its current description does not make this fully clear and gives the impression the that it is mainly focused on commercially oriented use cases.

This impression is reinforced by the spread of examples, only for concerts and an art event at a museum.

I propose that the description of Event is updated to better reflect its broad applicability, thus:

An event happening at a certain time past or future and location physical or virtual, such as a concert, lecture, meeting, festival, or historical event. Repeated events may be structured as separate Event objects. Where applicable ticketing information may be added via the offers property.

In addition a further example should be added demonstrating this capability:

{
  "@context": "http://schema.org",
  "@type": "Event",
  "name": "Signing of the Magna Carta",
  "startDate": "1215-06-15",
  "location": {
    "@type": "Place",
    "name": "Runnymede",
    "sameAs": "https://en.wikipedia.org/wiki/Runnymede"
  },
  "contributor": {
     "@type": "Person",
     "name": "King John of England",
     "sameAs": "http://www.wikidata.org/entity/Q129308"
  },
  "sameAs": "http://www.wikidata.org/entity/Q12519",
}

This proposal does not address potential future proposals for new types and/or properties discussed in the thread, but would be a useful enhancement if those come to fruition or not.

@github-actions
Copy link

This issue is being tagged as Stale due to inactivity.

@github-actions github-actions bot added the no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). label Jul 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).
Projects
None yet
Development

No branches or pull requests

1 participant