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

Version management

Difference between version and

At line 5 added one line
At line 6 changed one line
At line 11 added one line
* [Hot keys and shortcuts|Doc Hot Keys]: List of shortcuts and hot keys usable in KnowWE
At line 16 removed one line
At line 20 changed one line
These elements can be distributed over the wiki by placing them on different articles.
These elements can be distributed across the wiki by placing them on different articles.
At line 24 added one line
At line 26 added one line
At line 27 removed one line
At line 30 changed one line
* [Covering Models|Doc SetCoveringKnowledge]: Using set coverage models to derive solutions
* [Covering Models|Doc CoveringList]: Using set-covering models to derive solutions
At line 32 changed 2 lines
* [Question|Doc Questions]: Defining questions and questionnaires
* [DiaFlux|Doc Diaflux]: Using diagnostic flowcharts to ask questions and establish 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
At line 35 changed one line
* [Abstraction Tables|Doc AbstractionTable]: Use tables to define a bunch of rules about the same objects
* [Abstraction Tables|Doc AbstractionTable]: Use tables to define a set of rules about the same objects
At line 38 removed one line
! Executing your Knowledge
At line 40 removed one line
The created knowledge base can be tested directly in your 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.
At line 42 changed 2 lines
* [Using the knowledge|Doc KnowledgeUsage]: Run a interview session in the wiki and check the derived solutions
* [QuickInterview|Doc QuickInterview]: Embed a inline dialog to use the knowledge in a wiki page
! Execute your Knowledge
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
At line 46 removed one line
! Testing your Knowledge
At line 48 changed 2 lines
There is a bunch of functionalities to test your knowledge during 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
! 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
At line 51 changed 5 lines
* [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] and [TestCaseSTC|Doc TestCaseSTC]: Two alternative ways to define test cases
* [TestDocumentation|Doc TestDocumentation|
* [KnowledgeBaseBook|Doc KnowledgeBaseBook]: Create a PDF file out of a knowledge base to review the contents that have been compiled into it
* [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]
At line 57 changed 4 lines
! Using Semantic Wiki Extensions
* [SPARQL|Doc SPARQL]: Execute a SPARQL query on the triple store and embed the result into a wiki page
* [RDFSTestCase|Doc RDFSTestCase]: Define test queries and their expected results to verify the quality of the triple-store data
* [Tags|Doc Tags]: Define tag names for wiki pages and navigate them through a tag cloud
! 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
At line 87 added one line
At line 94 added one line
* [Tags|Doc Tags]: Define tag names for wiki pages and navigate them through a tag cloud
At line 72 changed one line
* [Time Database|Doc Time Database]: Recording value changes over the time
* [Time Database|Doc Time Database]: Record and reason over value changes over the time
At line 105 added one line
At line 82 changed 2 lines
* Dynamic list of all articles tagged with "documentation: [TagSearch Documentation|http://www.d3web.de/Wiki.jsp?page=TagSearch&tag=Documentation]