Extending EventStatusType (was Re: Scores for head to head events)

In addition to the existing http://schema.org/EventStatusType enumeration:

   - EventCancelled
   - EventPostponed
   - EventRescheduled
   - EventScheduled

Eleni observes that the following are missing:

   - EventInProgress
   - EventDelayed - an event is impeded from starting (i.e. moving from
   EventScheduled to EventDelayed) *[my interpretation]*

Richard suggests adding:

   - EventPaused - an event is in a scheduled intermission (e.g. half-time,
   drinks break, time-out - but not "Rain Stopped Play"?) *[my
   interpretation]*.

I would also propose adding:

   - EventSuspended - a started event is temporarily halted (i.e. moving
   from EventInProgress to EventSuspended, e.g. "Rain Stopped Play" or
   "Waterlogged Pitch" or "Crowd Invasion")



On 25 November 2015 at 17:41, Eleni Mikroyannidi <
Eleni.Mikroyannidi@bbc.co.uk> wrote:

> I like the modelling around measurements; it is quite general so it can
> fit for multiple purposes.
>
> The status of an event can also be inferred from the start and endDate of
> the event; e.g. If a competition has a startDate and no endDate then it's
> probably in progress or it hasn't happened yet….
>
> I think stating these things explicitly rather than inferring them  its
> more to the general approach of modelling in schema.org. This can be
> modelled by extending the EventStatusType: At the moment it has the
> following enumeration:
>
>    - EventCancelled
>    - EventPostponed
>    - EventRescheduled
>    - EventScheduled
>
> So it's missing EventInProgress status and EventDelayed.
>
> On 25/11/2015 17:35, "Daniel Stieglitz" <dstieglitz@stainlesscode.com>
> wrote:
>
> Paul is absolutely correct in saying that event status is key and we
> should work on defining an appropriate life cycle for events.
>
> There are a number of nuances when it comes to event status, much like
> with defining results. For example, games can be finished ("Completed,")
> but official results are tabulated sometimes hours later, which often
> require a separate state ("Closed, e.g.). At the most basic level we'd
> probably need Scheduled--->In Progress--->Delayed--->Postponed,
> Cancelled--->Completed. Plus sport-specific options where applicable.
> EventStatusType has additionalType semantics which could be used to achieve
> this narrowing.
>
>