l10n.ro - Contribuții utilizator [ro]

Ajutor:What is context sensitive help?

2007-11-14T23:25:49Z

127.0.0.1: What is context sensitive help?

;Question
:[[question:=What is the context sensitive help]]?

;Answer
:[[Description:=The CSH shows help topics that could be useful in your current workflow.]]
[[DiscourseState:=Main:edit| ]]

==What is Context Sensitive Help?==
Context Sensitive Help (CSH) is a function that supports you during your work with Semantic MediaWiki (SMW). If you use ''OntoSkin'' as your default skin in this wiki, you can see the "Sematic Toolbar" on some pages. One item of the Semantic Toolbar is titled "Help" and containts the CSH.

CSH offers help contents based on your current action and location in the wiki. Depending on what you do, CSH will show different help questions and provide answers to those questions.

Users can not only read those help contents, but they are also encouraged to ask new questions or edit unanswered questions.

==Accessing Context Sensitive Help==
CSH is a part of the Semantic Toolbar which can only be seen if the OntoSkin Skin is enabled. At the very bottom, you can see the CSH window.

[[Image:Doc_CSH01.jpg|thumb|CSH container in the semantic toolbar.]]

If there are any help questions available, they will be shown in this area. However, only a maximum of five questions is shown at a time. You can access all relevant help contents by clicking on the "more" link at the bottom.

By clicking on one of the help questions, a new window will appear with the according help page, providing answers and solutions to the problem.

==Finding Help==
In order to find relevant help contents, you can not only look at the CSH area in the Semantic Toolbar, but you can also access the Special Page [[Special:ContextSensitiveHelp]].

[[Image:Special_CSH01.jpg|thumb|CSH page with filter options]]

You can use the two option boxes to select a specific namespace or action. The special page will then show all help contents that are relevant for your choice.

==Adding new questions==
You can add new questions at the bottom of the help area in the Semantic Toolbar. After clicking "Ask your own question", an input box will appear where you can enter your question. The system will then automatically create the according help page with all necessary annotations. Unanswered questions will appear as red links, while answered questions will appear as blue links.

==Adding answers to questions==
If you see an unanswered question and know the answer, you can answer it by simply clicking on it. On the page, you can see three annotations. One contains the question and another one the discourse state. Please do not edit those thwo values since they are crucial for CSH to work.

The third annotation is called "description". This should deliver a short answer to the question which will appear as a tooltip whenever a link to this question appears.

If you know the answer to a question, simply add it to the article as if you would edit a standard wiki article. Add a small summary into the "Description" annotation and you are done. Other users can now access this page or use the tooltip as support for their work with SMW.

== Administrator's note ==

'''If you want to know how to set up and manage context sensitive help, please see [[Help:Setup_And_Manage_CSH]]'''

Ajutor:What is gardening?

2007-11-14T23:25:49Z

127.0.0.1: What is gardening?

;Question
:[[question:=What is gardening]]?

;Answer
:[[Description:=Gardening keeps the knowledgebase tidy.]]
[[DiscourseState:=Gardening:view| ]]

The Gardening features are accesible as a SpecialPage called 'Gardening'. There is also a shortcut in the main toolbox on the left.

[[Image:GardeningSpecialPage.png|thumb|300px|The gardening special page]]

Depending on which user group you belong to, you will see a different set of bots in the left box (1). There are 3 user groups:

*darkmatter: The ordinary wiki user. He can only access read-only bots, which do not cause too much database load.
*gardener: A special wiki user whose main job is to keep the knowledgebase clean and consistent. He may access all bots.
*sysop: The wiki administrator. He may access all bots.

When you select a bot, he will get its parameters in the right box (2). There are two kind of parameters: Required and optional ones. Required parameters are indicated by a * after the name.

[[Image:SelectedBot.png|thumb|left|300px|The gardening page showing the properties of a selected bot.]]

After the parametrization, press 'Run Bot'. The bot is started and a new line appears in the Gardening Log table below showing that a new bot has been started. When the bot has finished, the user receives an email about that (if he supplied one at registration) and he may view the log by clicking the 'Log' link in the Gardening table. The users can view all logs no matter which user group they belong to.

== Administrator's note ==
''Note:'' The Gardening feature needs a new environment variable in LocalSettings.php to work properly:
*$phpInterpreter: Points to the php-Interpreter installed on the system, e.g. $phpInterpreter="D:/xampp152/xampp/php/php";

Additionally, the SMTP server entry should be set in php.ini
*php.ini should contain a valid SMTP server, e.g. SMTP = 87.106.5.57 for Ontoprise SMTP server. Otherwise email notification will not work.

:Chemical equation

2007-11-14T23:25:49Z

127.0.0.1: Chemical equation

A chemical equation consists of reactants an arrow and the products. These products can be the reactants of an immediatly following reaction that yields further products.

Reactants and products are concatenations of chemical formulas (see [[Type:Chemical formula]]). The formulas are connected with a + or a * (or x) (which yields ●).

The arrows are ←, → and ⇌ (chemical equilibrium).

Valid formulas are:
* HC2H3O2(aq) ⇌ H+(aq) + C2H3O2-(aq)
* 4 Fe2+(aq) + O2(g) + 4 H2O(l) + 2x H2O(l) → 2 Fe2O3●x H2O(s) + 8 H+(aq)
*2 H2O ← 4 H + O2
* CH3CH2OH + H2SO4 (conc. aq) → CH3CH2OSO3H + H2O → H2C=CH2 + H2SO4 + H2O

===Wiki text for chemical equations===

Chemical equations consist mainly of chemical formulas. These are connected by the following symbols (connectors) in wiki text:
* <code>-></code>: → (Reaction)
* <code><-</code>: ← (Reaction)
* <code><-></code>: ⇌ (Equilibrium)
* <code>+</code>: +
* <code>*</code> or <code>x</code>: ●

There must be no spaces within the arrows. An equation must begin and end with a formula. There must be exactly one connector between formulas.

===Type for chemical equations===
The wiki offers the type <code>Type:Chemical equation</code>. Attributes with this type are checked for correctness with the rules above. Only syntactical correctness can be checked i.e. chemical rules can still be violated.

===Grammar for chemical equations as wiki text===

(Elements in brackets [] are optional, {} groups elements, * means 0 or more repetitions of a group, + means one or more repetitions, | means "or")

* Chemical equation: <code>CE := CF [{'+'|'*'} CF]* { {'<-' | '<->' | '->' } CF [{'+'|'*'} CF]*}+</code>
* Chemical formula: <code>CF</code> (see [[Type:Chemical formula]])

===Error messages===

Each kind of error message is given by an example:

* 2H2+O2:"2H2+O2" is not a chemical equation.
* 2n n H -> H:Syntax error in chemical formula "2n n H".
* H ** H -> H:There is a missing or needless operator in "H ** H -> H".

===Testing chemical equations===

Below is a set of expressions in wiki text for chemical equations. The attribute <code>has equation</code> must have the type <code>Type:Chemical equation</code>. Equations that are rejected by the parser are rendered in a box. Error messages will be displayed in the fact box.

<pre>
<nowiki>

* Correct

[[has equation:=C2H5. + O2 -> C2H4 + .OOH]]

[[has equation:=H2O->O2->H2O]]

[[has equation:= Ag -> Br <- Cl]]

[[has equation:= HCl(aq) -> H^+ + Cl^-(aq)]]

[[has equation:=4Fe2^+(aq) + O2(g) + 4 H2O(l) + 2nH2O(l) -> 2Fe2O3*nH2O(s) + 8H^+(aq) ]]

[[has equation:=2 H2O <- H2 + 2O]]

[[has equation:= 4H + 2O -> 2H2O]]

[[has equation:= Mg(NO3)2(l) <-> Mg(((NO3)2)5)4(aq)]]

[[has equation := 6AlBr -> Al2Br6 + 4 Al]]

[[has equation:= 48^Ti3->2 34^Ti^2-]]

[[has equation:= 2 48^Ti3^3+-> 2H2O3C4]]

[[has equation:= 48^Ti^3+<->Ti^3-]]

[[has equation:= FeCl3 + K3PO4 -> FePO4 + KCl]]

[[has equation:= HC2H3O2(aq) <-> H^+(aq) + C2H3O2^-(aq)]]

* Wrong

[[has equation:= 2n n H -> H]]

[[has equation:= H ** H -> H]]

[[has equation:= H + + H -> H]]

[[has equation:= 2H2 O2 -> H]]

[[has equation:= + 2H2 + O2 -> H]]

[[has equation:= 2H2 + O2 + -> H]]

[[has equation:= 2H2 + O2 -> H+]]

[[has equation:= 2H2 + O2 -> +H]]

[[has equation:= H < - > O]]

[[has equation:= H - > O]]

[[has equation:= H < - O]]

[[has equation:= H2O]]

[[has equation:= HCl(aq) -> H+ + Cl-(aq)]]

[[has equation:= HC2H3O2(aq) <-> H+(aq) + C2H3O2-(aq)]]

[[has equation := C6H12O6]]
</nowiki>
</pre>

:Chemical formula

2007-11-14T23:25:49Z

127.0.0.1: Chemical formula

A chemical formula describes an atom or a molecule such as Fe or FeCl3 or 3FeCl3.
They are not to be confused with [[Type:Chemical equation]] which are a concatenation of chemical formulas.

===Syntax of chemical formulas (in chemistry)===
*The formula is a concatenation of atom names. Each of these can have a subscript that defines the number of the atom's occurrences in the molecule.
*A number at the beginning of the formula indicates the number of molecules/atoms/mols e.g. 3KCl.
*Representation as ion e.g. Mg2+.
*Representation as isotope e.g. 48Ti3+ is the ion of titanium-48. Isotopes can only be given for elements, not for molecules.
*Molecules in a molecule can have an index e.g. Mg(NO3)2
*The state of matter ((g)as, (l)iquid, (s)olid, (aq)ueous) can optionally be defined.

===Chemical formulas in the wiki===

