sdg-corpora — Signals Data Governance corpora

Independently-versioned home for the ontology-grounded SDG corpora. Each commit is a reproducible convergence snapshot of the whole derivation chain — ontology → SKOS vocabulary → DDL footprint → corpus. Consumed via git submodule by aegir (train/eval), atelier (independent classification), and signals (governance).

Layout

dir	what	role
ontology/	540-template catalog (7 families), sdg-vocab.ttl, family_complex.json	the source
vocabulary/	annotations.{csv,parquet} (Atelier ReferenceCategory) + vocabulary.ttl (SKOS)	the shared type-system key, derived from the ontology
ddl/	deterministic relational footprint (CREATE TABLEs + cross-family FKs)	the schema
corpus/	generated textbook documents + populated relational tables (views on the footprint)	the data (added by generation runs)

The SKOS vocabulary (vocabulary/)

548 concepts: 7 BFO/CCO upper anchors (bfo:Process, cco:Artifact, cco:*ICE, …) + 540 template leaves — hierarchical (code / notation / label / abbrev / parent_code / description). It is grounded: the codes are the ontology (bfo_anchor_path → hierarchy; template → leaf). Regenerate via aegir/scripts/build_skos_vocab.py.

Releases (for Atelier's git data source)

A tagged release packages vocabulary/annotations.parquet + ontology/ + the populated DDL tables — without the per-column reference codes. Atelier pins the release and classifies columns into the SKOS vocabulary blind (values + vocab only); the reference (column→code, deterministic from the spine) is held back as the scoring key → independent, pre-training efficacy feedback on the corpus, and a clean measure of Aegir's downstream lift over it.

Loading the relational corpus into PostgreSQL

The parquet files under ddl/<run>/ remain the dataset of record; ddl/<run>/sql/ is the directly-loadable projection, one database flavor per directory:

flavor	schema source
sql/postgres/	assembled from the recorded column specs, types mapped by polyglot_sql
sql/trino/	the native ddl_text
sql/spark/	the Iceberg flavor (ddl_iceberg)

Each directory is self-contained — load the files in numeric order:

just load-postgres                                     # psql defaults ($PGHOST, $PGPORT, …)
just load-postgres "postgresql://user@host:5432/mydb"  # explicit connection

Every table carries its template/BFO provenance in-database as a table comment (SELECT obj_description('<table>'::regclass);), and the ontology↔table associations ship beside the SQL in ddl/<run>/ontology_entity_associations.json — a loaded database remains fully tag-able back to the ontology.

The comprehensive lowering (ddl-comprehensive/)

Where ddl/ is the 520-table catalog spine WITH row data and views, ddl-comprehensive/ is kvasir's deterministic schema over the ENTIRE certified union — every entity class, junction, and closed vocabulary the ontology carries (~5k relations, schema-only), each with its ontological source in ontology_entity_associations.json and its election citation in plan.json. FK constraints ship as a post-CREATE pass, so one command loads it anywhere:

just load-comprehensive "postgresql://user@host:5432/mydb"

Shipped only under a green HermiT certificate (certificate.json records the verdict).

Loading the ontology in Protégé

This repository is standalone: a fresh clone loads with nothing but its own files.

1. File → Open → ontology/sdg-ontology-comprehensive.owl — the comprehensive release: the catalog and the entity generations, with armed rdfs:domain/range semantics and BFO/CCO grounding — the certified union (HermiT-verified; see ontology/HERMIT_CERTIFICATE.md and ontology/grounding_certificate.json). Open ontology/sdg-ontology.owl instead for the catalog-scope ontology only. Manchester-syntax twins (.omn) sit beside both.
2. Imports resolve locally. Protégé reads ontology/catalog-v001.xml and maps the BFO + π(CCO) import IRI to ontology/imports/cco-module.ttl. No network access, no other repositories.
3. Reasoning. HermiT ships with Protégé; the certificates above record the verdicts this release was published under.

just check verifies the standalone invariants (imports resolvable, no machine-local paths, artifacts parse); just protege prints these instructions. Both are optional — the steps above need only Protégé itself.