execution status
- CURIE:
gmeow:executionStatus - IRI: https://blackcatinformatics.ca/gmeow/executionStatus
- Category: property
- Defined by:
gmeow:slices/procedures - Box roles: RBox role (What is this?)
The status of an execution occurrence, drawn from the open gmeow:ExecutionStatus value vocabulary. Non-functional: competing assessments from different monitoring sources coexist (Principle 9).
Structure
Property shape: object property; gmeow:Execution -> gmeow:ExecutionStatus
Practical Pattern
Use gmeow:executionStatus from gmeow:Execution to gmeow:ExecutionStatus 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.
Data Pipeline
- Source:
slices/extensions/procedures/examples/data-pipeline.ttl - Examples catalog: open in catalog#example-slices-extensions-procedures-examples-data-pipeline
# SPDX-FileCopyrightText: 2026 Blackcat Informatics® Inc. <paudley@blackcatinformatics.ca>
# SPDX-License-Identifier: CC-BY-4.0
#
# Worked example: a procedure separates CONTROL flow from DATA flow . A
# gmeow:Procedure has gmeow:ProcedureSteps; gmeow:ControlFlow edges say in what
# ORDER steps run, while gmeow:DataFlow edges say WHICH DATA moves between them —
# two distinct graphs over the same steps, because "runs after" and "depends on
# the output of" are different relations. A gmeow:Execution is one concrete RUN of
# the procedure, with an gmeow:executionStatus and its participant. The same model
# covers a recipe, a lab protocol, a CI build, and an agent flow (procedureType).
@prefix gmeow: <https://blackcatinformatics.ca/gmeow/> .
@prefix ex: <https://blackcatinformatics.ca/gmeow/examples/procedures/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
# --- One concrete run of the procedure, succeeded.
ex:run a gmeow:Execution ;
gmeow:executesProcedure ex:pipeline ;
gmeow:executionStatus gmeow:executionStatusSucceeded ;
gmeow:executionParticipant ex:scheduler .