Event Invitation

• CURIE: gmeow:EventInvitation
• IRI: https://blackcatinformatics.ca/gmeow/EventInvitation
• Category: class
• Defined by: gmeow:slices/calendar
• Box roles: TBox role (What is this?)

A social act inviting an agent to attend an event, reified as a relator. Models the invitation as an Agreement to attend, reusing gmeow:hasParty for the invitee and the invitation status for the response state. Standpoint-indexed: a disputed invitation status is several coexisting claims, none privileged (Principle 9).

Structure

Subclass of: gmeow:Agreement, gufo:Relator

Practical Pattern

Use gmeow:EventInvitation as a specialized kind of gmeow:Agreement, gufo:Relator. Add statement metadata or a standpoint when the assertion needs provenance, confidence, or vantage.

Example Snippets

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

Recurring Meeting

• Source: slices/core/calendar/examples/recurring-meeting.ttl
• Examples catalog: open in catalog#example-slices-core-calendar-examples-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:Agreement

External Equivalences

Equivalent or closely aligned targets: schema

Linkages

Generated from the canonical mapping DSL. SSSOM files are the generated public interchange form for term equivalences.

Term Equivalences

Usage Advice

Use when

• Use to reify the act of inviting an agent to an event as a first-class relator — so the invitee, the organizer's status, and the invitee's RSVP are each queryable and can disagree (Principle 9).

Avoid when

• Avoid flattening the invitation into a property on the event, and avoid using it for mere attendance (that is gmeow:Participation on the occurred event); the invitation is the social act, not the showing-up.

How to use

• Link it to its gmeow:invitationEvent and one or more gmeow:invitationInvitee, carry the organizer's view on gmeow:invitationStatus and the invitee's on gmeow:rsvpStatus; standpoint-index a disputed status via accordingTo rather than overwriting.

Examples

• ex:standupInvite a gmeow:EventInvitation; gmeow:invitationEvent ex:standupEvent; gmeow:invitationInvitee ex:lillith; gmeow:invitationStatus gmeow:invitationStatusAccepted.