Quiz: Enterprise Ontology Design Patterns & Schema Alignment

Quiz Summary

0 of 3 Questions completed

Questions:

You have already completed the quiz before. Hence you can not start it again.

Quiz is loading…

You must sign in or sign up to start the quiz.

You must first complete the following:

Results

Quiz complete. Results are being recorded.

Results

0 of 3 Questions answered correctly

Your time:

You have reached 0 of 0 point(s), (0)

Question 1 of 3

1. Question

Why is modelling Employee, Manager and Customer as subclasses of Person an anti-pattern, and what does the AgentRole pattern do instead?

Subclassing is too slow for reasoners, so the pattern replaces the OWL subclasses with SKOS concepts.
Correct Incorrect Correct answer

OWL limits the number of subclasses a class may have, so the pattern distributes them across imported modules.
Correct Incorrect Correct answer

OWL class membership is treated as rigid while these classifications are temporary and overlapping, so the pattern keeps the Agent distinct from the Role and links them through a property such as hasRole.
Correct Incorrect Correct answer

The subclasses would be inferred pairwise disjoint automatically, so the pattern declares them equivalent to one another instead.
Correct Incorrect Correct answer

Correct / 1 Points

Incorrect / 1 Points
Question 2 of 3

2. Question

A graph asserts that John isMemberOf the Orchestra and that the Orchestra isPartOf the Music Department, using a single universally transitive isPartOf property. What is the problem?

There is none, because membership and parthood are recorded with different property names.
Correct Incorrect Correct answer

The reasoner infers that John is a physical part of the Music Department, which is unsound; the fix is to define separately constrained sub-properties for the distinct part-whole types rather than one universally transitive isPartOf.
Correct Incorrect Correct answer

The reasoner flags an inconsistency, because a person cannot be part of a department.
Correct Incorrect Correct answer

The inference is sound, because all six Winston, Chaffin and Herrmann part-whole types are transitive by definition.
Correct Incorrect Correct answer

Correct / 1 Points

Incorrect / 1 Points
Question 3 of 3

3. Question

Your class ex:Employee is a close but not exact match for a class in an external vocabulary. Which alignment is appropriate and why?

A SKOS mapping predicate such as skos:closeMatch, which supports search and crosswalks without forcing the logical entailments that owl:equivalentClass would propagate across both graphs.
Correct Incorrect Correct answer

owl:sameAs, which is the standard predicate for asserting that two classes correspond.
Correct Incorrect Correct answer

owl:equivalentClass, because it is symmetric and therefore safer than a one-directional mapping.
Correct Incorrect Correct answer

rdfs:subClassOf asserted in both directions, which carries exactly the same weak semantics as skos:closeMatch.
Correct Incorrect Correct answer

Correct / 1 Points

Incorrect / 1 Points

Quiz: Enterprise Ontology Design Patterns & Schema Alignment

Quiz Summary

Information

Results

Results

Categories

1. Question

2. Question

3. Question