Geek Answers Handbook

Aligning two ontologies with an "adapter"

Simplification a bit, I have a domain ontology (D), expressed in OWL, which describes the devices, their capabilities, configurations. In addition, for each provider I would like to have a vendor-specific ontology (V) that will be connected to the domain. The question is how to align D and V? Is it possible to leave V as close as possible to the conditions of the provider or just a subclass of D classes for V (and, possibly, do the same for the data properties and object properties)? The idea is that the application uses ontology D for queries and output mechanisms, as far as I can hide the features of the provider.

The first option seems more logical (in the end, the semantic technology is connected), but I can anticipate some inconsistencies in some data types. For example, one vendor may express battery levels as a percentage, another uses words such as high, medium, low. I am not sure how to bring such data to a common denominator using OWL. There, perhaps, even more complex cases requiring the use of regular expressions and any scripted voodoo are usually made. (It is also interesting whether dataproperties should be used directly, or another layer of indirection should be added by wrapping dataproperties using object properties and concepts in dataproperty to be more prepared for typemismath).

In other words, it seems that the input should be pre-processed before entering the RDF ecosystem ... Or maybe there are other possibilities?

(for those who, as a rule, quickly mark the question as a duplicate, I do not ask for something like a comparison between the two ontologies , but rather organize “alignment” as preprocessing and a richer “adapter template” in OWL itself)

+4
source share
1 answer

In general, you should connect two ontologies by creating a new O ontology, which imports both D and V, and defines a bunch of axioms that connect classes and properties within them.

( , ), . , , , , , . OWL.

, OWL. , , V1 hasPowerLevel, , > . , V2 datatype hasPercentageRemaining, PowerCell [1,100]. PowerCell. , , - . .

    & sqsubseteq; POWERCELL
    PowerCell & sqsubseteq;
    PowerCell & equiv;
    & sqsubseteq; PowerCell & sqcap; & exist; & thinsp; hasPowerSource -1

.

    (hasPowerLevel ) & equiv; (hasPercentageRemaining [ >= 66])
    (hasPowerLevel value Medium) & equiv; (hasPercentageRemaining [< = 66, >= 33])
    (hasPowerLevel ) & equiv; (hasPercentageRemaining [< = 33])

, , "" OWL. hasPowerLevel

, , , voodoo. ( , "" dataproperties , ).

OWL- (, ) . , , , OWL. SWRL, RDF SPARQL SPIN.

, , , . , , , , . , , , .

+5

More articles:


All Articles