Given an OWL-DL ontology of an application domain, we derive an
application-specific relational model as known from classical
database design, where the relational model is created from an ER
model.
The mapping depends as usual on the cardinalities of properties;
namely whether a property is functional or not on a certain domain.
In particular, since properties may be defined for several classes,
where they can be functional on some of them, and multivalued on
others, a detailed schema inspection is necessary. We show that this
requires the definition of auxiliary classes at processing time
followed by containment checks. Thus, the process cannot be
implemented declaratively by a simple set of SPARQL queries, but
requires the use of a procedural framework that interferes with the
ontology.
