Changelog¶
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[2.4.0] - 2026-04-12 — Industry Extensions, Tooling Suite & Python SDK¶
Added¶
- 4 New L2 Industry Extensions:
- Financial Services (
l2-extensions/financial-services/) — 30 classes, 12 relations. Banking, insurance, asset management, KYC/AML compliance, credit/market/operational risk. - Manufacturing (
l2-extensions/manufacturing/) — 27 classes, 11 relations. Factory ops, production lines, BOM, MES/SCADA, quality control, OEE/yield KPIs. - Healthcare (
l2-extensions/healthcare/) — 28 classes, 10 relations. Hospitals, pharma R&D, clinical trials, EHR, GMP/HIPAA compliance. - Technology (
l2-extensions/technology/) — 29 classes, 12 relations. SaaS/platform products, microservices, CI/CD, DevOps, DORA metrics, MRR/churn. - L2/L3 Validator (
scripts/validate_l3.py) — 9-rule referential integrity checker for all L2/L3 files (parent refs, relation domain/range, alias consistency, naming, cycles). - Ontology Diff Tool (
scripts/diff_ontology.py) — Structural diff between two ontology versions or git refs, with field-level change tracking. - LLM Export Tool (
scripts/export_for_llm.py) — Generates compressed system prompt (~4K tokens), OpenAI function-calling tool definitions, and RAG-ready document chunks. - Neo4j Exporter (
scripts/export_neo4j.py) — Generates Cypher import script for loading ontologies into Neo4j graph database. - Python SDK (
uod/package) —OntologyGraphclass withload_ontology(),get_class(),path(),search(),instances_of(),ancestors(),descendants(),inherited_attributes(). - CI Validation Workflow (
.github/workflows/ontology-validate.yml) — GitHub Actions pipeline validating all L1/L2/L3 ontologies on every push/PR. alias_ofpattern — New class field for declaring enterprise-specific aliases (owl:equivalentClass), supported across JSON, OWL, and HTML visualization.
Changed¶
- Visualizer (
scripts/visualize_ontology.py) — Added: tree horizontal/vertical toggle, instance display in all 3 views, attribute display in detail panel, alias badge, root node label,sinceversion badges. - Merger (
scripts/merge_layers.py) — Now scansprivate_enterprise/directory; handlesalias_offield. - OWL Generator (
scripts/json_to_owl.py) — Emitsowl:equivalentClassfor classes withalias_of. - .gitignore — Added exclusions for
**/output/generated artifacts andstudio/.
[2.3.0] - 2026-04-11 — Architecture Folder Renaming¶
⚠️ Breaking Changes¶
- Architecture Folder Rename — The primary structural folders (
platform,core,extensions,enterprise) have been renamed tol0-platform,l1-core,l2-extensions, andl3-enterpriserespectively. All references and documentation links across the project have been updated to reflect this explicitly layered structure.
[2.2.0] - 2026-04-11 — Tooling Enhancements & F&B Extension¶
⚠️ Breaking Changes¶
Partyis nowabstract: true— Party can no longer be directly instantiated. All instances must use a concrete subclass (Person,Organization,OrgUnit). This aligns Party with the same pattern asResource(both are abstract children ofEntity) and matches its own definition as a "主体总类" (superclass).
Added¶
- Food & Beverage (F&B) Extension — Provided a new
extensions/fnb/extension covering industry specific classes for restaurants, menus, supply chains, etc. - Enterprise Build Pipeline Integration — Introduced new components into the builder scripts to elegantly merge core, extensions, and private enterprise datasets.
Changed¶
- Visualizer Engine (
visualize_ontology.py) — Overhauled the HTML output for mobile-responsiveness, better navigation, search optimization, and dynamic node rendering. - OWL Generator (
json_to_owl.py) — Refactored to seamlessly ingest multiple extension layers and robustly map them into TTL formats.
[2.1.0] - 2026-04-10 — Documentation Bilingual Overhaul & Cleanup¶
⚠️ Breaking Changes¶
- Removed
extensions/common/— The Common Enterprise Extension has been entirely removed from the ontology architecture to enforce stricter domain-specific extension boundaries.
Changed¶
- Documentation Overhauled (MkDocs) — Completely refactored the project's documentation structure into
docs-site/with native, section-by-section English-Chinese bilingual integration. The frontend language toggle has been removed for a unified reading experience. - Architecture Guide Restructured — Split the monolithic architecture manual into dedicated, granular guides (
four-layer-model.md,inheritance.md,platform-bindings.md). - README Redesign — Modernized
README.mdandREADME_CN.mdwith beautiful shields.io badges, cleaner tables, responsive Mermaid flowcharts, and correct MkDocs documentation links. - Repository Cleanup — Removed legacy static documentation (
docs/) and private enterprise example references. Updated.gitignoreto prevent committing.netlify-deploy/artifacts.
[2.0.0] - 2026-04-03 — Anti-Entropy Refactoring¶
⚠️ Breaking Changes¶
- L1 Core restructured: 25 classes → 24 classes (6 abstract: 4 domain roots + Party + Resource; 18 concrete leaves)
BusinessObjectreplaced byResource— all L2 extensions using"parent": "BusinessObject"must change to"parent": "Resource"DocumentRecordrenamed toDocument— all L2 extensions using"parent": "DocumentRecord"must change to"parent": "Document"Activityclass removed from L1 — now available inextensions/common/as a subtype ofProcess- Relations renamed/merged:
belongs_to+composed_of→part_ofis_accountable_for→accountable_forconstrained_bymerged intogoverned_by(generalized domain/range)supportsandrequires_decisionremoved (expressible via other relations)- Classes demoted to L2
extensions/common/:Channel,MarketSegment,Location,Decision
Added¶
- 4 Abstract Domain Root Classes:
Entity,Governance,Operational,Measurement— organizes all classes into a structured tree instead of a flat list Resourceabstract class — replacesBusinessObjectas parent for ProductService, Asset, DataObject, Document, SystemApplicationmigration_registry— unified registry providing migration guidance for removed classes, relations, and attributes- Schema lifecycle fields:
abstract,status,since,deprecated_since,replaced_byfor versioned evolution - Relation metadata:
cardinality(1:1, 1:N, N:1, N:M),inverse_offor bidirectional relation declarations extensions/common/L2 extension — Common Enterprise Extension containing demoted L1 classes plus new universally useful classes (Contract, Report, Project, Stakeholder, Regulation)scripts/validate_governance.py— Automated CI governance validator enforcing rules G-01 through G-08- Governance Rules G-01 through G-08 in CONTRIBUTING.md — hard structural constraints to prevent entropy growth
maxItems: 25constraint in core_schema.json — schema-level enforcement of class cap
Changed¶
- Relation domain/range generalized —
governed_bynow acceptsOperational → Governanceinstead ofProcess → Policy, enabling L2 reuse without creating duplicate relations measured_bygeneralized — domain changed fromGoaltoOperational, allowing any operational element to be measuredconsumes/producesgeneralized — range changed fromDataObjecttoResource- All L0 platform bindings updated to v2.0 (OWL/RDF, JSON-LD, GraphQL, SQL DDL)
extension_schema.jsonextendsfield relaxed — now supports both string and array format, enabling L2-to-L2 dependenciessample_instancesmade industry-neutral — removed retail/manufacturing specific examples- Consulting extension updated to use
Resource/Documentparent classes - Luxury Goods extension updated to use
Resource/Documentparent classes - README.md updated with v2.0 architecture diagram and class domain table
[1.2.0] - 2026-04-03¶
Changed¶
- Repository Flattening: Moved all core project files from
universal-ontology-definition/to the repository root for better accessibility and cleaner structure. - Updated
.gitignoreto includelegacy/archive and improve environment file exclusion.
Added¶
- L3 Enterprise Customization Layer (
enterprise/) - Enterprise layer documentation (
enterprise/README.md) - Enterprise customization JSON template (
enterprise/_template/enterprise_ontology_template.json)
[1.1.0] - 2026-03-30¶
Added¶
- L0 Platform & Syntax Bindings Layer (
platform/) - OWL 2 / RDF Turtle serialization (
platform/owl-rdf/core_ontology.ttl) - JSON-LD Context definition (
platform/json-ld/context.jsonld) - GraphQL Schema definition (
platform/graphql/schema.graphql) - PostgreSQL DDL mapping (
platform/sql/schema.sql) - Platform binding contribution template (
platform/_template/)
Changed¶
- Architecture upgraded from three-layer to four-layer (L0–L3)
- Updated README.md and README_CN.md to reflect four-layer architecture
- Updated
docs/architecture.mdwith L0 layer documentation - Version badge updated to 1.1.0
[1.0.0] - 2026-03-29¶
Added¶
- L1 Core Ontology (
core/universal_ontology_v1.json) - 25 universal entity classes covering Party, Organization, Process, Capability, Risk, Goal, KPI, etc.
- 16 standard relationship definitions
- 8 sample instances
- Consulting Industry and Domain Extension (
extensions/consulting/consulting_extension_v1.json) - 40+ consulting-specific classes (Engagement, Deliverable, Methodology, Framework, etc.)
- 34 industry relationship definitions
- 25+ sample instances
- Luxury Goods Industry and Domain Extension (
extensions/luxury-goods/luxury_goods_extension_v1.json) - 21 luxury-specific classes (Brand, Collection, SKU, Boutique, etc.)
- 10 industry relationship definitions
- 8 sample instances
- Extension Template (
extensions/_template/) for community contributors - JSON Schema validation for core and extension definitions
- Documentation: Architecture guide, design guide, extension development guide