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)
{
"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"
}
}
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:
duration
description
image
level (#82) - using the string "Beginner" for beginner friendly classes
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.
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
andEvent
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 recommendedsameAs
property for social media handles)eventAttendanceMode
(#225)offers
(including a recommendedurl
that links straight to the purchase page)url
(to a page describing the session)The following properties should be RECOMMENDED:
description
image
level
(#82) - using the string "Beginner
" for beginner friendly classesageRange
genderRestriction
beta:isFirstSessionAccessibleForFree
(#232)beta:isInteractivityPreferred
(#230)beta:participantSuppliedEquipment
(#229)beta:affiliatedLocation
(#227)maximumVirtualAttendeeCapacity
(#226)beta:donationPaymentUrl
(#234)ScheduledSession
andEvent
The following properties should be REQUIRED (inheriting from existing Modelling Opportunity Data specification):
startDate
The following properties should be RECOMMENDED:
duration
endDate
beta:virtualLocation
(#224) (including aurl
to the live class itself, e.g. a Facebook Live or Zoom URL)Example
Note full guidance will include the above fields, and individual ScheduledSessions.
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 recommendedsameAs
property for social media handles)offers
(including a recommendedurl
that links straight to the purchase page)url
(to a page describing the session)The following properties should be RECOMMENDED:
duration
description
image
level
(#82) - using the string "Beginner" for beginner friendly classesageRange
genderRestriction
beta:isFirstSessionAccessibleForFree
(#232)beta:participantSuppliedEquipment
(#229)beta:donationPaymentUrl
(#234)workFeatured
(#228)Example
The text was updated successfully, but these errors were encountered: