skills.rest
OntoLedgy
OntoLedgyOFFICIAL
Explore all skills by this author →
GitHub

ob-ontologist

Enforce BORO foundational principles in domain ontology modeling workflows.

Updated Aug 27, 2026
Search Tags:#ontology#domain-modeling#compliance-review#boro#ontological-analysis#legacy-reengineering#4d-extensionalism
One-click install
npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill ob-ontologist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ob-ontologist
Source: https://github.com/OntoLedgy/ol_ai_context_library/tree/main/skills/ob-ontologist
Command: npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill ob-ontologist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the risk of inconsistent, non-compliant domain ontology models that fail to align with BORO foundational principles, which leads to flawed domain analysis, failed legacy system re-engineering, and incompatible designs for OB/Ontoledgy solutions.

Core Features & Use Cases

  • BORO Entity Classification: Classify all domain entities against the BORO upper ontology (Elements, Types, Tuples, Sets) to ensure consistent, standards-aligned modeling.
  • Legacy Model Re-engineering: Transform existing data models, schemas, or legacy system artifacts into BORO-grounded ontology models, resolving common issues like conflated types, implicit relationships, and missing temporal analysis.
  • BORO Compliance Review: Audit existing ontology models for adherence to core BORO principles including 4D extensionalism, sign distinction, and valid identity criteria.
  • Use Case: If your team needs to modernize a legacy customer relationship management database that conflates customer entities with their employment status states, this Skill will produce a BORO-compliant model with distinct temporal parts and properly modeled tuple relationships for order and service interactions.

Quick Start

Use the ob-ontologist skill to re-engineer the existing legacy customer schema into a BORO-grounded ontology model with proper 4D temporal parts and tuple relationships for order interactions.

Frequently Asked Questions about ob-ontologist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is BORO ontology modeling and when do I need it for domain analysis?▼

BORO ontology modeling classifies domain entities into Elements, Types, Tuples, and Sets using 4D extensionalist temporal analysis. You need it when greenfield domain analysis requires strict foundational compliance or when resolving conflated entity types and implicit relationships.

How do I re-engineer a legacy data model into a BORO-compliant ontology?▼

To re-engineer a legacy data model into a BORO-compliant ontology, apply the Partridge re-engineering method to transform existing schemas. This resolves conflated types and missing temporal analysis by grounding entities in distinct temporal parts and first-class tuple relationships.

How does a BORO compliance review audit existing ontology models?▼

A BORO compliance review audits existing ontology models by validating adherence to core principles like 4D extensionalism, sign distinction, and valid identity criteria. This ensures upper ontology classification standards are met and identifies non-compliant modeling gaps.

Can I use 4D extensionalist temporal analysis to fix conflated legacy database schemas?▼

Yes, you can use 4D extensionalist temporal analysis to fix conflated legacy database schemas by separating persistent entity types from their temporal state parts. This resolves common issues like conflated customer entities with employment status states.

Best way to model first-class tuple relationships for legacy system modernization?▼

The best way to model first-class tuple relationships for legacy system modernization is enforcing BORO foundational principles. This properly structures order and service interactions as distinct tuples, avoiding implicit relationships found in non-compliant legacy schemas.

Why does my domain ontology model fail BORO identity criteria validation?▼

Domain ontology models fail BORO identity criteria validation when they conflate entity types with their temporal states or omit 4D extensionalist temporal parts. This creates inconsistent classifications that violate BORO upper ontology standards and foundational principles.

Related Skills

Explore More Education & Research Skills→
icartshicartsh
4

csharp-developer

Diagnose .NET solution gaps and produce an architectural plan.

Community
Advanced
robbytrobbyt
42

go-style-guide

Review Go code against the Go Style Guide for bugs and maintainability issues.

Community
Advanced
rohunvorarohunvora
5

ui-density

Analyze UI density across four dimensions and prescribe concrete fixes.

Community
Advanced
cooper538cooper538

review-task

Review task implementations for code quality and specification compliance.

Community
Advanced