This page (revision-44) was last changed on 29-Apr-2015 10:57 by Albrecht Striffler

This page was created on 26-Oct-2012 10:15 by Joachim Baumeister

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
44 29-Apr-2015 10:57 7 KB Albrecht Striffler to previous
43 29-Apr-2015 10:33 7 KB Albrecht Striffler to previous | to last
42 24-Nov-2014 11:17 6 KB Jochen Reutelshöfer to previous | to last
41 24-Nov-2014 11:13 6 KB Jochen Reutelshöfer to previous | to last

Page References

Incoming links Outgoing links
Doc Overview
Doc Overview

Version management

Difference between version and

At line 1 added 9 lines
%%Todo
Revise/update this page. Is it complete and up to date?
At first glance:
* Packages
* AbstractionTabel
* Todos
@user: Carsten Wasner
%
At line 3 removed one line
Therefore, many [JSPWiki|http://www.jspwiki.org/wiki/JSPWikiDocumentation] markups can be directly used in KnowWE.
At line 5 removed one line
At line 7 changed one line
At line 11 removed one line
* [Hot keys and shortcuts|Doc Hot Keys]: List of shortcuts and hot keys usable in KnowWE
At line 13 removed 3 lines
%%tags
FirstSteps
%
At line 17 removed one line
At line 21 changed one line
These elements can be distributed across the wiki by placing them on different articles.
These elements can be distributed over the wiki by placing them on different articles.
At line 26 added 2 lines
You then declare a new knowledge base by specifying the used packages, that should be included into this knowledge base.
For the creation of the knowledge base all knowledge elements of the specified packages are picked and included.
At line 25 changed one line
! Defining your Knowledge
* The mandatory markups to define a knowledge base: [Creating a knowledge base|Doc KnowledgeFormalization]
* Alternative compilation of knowledge bases, that should be only used for testing: [Explicit Compile|Doc PackageCompile]
At line 27 changed 2 lines
You may declare a new knowledge base by specifying the used packages, that should be included into this knowledge base.
For the creation of the knowledge base all knowledge elements of the specified packages are picked and included. Detailed descriptions on the definition of knowledge base elements are provided as following:
More detailed descriptions on the definition of knowledge base elements is also provided:
At line 30 changed 10 lines
* [Creating a knowledge base|Doc KnowledgeFormalization] and [KnowledgeBase|Doc KnowledgeBase]: The mandatory markups to define a knowledge base
* [Package|Doc Package]: Defining packages to group knowledge
* [Covering Models|Doc CoveringList]: Using set-covering models to derive solutions
* [Solution|Doc Solutions]: Defining solutions and groups of solutions
* [Question|Doc Questions]: Defining questions and questionnaires (groups of questions)
* [DiaFlux|Doc Diaflux]: Using diagnostic flowcharts to ask questions, derive abstractions, and establish solutions
* [Rule|Doc Rules]: Using rules to derive abstractions and score solutions
* [Abstraction Tables|Doc AbstractionTable]: Use tables to define a set of rules about the same objects
* [Property|Doc Properties]: Adding special behavior to objects and translate them into multiple languages
* [Resource|Doc Resources]: Adding multimedia resources to your knowledge base. To add clickable images with sensitive areas to questions, also have a look at the [Image Maps | Doc ImageMap].
* [Questions|Doc Questions]
* [Solutions|Doc Solutions]
* [Rules|Doc Rules]
* [Covering Models|Doc SetCoveringKnowledge]
* [Adding resources|Doc Resources]
* [Adding properties|Doc Properties]
At line 41 added one line
The created knowledge base can be tested by using the inline quick interview or by running test cases:
At line 42 changed one line
! Execute your Knowledge
* [Using the knowledge|Doc KnowledgeUsage]: Run a interview session in the wiki and check the derived solutions.
* [Knowledge Evaluation with test cases | Doc TestCase]: Explains, how knowledge can be evaluated in KnowWE using a suite of test cases.
* [Continuous Integration | Demo - Continuous Integration]: KnowWE provides a plugin for continuous integration of knowledge bases; a dashboard always informs you about the healthiness of your knowledge project.
At line 44 removed 52 lines
The created knowledge base can be tested directly in the wiki. For this you can use the inline quick interview or a user-driven simple click-dialog. Alternatively you may download the knowledge base as a separate file to run on Android or in a stand-alone application.
* [Using the knowledge|Doc KnowledgeUsage]: Run an interview session in the wiki and check the derived solutions
* [QuickInterview|Doc QuickInterview]: Embed an inline dialog to use the knowledge in a wiki page
* [ShowSolutions|Doc ShowSolutions]: Show the derived solutions and/or values in a wiki page
! Test your Knowledge
There exists a bunch of functionalities to test your knowledge during the development.
Some tests may be executed manually as required, but you can also define them to be running automatically in the background every time a change is applied to the wiki.
In this case, you can specify a signal in the left menu of the wiki to indicate the current quality status.
* [CIDashboard|Doc CIDashboard] and [CIDaemon|Doc CIDaemon]: Continuous integration of knowledge bases; a dashboard always informs you about the healthiness of your knowledge project
* [TestCasePlayer|Doc TestCasePlayer]: Execute the test cases to verify the behavior of the knowledge base
* [Timeline | Doc Timeline]: Execute and filter test cases
* [TestCase|Doc TestCase]: Define test cases to verify the behavior of the knowledge base. It explains, how knowledge can be evaluated in KnowWE using a suite of test cases
* [TestCaseTable|Doc TestCaseTable]: Table-based definition of test cases
* [TestCaseSessionRecord|Doc TestCaseSessionRecord]: An alternative way to define test cases
* [KnowledgeBaseBook|Doc KnowledgeBaseBook]: Create a PDF file from of a knowledge base to review the contents that have been compiled into it
* [Analysing KPIs (Key Performance Indicators)|Doc KPI]: Define KPIs and analyse how your knowledge base performs for these KPIs in different [TestCases|Doc TestCaseTable]
! Development of Ontologies
KnowWE allows to define ontologies in RDF(S) directly within the Wiki using the following markups:
* [Creating an Ontology | Doc Ontology]: How to create a new ontology
* [Namespace| Doc Namespace]: Define dinstinct namespaces or import 3rd party ontologies
* [Turtle| Doc Turtle]: Establish multiple relations for a resource using the Turtle syntax
* [SPARQL|Doc SPARQL]: Include SPARQL queries and embed the results into a wiki page
* [InlineSparql|Doc InlineSparql]: Show the information or number of lines of a SPARQL query inline in any non-markup text
Markups for Visualization of Ontologies:
* [SparqlVisualization | Doc SparqlVisualization]: A visualization where the visualized parts are defined using the SPARQL language (c.f. [SPARQL|Doc SPARQL]).
* [ConceptVisualization | Doc ConceptVisualization]: A simple visualization method where one or multiple ontology concepts are selected for visualization.
Also, a number of proprietary markups have been introduced in the past:
* [Class| Doc Class]: Define classes (rdfs:Class)
* [Individual| Doc Individual]: Define indiviuals
* [ObjectProperty| Doc ObjectProperty]: Define object properties with domain and range
* [Relation| Doc Relation]: Establish relations (triples) between resources
! Other helpful markups
* [Status|Doc Status]: Set a workflow status for a specific wiki page
* [Table|Doc Tables]: Define a table in a wiki page
* [Todo|Doc Todo]: Defines a todo entry for the wiki content
* [TodoList|Doc TodoList]: Displays a list of todo entries
* [UML|Doc UML]: Define UML diagrams based on PlantUML syntax
* [Include|Doc Include]: Includes a wiki page or a particular chapter of a wiki page into an other page
* [Tags|Doc Tags]: Define tag names for wiki pages and navigate them through a tag cloud
At line 98 changed 6 lines
* [Extended Expressions|Doc Expressions]: Conditions and actions in rules and DiaFlux
* [Time Database|Doc Time Database]: Record and reason over value changes over the time
* [Timechart|Doc Timechart]: Displays the trend of some values over the time
* [Variable|Doc Variable]: Assign results of expressions to questions
* [Constant|Doc Constant]: Define a constant to be used in expressions
* [Image Map|Doc ImageMap]: Define clickable images to answer questions
* [Extended Expressions|Doc Expressions] for conditions and actions in rules and DiaFlux.
* [Time Database|Doc Time Database] for recording value changes over the time.
* [Image Map|Doc ImageMap] for defining clickable images to answer questions
At line 110 changed one line
* Dynamic list of all articles tagged with "documentation: [TagSearch Documentation|http://www.d3web.de/Wiki.jsp?page=TagSearch&tag=Documentation]
%%tags
Documentation
%
This page (revision-44) was last changed on 29-Apr-2015 10:57 by Albrecht Striffler Top