Use case: Status of the event

[jpmckinney]

Use case name

Determine whether an event is tentative, confirmed, cancelled, rescheduled, etc.

Please insert the status of the use case

Idea

Use case creator

James McKinney

Stakeholders

Pretty much any calendaring system, ticketing system, etc. has the concept of a "canceled" event that preserves its other properties for reference (title, description, etc.).

Problem statement

The current situation is that an event can be modelled, but its status cannot. As such, consumers of data using this vocabulary cannot determine whether an event is tentative, cancelled, etc. These states are frequently encountered in real-world scenarios like when using a calendar, buying a ticket, etc.

At present, the only option offered by this vocabulary is to delete the event if it is cancelled. However, this is not the typical approach, as it is relevant to be able to refer to the event after it is cancelled.

Existing approaches

There are codelists for status values in:

• RFC 5545 (tentative, confirmed, cancelled)
• Schema.org (cancelled, moved online, postponed, rescheduled, scheduled)

Links

No response

Requirements

Determine the status of the event (tentative, cancelled, etc.)

Related use cases

No response

Comments

No response