Микроразметка Schedule
Узнайте как описать регулярные события с помощью микроразметки Schedule.
Schedule - Тип Schema.org
Описание: Расписание определяет повторяющийся временной период, используемый для описания регулярно происходящего События. Как минимум, расписание будет указывать repeatFrequency, который описывает интервал между событиями. Дополнительная информация может быть предоставлена для более точного определения расписания. Сюда входит указание дней недели или месяца, когда происходит повторяющееся событие, а также его начальное и конечное время. В расписании также могут указываться даты начала и окончания, чтобы определить активный период, например, для определения ограниченного календаря событий.
Микроразметка Schedule используется для описания повторяющегося временного периода, который характеризует регулярно происходящее событие. Важной частью является указание повторяющейся частоты (repeatFrequency), интервала между событиями. Дополнительная информация позволяет более точно определить расписание, включая дни недели или месяца проведения события, его начальное и конечное время. Также можно указать начальную и конечную даты события, чтобы определить его активный период.
Свойство | Ожидаемый тип | Описание |
---|---|---|
Properties from Schedule | ||
byDay |
DayOfWeek или Text | 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. |
byMonth |
Integer | Defines the month(s) of the year on which a recurring Event takes place. Specified as an Integer between 1-12. January is 1. |
byMonthDay |
Integer | Defines the day(s) of the month on which a recurring Event takes place. Specified as an Integer between 1-31. |
byMonthWeek |
Integer | Определяет недели месяца, в которые происходит повторяющееся событие. Указывается в виде целого числа от 1 до 5. Для большей ясности использовать вместе с byDay для обозначения концепций, таких как первый и третий понедельники месяца. |
duration |
Duration | The duration of the item (movie, audio recording, event, etc.) in ISO 8601 date format. |
endDate |
Date или DateTime | The end date and time of the item (in ISO 8601 date format). |
endTime |
DateTime или Time | 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.Note that Event uses startDate/endDate instead of startTime/endTime, even when describing dates with times. This situation may be clarified in future revisions. |
exceptDate |
Date или DateTime | 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. |
repeatCount |
Integer | Defines the number of times a recurring Event will take place. |
repeatFrequency |
Duration или Text | 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. |
scheduleTimezone |
Text | Indicates the timezone for which the time(s) indicated in the Schedule are given. The value provided should be among those listed in the IANA Time Zone Database. |
startDate |
Date или DateTime | The start date and time of the item (in ISO 8601 date format). |
startTime |
DateTime или Time | 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.Note that Event uses startDate/endDate instead of startTime/endTime, even when describing dates with times. This situation may be clarified in future revisions. |
Properties from Thing | ||
additionalType |
Text или URL | 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. Typically the value is a URI-identified RDF class, and in this case corresponds to the use of rdf:type in RDF. Text values can be used sparingly, for cases where useful information can be added without their being an appropriate schema to reference. In the case of text values, the class label should follow the schema.org style guide. |
alternateName |
Text | Псевдоним для элемента. |
description |
Text или TextObject | Описание элемента. |
disambiguatingDescription |
Text | Подсвойство описания. Краткое описание элемента, используемое для различения от других, схожих элементов. Для того чтобы описание было полезным для разрешения неоднозначности, может потребоваться информация из других свойств (в частности, name). |
identifier |
PropertyValue или Text или URL | The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See background notes for more details. |
image |
ImageObject или URL | An image of the item. This can be a URL or a fully described ImageObject. |
mainEntityOfPage |
CreativeWork или URL | Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See background notes for details. Обратное свойство: mainEntity |
name |
Text | Название элемента. |
potentialAction |
Action | Указывает на потенциальное действие, описывающее идеализированное действие, в котором этот объект мог бы выполнять роль 'объекта'. |
sameAs |
URL | URL страницы для ссылки, однозначно указывающей на идентичность объекта. Например, URL страницы объекта на Википедии, записи в Wikidata или официального веб-сайта. |
subjectOf |
CreativeWork или Event | Свойство Schema.org - subjectOf: A CreativeWork or Event about this Thing. Обратное свойство: about |
url |
URL | URL объекта. |
Instances of
Schedule may appear as a value for the following properties
Свойство | On Types | Описание |
---|---|---|
courseSchedule | CourseInstance | Represents the length and pace of a course, expressed as a Schedule. |
eventSchedule | Event | Associates an Event with a Schedule. There are circumstances where it is preferable to share a schedule for a series of repeating events rather than data on the individual events themselves. For example, a website or application might prefer to publish a schedule for a weekly gym class rather than provide data on every event. A schedule could be processed by applications to add forthcoming events to a calendar. An Event that is associated with a Schedule using this property should not have startDate or endDate properties. These are instead defined within the associated Schedule, this avoids any ambiguity for clients using the data. The property might have repeated values to specify different schedules, e.g. for different months or seasons. |
Source
https://github.com/schemaorg/schemaorg/issues/1457
Examples
Example 1
Copied
Example notes or example HTML without markup.
A Tai-Chi class runs throughout 2017. The class occurs weekly, every Wednesday at 7pm.
Example encoded as JSON-LD in a HTML script tag.
<script type="application/ld+json"> { "@context": "https://schema.org/", "@type": "Event", "url": "http://www.example.org/events/1", "name": "Tai chi Class", "description": "A weekly Tai-Chi class", "duration": "PT60M", "eventSchedule": { "@type": "Schedule", "startDate": "2017-01-01", "endDate": "2017-12-31", "repeatFrequency": "P1W", "byDay": "https://schema.org/Wednesday", "startTime": "19:00:00", "endTime": "20:00:00", "scheduleTimezone": "Europe/London" } } </script>
Structured representation of the JSON-LD example.
Example 2
Copied
Example notes or example HTML without markup.
A Meetup takes place on the 1st and 15th of every month between 9-10am
Example encoded as JSON-LD in a HTML script tag.
<script type="application/ld+json"> { "@context": "https://schema.org/", "@type": "Event", "name": "Example Meetup", "eventSchedule": { "@type": "Schedule", "repeatFrequency": "P1M", "byMonthDay": [1,15], "startTime": "09:00:00", "endTime": "10:00:00", "scheduleTimezone": "America/Glace_Bay" } } </script>
Structured representation of the JSON-LD example.
Example 3
Copied
Example notes or example HTML without markup.
Starting from 2th December an Event will run daily between 9-10am for 10 occurences.
Example encoded as JSON-LD in a HTML script tag.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Event", "name": "Count Example", "eventSchedule": { "@type": "Schedule", "startDate": "2016-12-24", "repeatFrequency": "P1D", "repeatCount": 10, "startTime": "09:00:00", "endTime": "10:00:00", "scheduleTimezone": "Europe/London" } } </script>
Structured representation of the JSON-LD example.
Example 4
Copied
Example notes or example HTML without markup.
An Event runs twice a day, at 9am-10am and 2pm-3pm but only Monday to Friday
Example encoded as JSON-LD in a HTML script tag.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Event", "name": "Example", "eventSchedule": [ { "@type": "Schedule", "repeatFrequency": "P1D", "byDay": [ "https://schema.org/Monday", "https://schema.org/Tuesday", "https://schema.org/Wednesday", "https://schema.org/Thursday", "https://schema.org/Friday" ], "startTime": "09:00:00", "endTime": "10:00:00", "scheduleTimezone": "America/Glace_Bay" }, { "@type": "Schedule", "repeatFrequency": "P1D", "byDay": [ "https://schema.org/Monday", "https://schema.org/Tuesday", "https://schema.org/Wednesday", "https://schema.org/Thursday", "https://schema.org/Friday" ], "startTime": "14:00:00", "endTime": "15:00:00", "scheduleTimezone": "America/Glace_Bay" } ] } </script>
Structured representation of the JSON-LD example.
Example 5
Copied
Example notes or example HTML without markup.
An Event runs on the second Monday of every month, from 6pm-7:30pm. Because this kind of recurrence goes beyond that expressible using <a href="https://schema.org/DayOfWeek">https://schema.org/DayOfWeek</a>, it is specified instead using iCal's <a href="https://icalendar.org/iCalendar-RFC-5545/3-8-5-3-recurrence-rule.html">syntax for byDay recurrence rules</a>.
Example encoded as JSON-LD in a HTML script tag.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Event", "name": "Example", "eventSchedule": [ { "@type": "Schedule", "repeatFrequency": "P1M", "byDay": "2MO", "startTime": "18:00:00", "endTime": "19:30:00", "scheduleTimezone": "Asia/Shanghai" } ] } </script>
Structured representation of the JSON-LD example.
Example 6
Copied
Example notes or example HTML without markup.
A reading series occuring the first and third Wednesdays of the month.
Example encoded as JSON-LD in a HTML script tag.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "LiteraryEvent", "name": "Local Bookseller Author Night", "description": "Join us the first and third Wednesdays of each month for readings by local authors.", "eventSchedule": { "@type": "Schedule", "byDay": "https://schema.org/Wednesday", "byMonthWeek": [1, 3], "startTime": "20:00:00", "endTime": "22:00:00" } } </script>
Structured representation of the JSON-LD example.