has party

Relates an agreement to an agent that is bound by it. NOT functional: an agreement binds two or more parties, and each is attached by a separate gmeow:hasParty statement.

Structure

Property shape: object property; gmeow:Agreement -> gmeow:Agent

Practical Pattern

Use gmeow:hasParty from gmeow:Agreement to gmeow:Agent 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.

Employment Contract

# SPDX-FileCopyrightText: 2026 Blackcat Informatics® Inc. <paudley@blackcatinformatics.ca>
# SPDX-License-Identifier: CC-BY-4.0
#
# Worked example: an agreement as a relator. A gmeow:Agreement (here a
# gmeow:Contract, the legally-enforceable specialization) is a gufo:Relator that
# binds its parties via gmeow:hasParty — the agreement IS the relationship, not a
# property of either party. It bears a structured gmeow:AgreementName (an
# Appellation, so multilingual co-equal titles are first-class). Other relators
# can be gmeow:foundedOn it: the employment Membership below exists BECAUSE of the
# contract, so its grounding is recorded rather than assumed.
@prefix gmeow: <https://blackcatinformatics.ca/gmeow/> .
@prefix ex:    <https://blackcatinformatics.ca/gmeow/examples/agreements/> .

# --- The contract: a relator binding the two parties, bearing a formal name.
#     (Validity bounds — gmeow:validFrom/validUntil — are statement-level RDF-1.2
#     annotations, carried in the statement layer rather than as A-box triples.)
ex:contract a gmeow:Contract ;
    gmeow:hasParty         ex:acme , ex:dana ;
    gmeow:hasAgreementName ex:contractName .

Common Companion Terms

gmeow:Agreement, gmeow:Agent

Usage Advice

Use when

Avoid when

How to use

Examples