This page (revision-110) was last changed on 22-Feb-2014 16:17 by Albrecht Striffler

This page was created on 20-Nov-2012 15:13 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
110 22-Feb-2014 16:17 2 KB Albrecht Striffler to previous
109 22-Feb-2014 16:17 2 KB Albrecht Striffler to previous | to last
108 22-Feb-2014 16:17 2 KB Albrecht Striffler to previous | to last
107 18-Dec-2012 11:02 2 KB Sebastian Furth to previous | to last
106 18-Dec-2012 00:11 2 KB Albrecht Striffler to previous | to last
105 17-Dec-2012 20:08 2 KB Sebastian Furth to previous | to last
104 17-Dec-2012 20:06 2 KB Sebastian Furth to previous | to last
103 17-Dec-2012 20:04 3 KB Volker Belli to previous | to last
102 17-Dec-2012 20:02 3 KB Volker Belli to previous | to last
101 17-Dec-2012 20:01 3 KB Volker Belli to previous | to last

Page References

Incoming links Outgoing links
Products
Products

Version management

Difference between version and

At line 1 removed 5 lines
!!! Main products
* __[d3web-Core|d3web-Core]__: The reasoning engine and persistence components for problem-solving knowledge including decision trees, (heuristic) rules, set-covering models and diagnostic flowcharts ([LGPL|http://www.gnu.de/documents/lgpl.de.html] with commercial extensions).
* __[KnowWE]__ (Knowledge Wiki Environment): As the successor of KnowME the system KnowWE (Knowledge Wiki Environment) offeres a web-based wiki front-end for the knowledge acquisition and supports the collaborative engineering of knowledge at different formalization levels.
At line 8 changed one line
The applications listed below are applications using either d3web-Core, or both, d3web-Core and KnowWE.
! [d3web-Core|d3web-Core]
The reasoning engine and persistence components for problem-solving knowledge including decision trees, (heuristic) rules, set-covering models and diagnostic flowcharts ([LGPL|http://www.gnu.de/documents/lgpl.de.html], optional commercial extensions).\\
[more...|d3web-Core]
At line 10 removed 4 lines
!! Open Source Applications
* __[KnowWE-Headless-App]__: An version of KnowWE without the normally underlying web server. It can be used to produced d3web knowledge bases from wiki pages in a batch process.
* __ProKEt__: Prototyping of knowledge-based dialog systems.
* __WUMPS__: Knowledge acquisition based on Office documents.
At line 15 changed 3 lines
!! Free Applications
* __[Mobile-App]__: Application allowing to use d3web problem solving knowledge in a stand alone application.
* __[Droid3web-App]__: Application allowing to use d3web problem solving knowledge on your mobile device.
! [KnowWE] (Knowledge Wiki Environment)
As the successor of KnowME the system KnowWE (Knowledge Wiki Environment) offeres a web-based wiki front-end for the knowledge acquisition and supports the collaborative engineering of knowledge at different formalization levels ([LGPL|http://www.gnu.de/documents/lgpl.de.html], optional commercial extensions). \\
[more...|KnowWE]
At line 19 changed 3 lines
!!Commercial Applications
* __[KnowledgeBaseBook]__: Generates a DocBook XML file of an executable d3web knowledge base, i.e., the knowledge base book. The DocBook XML can be used for further transformations. The application produces a PDF printout.
* __[Testing-App]__: Allows to continuously run specified tests on a d3web knowledge base in development.
! Dialog Applications
* __ProKEt__: Prototyping of knowledge-based dialog systems ([LGPL|http://www.gnu.de/documents/lgpl.de.html]).
* __[Mobile-App]__: Application allowing to use d3web problem solving knowledge in a stand alone application (free-to-use).
* __[Droid3web-App]__: Application allowing to use d3web problem solving knowledge on your mobile device (free-to-use).
At line 23 changed one line
!!! Modules (under construction)
! Knowledge Engineering Tools
* __[KnowledgeBaseBook]__: Generates a DocBook XML file of an executable d3web knowledge base, i.e., the knowledge base book. The DocBook XML can be used for further transformations. The application produces a PDF printout (commercial application).
* __WUMPS__: Knowledge acquisition based on Office documents ([LGPL|http://www.gnu.de/documents/lgpl.de.html]).
* __[KnowWE-Headless-App]__: An version of KnowWE without the normally underlying web server. It can be used to produce d3web knowledge bases from wiki pages in a batch process ([LGPL|http://www.gnu.de/documents/lgpl.de.html]).
* __[Testing-App]__: Allows to continuously run specified tests on a d3web knowledge base in development (commercial application).
\\
\\
%%collapsebox-closed
! Modules (under construction)
At line 33 changed 6 lines
%%Todo
Licenses
* add articles for the different licenses and link them
* d3web-KnowWE-Releases contain all used licenses...
@user: Albrecht Striffler
%
[...additional module information (under construction)|Modules Under Construction]
At line 41 removed 43 lines
%%Todo
Module-Plugin implementation
* Jenkins-Plugin to upload Plugin/Module information
** [https://wiki.jenkins-ci.org/display/JENKINS/Extend+Jenkins]
** SVN: https://svn.jenkins-ci.org/
** Download jenkins war and add to tomcat
** Get hello world plugin and import into new workspace
** Plugin execution not covered by lifecycle configuration does not matter, it is just ugly
** Maven install hello world plugin
** Copy hello-world.jar to WEB-INF\lib
** Copy hello-world.hpi to WEB-INF\plugins
** Start tomcat/jenkins
** Hello world plugin will be available as post step option
** Start implementing new plugin to upload build data to d3web.de page as a attachment
** [Some additional code snipplets on how to upload files to a KnowWE Action|Upload a file to KnowWE]
** Provide information needed for module pages
@user: Alex Legler
%
%%Todo
Module-Plugin implementation
* Design ontologie about module information. We want for example the following information per module:
** What maven modules / svn projects are part of this module (will be defined on the module page with turtle markup)
** What projects are not in any complex/aggregated module
** What are the last x changes to any project of a module
** What is the heat of the module (changes/day in the last month?)
** What are the test stats for the module
** General stats, if possible? LoC, Classes, BuildNumber
** Authors (people who created modules, changed them)
** More interesting stuff?
* Write KnowWE-Plugin to add data provided by Jenkins-Plugin to the rdf2go model.
* If there is time: Write KnowWE-Plugin to render module information from rdf2go model in a nicer way. If there is no time: Use default SparqlRenderer
@user: Sebastian Furth
%
!Product Ontology
* [Product Ontology]
* [CIConnector] (includes some DEMO-SPARQLs)
At line 87 changed 8 lines
!Quality assessment of the modules:
%%Table
| no | Not officially included, experimental demo
| alpha | Basic functions included, API to be considered as unstable documentation partly available/not available mostly untested
| beta | All functions are included documentation available functionality tested on unit level
| release | All functions are included documentation available functionality tested on system level (integration tests) internal processes fully applied (issue management, development process)
%
%%
This page (revision-110) was last changed on 22-Feb-2014 16:17 by Albrecht Striffler Top