feat(acms): implement UKO Layer 2 Paradigm Vocabularies (uko-oo, uko-func, uko-proc) #575

Closed
opened 2026-03-04 23:42:55 +00:00 by freemo · 0 comments
Owner

Metadata

Field Value
Commit Message feat(acms): implement UKO Layer 2 Paradigm Vocabularies (uko-oo, uko-func, uko-proc)
Branch feature/m6-uko-layer2-paradigm-vocabularies

Summary

Implement the Layer 2 paradigm/format-specific UKO vocabulary specializations: Object-Oriented (uko-oo:), Functional (uko-func:), and Procedural (uko-proc:). These refine Layer 1 uko-code: domain classes with paradigm-specific concepts and extend the parent DetailLevelMap with additional named levels.

Spec Reference

Section: Architecture > ACMS > UKO > Ontology Hierarchy > Layer 2: Paradigm / Format Specializations
Lines: ~42333-42422

Current State

No Layer 2 vocabulary files or paradigm-specific classes exist in the codebase. Layer 1 vocabularies (prerequisite) are also not yet implemented.

Description

uko-oo: (Object-Oriented)

  • Classes: Class (subClassOf uko-code:TypeDefinition, uko:Container), Interface (subClassOf uko-code:TypeDefinition, uko:Boundary), Method (subClassOf uko-code:Callable), Attribute (subClassOf uko:Atom)
  • Properties: inheritsFrom (Class→Class), implements (Class→Interface)
  • DetailLevelMap insertions: CLASS_HIERARCHY at depth 3 (OO-specific), SIGNATURES_WITH_DOCS at depth 5
  • Per-type rendering tables at selected depths (spec lines 42394-42402)

uko-func: (Functional)

  • Classes: PureFunction (subClassOf uko-code:Callable), TypeClass (subClassOf uko-code:TypeDefinition, uko:Boundary), Monad (subClassOf uko-code:TypeDefinition)
  • DetailLevelMap: Extends uko-code: with functional-specific renderings (purity annotations, pattern match structures, type class laws)
  • Per-type rendering tables (spec lines 42404-42411)

uko-proc: (Procedural)

  • Classes: Procedural-specific (function declarations, global variables, header files, struct definitions, macros)
  • DetailLevelMap: Extends uko-code: with procedural-specific renderings (header exports, macro signatures, inline assembly)
  • Per-type rendering tables (spec lines 42413-42421)

Each paradigm vocabulary must:

  1. Properly inherit from Layer 1 uko-code: classes via rdfs:subClassOf
  2. Extend the parent DetailLevelMap, potentially inserting new named levels between existing ones
  3. Shift subsequent integer assignments when inserting new levels

Acceptance Criteria

  • uko-oo: OWL/Turtle file with Class, Interface, Method, Attribute, inheritsFrom, implements
  • uko-func: OWL/Turtle file with PureFunction, TypeClass, Monad
  • uko-proc: OWL/Turtle file with procedural-specific classes
  • DetailLevelMap inheritance: Layer 2 maps correctly extend Layer 1 maps with inserted levels
  • Depth integer reassignment works correctly when paradigm inserts new named levels
  • Unit tests for DetailLevelMap inheritance chain (Layer 2 → Layer 1 → Layer 0)
  • Turtle syntax validation passes for all vocabularies
  • Depends on: UKO Layer 1 Domain Ontologies
  • Parent epic: #367 (Multi-Agent RDF Knowledge Graph)
  • Prerequisite for: UKO Layer 3 (uko-py, uko-ts, uko-rs, uko-java)

Suggested Milestone

v3.5.0

Priority

Low

Suggested Assignee

@hamza.khyari

Subtasks

  • Code: Implement uko-oo: OWL/Turtle ontology with Class, Interface, Method, Attribute, inheritsFrom, implements
  • Code: Implement uko-func: OWL/Turtle ontology with PureFunction, TypeClass, Monad
  • Code: Implement uko-proc: OWL/Turtle ontology with procedural-specific classes
  • Code: Implement DetailLevelMap inheritance with level insertion and integer reassignment logic
  • Docs: Document Layer 2 paradigm vocabulary hierarchy and DetailLevelMap extension mechanism
  • Behave tests: Add BDD feature file features/acms/uko_layer2_paradigm_vocabularies.feature covering paradigm-specific class resolution and detail level inheritance
  • Robot tests: Add Robot Framework integration test for Layer 2 → Layer 1 → Layer 0 inheritance chain and Turtle syntax validation
  • ASV benchmarks: Add ASV benchmark for DetailLevelMap inheritance chain resolution performance (benchmarks/bench_detail_level_map.py)
  • Quality: coverage ≥97%: Verify via nox -s coverage_report
  • Quality: nox full suite: Run nox (all default sessions), fix any errors

Definition of Done

