Normative term documentation for the vcfr: namespace. This page covers classes,
properties, and alignment points to external ontologies for representing VCF files, records,
and per-sample calls in RDF.
This hierarchy summarizes the core design: file/header representation, record/call structure,
and typed definitions for INFO/FORMAT/FILTER/ALT metadata.
Loading hierarchy diagram...
Raw hierarchy is serialized in RDF 1.1 Turtle (TTL), generated from
ontology/vcf-rdfizer-vocabulary.ttl and loaded from assets/ontology-hierarchy.ttl.
Declares the VCF Type enum for INFO/FORMAT definitions.
-
Datatype Properties
Grouped by modeling concern to keep implementation and query logic predictable.
Domain notes: vcfr:fieldValue, vcfr:fieldValueInteger,
vcfr:fieldValueDecimal, and vcfr:fieldValueBoolean use rdf:Resource
as domain to allow both INFO and FORMAT value nodes to share the same property set.
The SHACL profile in shacl/vcf-rdfizer-vocabulary.shacl.ttl defines structural checks
for the core graph pattern. It validates class-specific requirements while still allowing incremental
conversion workflows (for example optional call details).
Current profile highlights: 9 node shapes and
explicit support for typed null literals via vcfr:Null on selected fields.
Enforces sample identity while allowing variable FORMAT coverage.
vcfr:InfoFieldValueShape
vcfr:InfoFieldValue
Optional vcfr:fieldValue typed as xsd:string or vcfr:Null; optional vcfr:declaredBy
Validates typed INFO value nodes without requiring a rigid minimum field set.
vcfr:FormatFieldValueShape
vcfr:FormatFieldValue
Optional vcfr:fieldValue typed as xsd:string or vcfr:Null; optional vcfr:declaredBy
Same value-node pattern as INFO, specialized for FORMAT payloads.
External Ontology Usage
External ontologies are used explicitly for compatibility instead of duplicating mature concepts.
The table below documents where and how each reference is used.