Availability Plan

The operational lifecycle state of an availability plan.

The authoring shape of an availability plan, such as a single slot, recurring schedule, exception, or availability window.

Concrete bookable availability occurrences generated or authored from a listing or availability plan.

The number of booking units included in the default purchasable unit, interpreted with bookingUnitType.

The unit a customer buys or books against an offer, such as minutes, hours, days, nights, or a custom unit.

The named facility resource selected by an availability plan, concrete slot, reservation, or transaction item.

An RFC6570 URI template used to generate a stable identifier for each occurrence produced by a schedule.

Per-occurrence metrics rollups for concrete availability slots or generated occurrence keys.

The maximum number of people who can attend or be booked into an event, venue, or availability plan.

The maximum number of resource uses available for a facility or slot-style opportunity.

The offer or set of offers available for an event, facility use, availability slot, or other item. In TMC this is projected from the parent listing and its offer options, with occurrence-level overrides when a slot has different price or availability.

The parent availability plan that an exception or override applies to.

The OpenActive event type that should be assigned to occurrences generated from a schedule, such as ScheduledSession for recurring classes or sessions.

A human-readable note about how an availability plan is scheduled when the structured schedule fields do not tell the whole story.

The IANA time zone used to interpret dates, times, schedules, and generated availability occurrences.

An RFC6570 URL template used to construct an action target or a stable public URL for generated schedule occurrences.

Defines the day(s) of the week on which a recurring Event takes place. May be specified using either DayOfWeek, or alternatively Text conforming to iCal's syntax for byDay recurrence rules.

Defines the month(s) of the year on which a recurring Event takes place. Specified as an Integer between 1-12. January is 1.

Defines the day(s) of the month on which a recurring Event takes place. Specified as an Integer between 1-31.

Defines the week(s) of the month on which a recurring Event takes place. Specified as an Integer between 1-5. For clarity, byMonthWeek is best used in conjunction with byDay to indicate concepts like the first and third Mondays of a month.

The duration of the item (movie, audio recording, event, etc.) in ISO 8601 date format.

The end date and time of the item (in ISO 8601 date format).

The endTime of something. For a reserved event or service (e.g. FoodEstablishmentReservation), the time that it is expected to end. For actions that span a period of time, when the action was performed. E.g. John wrote a book from January to December. For media, including audio and video, it's the time offset of the end of a clip within a larger file.\n\nNote that Event uses startDate/endDate instead of startTime/endTime, even when describing dates with times. This situation may be clarified in future revisions.

Defines a Date or DateTime during which a scheduled Event will not take place. The property allows exceptions to a Schedule to be specified. If an exception is specified as a DateTime then only the event that would have started at that specific date and time should be excluded from the schedule. If an exception is specified as a Date then any event that is scheduled for that 24 hour period should be excluded from the schedule. This allows a whole day to be excluded from the schedule without having to itemise every scheduled event.

An RFC6570 URI template used to generate a stable identifier for each occurrence produced by a schedule.

Defines the number of times a recurring Event will take place.

Defines the frequency at which Events will occur according to a schedule Schedule. The intervals between events should be defined as a Duration of time.

The OpenActive event type that should be assigned to occurrences generated from a schedule, such as ScheduledSession for recurring classes or sessions.

The start date and time of the item (in ISO 8601 date format).

The startTime of something. For a reserved event or service (e.g. FoodEstablishmentReservation), the time that it is expected to start. For actions that span a period of time, when the action was performed. E.g. John wrote a book from January to December. For media, including audio and video, it's the time offset of the start of a clip within a larger file.\n\nNote that Event uses startDate/endDate instead of startTime/endTime, even when describing dates with times. This situation may be clarified in future revisions.

The IANA time zone used to interpret dates, times, schedules, and generated availability occurrences.

An RFC6570 URL template used to construct an action target or a stable public URL for generated schedule occurrences.

The date and time after which the offered item, space, service, reward, or benefit is no longer available for use, redemption, access, pickup, or fulfillment.

The availability authoring rules attached to a listing, used for schedules, recurrence, exceptions, capacity defaults, and plan-level overrides.

The schedule model used to represent a listing's availability, such as a single date/time, recurring time slots, day-based availability, work hours, or no schedule.

A derived availability summary stored on the listing for fast search filters, such as days of week, time of day, next start time, and generation window.

Concrete bookable availability occurrences generated or authored from a listing or availability plan.

The date and time when the offered item, space, service, reward, or benefit becomes available for use, redemption, access, pickup, or fulfillment.

The current availability state of the offer, such as in stock, sold out, preorder, or limited availability.

Whether an event or listing should be presented as a dense set of time slots rather than a small set of individually named sessions.

An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. In RDFa syntax, it is better to use the native RDFa syntax - the 'typeof' attribute - for multiple types. Schema.org tools may have only weaker understanding of extra types, in particular those defined externally.

An alias for the item.

A description of the item.

A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation.

The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc.

An image of the item. This can be a URL or a fully described ImageObject.

Type to which this subject belongs. Use for membership in a value set (Enumeration), not inheritance. Example: K2 instanceOf mountain; volcano subClassOf mountain.

Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See background notes for details.

The name of the item.

Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.

Associates a term with another vocabulary term that is useful to understand alongside it, without claiming hierarchy or equivalence.

URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website.

A CreativeWork or Event about this Thing.

URL of the item.