Overview
- Namespace URI:
https://vitalvault.org/vocab/core#- Preferred Prefix:
vv:- Version:
- 1.0
- Status:
- Stable
- Schema File:
- core.ttl (Turtle/RDF)
The Core Vocabulary defines cross-cutting concepts used by all VitalVault 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.
Classes
vv:DataProvenance
owl:Class
Classification of how health data was generated or collected. All data in VitalVault is tagged with provenance to distinguish consumer-generated wellness data from clinical-grade diagnostics.
Subclass of: prov:Entity
vv:ConsumerGenerated
vv:DataProvenance
Data generated directly by the user through personal devices in a non-clinical setting (e.g., Apple Watch POTS check).
Different from: vv:ClinicalGenerated
vv:ClinicalGenerated
vv:DataProvenance
Data generated in a clinical setting under healthcare provider supervision (e.g., hospital ECG, lab results).
Different from: vv:ConsumerGenerated
Data Properties
vv: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
vv:dataProvenance
owl:ObjectProperty
Classification of how this data was generated (consumer vs clinical).
Range: vv:DataProvenance
Example: vv:ConsumerGenerated
vv: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://user.vitalvault.org/profile/card#me>
See also: WebID Specification
Usage Example
@prefix vv: <https://vitalvault.org/vocab/core#> .
@prefix pots: <https://vitalvault.org/vocab/pots#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
<#pots-check-123> a pots:POTSCheckResult ;
vv:schemaVersion "1.2" ;
vv:dataProvenance vv:ConsumerGenerated ;
prov:wasAttributedTo <https://user.vitalvault.org/profile/card#me> ;
prov:wasGeneratedBy [
a prov:Activity ;
prov:wasAssociatedWith <https://user.vitalvault.org/profile/card#me> ;
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
VitalVault extends the W3C PROV-O (Provenance Ontology) for comprehensive data lineage tracking:
- All health data entities are
prov:Entityinstances vv:creatorWebIDlinks toprov: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