Core Vocabulary v1.0

Cross-application schema versioning, provenance, and identity

Overview

Namespace URI:
https://ns.cascadeprotocol.org/core/v1#
Preferred Prefix:
cascade:
Version:
1.0
Status:
Stable
Schema File:
core.ttl (Turtle/RDF)

The Core Vocabulary defines cross-cutting concepts used by all Cascade Protocol health data applications. It provides essential infrastructure for schema versioning, data provenance tracking, and user identity management. Domain-specific vocabularies (e.g., pots:, ecg:) import this core vocabulary.

Download TTL Back to Documentation

Classes

cascade:DataProvenance

owl:Class

Classification of how health data was generated or collected. All data in the Cascade Protocol is tagged with provenance to distinguish consumer-generated wellness data from clinical-grade diagnostics.

Subclass of: prov:Entity

cascade:ConsumerGenerated

cascade:DataProvenance

Data generated directly by the user through personal devices in a non-clinical setting (e.g., Apple Watch POTS check).

Different from: cascade:ClinicalGenerated

cascade:ClinicalGenerated

cascade:DataProvenance

Data generated in a clinical setting under healthcare provider supervision (e.g., hospital ECG, lab results).

Different from: cascade:ConsumerGenerated

Data Properties

cascade:schemaVersion

owl:DatatypeProperty

Semantic version of the ontology schema used to serialize this data (format: major.minor.patch).

Range: xsd:string

Example: "1.2", "2.0.1"

See also: Semantic Versioning

cascade:dataProvenance

owl:ObjectProperty

Classification of how this data was generated (consumer vs clinical).

Range: cascade:DataProvenance

Example: cascade:ConsumerGenerated

cascade:creatorWebID

owl:ObjectProperty

Solid WebID URI of the user who created this data. Used for access control and data ownership tracking.

Subproperty of: prov:wasAttributedTo

Range: rdfs:Resource

Example: <https://id.cascadeprotocol.org/users/abc123>

See also: WebID Specification

Usage Example

@prefix cascade: <https://ns.cascadeprotocol.org/core/v1#> .
@prefix pots: <https://ns.cascadeprotocol.org/pots/v1#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<#pots-check-123> a pots:POTSCheckResult ;
    cascade:schemaVersion "1.2" ;
    cascade:dataProvenance cascade:ConsumerGenerated ;
    prov:wasAttributedTo <https://id.cascadeprotocol.org/users/abc123> ;
    prov:wasGeneratedBy [
        a prov:Activity ;
        prov:wasAssociatedWith <https://id.cascadeprotocol.org/users/abc123> ;
        prov:startedAtTime "2025-10-31T10:00:00Z"^^xsd:dateTime
    ] ;
    pots:date "2025-10-31T10:00:00Z"^^xsd:dateTime ;
    pots:protocol "nasaLean" .

W3C PROV-O Integration

The Cascade Protocol extends the W3C PROV-O (Provenance Ontology) for comprehensive data lineage tracking:

  • All health data entities are prov:Entity instances
  • cascade:creatorWebID links to prov:Agent (the user)
  • Generation activities tracked via prov:wasGeneratedBy
  • Temporal metadata captured with prov:startedAtTime

Design Principles

  • Modularity: Core vocabulary is stable; domain vocabularies evolve independently
  • Standards-based: Built on W3C RDF, OWL, and PROV-O recommendations
  • Solid-compatible: Designed for Solid Pod storage with WebID-based access control
  • Future-proof: New health apps can extend without breaking existing data