This page (revision-45) was last changed on 20-Mar-2018 17:02 by Joba Baumeister

This page was created on 20-Nov-2012 15:30 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
45 20-Mar-2018 17:02 9 KB Joba Baumeister to previous
44 20-Mar-2018 17:02 9 KB Joba Baumeister to previous | to last
43 20-Mar-2018 17:01 9 KB Joba Baumeister to previous | to last
42 24-Feb-2016 10:56 9 KB Albrecht Striffler to previous | to last
41 05-Sep-2014 16:17 9 KB Joba Baumeister to previous | to last

Page References

Incoming links Outgoing links
User FAQ
User FAQ

Version management

Difference between version and

At line 1 added 6 lines
%%Todo
Review the FAQ.
@user: Volker Belli
%
At line 3 removed one line
At line 6 removed one line
At line 12 added one line
A: In general, d3web provides problem-solving knowledge to solve diagnosis tasks, where observations are entered (or batched) into the system and appropriate diagnoses are returned as a result. This kind of methods can be also used to implement recommender systems and classification systems. You may have a look at some of our [examples|Demos] to get a first impression. A good source for inspiration are also the [Success Stories].
At line 9 removed 3 lines
A: In general, d3web provides problem-solving knowledge to solve diagnosis tasks, where observations are entered (or batched) into the system and appropriate diagnoses are returned as a result. This kind of methods can also be used to implement recommender and classification systems. You may have a look at some of our [examples|Demos] to get a first impression. A good source for inspiration are also the [Success Stories].
At line 14 changed one line
A: __d3web__ is a platform for diagnostic tasks. As a part of d3web, there id d3web-Core and d3web-KnowWE, among others.\\ __d3web-Core__ is a Java implementation of problem-solving methods for diagnosis tasks. It provides an API, so that applications can use d3web as an embedded application. Besides the problem-solving methods, d3web-Core also includes many additional APIs, e.g., for the persistence of knowledge bases (loading/saving).\\ __KnowWE__ (Knowledge Wiki Environment) is a development environment for building knowledge bases. It includes d3web-Core and offers editors to develop d3web knowledge. KnowWE runs as a JSP-server application on all systems with Java 8 or greater installed.\\ __KnowME__ is the predecessor of KnowWE, not being under active development any longer.
A: __d3web__ is platform for diagnostic tasks. As a part of d3web, there id d3web-Core and d3web-KnowWE, among others.\\ __d3web-Core__ is a Java implementation of problem-solving methods for diagnosis tasks. It provides an API, so that applications can use d3web as an embedded application. Besides the problem-solving methods, d3web-Core also includes many additional APIs, e.g., for the persistence of knowledge bases (loading/saving).\\ __KnowWE__ (Knowledge Wiki Environment) is a development environment for building knowledge bases. It includes d3web-Core and offers editors to develop d3web knowledge. KnowWE runs as a JSP-server application on all systems with Java 6 or greater installed.\\ __KnowME__ is the predecessor of KnowWE, not being under active development any longer.
! Q: I already working with KnowME. How is this related to d3web?
KnowME is a rich-client application, where d3web knowledge bases can be developed with a stand-alone application. The KnowME is the predecessor of KnowWE. Please note that KnowME is no longer under development. Being replaced by KnowWE since 2008, KnowME reached its EOL and you should consider to migrate to KnowWE, which is pretty much compatible. If you want to migrate, please contact us directly by [emailing to info@d3web.de|mailto:info@d3web.de?subject=Migrate KnowME to wiki environment].
At line 20 added 2 lines
! Q: What is the current life-status of the systems?
A: d3web (with both d3web-Core3 and d3web-KnowWE, among others) are under active development. The University of Würzburg, Germany (Group Artificial Intelligence, Prof. Puppe) and the denkbares GmbH are improving and extending the software continuously. The denkbares GmbH also provides stable versions of d3web on a regular basis. The system KnowME was finally declared as "deprecated" in 2008 and is not under development any longer.
At line 17 changed one line
! Q: I am already working with KnowME. How is this related to d3web?
!! Knowledge Engineering
At line 19 removed 23 lines
KnowME is a rich-client application where d3web knowledge bases can be developed using a stand-alone application. KnowME is the predecessor of KnowWE. Please note that KnowME is no longer under development. Being replaced by KnowWE since 2008, KnowME reached its EOL and you should consider to migrate to KnowWE, which is pretty much compatible. If you want to migrate, please contact us directly by [emailing info@d3web.de|mailto:info@d3web.de?subject=Migrate KnowME to wiki environment].
! Q: What is the current state of the systems?
A: d3web (with both d3web-Core3 and d3web-KnowWE, among others) are under active development. The University of Würzburg, Germany (Group Artificial Intelligence, Prof. Puppe) and denkbares GmbH are improving and extending the software continuously. denkbares GmbH also provides stable versions of d3web on a regular basis. The KnowME system was finally declared as "deprecated" in 2008 and is not under development any longer.
!! KnowWE: Knowledge Engineering
! Q: How to use JSPWiki's new look 'haddock' in KnowWE
A: Newer version of JSPWiki provide the shiny look n feel template 'Haddock'. KnowWE is able to use Haddock as well. Just open your custom properties
{{{
'KnowWE/webapps/KnowWE/WEB-INF/classes/jspwiki-custom.properties
}}}
in a text editor and change the property jspwiki.templateDir to
{{{
jspwiki.templateDir = haddock
}}}.
After a restart of KnowWE you should be able to use the Haddock template.
At line 43 changed 11 lines
A: Yes. In principle, KnowME and KnowWE use the identical knowledge representations as both build on d3web. So, already developed knowledge bases can be easily transfered to KnowWE. However, the more advanced system KnowWE provides additional knowledge representations, that also allow advanced applications, graphical knowledge modeling for instance. Being replaced by KnowWE since 2008, KnowME reached its EOL and you should consider to migrate to KnowWE, which is pretty much compatible. If you want to migrate, please contact us directly by [emailing info@d3web.de|mailto:info@d3web.de?subject=Migrate KnowME to wiki environment].
! Q: I started to build a knowledge base with ontoprise/semafora SemanticGuide. Is it possible to switch to KnowWE?
A: Yes, you can. Basically the SemanticGuide diagnostic flowcharts implements a subset of the functionality KnowWE provides. A successful migration of a real-world knowledge was already performed and reported. The result was an automated batch-converter that creates a KnowWE folder out of a SemanticGuide database, including all its contents. A description - including the source code of the converter - can be found at '[How to Migrate From SemanticGuide to KnowWE]'.
! Q: What types of problem-solving knowledge do you support in the current implementation of d3web?
A: Yes. In principle, KnowME and KnowWE use the identical knowledge representations as both build on d3web. So, already developed knowledge bases can be easily transfered to KnowWE. However, the more advanced system KnowWE provides additional knowledge representations, that also allow for a graphical knowledge modeling for instance. Being replaced by KnowWE since 2008, KnowME reached its EOL and you should consider to migrate to KnowWE, which is pretty much compatible. If you want to migrate, please contact us directly by [emailing to info@d3web.de|mailto:info@d3web.de?subject=Migrate KnowME to wiki environment].! Q: What types of problem-solving knowledge do you support in the current implementation of d3web?
At line 56 changed 3 lines
! Q: Am I able to model temporal relations between values in d3web?
! Q: Am I able to model temporal relations between values in d3web.
At line 61 changed 6 lines
! Q: What kind of knowledge is supported by d3web?
A: d3web supports a wide range of different types of knowledge. The main advantage is that all problem solving mechanisms can be combined and used within one knowledge base. The commonly used types of knowledge are:
* [Diagnostic Flowcharts | Doc Diaflux]
* [Set Covering Models | Doc CoveringList]
! Q: What kind of knowledge is supported by d3web.
A: d3web supports a wide range of different types of knowledge. The main advantage is that all problem solving mechanisms can be combined ind used within one knowledge base. The commonly used types of knowledge are:
* [Diagnostic Flowcharts | Doc DiaFlux]
* [Set Covering Models | Doc SetCoveringKnowledge]
At line 71 removed 2 lines
At line 41 added one line
A: Yes. Despite diagnostic knowledge, KnowWE also allows to specify semantic information which is denoted in a build in triple-store and can be access using SPARQL from any wiki page. This functionality is also used in this website, to add additional information to products and modules.
At line 75 removed 15 lines
A: Yes. Despite its diagnostic knowledge support, KnowWE also allows to specify semantic information which is denoted in a built-in triple-store and can be accessed using SPARQL from any wiki page. This functionality is also used on this website to add additional information to products and modules.
! Q: How can i get Admin rights in a (local) KnowWE installation?
A: Take the two files attached to this page and copy them into your wiki-sources folder (right with all the txt-files). Then (re-)start the wiki.
The admin account is:
__User__: knowweadmin \\
__password__: knowwed3web
''Note:'' Be sure to deactivate this account before you go online!
At line 91 removed one line
At line 50 added one line
At line 100 removed one line
At line 102 removed 2 lines
At line 109 changed 9 lines
! Q: Is d3web free to use?
A: Yes. Definitely! All core components to develop knowledge base systems are open source and free to use. Due to LGPL, you are also allowed to embed it into your own software products, even if they are commercial.
! Q: What do I need to develop and/or publish my own knowledge based system?
! Q: What I need to develop and/or publish my own knowledge based system?
At line 120 removed one line
At line 63 added one line
After developing your knowledge base, you can compile the knowledge base into a single file and publish. The knowledge base can be executed it together with your own application, where you have embedded the d3web-Core runtime environment. Alternatively you can also use one of the existing stand-alone runtime, available for Windows, Mac OS, Linux or Android. Please note that for the latter case not all existing runtime environments are open-source, but all of them are open-source, but all are free for non-comercial use.
At line 123 removed 3 lines
After developing your knowledge base, you can compile the knowledge base into a single file and publish. The knowledge base can be executed together with your own application, where you have embedded the d3web-Core runtime environment. Alternatively you can also use one of the existing stand-alone runtime, available for Windows, Mac OS, Linux or Android. Please note that for the latter case not all existing runtime environments are open-source, but all are free for non-comercial use.
At line 127 removed one line
At line 130 removed one line
At line 132 removed one line
At line 135 removed one line
At line 137 removed one line
At line 140 changed 3 lines
%%tags
User FAQ
%
This page (revision-45) was last changed on 20-Mar-2018 17:02 by Joba Baumeister Top