How to extract/build a Domain Model from Description Logic Knowledge Base(s)

43 views Asked by At

hopefully my question is not trivial or already answered elsewhere.

Problem Description
Let's assume we have a DL Knowledge Base KmySys = (Tsys, AmySys) representing a software architecture. The knowledge KmySys models software components (e.g., APIs, Storages, DBs, Servers etc.) and their communication (e.g. Protocols, Authorizations, Permissions, Data flow etc.). The terminological part Tsys is shared amongst several possible models and the assertional part AmySys is the instantiation of the resources constituting my specific software.
Now, let's also assume that we have a DL "Domain Knowledge" Kd = (Td, Ad) that contains concepts and roles definitions, and possibly individuals thereof, of a specific domain. This "Domain Knowledge" can be thought of as extra knowledge that we want to combine with the model of our software to draft a report of some kind: for example, it might contain concepts related to security, access control, cryptography.
Some of the knowledge in KmySys "intersects" Kd and some does not. The intersecting knowledge is relevant for the domain modeling, the remaining is not and can be dropped.

Question
Is there any procedure to:

  1. Using the individuals from KmySys, create a new ontology with assertions inferred from definitions in Td ?
  2. Exclude all the info not relevant for the domain d, that is, all individuals in KmySys that do not belong to any concept in Td?
  3. Include all the info from Td so that the final ontology is a sort of domain-specific model of the original model?


In Short: How to instantiate the domain knowledge Kd over existing individuals from a knowledge KmySys?

I have googled extensively for papers on this problem and found results on Ontology Merging, Mapping, Matching, something on Projections and so on... but it doesn't seem to me that the formulation of the problem is the same as in my case. The problem vaguely resembles merging, only that I want to preserve the domain knowledge and drop the non-relevant system knowledge.

I am a little confused...
Is this a projection problem?
Is this a merging problem?
Can somebody please point me to relevant research?

0

There are 0 answers