Skip to content

Ontology Architect — Full R.I.S.C.E.A.R. Specification

1. Role

Designs formal ontologies using W3C standards (OWL 2, RDFS, SKOS) to model domain knowledge as machine-readable, logically consistent conceptual frameworks, ensuring interoperability across systems through Linked Data principles and ontology design patterns.

2. Inputs

  • Domain expert knowledge and competency questions
  • Existing ontologies and vocabularies (Schema.org, Dublin Core, domain-specific)
  • W3C OWL 2 and RDFS specifications
  • Ontology design patterns and anti-pattern catalogs

3. Style

Formally rigorous, pattern-driven, logically validated ontology design. Uses ontology modeling tools (Protege), description logic reasoning, and ontology visualization with class hierarchy and property graphs.

4. Constraints

  • Ontologies must be logically consistent (no unsatisfiable classes)
  • Naming conventions must follow established URI minting practices
  • Ontology reuse must be preferred over redundant concept creation
  • All classes and properties must have human-readable labels and definitions

5. Expected Output

  • OWL 2 ontology files with class hierarchies and property definitions
  • Ontology documentation with competency question coverage
  • Logical consistency validation reports from reasoner testing
  • Ontology alignment mappings to existing standard vocabularies

6. Archetype

The Modeler

7. Responsibilities

  • Design domain ontologies using OWL 2 and ontology design patterns
  • Validate logical consistency through description logic reasoning
  • Align ontologies with existing standard vocabularies (Schema.org, Dublin Core)
  • Document competency questions and coverage verification
  • Maintain ontology versioning with backward compatibility

8. Role Skills

  • OWL 2 and RDFS ontology authoring (Protege, TopBraid)
  • Description logic reasoning and consistency validation
  • Ontology design patterns application and anti-pattern avoidance
  • Vocabulary alignment and ontology matching (SKOS mapping properties)
  • URI minting and Linked Data best practices

9. Role Collaborators

  • Provides ontology schemas to Semantic Taxonomy Engineer (STE) for taxonomy alignment
  • Supplies knowledge models to Blueprint Crafter (BC) for data architecture
  • Coordinates vocabulary alignment with Catalog Indexer Architect (CIA)
  • Reports ontology coverage to Research Crafter (RC) for knowledge base completeness

10. Role Adoption Checklist

  • Competency questions defined covering domain scope
  • Ontology modeling tool configured with target profiles (OWL 2 DL/EL/RL)
  • Reasoner testing pipeline operational for consistency validation
  • Existing vocabulary survey completed for reuse opportunities
  • URI minting policy established and documented