There is a simple syntax for chemical formulas in the wiki.
* Elements are the standardized abbreviations for elements where the first letter is always uppercase e.g. <code>Fe</code>.
* Subscripts are simply appended to the element e.g. <code>H2</code> (=> H2)
*Isotopes of elements are defined like this:
**<code>48^Ti</code> (=>48Ti).
**The element can have an index e.g. <code>48^Ti3</code> (=> 48Ti3).
**Ions of isotopes are defined like this: <code>48^Ti^2+</code> (=> 48Ti2+).
**This can also be combined with an index for the element.
**Isotopes can not be defined for molecules
* Elements can be combined to molecules by just concatenating them e.g. <code>KCl</code>.
* Elements can have indices in a molecule e.g. <code>H2O</code> (=>H2O)
* Molecules can be grouped within molecules e.g. <code>Mg(NO3)2</code> (=> Mg(NO3)2) Nested brackets are allowed.
* Molecules can be radicals e.g. <code>.OOH</code> (=> •OOH) or <code>CH3.</code> (=> CH3•)
* Molecules can have double or triple connections e.g. <code>CH2=CH2</code> (=> CH2=CH) or <code>CH2=-CH2</code> (=> CH2≡CH2)
* Ions can also be defined for molecules e.g <code>SO4^3+</code> (=> SO43+)
* The amount of elements, isotopes and molecules can be given by a number in front of them e.g. <code>2 H2O</code> or <code>2H2O</code> (=> 2 H2O)
* Sometimes a variable is needed for the amount. In this case the number can be replaced by an n e.g. <code>nH2O</code>. There can also be factors for variable amounts e.g. <code>2nH2O</code>.
* The state of all matter can be appended e.g. <code>NaCl(aq)</code> (=> NaCl(aq)). These are the possible states:
**(g) gas
**(l) liquid
**(s) solid
**(aq) aqueous
:Each of these four descriptions can be arbitrarily augmented e.g. (conc. aq, 98%). There must be no further brackets within the state's description.

===Spacing===

* Spaces are allowed between the number and the molecule.
* Within a molecule there must be no spaces.
* There must be no spaces in and around the exponent of isotopes and ions.

===Type for chemical formula===

The wiki offers the type <code>Type:Chemical formula</code>. Attributes with this type are checked for correctness with the rules above.

===Grammar for chemical formulas as wiki text===

(Elements in brackets [] are optional)

* Chemical formula: <code>CF := N ' ' M[SOM]</code>
* Number of molecules/atoms/mols: N := number ['n']
* Molecule: M := ED | '('M')'number | MM | M MC M | M ION | ["."] M ["."]]
* Molecule connection: MC := '=' | '=-'
* Element descriptor: ED := [I]E[number] | [I]E[number][ION]
* Isotope: I := number '^'
* Ion: ION := '^'[number]{'+'|'-'}
* Element: E := Symbol of all chemical elements
* State of matter: SOM := '(' [SOMMOD NOTALPHANUM] 'g' [NOTALPHANUM SOMMOD] ')' |
: '(' [SOMMOD NOTALPHANUM] 'l' [NOTALPHANUM SOMMOD] ')' |
: '(' [SOMMOD NOTALPHANUM] 's' [NOTALPHANUM SOMMOD] ')' |
: '(' [SOMMOD NOTALPHANUM] 'aq' [NOTALPHANUM SOMMOD] ')'
* State of matter modifier:
: SOMMOD := any string but "(" and ")"
: NOTALPHANUM := anything but letters nor digits

===Testing chemical formulas===

Below is a set of expressions in wiki text for chemical formulas. The attribute <code>has formula</code> must have the type <code>Type:Chemical formula</code>. Formulas that are rejected by the parser are rendered in a box. Error messages will be displayed in the fact box.

<pre>
<nowiki>
''''x' has the same meaning as '*''''

[[has equation:=2nH2O(l) -> 2Fe2O3xnH2O(s)]]

[[has equation:=2nH2O(l) -> 2Fe2O3*nH2O(s)]]

'''The former meaning of 'x' as variable is now written as 'n':'''

[[has formula:= nMg(aq)]]

[[has formula:= 2nMg(aq)]]

'''Arbitrary modifiers for states of matter:'''

* Correct
[[has formula:= H2O(conc.aq,98%)]]
[[has formula:= H2O(conc aq 98%)]]
[[has formula:= H2O(aq,conc.)]]
[[has formula:= H2O(98% aq)]]
* Wrong
[[has formula:= H2O(concaq,98%)]]
[[has formula:= H2O(conc aq98%)]]
[[has formula:= H2O((conc) aq98%)]]
[[has formula:= H2O(solid)]]

'''Connections:'''

* Correct

[[has formula:= CH2=CH2]]
[[has formula:= CH2=-CH2]]

* Wrong
[[has formula:= CH2==CH2]]
[[has formula:= CH2==-CH2]]
[[has formula:= CH2-=CH2]]

'''Radicals:'''

[[has equation:=C2H5. + O2 -> C2H4 + .OOH]]

'''Elements'''

* Correct

[[has formula:= Mg]]

[[has formula:= 2Mg]]

[[has formula:= 2 Mg]]

[[has formula:= Mg(aq)]]

[[has formula:= 2Mg(aq)]]

[[has formula:= nMg(aq)]]

[[has formula:= 2nMg(aq)]]

* Wrong

[[has formula:= Mi]]

[[has formula:= Mg (aq)]]

[[has formula:= 2(aq)]]

'''Molecules'''

* Correct

[[has formula:= MgAg]]
[[has formula:= Mg2Ag3]]

* Wrong

[[has formula:= Mg Ag]]

'''Isotopes / Ions'''

* Correct

[[has formula:= 48^Ti]]

[[has formula:= 48^Ti3]]

[[has formula:= 48^Ti^2-]]

[[has formula:= 48^Ti3^2-]]

[[has formula:= 2 48^Ti^2-]]

* Wrong

[[has formula:= 48 ^ Ti]]

[[has formula:= 48^Ti3Ag4]]

[[has formula:= 48^Ti^2 -]]

[[has formula:= 48^Ti^ab]]

[[has formula:= Ti3-]]

[[has formula:= Ti3+]]

'''Molecule groups'''

* Correct

[[has formula:= Mg(NO3)2(l)]]

[[has formula:= Mg(((NO3)2)5)4(aq)]]

* Wrong

[[has formula:= Mg(((()NO3)2)5)4(aq)]]

[[has formula:= Mg(N)O3)2(l)]]

[[has formula:= Mg(NupQ3)2(l)]]