This issue is complete when:

  • All subtasks above are completed and checked off.
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
## Metadata | Field | Value | |-------|-------| | **Commit Message** | `feat(acms): implement UKO Layer 2 Paradigm Vocabularies (uko-oo, uko-func, uko-proc)` | | **Branch** | `feature/m6-uko-layer2-paradigm-vocabularies` | ## Summary Implement the Layer 2 paradigm/format-specific UKO vocabulary specializations: Object-Oriented (`uko-oo:`), Functional (`uko-func:`), and Procedural (`uko-proc:`). These refine Layer 1 `uko-code:` domain classes with paradigm-specific concepts and extend the parent DetailLevelMap with additional named levels. ## Spec Reference **Section**: Architecture > ACMS > UKO > Ontology Hierarchy > Layer 2: Paradigm / Format Specializations **Lines**: ~42333-42422 ## Current State No Layer 2 vocabulary files or paradigm-specific classes exist in the codebase. Layer 1 vocabularies (prerequisite) are also not yet implemented. ## Description ### `uko-oo:` (Object-Oriented) - **Classes**: `Class` (subClassOf `uko-code:TypeDefinition`, `uko:Container`), `Interface` (subClassOf `uko-code:TypeDefinition`, `uko:Boundary`), `Method` (subClassOf `uko-code:Callable`), `Attribute` (subClassOf `uko:Atom`) - **Properties**: `inheritsFrom` (Class→Class), `implements` (Class→Interface) - **DetailLevelMap insertions**: `CLASS_HIERARCHY` at depth 3 (OO-specific), `SIGNATURES_WITH_DOCS` at depth 5 - Per-type rendering tables at selected depths (spec lines 42394-42402) ### `uko-func:` (Functional) - **Classes**: `PureFunction` (subClassOf `uko-code:Callable`), `TypeClass` (subClassOf `uko-code:TypeDefinition`, `uko:Boundary`), `Monad` (subClassOf `uko-code:TypeDefinition`) - **DetailLevelMap**: Extends `uko-code:` with functional-specific renderings (purity annotations, pattern match structures, type class laws) - Per-type rendering tables (spec lines 42404-42411) ### `uko-proc:` (Procedural) - **Classes**: Procedural-specific (function declarations, global variables, header files, struct definitions, macros) - **DetailLevelMap**: Extends `uko-code:` with procedural-specific renderings (header exports, macro signatures, inline assembly) - Per-type rendering tables (spec lines 42413-42421) Each paradigm vocabulary must: 1. Properly inherit from Layer 1 `uko-code:` classes via `rdfs:subClassOf` 2. Extend the parent DetailLevelMap, potentially inserting new named levels between existing ones 3. Shift subsequent integer assignments when inserting new levels ## Acceptance Criteria - [ ] `uko-oo:` OWL/Turtle file with Class, Interface, Method, Attribute, inheritsFrom, implements - [ ] `uko-func:` OWL/Turtle file with PureFunction, TypeClass, Monad - [ ] `uko-proc:` OWL/Turtle file with procedural-specific classes - [ ] DetailLevelMap inheritance: Layer 2 maps correctly extend Layer 1 maps with inserted levels - [ ] Depth integer reassignment works correctly when paradigm inserts new named levels - [ ] Unit tests for DetailLevelMap inheritance chain (Layer 2 → Layer 1 → Layer 0) - [ ] Turtle syntax validation passes for all vocabularies ## Related Issues - Depends on: UKO Layer 1 Domain Ontologies - Parent epic: #367 (Multi-Agent RDF Knowledge Graph) - Prerequisite for: UKO Layer 3 (uko-py, uko-ts, uko-rs, uko-java) ## Suggested Milestone v3.5.0 ## Priority Low ## Suggested Assignee @hamza.khyari ## Subtasks - [ ] **Code**: Implement `uko-oo:` OWL/Turtle ontology with Class, Interface, Method, Attribute, inheritsFrom, implements - [ ] **Code**: Implement `uko-func:` OWL/Turtle ontology with PureFunction, TypeClass, Monad - [ ] **Code**: Implement `uko-proc:` OWL/Turtle ontology with procedural-specific classes - [ ] **Code**: Implement DetailLevelMap inheritance with level insertion and integer reassignment logic - [ ] **Docs**: Document Layer 2 paradigm vocabulary hierarchy and DetailLevelMap extension mechanism - [ ] **Behave tests**: Add BDD feature file `features/acms/uko_layer2_paradigm_vocabularies.feature` covering paradigm-specific class resolution and detail level inheritance - [ ] **Robot tests**: Add Robot Framework integration test for Layer 2 → Layer 1 → Layer 0 inheritance chain and Turtle syntax validation - [ ] **ASV benchmarks**: Add ASV benchmark for DetailLevelMap inheritance chain resolution performance (`benchmarks/bench_detail_level_map.py`) - [ ] **Quality: coverage ≥97%**: Verify via `nox -s coverage_report` - [ ] **Quality: nox full suite**: Run `nox` (all default sessions), fix any errors ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done.
freemo added this to the v3.5.0 milestone 2026-03-05 00:30:01 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#575
No description provided.