RSVP status

The RSVP response status as asserted by the invitee — needs-action, accepted, declined, tentative. Distinct from invitationStatus: the organizer's view and the invitee's view may disagree, and both claims coexist (Principle 9).

Structure

Property shape: object property; gmeow:EventInvitation -> gmeow:RsvpStatus

Practical Pattern

Use gmeow:rsvpStatus from gmeow:EventInvitation to gmeow:RsvpStatus when the relationship itself belongs in the native GMEOW graph.

Example Snippets

These snippets are generated from canonical slice examples and trimmed to the Turtle blocks where this term appears.

Recurring Meeting

# SPDX-FileCopyrightText: 2026 Blackcat Informatics® Inc. <paudley@blackcatinformatics.ca>
# SPDX-License-Identifier: CC-BY-4.0
#
# Worked example: a recurring meeting with invitations. A gmeow:EventSchedule
# repeats a TEMPLATE event by a gmeow:RecurrenceRule (an RFC 5545 RRULE string),
# all anchored in an explicit gmeow:TimeZone (IANA id) — so "every Monday 09:00"
# is unambiguous across DST. Invitations are reified gmeow:EventInvitations
# carrying both the organiser-side gmeow:invitationStatus and the invitee's own
# gmeow:rsvpStatus. The event's kind is an open vocabulary: there is no seed
# "meeting" EventType, so one is minted (the custom-value idiom, P9).
@prefix gmeow: <https://blackcatinformatics.ca/gmeow/> .
@prefix ex:    <https://blackcatinformatics.ca/gmeow/examples/calendar/> .
@prefix rdfs:  <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd:   <http://www.w3.org/2001/XMLSchema#> .

# --- A reified invitation: organiser status AND the invitee's own RSVP.
ex:invite a gmeow:EventInvitation ;
    gmeow:invitationEvent   ex:standup ;
    gmeow:invitationInvitee ex:dana ;
    gmeow:invitationStatus  gmeow:invitationStatusAccepted ;
    gmeow:rsvpStatus        gmeow:rsvpStatusAccepted .

Common Companion Terms

gmeow:EventInvitation, gmeow:RsvpStatus

Usage Advice

Use when

Avoid when

How to use

Examples