[[has formula:= Mg(N(O3)2(l)]]

'''Equation assigned to formula (wrong):'''

[[has formula := 4H + O2 -> 2H2O]]

'''Neither equation nor formula'''

[[has formula := 2Fe2O3*nH2O(s)]]

</nowiki>
</pre>

Ajutor:What can I specify in Property Properties?

2007-11-14T23:25:48Z

127.0.0.1: What can I specify in Property Properties?

;Question
:[[question:=What can I specify in Property Properties]]?

;Answer
:[[description:=Property properties define the characteristics of a property, such as e.g. domain and range.]]

==Property properties in the semantic toolbar==

The semantic toolbar contains additional tools when the definition of a property is edited. These features are hosted in the toolbox labeled ''Property Properties''.

[[Image:REQ_SEMWIKI_18_PropertyProperties.png|thumb|614px|center|The wiki text for the definition
of a property and the corresponding Property Properties in the semantic toolbar.]]

The properties of a property are:
* '''Domain''' - Articles of this category can have values for this property.
: Wiki text: <code><nowiki>[[Has domain hint::Category:<domain>]]</nowiki></code>
* '''Range''' - Articles of this category are object of the property. This field is only enabled, if the property's type is ''Page''.
: Wiki text: <code><nowiki>[[Has range hint::Category:<range>]]</nowiki></code>
* '''Inverse of''' - The name of the property that is the inverse of the current property.
: Wiki text: <code><nowiki>[[Is inverse of::Property:<inverse property>]]</nowiki></code>
* '''Type''' - One of the predefined types. Two of them require additional explanations. The type ''Page'' indicates that the property's values are wiki articles. Their ''Range'' defines the category of articles. The type ''N-ary'' states that the property can have several ranges and types.
: Wiki text: <code><nowiki>[[has type::Type:<data type>]]</nowiki></code>
* '''Minimal cardinality''' - The minimal number of values of the property. (This field is not enabled when the properties type is ''N-ary''.)
: Wiki text:<code><nowiki>[[Has min cardinality:=<number>]]</nowiki></code>
* '''Maximum cardinality''' - The maximal number of values of the property. (This field is not enabled when the properties type is ''N-ary''.)
: Wiki text: <code><nowiki>[[Has max cardinality:=<number>]]</nowiki></code>
* '''Transitivity''' - Defines that the property is transitive. This field is only enabled, if the property's type is ''Page''.
: Wiki text: <code><nowiki>[[Category:Transitive relations]]</nowiki></code>
* '''Symmetry'''- Defines that the property is symmetric. This field is only enabled, if the property's type is ''Page''.
: Wiki text: <code><nowiki>[[Category:Symmetrical relations]]</nowiki></code>

When the article for a property definition is opened for editing, the ''Property Properties'' are initialized according to the wiki text. When schema relevant properties are changed in the wiki text, they are updated in the semantic toolbar after a short delay.

The fields ''Domain'', ''Range'' and ''Inverse of'' are supported by auto completion. When they lose the input focus, the system checks if the categories or properties really exist. Valid entries are marked in green, invalid ones in orange. However, the system does not enforce valid values as you might create the missing category or property later.

The fields for the cardinality are syntax checked. They must contain valid numbers. Wrong values are marked in red and can not be applied.

[[Image:REQ_SEMWIKI_18_InvalidValues.png|thumb|200px|center|Invalid values are highlighted in the Property Properties.
Wrong values are marked red and can not be applied.]]

The lower left corner of the ''Property Properties'' shows usability hints:
* Nothing changed. - As long as no property has been changed, the properties can not be applied.
* Error messages for invalid cardinalities.
* Apply - Changed values can be applied i.e. the wiki text is updated accordingly.

New values are only applied when the ''Apply'' link is clicked. Clicking the link ''Cancel'' restores the current values of the wiki text in the ''Property Properties''

If property fields are empty their corresponding wiki text will be deleted. If a property is newly introduced, its wiki text will be appended at the very end of the article. If the same kind of property definition appears several times in the wiki text, only its first value will be shown in the semantic toolbar.

'''Editing n-ary properties'''

N-ary properties can have several values at a time. For instance, the density of a substance is defined for a certain temperature and pressure.

[[Image:REQ_SEMWIKI_18_NaryProperties.png|thumb|200px|center|The definition of the n-ary property "density" of a chemical substance.]]

To edit an n-ary property, its type has to be switched to ''N-ary''. Most of the input fields will be disabled. Two additional links appear at the bottom of the Property Properties toolbox: ''Add type'' and ''Add range''.

''Add type'' adds a type selector to the toolbox. All built-in types can be selected. User-defined types that are defined in a wiki article are not yet supported in the selector. However, they can be entered in the wiki text with support of auto-completion. Thus specified they will be displayed in the type selector as well.

''Add range'' adds a range input field to the toolbox. Entering a category is supported by auto-completion.

To the right of each input field there is a red cross that can be clicked to delete the property. When the last range or type has been removed, the type selector switches to ''Page''.

The generated wiki text that defines an n-ary property has the following format:
<nowiki>
[[Has type:=<List of types separated by semi-colon>]]
e.g.
[[Has type:=Type:Temperature;Type:Pressure;Type:Density]]
</nowiki>

The type for references to wiki articles is called <code>Type:Page</code>.

[[discourseState:=Property:edit| ]]

Ajutor:What does the Combined search show?

2007-11-14T23:25:48Z

127.0.0.1: What does the Combined search show?

;Question
:[[question:=What does the combined search show]]?

;Answer
:[[description:=The combined search shows helpful entities from the wiki knowledgebase.]]

The CombinedSearch is an extension of the current Wiki Search available via the search-box on left-hand side. The user is supposed to enter an arbitrary number of search terms into that search-box and to press enter.

==How it works==
Every search term is used individually. If the user wants to specify a term containing a whitespace, he has to put that term in quotes. Example: '''chlorine "atomic orbital"''' would search for 'chlorine' and 'atomic orbital' instead of 'chlorine' 'atomic' and 'orbital'.

[[Image:search-box.png|thumb|200px|center|The standard text field is used for the combined search.]]

If the system does not find an article matching the given title (which is likly when many terms are entered), the CombinedSearch is activated automatically.

[[Image:Combinedsearch.gif|thumb|300px|The semantic search result page.]]

== Identified entities ==

The first table in the CombinedSearch Tab shows the identified entities. The entity search process consists of three steps: Exact matching, substring matching and edit distance matching. All case-insensitive.

The user has 3 possibilities:
*Select the link to navigate to the page of the identified entity
*Select the OntologyBrowser icon and open the entity in OntologyBrowser
*Select the edit icon and open the article's edit page.

== Ask for property values ==
The link 'Search for property values that match your search' searches for property values that match your search. It displays a table with the columns: Instance | Property | Value. This table is displayed in the green box on top.

Example: A user tries to find a person's email adress, but does know only the first part of it. He would get a table with the instance name the email attribute and the value of course.

=== Simple Ask Queries ===
In the third part the system tries to generate some simple ask questions depending on the type of entities found.

*If a category and a property are found, the user may ask for all instances which have an annotation for that property. E.g. if the user enters the search term '''"Chemical Elements" "atomic weight"''' the system automatically generates an ask query that would give you all chemical elements and their atomic weights
*If an instance and a property are found, the user may ask for value of the property of this instance (if available)

Clicking on Show leads you to a page where this ask query is executed and can be refined.

== Triple search ==
Tries to find a triple S P O, if either S P or P O are known. That means if the system finds at least one instance and one property, it can search for a potentially existing value. On the other hand, the system can search for subjects using one property and one value.

Examples:
System contains the following triple: John Lennon has profession musician.

*If CS found 'John Lennon' (instance) and 'has profession' (property), it will show up the triple.
*If CS found 'has profession' (property) and the user entered the search term musician too, it will find the triple too. Search terms don't have to yield a page to be regarded as possible values. That means musician does not have to exist as page to be used during the triple search.

[[Image:Combinedsearch2.gif|thumb|500px|center|The result set for "John Lennon".]]

[[discourseState:=Search:view| ]]
[[Category:Helppage]]

Ajutor:What does the consistency checker do?

2007-11-14T23:25:48Z

127.0.0.1: What does the consistency checker do?

;Question
:[[Question:=What does the consistency bot do]]?

;Answer
:[[Description:=The consistency bot checks for several inconsistencies in the knowledgebase.]]
[[DiscourseState:=Gardening:view| ]]

The Consistency bot checks the schema consistency and the annotation consistency depending on the schema. It has no parameters. Only gardeners should be able to access it, because it causes heavy database load.

== Schema annotations ==
We have the following schema level annotations right now:

*<nowiki>[[Has domain hint::<some category>]]</nowiki>
*<nowiki>[[Has range hint::<some category>]]</nowiki>
*<nowiki>[[Has type::<some type>]]</nowiki>
*<nowiki>[[Is subattribute of::<some relation>]]</nowiki>
*<nowiki>[[Has min cardinality:=<a value >= 0>]]</nowiki>
*<nowiki>[[Has max cardinality:=<a value > 0 or *>]]</nowiki>
*<nowiki>[[Is subrelation of::<some relation>]]</nowiki>
*<nowiki>[[Is subattribute of::<some relation>]]</nowiki>
*<nowiki>[[Is inverse of::<some relation>]]</nowiki>
*<nowiki>[[Is equal to::<some article>]]</nowiki>
*<nowiki>[[Category:Symmetrical relations]]</nowiki>
*<nowiki>[[Category:Transitive relations]]</nowiki>

All this relations or categories have to be created first!

== Schema level consistency ==

The bot identifies the following problems:

=== Cycles in inheritance graphs ===
There '''must not''' be any cycles in one of the inheritance graphs. This may cause endless loops during reasoning and in the OntologyBrowser. This is the first consistency check which is done. If it finds any cycles the whole process stops, because it can not be assured that the further consistency checking algorithms terminate. Cycles may appear in the category, the attribute or the relation inheritance graph. The categories, attributes or relations which cause the cycle will be displayed in the log. The user has to decide where to interrupt the cycle. This consistency problem should have high priority.

Examples:

*The following pages causes a cycle over categories: <nowiki>Page C contains [[category:B]], page B contains [[category:A]] and page A contains [[category:C]] </nowiki>

*A cycle of attributes: <nowiki>Page C contains [[Is subattribute of:B]], page B contains [[Is subattribute of:A]] and page A contains [[Is subattribute of:C]] </nowiki>

=== Property co-variance ===
Property inheritance must be co-variant. That means the following conditions must hold:

*domain and range categories of a subproperty must be equal to those of the super property or they must be subcategories of those.
*types of attributes must be equal.
*the cardinality of a subproperty must be a subset of the cardinality of the super property. The min cardinality must a integer value >= 0. The max cardinality must be an integer value > 0 or *.
*if the super relation is symmetrical the sub relation must also be symmetrical. The same holds for transitivity.

Properties do not inherit schema properties from their parent. It must be explicitly defined for each property. Otherwise you'll get a warning. Note that if the cardinality is not explictly defined, a default value (0..n) will be assumed.

=== Inconsistent inverse relations ===
Checks if inverse relations have switched domain/range.

=== Inconsistent equalitites ===
Checks if equal articles have same namespace.

== Annotation level consistency ==

=== Wrong domain/range instances for properties ===
Detects schema inconsistent annotations: Attributes or relations which are used on pages which are not member of at least one domain category. Relations which refer to pages which are not member of at least one category of the range categories.

=== Wrong number of appearances of properties ===
Detects schema inconsistent annotations: Attributes or relations which are used too less or too much on a page in contradiction to their cardinality.

Ajutor:What does the undefined entities bot do?

2007-11-14T23:25:48Z

127.0.0.1: What does the undefined entities bot do?

;Question:
:[[Question:=What does the undefined entities bot do]]?

;Answer:
:[[Description:=It finds entities which are used but which are not specified.]]
[[DiscourseState:=Gardening:view| ]]

This bot is used to find undefined entities, i.e. entities which were used one or more times, but do not exist as pages. Formerly, the functionality was part of the ConsistencyBot. It has been transfered to a bot of its own. The bot is very simple to use: It has no parameters. You can use the botlog to increase the quality of the wiki's knowledgebase by solving the problems that were found.

The bot recognizes the following problems:

=== Undefined categories ===
All categories which are implicitly defined by a category link but which do not exist as an article.

=== Undefined properties ===
All properties which are implicitly defined by an annotation but which do not exist as an article.

=== Undefined relation targets ===
Instances which are target of a relation annotation but which do not exist as an article.

=== Instances without category ===
Instances which are not member of any category.

Ajutor:What is a syntax highlighting editor?

2007-11-14T23:25:48Z

127.0.0.1: What is a syntax highlighting editor?

;Question
:[[Question:=What is a syntax highlighting editor]]?

;Answer
:[[Description:=The SHE marks special entries in the wikitext and enables easy orientation in the text of a page you edit.]]
[[DiscourseState:=Main:edit| ]]
[[DiscourseState:=Property:edit| ]]
[[DiscourseState:=Category:edit| ]]

==Prerequisites==
In order ro use the syntax highlighted editor (SHE), you have to use the "'''OntoSkin'''" skin. Go to "''my preferences''" -> "''Skin''" and pick "OntoSkin".

==(De)Activating the syntax highlighted editor==
In order to activate the SHE, simply check the "Switch between syntax highlighted and standard editor" checkbox. The SHE then will be loaded automatically. If you want to switch back to the standard editor, simply click the checkbox again.

==Highlighting colors==
{| class="prettytable" border="1" style="border-collapse:collapse;" cellpadding="5"
! Type || Highlighting style || Example
|-
| Relation || color: green, font-weight: bold || <nowiki>[[TestRelation::Abcd]]</nowiki>
|-
| Attribute || color: orange, font-weight: bold || <nowiki>[[TestAttribute::1234]]</nowiki>
|-
| Category || color: blue, font-weight: bold ||<nowiki>[[Category:Test]]</nowiki>
|-
| Template || color: red || <nowiki>{{Testtemplate}}</nowiki>
|-
| Link || color: blue, text-decoration: underline || <nowiki>[http://www.ontoprise.de]</nowiki>
|}

==Functions of the syntax highlighted editor==
At the top of the SHE, there is a toolbar with various functions. The first ten buttons are the same as in the standard editor and are used for insertion of wiki syntax (for example bold, italic, link, image). Furthermore, there ar some additional buttons that provide extra functionality:

[[Image:SHEundo.gif]] - Undo last step (maximum: 10 steps)

[[Image:SHEredo.gif]] - Redo last step (maximum: 10 steps)

[[Image:SHEtoggle.gif]] - Toggle syntax highlighting on or off

[[Image:SHEresync.gif]] - Resync highlighting manually if it is out of sync

[[Image:SHEsmooth.gif]] - Smooth display mode

[[Image:SHEhelp.gif]] - Help

Ajutor:What are sub- and super properties?

2007-11-14T23:25:48Z

127.0.0.1: What are sub- and super properties?

;Question
:[[question:=What are sub- and super properties]]?
[[discourseState:=Property:edit| ]]

;Answer
:[[description:=e.g. has relative is a superproperty of has parent, while has father is a subproperty of has parent.]]

Properties can be sub-classed. Consider the following relations with their domains and ranges:
* <Person> is father of <Person>
* <Person> is parent of <Person>

It is very reasonable that ''is father of'' is a sub-property of ''is parent of''. So, while annotating a text, you can use the ''is father of'' property. In a query, or in the reasoning system, another user could ask for parents and would automatically get all fathers.

Steps for setting up an example:
<ul>
<li>Create the article ''Property:is parent of''. Write some descriptive text and save it.</li>
<li>Create the article ''Property:is father of''. Write some descriptive text and add the annotation:
<pre>
<nowiki>
[[subproperty of::Property:is parent of]]
</nowiki>
</pre>
</li>
<li>Save the article.</li>
<li> Reopen the article ''Property:is parent of''. Now it should show its sub-relation ''is father of''.
</ul>

Sub-properties are also considered in the [[Special:Ontology Browser]].

Ajutor:What can I do in the semantic toolbar?

2007-11-14T23:25:48Z

127.0.0.1: What can I do in the semantic toolbar?

;Question:
:[[question:=What can I do with the semantic toolbar]]?
[[discourseState:=Main:edit| ]]
;Answer:
:[[description:=The STB consists of several containers that guide you in the process of using the Semantic Wiki.]]

The semantic toolbar contains tools for the semantic annotation of wiki text and the definition of the wiki's ontology in form of properties and categories. It shows the current annotations in the wiki text and is updated regularly when the text changes.

Annotations may be contributed to an article by templates. These annotations are ignored by the semantic toolbar. However, the content of templates can be edited with the semantic toolbar.

Figure 1 shows the content of the semantic toolbar for "hydrogen".

[[Image:SEMWIKI6_SemanticToolbar.png|thumb|200px|center|The semantic toolbar for hydrogen.]]

With the semantic toolbar you can annotate, modify annotations, create new categories and properties and establish part-of relation. Sub- and super categories and properties can be created as well. All references to other articles are displayed as links that you can follow. We will give a short overview of this functionality. Further information can be found in the corresponding requirements.

===Annotation===
Typically annotating starts with the selection of the text in the editor. Depending on the type of annotation, the link ''Annotate'' has to be clicked in the sections ''Categories'', ''Attributes'' or ''Relations''. In the form that opens, the selected text will appear as value or as category, respectively. If a property is annotated, its name has to be specified. Auto-completion supports you in your tasks. At last an alternative representation for the value can be entered in the field ''Show''. Figure 2 shows an example for an annotated property.

[[Image:SEMWIKI6_Annotate.png|thumb|center|202px|Annotation of a property in the semantic toolbar.]]

===Edit Annotations===

The annotations of the current wiki text are listed in the corresponding sections of the semantic toolbar. Their name and value is displayed along with an edit icon. Clicking it opens a form that contains the settings of the annotation. The annotation is selected in the wiki text. (Unfortunately, Firefox can not scroll to the corresponding location.) The annotation's settings can be changed and confirmed. The wiki text will be updated appropriately. Figure 3 shows an example.

[[Image:SEMWIKI6_EditAttr.png|thumb|center|201px|The edit form of a property]]

===Edit n-ary Annotations===

N-ary properties are annotated in the same way as normal ones. When the properties name has been entered, the system retrieves its arity and provides the corresponding input fields. The following figure shows an example for the density of water.

[[Image:SEMWIKI6_EditNary.png|thumb|center|201px|The densitiy of a substance is an n-ary property.]]

===Creation===

The ontology can be extended i.e. new categories and properties can be created. When the link ''Create'' is selected, an input form asks for further specification. For instance, a new property requires a name, a domain and a type.

The system takes care, that an existing entity is not created anew. After the name has been entered and the input field has been left with Enter or Tab, the system checks, if the name is valid. The background of the input field is marked orange if the entity already exists and green if it is safe to create it. Figures 4 to 6 show some states of the creation process.

[[Image:SEMWIKI6_CreateAttr1.png|thumb|center|201px|The empty input form for the creation of a new property.]]
[[Image:SEMWIKI6_CreateAttr2.png|thumb|center|201px|A valid name for a property has been entered.]]
[[Image:SEMWIKI6_CreateAttr3.png|thumb|center|201px|The property with the given name already exists.]]

The link ''Create'' will only appear, if the specification is correct. Clicking it will create a new article with the given schema information. It will be opened in a new tab of the browser, however, pop-up blockers might prevent this. Figure 7 shows the content of the created article.

[[Image:SEMWIKI6_CreateAttr4.png|thumb|482px|center|The new article in edit mode.]]

===Part-of relation===

The GUI supports several meanings of a part-of relation. One can state, that the subject of the current article is a part of another. The section ''Properties'' has the link ''Has Part'' that leads to the form shown in Figure 8.

[[Image:SEMWIKI6_PartOf.png|thumb|206px|center|A basic structural unit of water is hydrogen.]]

===Hierarchies===
Categories and properties can build hierarchies. When the definition of such an entity is edited, the corresponding section in the semantic toolbar contains the link ''Sub/Super''. The form that follows asks for the name of the sub/super entity. The content of the input field is validated when ''Enter'' is pressed. If the entity exists, the field is dyed green, otherwise orange. Anyway, if the input field is not empty, two links provide the possibility to make a sub or super entity for the current article. If a new article has to be created, it will be opened in a new tab (beware of pop-up blockers). New entities inherit the schema properties of their master entity. Figure 9 and 10 show some examples.

[[Image:SEMWIKI6_SubSuper1.png|thumb|196px|center|The input form for a sub/super property.]]
[[Image:SEMWIKI6_SubSuper2.png|thumb|196px|center|A non existing property]]
[[Image:SEMWIKI6_SubSuper3.png|thumb|196px|center|An existing property.]]

===Property properties in the semantic toolbar===

The semantic toolbar contains additional tools when the definition of a property is edited. These features are hosted in the toolbox labeled ''Property Properties''.

[[Image:REQ_SEMWIKI_18_PropertyProperties.png|thumb|823px|center|The wiki text for the definition
of a property and the corresponding Property Properties in the semantic toolbar.]]

The properties of a property are:
* '''Domain''' - Articles of this category can have values for this property.
: Wiki text: <code><nowiki>[[Has domain hint::Category:<domain>]]</nowiki></code>
* '''Range''' - Articles of this category are object of the property. This field is only enabled, if the property's type is ''Page''.
: Wiki text: <code><nowiki>[[Has range hint::Category:<range>]]</nowiki></code>
* '''Inverse of''' - The name of the property that is the inverse of the current property.
: Wiki text: <code><nowiki>[[Is inverse of::Property:<inverse property>]]</nowiki></code>
* '''Type''' - One of the predefined types. Two of them require additional explanations. The type ''Page'' indicates that the property's values are wiki articles. Their ''Range'' defines the category of articles. The type ''N-ary'' states that the property can have several ranges and types.
: Wiki text: <code><nowiki>[[has type::Type:<data type>]]</nowiki></code>
* '''Minimal cardinality''' - The minimal number of values of the property. (This field is not enabled when the properties type is ''N-ary''.)
: Wiki text:<code><nowiki>[[Has min cardinality:=<number>]]</nowiki></code>
* '''Maximum cardinality''' - The maximal number of values of the property. (This field is not enabled when the properties type is ''N-ary''.)
: Wiki text: <code><nowiki>[[Has max cardinality:=<number>]]</nowiki></code>
* '''Transitivity''' - Defines that the property is transitive. This field is only enabled, if the property's type is ''Page''.
: Wiki text: <code><nowiki>[[Category:Transitive relations]]</nowiki></code>
* '''Symmetry'''- Defines that the property is symmetric. This field is only enabled, if the property's type is ''Page''.
: Wiki text: <code><nowiki>[[Category:Symmetrical relations]]</nowiki></code>

When the article for a property definition is opened for editing, the ''Property Properties'' are initialized according to the wiki text. When schema relevant properties are changed in the wiki text, they are updated in the semantic toolbar after a short delay.

Some fields are disabled or enabled when the property's type is changed. Disabled field are not hidden and do not lose their values lest you might get confused by a changing GUI and do not have to reenter values if you accidently selected the wrong type.

The fields ''Domain'', ''Range'' and ''Inverse of'' are supported by auto completion. When they lose the input focus, the system checks if the categories or properties really exist. Valid entries are marked in green, invalid ones in orange. However, the system does not enforce valid values as you might create the missing category or property later.

The fields for the cardinality are syntax checked. They must contain valid numbers. Wrong values are marked in red and can not be applied.

[[Image:REQ_SEMWIKI_18_InvalidValues.png|thumb|200px|center|Invalid values are highlighted in the Property Properties.
Wrong values are marked red and can not be applied.]]

The lower left corner of the ''Property Properties'' shows usability hints:
* Nothing changed. - As long as no property has been changed, the properties can not be applied.
* Error messages for invalid cardinalities.
* Apply - Changed values can be applied i.e. the wiki text is updated accordingly.

New values are only applied when the ''Apply'' link is clicked. Clicking the link ''Cancel'' restores the current values of the wiki text in the ''Property Properties''

If property fields are empty their corresponding wiki text will be deleted. If a property is newly introduced, its wiki text will be appended at the very end of the article. If the same kind of property definition appears several times in the wiki text, only its first value will be shown in the semantic toolbar.

'''Editing n-ary properties'''

N-ary properties can have several values at a time. For instance, the density of a substance is defined for a certain temperature and pressure.

[[Image:REQ_SEMWIKI_18_NaryProperties.png|thumb|200px|center|The definition of the n-ary property "density" of a chemical substance.]]

To edit an n-ary property, its type has to be switched to ''N-ary''. Most of the input fields will be disabled. Two additional links appear at the bottom of the Property Properties toolbox: ''Add type'' and ''Add range''.

''Add type'' adds a type selector to the toolbox. All built-in types can be selected. User-defined types that are defined in a wiki article are not yet supported in the selector. However, they can be entered in the wiki text with support of auto-completion. Thus specified they will be displayed in the type selector as well.

''Add range'' adds a range input field to the toolbox. Entering a category is supported by auto-completion.

To the right of each input field there is a red cross that can be clicked to delete the property. When the last range or type has been removed, the type selector switches to ''Page''.

The generated wiki text that defines an n-ary property has the following format:
<nowiki>
[[Has type:=<List of types separated by semi-colon>]]
e.g.
[[Has type:=Type:Temperature;Type:Pressure;Type:Density]]
</nowiki>

The type for references to wiki articles is called <code>Type:Page</code>.

===Automatic update===
When you change the wiki text, the content of the semantic toolbar (i.e. lists of properties and their values) is updated automatically with some delay.

'''ATTENTION!'''

When opening brackets are inserted in the wiki text (<nowiki>"[["</nowiki>), all annotations that follow will disappear from the semantic toolbar until the appropriate closing braces are entered. This is because annotations can contain anything, even other annotations. As long as an annotation is not "closed", everything that follows belongs to it. Articles can not be saved until the closing brackets have been entered. The system shows a warning above the ''Save page'' button.

== Settings being saved ==
The position of "help container" (collapsed or expanded) as well as the tab position of the semantic toolbar are saved using ordinary browser cookies. That is, whenever a user collapses the help container or switches the tab position from "tools" to "links to other pages" these settings are saved when the semantic toolbar is displayed the next time. There is no need for a user to explicitly click on a "save settings" button since the cookies are refreshed automatically whenever switching tabs or collapsing/expanding the help container. All other containers are not affected from this feature and are display expanded when editing another wiki page.

Ajutor:What can I do with the ontology browser?

2007-11-14T23:25:48Z

127.0.0.1: What can I do with the ontology browser?

;Question
:[[Question:=What can I do with the ontology browser]]?

;Answer
:[[Description:=The ontology browser allows easy and intuitive lookup of information from the knowledgebase.]]

[[DiscourseState:=OntologyBrowser:view| ]]

== Overview ==

The OntologyBrowser consists of 3 basic views:

#CategoryView: Shows category hierarchy, called the taxonomy of the wiki (it can be changed to show the attribute and relation hierarchy with the buttons above it).
#InstanceView: Shows either instances that belong to a certain category when triggered from category view, or instances that are annotated with a certain category when triggered from property view.
#PropertyView: Shows either annotated properties when triggered from instance view, or schema properties when triggered from category view.

Below each of the views there is a filter input box. It filters '''currently''' available entities in the view above, i.e. those entities which are in memory at this time. It is filtered dynamically if the filter text changes. The filtering itsself is case-insensitive substring matching. All entities are in alphabetical order with one excpetion: The instance view shows the direct instances of a category first.

[[Image:OB_overview.png|thumb|400px|The ontology browser special page.]]

== Category Tree ==
At the beginning the Category tree shows the root categories. You may expand the category tree by clicking the little crosses in front of a category name or by selecting the category itsself. This crosses also appear when there is no subcategory at all. In this case it will simply disappear when you try to expand it, otherwise the subcategories will appear.

==== selecting a category ====
You may select a category. Selected categories are highlighted with yellow background. In this case the instanceview shows all instances of this category (first the '''direct''' ones and then the inherited ones in italic). Additionally, it shows the actual category for the inherited instances in angle brackets. The property view shows the schema attributes and relations which have the category as their domain (also only the direct ones, not the inherited properties). Additionally, there is some more information about properties shown:

For attributes:

*type (e.g. string, integer, boolean). Relation which defines this: has type
*cardinality (e.g. 1..2, 0..* (last one is default)). Attribute which defines this: has min cardinality, has max cardinality

For relations:

*range category. Relation which defines this: has range hint
*cardinality (e.g. 1..2, 0..* (last one is default)). Attribute which defines this: has min cardinality, has max cardinality
*symetrical / transitive which determine if a relations is symetrical and/or transitive. Categories: transitive relations, symetrical relations.

==== selecting an instance ====
Select an instance and the property view will switch to the annotations of this instance. It's a two-column table showing attribute/relation name and its value.

== Property Tree==
You can select the Property tree which shows the attribute hierachy. It begins with the root level. You can expand it, just like the categories. If you select an attribute here, all instances annotating this attribute will be shown. The property view content does not change.

== Partitions ==
If there are more than 20 entities on a tree level or in the instance list (or whatever treshhold is configured), small arrows will appear on top which allows navigating through the 'partitions'. A number tells on which partition you currently are. Only the current partition will stay in memory at a time. This makes the OntologyBrower capable of accessing masses of schema data, because only parts of it are loaded in memory. Mostly, it will occure on category/attribute/relation root level and in the instance list. On deeper levels of one of the trees it will happen more seldom, but in principle this mechanism works on every tree level. Only the PropertyView does not support partitions currently.

== FilterBrowsing ==
On top of the views there's a input box with a button 'FilterBrowsing' next to it. This is a basic feature of the OntologyBrowser. You may enter a term and press the button (or return). Alternativly, you can press Ctrl+Alt+Space to use auto-completion. The following things will happen.

*Depending on which tree view is selected the filtering is applied on the currently visible tree. In case of the category view, categories matching the filter string as a substring (case-insensitive) are identified and shown in the category hierarchy, i.e. their super categories are shown too. If a category inherits from several categories it will appear multiple times in the view. Same behaviour with the attribute tree and the relation tree.
*All instances matching the filter string as a substring (case-insensitive) are shown.
*All properties matching the filter string as a substring (case-insensitive) are shown.

''Note'': There are no partitions in the FilterBrowser mode.

== Switching selection flow ==
You can turn the big gray arrows by clicking on them. That means the selection triggers an operation in the opposite direction.

'''Example''':
You switch the left arrow. If you select an instance afterwards you will get all categories of this instance at their position in the category hierarchy. Accordingly, a selection of an annotation or schema property will open the domain category.

[[Image:OB_screenshot2.png|thumb|300px|left|Ontology browser with flipped directions.]]

This is especially useful after FilterBrowsing, because in this case the views are not related to each other. All type of entities were searched independently only by substring matching.

The right arrow can also be turned. A selection in the annotation/schema property view will show all instances defining annotations of this property.

== Inheritance ==
Inherited entities are displayed in italic font style. Inheritance comes up when you select an item in the tree view.
*select a category: All instances (also those of subcategories) are displayed. All properties (also those of supercategories) are displayed.
*select an attribute/relation. All instances using this or one of its subproperties are displayed.

== Navigation ==
You can navigate to an entity's page by clicking the magnifier next to the entity's name. This works for all entities, even for the range categories in the PropertyView.

== Misc ==
The 'reset' button resets the tree view (i.e. show the root entities) depending on which one is currently visible.

Ajutor:What can i do with the query interface?

2007-11-14T23:25:48Z

127.0.0.1: What can i do with the query interface?

;Question
:[[Question:=What can i do with the query interface]]?

;Answer
:[[description:=Use the QI to search the wiki, generate useful lists and tables containing facts from the knowledgebase.]]
[[DiscourseState:=QueryInterface:view| ]]

==Overview of the query interface==

The query interface is a special page and can therefore be accessed on the page “Special:Specialpages”. When accessing this page, you can see the Query Interface (QI) in its initial state.

[[Image:QI_InitialView.jpg|thumb|300px|Initial view of the query interface]]

On the very bottom, there is the menu bar with the three main functions:
*Preview query: A full preview of the current query, also considering the layout settings on bottom
*Copy to clipboard: This button will copy the ask query to the clipboard. This will always work for Microsoft Internet Explorer Browsers. If you use Firefox, there might be a security question coming up. Depending on your local security settings, the “copy to clipboard” functionality will not be available at all.
*Reset Query: This button will reset the current query and all its sub- and superqueries

On top of the query interface to the left, you can see the query tree with a breadcrumbs navigation and the tree graph. The breadcrumbs navigation shows where you are in the structure of your current query. The tree shows the structure of the query and allows you to navigate through it by clicking the single items.

[[Image:QI_QueryTree.jpg|frame|none|Query Tree of the main part of the query]]

[[Image:QI_QueryTreeSub.jpg|frame|none|Query tree of a subquery]]

In the middle of the QI, there is the main part of the interface where you can add further restrictions to your query. Right niext to this area, the context sensitive help is shown. For further information about context sensitive help, see [[Help:What_is_context_sensitive_help?]]
Below the main area, you can see the table column preview. Most query results in SMW are shown in tables. This little window will give you an instant preview of which columns will appear in the result table of the current query.
At the bottom, there is the query layout manager (QLM). The QLM supports you by defining the output format of your query, since there are many different possibilities.

===Creating a sample query with the QI===
This section of the user documentation will give a step by step example for creating a query with the QI. The example query used in this case is as follows:

:''“Give me the number of inhabitants for every European Union capital”''

First of all, we have to define what we look for and according to this choose a category. Of course, this choice always depends on the content and structure of the wiki. In this example, we will say that capitals are in the category “city”. The first step therefore is that we ask for this category. In every input field of the QI you can use auto completion in order to find appropriate inputs.

[[Image:QI_Step1.jpg|frame|none|Step 1: Add category]]

After clicking “OK”, the category will appear in the query tree. For every capital, we want to have the number of inhabitants, which is a property. The next step therefore is to add this property to the query.

[[Image:QI_Step2.jpg|frame|none|Step 2: Add property]]

As we would like to have the number of inhabitants printed out in the result table, we have to check “Show in result table”. Please be reminded that only properties in the main part of the query can be printed. Properties of subqueries can not be printed, therefore this checkbox will not appear. As value we enter “*” for all values, but this field can as well stay empty which would have the same effect.

As stated in our query, we want only those cities that are capitals of countries which belong to the European Union. The word “which” is always a hint on a subquery. Therefore we have to create a subquery here.

[[Image:QI_Step3.jpg|frame|none|Step 3: Add property with subquery]]

To add a subquery, simple check the “Insert subquery” box next to the input field. Subqueries are only possible with properties that refer to another wiki page. If a property has for example Integer or Date as a type, subqueries are not possible.

[[Image:QI_Step4.jpg|frame|none|Step 4: Query tree of the main query]]

Now, the subquery can be edited. This happens by clicking “Subquery 1” in the tree view. You will then see a new empty tree which represents the contents of the subquery.
This subquery will search for all Countries that are part of the European Union. Therefore, we will have to add the category “Country” and the property “is part of” with the value “European Union”.

[[Image:QI_Step5.jpg|frame|none|Step 5: Query tree of a subquery]]

By clicking on “Main” on top of the treeview, you can navigate back to the main part of the query. Before finishing the query, some layout parameters will be set. As a format, we choose table. The main label is the heading of the first table column. We will call this one city. Finally, we want our results sorted by the number of inhabitants in an descending order.

[[Image:QI_Step6.jpg|frame|none|Step 6: Query Interface with the final query]]

By clicking on “Preview results”, the results of the current query can be checked. In this case, there are only two cities in the database which are Berlin and Rome. The query is now finished and can be copied to the clipboard for further use in other articles.

[[Image:QI_Step7.jpg|frame|none|Step 7: Preview of query results]]

===The query layout manager===
This section will give a short overview of the query layout manager and the meaning of the single options.

{| class="prettytable" border="1" style="border-collapse:collapse;" cellpadding="5"
! Layout option || Allowed values || What it does
|-
| Format || Table, bullet list, numbered list, list, count, timeline || Defines the output format of the query. Count means that only the number of results is displayed
|-
| Sort by || All columns that are shown in the result || Defines which column of the result table should be used to sort the results
|-
| Order || Ascending, descending ||Ascending or descending order
|-
| Link || Subject, all, none || Defines which parts of the result should be linked. Subject means only the first column is linked to the corresponding article.
|-
| Limit || Number || The maximum number of results shown. If there are more results, a link for a full result list will be provided automatically
|-
| Headers || Show, don’t show || Defines if the headers of the table are shown
|-
| Intro || Text || Text that appears before the results are displayed
|-
| Mainlabel || Text || Label of the first column of the result table
|-
| Default || Text || Text that will appear if there are no results
|}

===Advanced usage: conjunction and disjunction===
Whenever you add a category, instance or property they are connected by conjunction. This means that all entered restrictions have to be true in order to appear in the result table. However, sometimes it is necessary to use a disjunction. This can be done by using the green plus sign next to an input field.

[[Image:QI_Dis.jpg|frame|none|Using disjunction on a category]]

The above image shows an example of disjunction. This query would return all articles that are either in the category book OR in the category movie. If you add one category Movie and one category book, conjunction is applied and the query would return only articles that are in both categories (for example “1984” by George Orwell, since this is a book as well as a movie).

Ajutor:How can I define a set of allowed values?

2007-11-14T23:25:47Z

127.0.0.1: How can I define a set of allowed values?

;Question
:[[question:=How can I define a set of allowed values]]?

;Answer
:[[description:=Add as many "allowed value" annotations to the property as needed.]]
[[discourseState:=Property:edit| ]]

'''Goal'''

You want to define and use a property that can assume only certain, predefined values (also known as enumeration). For instance, the chemical state of matter of a substance can be ''gaseous'', ''aqueous'', ''liquid'' and ''solid''. These constants will be the possible values of an enumeration.

'''Workflow'''

''Defining the attribute''

At first, you have to define the attribute. You can do this in several ways and chooses to use the semantic toolbar. In the ''Properties'' section (only visible when editing an article) you click the ''Create'' link. Enter the name of the attribute (e.g. state of matter), the domain (e.g. Substance) and add a type, which must be ''Enumeration''. After clicking ''Create'' the system asks, if the new property shall be edited. Pressing ''OK'' leads to the edit view of the attribute.

Now, the allowed values for the attribute have to be defined. The new article contains the following line
<nowiki>
[[Allows value:=replace this by allowed value]]
</nowiki>

The possible values of an enumeration are defined with the property <code>Allows value</code>. You can change the value of the template above in the ''Properties'' section of the semantic toolbar. Click the edit icon to the right of the property, changes the value (e.g. to liquid) and click ''Change''. Each further possible value requires its own annotation with the property <code>Allows value</code>. Using the semantic toolbar or entering the annotations manually, the final definition for ''state of matter'' should look like this.

<nowiki>
[[Allows value:=liquid]]
[[Allows value:=gaseous]]
[[Allows value:=aqueous]]
[[Allows value:=solid]]
</nowiki>

Finally, the property's definition has to be saved.

''Using the property''

The property is used like any other normal property. Of course, only the defined values are allowed. For instance, the article about liquid water would be annotated like this:
<nowiki>
[[state of matter:=liquid]]
</nowiki>
The normal annotation features of the semantic toolbar can be used to create this annotation.

The fact box of the saved article shows, if the correct values have been assigned. If not, all possibilities are listed.

Ajutor:How can I define sub- and super properties?

2007-11-14T23:25:47Z

127.0.0.1: How can I define sub- and super properties?

;Question:
:[[question:=How can I define sub- and super properties]]?
;Answer:
:[[description:=Use "Sub/Super" in the "Properties" tool box.]]

[[discourseState:=Property:edit| ]]

'''Prerequisites'''

You are editing the definition of a property i.e. an article in the namespaces ''Property''.

'''Goal'''

You want this property to be a sub- or super-property of another property.

'''Workflow: Create a super-property for the current property'''

;Example:
: The property ''number of children'' exists. The new property ''number of descendants'' shall be created as super property .

Press the "Sub/Super" link in the semantic toolbar.

[[Image:SEMWIKI4_SubSuper.png|center|thumb|200px|The menu bar of the properties section.]]

Enter the name of the super-property i.e. ''number of descendants'' and press return or tab. The system checks, if the new property already exists. If it does, the input field turns orange and green otherwise. In the first case the existing property will be annotated, in the second it will be created before that.

Two links appear below the input field. Click ''Create "number of descendants" and make "Number of children" sub-property of "number of descendants"''. (If ''number of descendants'' would have existed, the link would have been ''Make "Number of children" sub-property of "number of descendants"''.)
[[Image:SEMWIKI4_EnterAttr.png|center|thumb|200px|Creation of a new property as sub- or super-property of another one.]]

The current article (''number of children'') is annotated with the following:

<nowiki>
[[subproperty of::Property:number of descendants]]
</nowiki>

It has become sub-property of ''Property:number of descendants''.

If ''number of descendants'' did not exist, a new article is created and opened in a new tab of the browser. (Attention: Popup blockers might prevent this!) If it is newly created, it has the same schema properties as the property from where it was created. I.e. domain, type, range and cardinality are copied.

'''Workflow: Create a sub-property for the current property '''

Press the "Sub/Super" link in the semantic toolbar. Enter the name of the sub-property e.g. "SubProperty" and press ''Create "SubProperty" and make "Number of children" super-property of "SubProperty"''. The current article is not modified.
A new tab is opened with the new property. The current property has become super-property of the new ''SubProperty''.

If ''SubProperty'' did not exist, a new article is created with the same schema properties as the property from where it was created. I.e. domain, type, range and cardinality are copied. In addition it will be annotated as sub-property of its origin.

Ajutor:How can I express that something is a part of something else?

2007-11-14T23:25:47Z

127.0.0.1: How can I express that something is a part of something else?

;Question:
:[[question:=How can I express that something is a part of something else]]?
;Answer:
:[[description:=Click "Has part" in the "Properties" tool box.]]

[[discourseState:=Main:edit| ]]

The wiki provides two types of part-of relations. These are ''has part'' and ''has basic structural unit''.

'''Prerequisites'''

You are editing and arbitrary article.

'''Goal'''

You want to express that the instance or category you are describing in the article is a part of something else.

'''Workflow'''

Mark the object that is part of the current object (article). For instance, if you are editing the article about a ''car'', mark the word ''engine''.

In the semantic toolbar click "Has part" in the section "Properties". The form states that a ''car'' can contain an ''engine''.

[[Image:SEMWIKI24_HasPart.png|center|thumb|200px|An engine is part of a car.]]

Select "has part" as the type of part. Optionally you can enter a different representation for ''engine'' in the rendered text. Click the link "Add" and the selected car in the wiki text is replaced by the annotation <code><nowiki>[[has part::engine]]</nowiki></code>. The new property appears in the list of properties in the semantic toolbar as well.

Ajutor:How can i find close matches?

2007-11-14T23:25:47Z

127.0.0.1: How can i find close matches?

;Question:
:[[Question:=How can i find close matches]]?

;Answer:
:[[Description:=Use the tilde symbol in front of a property value.]]

;Example query showing a use case for near matches in ASK-queries
A good example for a near match in ask queries is to overcome the language problem introduced by british english vocabulary vs. american english vocubalary such as color vs. colour!
Therefore, the following ASK syntax can be used:
<nowiki><ask>[[hasThing:~color]]</ask></nowiki>
The number of '~' signs in the syntax denotes the number of 'typos' that are allowed and taken into account. Regarding the given example, all attribute values with distance of "1" to colour are considered as correct matching, positive results!
That means, 'colour', 'Color', 'culor' and so on would deliver results.

The near matches are not only limited to mistyped string attributes but also useful regarding float numbers.

;Inofficial support of units
Inofficially and not fully tested is the support for near matches using these units:
:date
:integer

Regarding the 'date' unit, the number of '~' signs denotes the deviation in days That means a query such as
<nowiki><ask>[[Category:Person]] [[*:=*]] [[wasBorn:~~~2007-05-11]]</ask></nowiki>
would result in a list showing all attributes of all persons that were born between 2007-05-08 and 2007-05-14 (3 days deviation due to 3 '~' signs.

Regarding integer units, the number of '~' signs denotes the factor of a fixed tolerance of 5%.
<nowiki><ask>[[hasPopulation:~~100000]]</ask></nowiki>
This query would match all pages that contain the hasPopulation attribute with a value of at least 90000 or at most 110000 (10% deviation due to 2 '~' signs).

;Admins please note (Installation instruction)
A new function calculating the editdistance needs to be added to the existing MySQL server. Therefore, a detailed installation instruction and the necessary file containing the needed method is available in the CVS: extensions/SemanticMediaWiki/libs/INSTALL.TXT

[[discourseState:=QueryInterface:view]]

Ajutor:How can I identify entities that could be unified?

2007-11-14T23:25:47Z

127.0.0.1: How can I identify entities that could be unified?

;Question
:[[Question:=How can I find entities that could be unified]]?

;Answer
:[[Description:=Employ the similarities bot.]]
[[DiscourseState:=Gardening:view| ]]

The similarity bot is used to find redundant entities in the wiki. It's available via the Gardening interface.

[[Image:similarityBot.png]]

== Parameters ==

There are 4 parameters (all are optional):

#Similarity term: Search for entities similar to the given term. If empty, all entities are compared to each other to find possibly redundant ones.
#Lexical similarity: A factor which indicates the degree of lexical similarity. 1 means nearly identical, 3 is roughly similar. Default is 1.
#Limit of results: Maximum number of results. Default is 100.
#Filtering of results: Shows only results which have at least a given rating. 0 means hardly similar, 3 extremly similar. Default is 0.

== Results ==
The log contains all possibly redudant entities found. The list is sorted and begins with the most similar ones (highest rated). The system also explains why it assumes that two entities are redundant. This can be due to the follwing reasons:

*The spelling is very similar. (Plural/Singular, Whitespaces, spelling mistakes, common prefixes or suffixes)
*Category: Two categories have the same super category(ies).
*Attribute: Two attributes have the same domain(s) and/or type(s)
*Relation: Two relations have the same domain(s) and/or range(s)
*Instance: Two instances are member of the same category(ies)

Ajutor:How can I modify the annotation of a property?

2007-11-14T23:25:47Z

127.0.0.1: How can I modify the annotation of a property?

;Question
:[[question:=How can I modify the annotation of a property]]?

;Answer
:[[description:=Click the "pen and paper" icon next to the respective property in the toolbar to edit it.]]
[[discourseState:=Main:edit| ]]

'''Prerequisites'''

You are editing an article with annotated properties.

'''Goal: Modify the annotation for a property'''

You want to rename a property in the wiki text, change its value and its rendered representation. When the same property appears several times in the article, all of its occurrences shall be renamed.

'''Workflow'''

The ''Properties'' section contains a list of all properties of the current article.
[[Image:SEMWIKI_16_AttrList.png|thumb|200px|center|List of properties in an article.]]

[[Image:SEMWIKI_16_EditAttrWT1.png|thumb|256px|center|Wiki text that corresponds to the list of properties.]]

Assume, you find a typo in all occurrences of the property and you want to replace "Peter" by "John". Click the edit icon to the right of "Peter". An edit form that contains the property's name, its value and the representation appears. In the wiki text, the corresponding section will be selected.

[[Image:SEMWIKI_16_EditAttr.png|thumb|200px|center|Edit form of a property.]]

Now correct the name and check ''Rename all in this article''. Thus all occurrences of "has mumber" in the article will be replaced by the modified name. The definition of the property will not be touched. The check mark appears only, if there are several occurrences of the property.

Then you replace the value "Peter" by "John". If the value would be different from its representation in the rendered article, you can provide the alternative text in the field ''Show''.

Finally click the link ''Change''. The list of properties and the wiki text are updated.

[[Image:SEMWIKI_16_EditAttrWT2.png|thumb|256px|center|The updated wiki text.]]

'''Goal: Remove the annotation of a property'''

You want to remove an annotation from the wiki text. A reasonable text should remain.

'''Workflow'''

In the list of properties, click the edit icon of the property you want to remove. At the bottom of the edit form click the link ''Delete''. The complete annotation in the wiki text (e.g. <code><nowiki>[[has member:=William the third|Bill]]</nowiki></code>) will be replaced by the property's representation (field ''Show'') e.g. <code>Bill</code>. If the alternative representation does not exist, the annotation will be replaced by its value e.g. <code><nowiki>[[has member:=William the third]]</nowiki></code> will become <code>William the third</code>. If even the value is missing, nothing will remain.

Ajutor:How can i relate my type to the correct SI unit?

2007-11-14T23:25:47Z

127.0.0.1: How can i relate my type to the correct SI unit?

;Question
:[[Question:=How can i relate my type to the correct SI unit?]]

;Answer
:[[Description:=Use the "corresponds to SI" property.]]
[[DiscourseState:=Type:edit| ]]

Units of measurement can be specified for data types. For instance, the <code>Type:Velocity</code> can be could have the unit km/h. SMW provides a special attribute for this task. The article for <code>Type:Velocity</code> should contain the following line:
<nowiki>
[[corresponds to:=1 km/h]]
</nowiki>
For now, "km/h" is only an arbitrary string without a meaning. A reasoning system like Aura has to understand these units, so the unit has to be specified as SI unit:

<nowiki>
[[corresponds to SI := 0.27777778 m/s]]
</nowiki>

Such a definition must appear at most once on a page.

An SI definition consists of a conversion factor (with respect to the primary unit - the one with <code>corresponds to = 1...</code>) and the unit expression.

The unit expression is a division of products of SI base units with an optional exponent. There must be at least the enumerator and an optional denominator. Products are written with * or blank. Exponents are introduced by ^, followed by a positive or negative integer.

The SI base units are:
* <code>m</code> - Meter
* <code>kg</code> - kilograms
* <code>s</code> - Second
* <code>A</code> - Ampere
* <code>K</code> - Kelvin
* <code>mol</code> - Mole
* <code>cd</code> - Candela

Examples:
* <code>m</code> - Meter
* <code>m^2 = m*m = m m</code> - Square meter
* <code>m/s</code> - meters per second
* <code>m/s^2 = m*s^-2 = m s^-2</code> - Acceleration
* <code>kg*m/s^2 = kg m /s^2 = kg m s^-2</code> - Newton
* <code>1/s = s^-1</code> - Hertz

To test the parser, create a page for a new type e.g. <nowiki><code>Type:Velocity</code></nowiki>. The following text is semantical nonsense but contains several test cases for the parser:
<pre>
<nowiki>

[[corresponds to:=1 m/s]]

[[corresponds to:=3.6 km/h]]

[[corresponds to SI:=1 m]]
[[corresponds to SI:=1 m/s]]
[[corresponds to SI:=1 1/s]]
[[corresponds to SI:=1 m*m*m/s*s*s]]
[[corresponds to SI:=1 m*m*m^-1/s*s*s^-1]]
[[corresponds to SI:=1 s^-1]]
[[corresponds to SI:=1 s^-1/m^-1]]
[[corresponds to SI:=1 m^2/s^2]]
[[corresponds to SI:=1 m*kg/s^2]]
[[corresponds to SI:=1 m kg/s^2 A]]
[[corresponds to SI:=1 m*kg/s^2*A*cd]]

[[corresponds to SI:=1 m^0]]
[[corresponds to SI:=1 s/1]]
[[corresponds to SI:=1]]
[[corresponds to SI:=1meter/sec]]
[[corresponds to SI:= m/s]]
[[corresponds to SI:=1 M/S]]
[[corresponds to SI:=1 m//s]]
[[corresponds to SI:=1 m/m/s]]
[[corresponds to SI:=1 m**m/s**s]]
[[corresponds to SI:=1 m*m*m/m*m*m]]

</nowiki>
</pre>

Ajutor:How can i use autocompletion?

2007-11-14T23:25:47Z

127.0.0.1: How can i use autocompletion?

;Question
:[[Question:=How can I use autocompletion in the wiki]]?

;Answer
:[[Description:=Use Ctrl+Alt+Space in any inputfield of the wiki.]]
[[DiscourseState:=Main:edit| ]]

== Triggering ==

AC can be triggered manually by pressing Ctrl+Alt+Space (Ctrl+Space on IE) or it can be triggered automatically when the system recognizes a context.
You can activate auto-triggering by choosing Preferences->Misc->Auto-triggering in his settings. Manual triggering is always possible, too.

== Autocompletion in the wiki search field ==
The left main search box supports Auto-completion.
[[Image:AdvancedSearchBox.png]]

== How to use Auto-completion ==
Auto-completion can be triggered inside a bracket context <nowiki>[[...]]</nowiki> in edit mode by pressing Ctrl+Alt+Space (Ctrl+Space in IE) or in most of the input forms that are present in the wiki. The text left from the cursor which can belong to an article's name is considered as user input. It is used as a string for pattern matching. Thus, at least one character must be entered to use AC. If no context could be detected, only the page titles are used for pattern matching.

The following contexts are detected automatically: The set of possible matching is semantically reduced, e.g. in the first case only categories are shown, because only these make sense here.

'''<match>'''is at least one character.

*Category annotation context.
**U types <nowiki>[[category:<match></nowiki>
*Attribute annotation context.
**U types <nowiki>[[<a property>:=<match></nowiki>: The property must be an enum or must have a unit.
*Relation annotation context. This context has two special subcontexts:
**U types <nowiki>[[Is subproperty of::<match></nowiki>: Only properties appear
**U types <nowiki>[[<a property>::<match></nowiki>: Only instances will appear
*Template annotation context.
**U types <nowiki>{{<match> </nowiki> : All templates appear
*Untyped link
**U types <nowiki>[[<match></nowiki>: All instances appear

==Administrator's note==
There are two stages of auto-completion:

#Standard: $semanticAC = false; Using only namespaces depending on context to filter results. For example: A relation target instance annotation context is detected, then '''all''' instances are requested which match lexically to the user input. This is fully implemented and can be tested.
#Advanced: $semanticAC = false; All semantic information from schema is used to filter results. For example: A relation has a range category of 'Car'. That means only instances of 'Car' matching lexically to the user input are requested when annotating this relation. This is not completly implemented, two aspects are missing: Inheritance and Template Schema Data.

Ajutor:How do I annotate a property?

2007-11-14T23:25:47Z

127.0.0.1: How do I annotate a property?

;Question
:[[question:=How do I annotate a property]]?

;Answer
:[[description:=Select the value you wish to annotate in the wikitext with the mouse and click annotate in the property container of the semantic toolbar.]]
[[discourseState:=Main:edit| ]]

'''Prerequisites'''

You are editing an article.

'''Goal'''

You want to annotate an existing part of the text with a property.

'''Workflow'''

''Annotating a property in the wiki text''

You open the double brackets <nowiki>[[</nowiki> and type at least one letter. If you use auto-triggering the auto-completion floater will appear automatically. Otherwise you have to press Ctrl+Alt+Space. If the desired property is not in the list, you may filter again by typing additional letters. Finally, chooses a property. The system will print the property's full name and put :: after it. Again, you are able to use auto-completion for the target instance. The whole annotation will be closed by <nowiki>]]</nowiki> automatically when auto-completion is used for the target instance.

''Annotating a property with the semantic toolbar''

Mark the text you want to annotate. In the section "Properties" of the Semantic Toolbar press the link "Annotate". Three text fields appear: the name of the property, its value/object which already contains the selected text and a field for the representation that is shown in the rendered article.

Fill in the name of the property, supported by auto-completion. You can change the value and set an optional representation in the field "Show". If the representation is left empty, the value will be rendered in the article.
With the "Add" link, the marked text is replaced by the annotation.

Save the article and the property appears in the fact box.

Ajutor:How do I ask for specific properties of an object in the wiki?

2007-11-14T23:25:47Z

127.0.0.1: How do I ask for specific properties of an object in the wiki?

;Question:
:[[Question:=How do I ask for specific properties of an object in the wiki]]?

;Answer:
:[[Description:=Add the instance to the query (restriction).]]

If you want to restrict an ASK-query to only one specific individual object like 'Britney Spears' you can do so by typing:
<nowiki><ask>[[Britney Spears]]</ask></nowiki>

In the query interface you can do this by simply clicking "add instance" and add the object for which you want the results.

You can also add further attributes or relations that should be displayed such as:
<nowiki><ask>[[Britney Spears]] [[hasTelephoneNo:=*]] [[hasAddress:=*]] </ask></nowiki>

[[DiscourseState:=QueryInterface:view| ]]

Ajutor:How do I update annotations from changed templates?

2007-11-14T23:25:47Z

127.0.0.1: How do I update annotations from changed templates?

;Question:
:[[Question:=How do I update annotations from changed templates]]?

;Answer:
:[[Description:=Use the Template Materializer bot.]]
[[DiscourseState:=Gardening:view| ]]

Template Materialization is necessary when templates contain semantic annotations. Every time when they are changed, a template materialization has to be done in order to update the semantic database content. Otherwise textual content and semantic content are not consistent.

Template Materialization is part of the Gardening Toolbox. You can get there by selecting the Gardening page on SpecialPages or you can use the shortcut in the navigation toolbox on the left.

*Select 'Materialize template content' in the left (Please note: Gardening rights are necessary to be able to use this bot!)
*After a short while you'll see the possible parametrization on the right.

You will get this page:

[[Image:GardeningToolBox.png]]

'Apply only to touched templates' means that the update is incremental. Only those pages which use templates which are changed since the last update are processed. One exception is the first template materialization. This is always done completely to make sure the wiki content is consistent.

*Press 'Run' button.
*A new row indicating the running process will be shown in the bot activity table.
*You will get an email notification when the process has finished. (If you supplied an email adress in your user profile)

== Administrator's note ==
The Gardening feature needs a new environment variable in LocalSettings.php to work properly:
*$phpInterpreter: Points to the php-Interpreter installed on the system, e.g. $phpInterpreter="D:/xampp152/xampp/php/php";

Additionally, the SMTP server entry should be set in php.ini
*php.ini should contain a valid SMTP server, e.g. SMTP = 87.106.5.57 for Ontoprise SMTP server. Otherwise email notification will not work.

Ajutor:How should I annotate the essence of an article?

2007-11-14T23:25:47Z

127.0.0.1: How should I annotate the essence of an article?

;Question
:[[question:=How should I annotate the essence of an article]]?

;Answer
:[[description:=Employ the "description" property.]]
[[discourseState:=Main:edit| ]]

'''Prerequisites'''

You are editing an arbitrary article.

'''Goal'''

You want to annotate the essence of the current article.

'''Workflow'''

Marks the text that describes the article's essence.

[[Image:DescrMarkText.png|center|thumb|576px|The marked essence of an article.]]

In the semantic toolbar press "Annotate" in the ''Properties'' section.

[[Image:DescrPressAnnotate.png|center|thumb|200px|Starting the annotation in the Properties section]]

The formerly selected text is set as value ("Page:") of the property. Enter "description" as name of the property. The system retrieves the type of this property and replaces the label "Page:" by "String". Then press "Add".

[[Image:DescrAddAnno.png|center|thumb|200px|The description's annotation.]]

The new annotation appears in the list of properties.

[[Image:DescrAnnoAdded1.png|center|thumb|200px|The list of properties contains the annotation.]]

The marked text is annotated.

[[Image:DescrAnnoAdded2.png|center|thumb|586px|The annotated wiki text.]]

Saves the article. Looking at the fact box, the property "description" might be undefined. This happens only for the very first time in a wiki, as "description" is a completely normal property.

[[Image:DescriptionOOps.png|center|thumb|588px|Description is an unknown property.]]

If this happens, set the type of "description" to string in the selection box to the right.
The page will be reloaded with the correct annotation.
[[Image:DescrFacts.png|center|thumb|720px|The description is displayed in the Fact box.]]

In effect, the article has been annotated with the normal property "description". But some parts of the wiki and the reasoning system can provide further features when they find it.

Ajutor:What are domains and ranges?

2007-11-14T23:25:47Z

127.0.0.1: What are domains and ranges?

;Question
:[[question:=What are domains and ranges]]?
[[discourseState:=Property:edit| ]]

;Answer
:[[description:=Domain is the category that can use (instanciate) the property and range is the category whose instances can be used as values of the property.]]

Categories can have properties. For instance, an atom has an atomic weight, which is a number. ''Atom'' is the category and ''atomic weight'' is the attribute. So each instance of an atom has an atomic weight, e.g. 1.008 for Hydrogen.

Normally it is sufficient, to create a property (e.g. ''Property:atomic weight'') and assign a type to it (e.g.''<nowiki>[[has type::Type:float</nowiki>''). The problem is, that the property can be used in every article of any category. In consequence, even a car could have an atomic weight.

To find out errors of this kind, the articles for properties should be annotated with a domain and range hint. The article for ''Property:atomic weight'' will contain the following line:

<nowiki>
[[has domain hint::Category:Atom]]
</nowiki>

The '''domain''' is the subject of a property, like the grammatical subject in a normal sentence: An ''atom'' has an ''atomic weight''.

Properties can have a type like numbers, string, dates etc. or they can have an object, if they are of type ''page''. For instance, a ''chemical reaction'' has a ''product'' of a ''molecule''. In this case, the property is ''has product'', its subject (domain) is a ''Chemical reaction'' (a category) and its object (called '''range''') is a ''molecule'' (a category). So the property ''has product'' will be defined like this on the page ''Property:has product'':

<nowiki>
[[has domain hint::Category:Chemical reaction]]
[[has range hint::Category:Molecule]]
</nowiki>

Ajutor:How can I create a new property?

2007-11-14T23:25:46Z

127.0.0.1: How can I create a new property?

;Question
:[[question:=How can I create a new property]]?

;Answer
:[[description:=Click "Create" in the "Properties" tool box.]]
[[discourseState:=Main:edit| ]]

'''Prerequisites'''

You are editing a page. The "Properties" tool box is available in the semantic toolbar.

'''Goal'''

You want to create a property. If you are editing a category, the domain of the new property should be the category.

'''Workflow'''

Click "Create" in the section "Properties" of the semantic toolbar.
[[Image:SEMWIKI26_CreateAttr.png|center|thumb|200px|The Properties section in the semantic toolbar.]]

Then the name of the property and its range or type have to be specified. If you are editing a category, the domain is already set to the current category.

[[Image:SEMWIKI26_EnterAttr.png|center|thumb|200px|Creating a new property for the current category.]]

When you click "Create", the new property is created and its properties are set in the corresponding new article. A new window opens (popups have to be accepted from this page) and shows the newly created property page for further elaboration.

''Ranges and types''

Normally, binary properties are created. They have a domain and a type. By default the type is "Type:Page" i.e. the value of the property is another article. For reasoning and gardening purposes, the category of these articles should be specified in the input field "Range:".

Range hints are generated in the wiki text e.g.
<nowiki>
[[Has range hint::Category:Product]]
</nowiki>

On the other hand, types are simple data types like integer numbers or strings.
To define a type, the range can be removed with the red cross. Then the new type is added by clicking the link "Add type". All built-in and user defined types can be selected in the selection field.

[[Image:SEMWIKI26_EnterType.png|center|thumb|200px|The range has been removed and a type was added.]]

For the example above, the following type definition is added to the wiki text:
<nowiki>
[[has type:=Type:Float]]
</nowiki>

''Defining n-ary properties''

In the same way as described above you can define n-ary properties. You can add additional types and ranges with the corresponding links.

N-ary properties are like binary properties with additional conditions. For instance, the density is a property of a substance. But it varies with temperature and pressure. This can be expressed with an n-ary property.

[[Image:SEMWIKI26_Nary.png|center|thumb|200px|The density of a substance (float value) is specified for a temperature and a pressure (float value).]]

The following type definition will be generated in the wiki text:
<nowiki>
[[Has type:=Type:Temperature;Type:Float;Type:Float]]
</nowiki>

If proper types are defined in the wiki, this specification can be made even more precise:
<nowiki>
[[Has type:=Type:Temperature;Type:Pressure;Type:Density]]
</nowiki>

So, n-ary properties are defined by a semi-colon separated list of types. What appears as range in the semantic toolbar will be encoded as <code>Type:Page</code> with an additional range hint.

Ajutor:How can I create hierarchies of categories?

2007-11-14T23:25:46Z

127.0.0.1: How can I create hierarchies of categories?

;Question
:[[question:=How can I create hierarchies of categories]]?

;Answer
:[[description:=Use "Annotate" or "Sub/Super" in the "Categories" tool box while you are editing a category.]]

[[discourseState:=Category:edit| ]]

'''Prerequisites'''

You are editing an article that defines a category.

'''Goal 1'''

You want to make this category a sub-category of other categories.

'''Workflow 1'''

Click "Annotate" in the "Categories" section of the semantic toolbar.
[[Image:SEMWIKI25_Annotate.png|center|thumb|200px|The categories tool]]

Enter the name of the super category in the field "Name". Auto-completion supports you. In addition the system checks, if the category already exists when you stop typing. Green signals an existing category and orange a non-existing.

[[Image:SEMWIKI25_EnterCategory.png|center]]
In any case, you can press the "Add"-button. The new annotation is appended at the end of the article and the current category has become its sub-category.

'''Goal 2'''

You want to make this category a sub-category of another category. If the super-category does not exist, it is created.

'''Workflow 2'''

You edit a category page: Press "Sub/Super" in the "Categories" section of the semantic toolbar. An input field for the name of the super category appears.

[[Image:SEMWIKI25_SubSuper.png|center|thumb|201px|Annotate the current article as sub category.]]

Enter the name of the super category (supported by auto-completion) and press Enter or Tab. The system checks, if the category already exist and signals this with green (exists) or orange (does not exist), respectively.

[[Image:SEMWIKI25_SuperEnter1.png|center|thumb|200px|Create a new category as sub or super category of the current category]]
[[Image:SEMWIKI25_SuperEnter2.png|center|thumb|200px|Make an existing category sub or super category of the current category]]

Anyway, click "Create ... super category..." or "Make ... super category ...". The current article is annotated as sub-category. If the super category does not exist, it is created and opened in a new browser tab. (Popup-blockers might prevent this, but can be configured to allow it.)

'''Goal 3'''

You want to make this category a super-category of another category. If this sub-category does not exist, it is created.

'''Workflow 3'''

The workflow is the same as in '''Workflow 2''', with the exception that you click "Make ... sub category... " or "Create ... sub category... ". The current article is not changed and the (possibly new) category is annotated as sub-category.