AI curriculum

Course outline for Semantic Web and Ontology Engineering

Shared file formats do not ensure that two datasets use the same identities or meanings. Encode a small role-and-skills ontology, query its triples, and inspect a bounded inference. Apply a separate validation check so missing data and inferred types are not confused with invalid records.

About Semantic Web and Ontology Engineering

Shared file formats do not ensure that two datasets use the same identities or meanings. Encode a small role-and-skills ontology, query its triples, and inspect a bounded inference. Apply a separate validation check so missing data and inferred types are not confused with invalid records.

Semantic Web and Ontology Engineering Course Objectives

  • Encode schema and instance triples using stable URIs.
  • Query supplied RDF datasets with SPARQL.
  • Explain a selected OWL entailment and its assumptions.
  • Distinguish open-world inference from closed-world validation.
  • Compare ontology versions using reproducible query, reasoner, and validation results.

Pre-requisites

  • Ability to distinguish entities, relationships, schema, facts, and domain rules.
  • Basic query or programming experience and familiarity with structured data.

Before this course

Complete the required courses or bring equivalent experience. Recommended courses add useful depth; they are not enrolment gates.

Required preparation

Recommended preparation

Understands entities, relationships, schema, and facts before learning RDF/OWL and reasoning semantics; basic query or programming skills remain necessary.

Find your place in the learning map

Lab Setup

  • Local ontology editor and supplied RDF/SPARQL, reasoner, and SHACL tooling with pinned versions.
  • Small synthetic role/skill datasets, prepared shapes, expected query results, and a supported-axiom reference.
  • No hosted graph service or unrestricted natural-language rule conversion is assumed.

Detailed Course Outline

Module 1: Encode shared identities and meanings

  • RDF: Encode subject, predicate, and object triples with stable URIs, distinguishing shared identifiers from labels and dataset formatting.
  • RDFS: Define a class and property vocabulary, recognizing that domain and range declarations support type inference rather than record rejection.
  • OWL: Express bounded ontology axioms and inspect selected entailments without treating inferred types as evidence of closed-world data validity.

Practical outcome: Encode URI-identified facts and a small class/property vocabulary while distinguishing declarations from instance data.

Module 2: Query and inspect a bounded ontology

  • SPARQL: Write reproducible relationship queries over supplied triples and compare fixed query results across two ontology versions.
  • Ontology modelling: Separate schema declarations from instance facts and choose explicit identity and relationship meanings for the role-and-skills domain.
  • Description logic: Express a supplied small class axiom within the selected reasoner's supported fragment and explain its inferential assumptions.

Practical outcome: Run reproducible relationship queries and express a supplied small class axiom within the selected reasoner's supported fragment.

Module 3: Separate inference from validation

  • Open-world assumption: Treat absent assertions as unresolved information rather than falsehood, separating missing required data from ontology entailment.
  • Reasoning: Compare asserted and entailed facts, document a supported type inference, and inspect the reasoner's response to an inconsistent fixture.
  • Knowledge integration: Combine two RDF datasets using shared identities and meanings, recording versions and unresolved information rather than assuming semantic agreement.
  • Closed-world validation: Apply supplied SHACL shapes to required values separately from OWL reasoning, reporting validation failures without equating absence with falsehood.

Practical outcome: Integrate two datasets, compare asserted and entailed facts, and run supplied SHACL shapes separately from OWL reasoning.

Practical exercise

  • Produce an RDF ontology, SPARQL query set, version manifest, and separate reasoner and validation reports for two synthetic datasets.
  • Show one expected type inference and explain why an OWL domain/range declaration can infer a type rather than reject a record.
  • Introduce a missing required value and an inconsistent fixture; identify the validation failure and the selected reasoner's reported result without treating absence as false.
  • Compare two ontology versions against three fixed queries and record changed entailments, validation results, and unresolved information.

What you will produce

Query a small RDF ontology and distinguish its entailed facts from separately validated data constraints.

How the work is checked

  • URI identities and schema/instance separation are preserved across both datasets.
  • Three fixed queries match the versioned expected results.
  • The learner explains a domain/range inference and open-world unknowns correctly.
  • Reasoner and SHACL reports remain separate and identify the supplied failure cases.

Six-hour prepared ontology lab with limited supported axioms and supplied SHACL shapes. SHACL validates the specified data graph and shape scope; a passing report does not prove completeness or truth. OWL inconsistency is not a missing-field validation failure. Not description-logic mastery, arbitrary rule support, or guaranteed truth of inferred facts.

When another approach is better

  • Prefer a simpler schema when shared semantic inference is not needed.
  • Do not use OWL alone to enforce closed-world record completeness or treat approximate matches as identical entities.

How we train

Contact us for full course details, including duration, delivery options and lab requirements.

Ask about exercises, instructor feedback and the prior knowledge you need. Tool-specific courses marked provisional may become modules in a broader course.

Discuss your learning goals