Verification Result

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

An information object recording the outcome of a verification activity — verified, failed, unverified, expired, revoked, policy-failed, finality-pending, etc. A verification result is an observation output, not an axiom of correctness (Principle 12).

Structure

Subclass of: gmeow:InformationObject

Practical Pattern

Use gmeow:VerificationResult as a specialized kind of gmeow:InformationObject. 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.

Software Release

• Source: slices/core/attestation/examples/software-release.ttl
• Examples catalog: open in catalog#example-slices-core-attestation-examples-software-release

# SPDX-FileCopyrightText: 2026 Blackcat Informatics® Inc. <paudley@blackcatinformatics.ca>
# SPDX-License-Identifier: CC-BY-4.0
#
# Worked example: a supply-chain attestation. A gmeow:Attestation binds an
# gmeow:attester (who vouches) to an gmeow:attestedSubject (what is vouched for)
# under an gmeow:attestationType drawn from the open vocabulary of real formats
# (SLSA provenance, in-toto, DSSE, C2PA, verifiable credential, …). Here a CI
# pipeline issues a SLSA-provenance attestation over a release bundle, carries
# the signed artifact, and a relying party records a gmeow:VerificationResult —
# the attestation is a claim; verifying it is a separate, recorded act.
@prefix gmeow: <https://blackcatinformatics.ca/gmeow/> .
@prefix ex:    <https://blackcatinformatics.ca/gmeow/examples/attestation/> .
@prefix xsd:   <http://www.w3.org/2001/XMLSchema#> .

# --- Verification is its own recorded act: the deploy gate checked the chain.
ex:verifyResult a gmeow:VerificationResult ;
    gmeow:hasVerificationStatus gmeow:verificationStatusVerified ;
    gmeow:verifiedBy            ex:relyingParty .

Common Companion Terms

gmeow:InformationObject

External Equivalences

Equivalent or closely aligned targets: schema, vc

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 record the OUTCOME a verifier reached when checking an attestation — verified, failed, expired, revoked, policy-failed, finality-pending — as a held observation output carrying its own status, verifier, and time.

Avoid when

• Avoid reading a 'verified' result as a global truth verdict — it records what one verifier observed under one policy at one time, not that the underlying claim is correct (Principle 12); competing results from different verifiers coexist (Principle 9).

How to use

• Mint the result, set gmeow:hasVerificationStatus (the EL minimum), name gmeow:verifiedBy and the time, and link it from the Attestation with gmeow:verificationResult; treat a later contradicting result as another coexisting VerificationResult, not an overwrite.

Examples

• ex:verifyOutcome a gmeow:VerificationResult; gmeow:hasVerificationStatus gmeow:verificationStatusVerified.