This page (revision-44) was last changed on 05-Dec-2018 17:56 by Tim Abler

This page was created on 17-Dec-2012 19:29 by Albrecht Striffler

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 05-Dec-2018 17:56 2 KB Tim Abler to previous
43 05-Dec-2018 17:54 2 KB Tim Abler to previous | to last
42 09-May-2015 00:46 2 KB Albrecht Striffler to previous | to last
41 09-May-2015 00:28 2 KB Albrecht Striffler to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 3 added one line
At line 5 changed one line
Packages can be used to define knowledge bases in KnowWE on different articles. Knowledge markups like [Questions|Doc Questions] and [Rules|Doc Rules] can be added to certain packages and the packages can later be added to a knowledge base.
Packages can be used to define knowledge in KnowWE on different articles. Knowledge markups like [Questions|Doc Questions] and [Rules|Doc Rules] can be added to certain packages and the packages can later be added/compiled to a knowledge base.
At line 8 changed one line
!!!Syntax - Basic
Also, ontologies are defined within the package mechanism.
At line 12 removed one line
!!Add all knowledge markups to a package at once
At line 14 changed one line
You can add the following markup in an arbitrary position on the article.
!! All markups of one article in the same package
At line 16 added 2 lines
By adding the following markup (in an arbitrary position on the article) the entire page including all markups are added to the package with the specified name {{myPackageName}}. The {{@package}} annotations shown below are then no longer necessary, but can be used to add the specific markup section to another package (as the one given with {{~%%Package}}). KnowledgeBases and Ontologies defined on articles with such a package markup will also be compiling that specified package, as long as nothing else is specified using the {{@uses}} annotation.
At line 20 removed one line
By doing this, all markups of this article are in the pagacke "myPackageName".
At line 22 changed 2 lines
!!Add a single knowledge markup to a package
Almost all knowledge markup support the annotation "@package: myPackageName".
!! Single markups of one article in different packages
When you want to put the markups on one article into different packages, you need to specifiy the package name within each markup.
Almost all knowledge markups support the annotation "@package: myPackageName".
At line 26 changed one line
__Example:__
__Example:__ The following questions are put into the package name {{myPackageName}}.
At line 38 removed one line
!!! Define a knowledge base containing a certain package
At line 40 changed one line
After adding knowledge markups to a certain package, the package can be compiled to a certain knowledge base using the following markup.
!! Compiling knowledge within a package
At line 45 added 2 lines
After adding knowledge to a certain package, the package can be compiled to a certain knowledge base using the following markup.
At line 53 added 33 lines
The knowledge base downloadable in this markup will then only contain the knowledge defined for the used package.
It is also possible to compile multiple markups and to add knowledge markups to multiple packages.
Alternatively, ontology definitions can be comiled by using the markup
{{{
%%Ontology
@uses: myPackageName
%
}}}
!!Using multiple packages for the same knowledge base or ontology
It is also possible to add/compile multiple packages in the same {{~%~%KnowledgeBase}} or {{~%~%Ontology}} markup. This way, it is for example possible to have a package {{common}} defining some common terminology. Then there can be different packages for different domains, let call them {{domain1}} and {{domain2}}. Together with the package {{common}}, they will each come together in knowledge base or ontology, e.g. by using the following:
{{{
%%Knowledgebase
@uses: common
@uses: domain1
%
}}}
Check out the following demo pages to see such a configuration in action: [Multi-Package Demo]
!!! See Also
* [KnowledgeBase|Doc KnowledgeBase]
* [Ontology|Doc Ontology]