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

Guidance for virtual and on-demand events #231

Open
nickevansuk opened this issue Mar 25, 2020 · 4 comments
Open

Guidance for virtual and on-demand events #231

nickevansuk opened this issue Mar 25, 2020 · 4 comments
Labels
proposal Proposed changes to the specification virtual events Properties for events held online (e.g. via streaming)

Comments

@nickevansuk
Copy link
Contributor

nickevansuk commented Mar 25, 2020

Proposer

ODI

Use Case

Taking into account the proposed properties, guidance is required for implementers to know which properties are required vs recommended.

Proposal

For virtual events

SessionSeries and Event

The following properties should be REQUIRED (inheriting from existing Modelling Opportunity Data specification):

  • name
  • activity
  • organizer (including a required @id to give each organizer a globally unique identifier as a URL, and recommended sameAs property for social media handles)
  • eventAttendanceMode (Add eventAttendanceMode to Event #225)
  • offers (including a recommended url that links straight to the purchase page)
  • url (to a page describing the session)

The following properties should be RECOMMENDED:

ScheduledSession and Event

The following properties should be REQUIRED (inheriting from existing Modelling Opportunity Data specification):

  • startDate

The following properties should be RECOMMENDED:

Example

Note full guidance will include the above fields, and individual ScheduledSessions.

{
  "type": "SessionSeries",
  ...
  "eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode",
  "beta:affiliatedLocation": {
    "type": "Place",
    "name": "Middlesbrough Sports Village",
    "address": {
      "type": "PostalAddress",
      "streetAddress": "Alan Peacock Way",
      "addressLocality": "Village East",
      "addressRegion": "Middlesbrough",
      "postalCode": "TS4 3AE",
      "addressCountry": "GB"
    },
    "geo": {
      "type": "GeoCoordinates",
      "latitude": 54.543964,
      "longitude": -1.20978500000001
    }
  },
  "beta:isInteractivityPreferred": true,
  "beta:participantSuppliedEquipment": "https://openactive.io/Required",
  "beta:donationPaymentUrl": "https://www.paypal.com/donate/acme_fit"
}
{
  "type": "ScheduledSession",
  ...
  "maximumVirtualAttendeeCapacity": 20,
  "beta:virtualLocation": {
    "type": "VirtualLocation",
    "name": "Zoom Video Chat",
    "url": "https://zoom.us/j/1234567890/signup",
    "description": "Please log into Zoom a few minutes before the event, and mute your mic while you wait for the session to start"
  }
}

For on-demand events

OnDemandEvent (#228)

The following properties should be REQUIRED:

  • name
  • activity
  • organizer (including a required @id to give each organizer a globally unique identifier as a URL, and recommended sameAs property for social media handles)
  • offers (including a recommended url that links straight to the purchase page)
  • url (to a page describing the session)

The following properties should be RECOMMENDED:

Example

{
  "type": "OnDemandEvent",
  ...

  "workFeatured": {
    "type": "VideoObject",
    "url": "https://www.youtube.com/watch?v=3fbCs0GVjgQ"
  },
  "beta:participantSuppliedEquipment": "https://openactive.io/Required",
  "beta:donationPaymentUrl": "https://www.paypal.com/donate/acme_fit"
}
@nickevansuk nickevansuk added proposal Proposed changes to the specification virtual events Properties for events held online (e.g. via streaming) labels Mar 25, 2020
@nickevansuk
Copy link
Contributor Author

nickevansuk commented Mar 25, 2020

Note genderRestriction was accidentally omitted from the recommended properties in the discussion today, so have added above in line with the existing status of the same property in the Modelling Opportunity Data specification.

@nickevansuk
Copy link
Contributor Author

nickevansuk commented Mar 26, 2020

Note the proposal above has been updated to reflect the revised nomenclature from the referenced issues.

@nickevansuk
Copy link
Contributor Author

Note that the above has now been updated to include #234

@nickevansuk
Copy link
Contributor Author

nickevansuk commented Apr 2, 2020

Noting the expedited addition of the required field organizer @id, to pave the way for both safeguarding and booking of virtual events

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal Proposed changes to the specification virtual events Properties for events held online (e.g. via streaming)
Projects
None yet
Development

No branches or pull requests

1 participant