The Ontology Project federates by namespace. The universal layer (TOP Core) lives at top: and holds the eight Category-Level Objects and twenty-eight leaves that operators across every domain recognize as first-class concepts. Each reference graph (clinical research, future CMC, future energy, future manufacturing) gets its own prefix, its own resolution target, and extends Core by declaring rdfs:subClassOf against a Core concept. Domain extensions inherit the provenance contract, PROV-O alignment, and NGSI-LD wire format from Core at zero cost.
Active namespaces
top:
The universal layer. Eight Category-Level Objects (Agent, Location, Resource, Scope, Temporal, Evidence, Outcome, Constraint) and twenty-eight leaves (Person, Organization, Group, Autonomous Agent, Schedule, Window, Activity, Milestone, Document, Log, Attestation, Credential, Observation, Status Change, Artifact, Conclusion, Physical, Virtual, Storage, System, Equipment, Material, Portfolio, Program, Project, Physical Limit, Regulatory Law, Safety Guardrail). Twenty-three PROV-O alignments via skos:exactMatch / skos:closeMatch; provenance contract (identifier, observedAt, status) enforced as SHACL underneath.
topcr:
The first reference graph built on TOP Core. Eight top-levels (Sponsor, Study, Site, Participant, Visit, Investigational Product, Oversight Body, Event) plus the StudySite operational pivot. Sponsor is sealed at v0.1.4; Site has lifted to v0.2.0; Study at v0.3.0; Visit, Event, Participant, IP, and Oversight Body queued. Currently published under the legacy top: prefix from before Core claimed that namespace; rebase to topcr: is the next priority so top: cleanly means the Core layer everywhere.
Future namespaces
Each of the namespaces below is a candidate for a separate working group. Each domain converges on its strawman first; the schema follows. The pattern is the same across all of them: hand-write a strawman intermediate, run the translator scaffold, ship the artifacts.
topcmc:Clinical CMC Queued
Chemistry, Manufacturing, and Controls reference graph for biologics and small molecules in clinical development.
topdd:Drug Discovery Queued
Target identification, lead optimization, preclinical, and IND-enabling work, upstream of clinical.
topct:Cell & Gene Therapy Queued
Cell-therapy and gene-therapy operations, with Sample and Supply / Logistics elevated to top-level given their primacy in this domain.
toprd:Rare Disease Queued
Rare-disease operations with Participant elevated and patient-registry mechanics first-class.
topenergy:Energy & Process Industries Queued
Operator-grounded reference graph analogous to ISO 15926 and CFIHOS in coverage, but built on the same OOUX-first pattern.
topmfg:Manufacturing Queued
Batch processing, supply chain, and master-batch-record operations.
How a URI resolves
TOP Core use hash URIs at a single namespace document: https://top.scientix.ai/v1#<ClassName>. Domain reference graphs use the per-namespace pattern https://top.scientix.ai/onto/<namespace>/<version>#<ClassName>. When a JSON-LD or RDF tool follows either URI, it lands on the matching page; the fragment scrolls to the class definition. Examples:
https://top.scientix.ai/v1#Agent
https://top.scientix.ai/v1#Activity
https://top.scientix.ai/v1#Document
https://top.scientix.ai/onto/clinical/v1#Sponsor
https://top.scientix.ai/onto/clinical/v1#Site
The same fragment-on-page pattern applies to every future namespace. Versions stay in the URI so a graph that pinned to v1 is never silently retargeted at a later version; new versions resolve at v2, v3, and so on, alongside their predecessors.
