beta:virtualLocationas a singular not array, as multiple broadcast platforms are likely an edgecase in this sector. We agreed to re-evaluate this before moving the property out of beta.
OnDemandEvent, to easily make use of all the existing properties of Events.
workFeaturedto embed any video or other media (e.g. a
none) - to account for events where equipment is optional (an alternative is provided for those without). Consensus was that context would indicate the meaning of the attribute, with additional guidance being provided in
beta:isInteractivityPreferredboolean for now, as interaction being strictly “Required” is probably an edge case
attendeeInstructionshould be used to provide further detail if required.
maximumAttendeeCapacityproperty still exists and is used widely, and
remainingAttendeeCapacityis used heavily by the Open Booking API.
VirtualLocation, so as not confuse any logic around booking (keeping booking separate for now, and readdressing this with any additions to Open Booking API to handle virtual classes in future)
VirtualLocation(e.g. that specific Zoom room), not the entire event.
beta:affiliatedLocationwas proposed for the original locations of an online-only event, to ensure that the existing data users’ implementations would be intentionally broken by the lack of a
locationfield in all cases, and hence they would not misrepresent virtual classes as physical ones.
EventMovedOnline, which can therefore be removed.
eventAttendanceModeis set to
locationMUST NOT be included.
VirtualLocationas a beta field, but keep this RECOMMENDED
ScheduledSessionupdate to match current spec
Beginner” for now, as a short term solution to save trying to solve the larger levels problem.