How to extract/build a Domain Model from Description Logic Knowledge Base(s)
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:
- Using the individuals from KmySys, create a new
ontology with assertions inferred from definitions in
Td ?
- 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?
- 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?
ontology modeling projection description-logic merging-data
asked Nov 14 '18 at 17:16
akyaky
333
add a comment |
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:
- Using the individuals from KmySys, create a new
ontology with assertions inferred from definitions in
Td ?
- 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?
- 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?
ontology modeling projection description-logic merging-data
asked Nov 14 '18 at 17:16
akyaky
333
add a comment |
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:
- Using the individuals from KmySys, create a new
ontology with assertions inferred from definitions in
Td ?
- 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?
- 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?
ontology modeling projection description-logic merging-data
asked Nov 14 '18 at 17:16
akyaky
333
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:
- Using the individuals from KmySys, create a new
ontology with assertions inferred from definitions in
Td ?
- 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?
- 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?
ontology modeling projection description-logic merging-data
ontology modeling projection description-logic merging-data
asked Nov 14 '18 at 17:16
akyaky
333
asked Nov 14 '18 at 17:16
akyaky
333
asked Nov 14 '18 at 17:16
akyaky
333
asked Nov 14 '18 at 17:16
akyaky
333
asked Nov 14 '18 at 17:16
akyaky
333
333
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53305561%2fhow-to-extract-build-a-domain-model-from-description-logic-knowledge-bases%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53305561%2fhow-to-extract-build-a-domain-model-from-description-logic-knowledge-bases%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
