Page History
...
5 Strategy for adding relations in taxonomy type knowledge bases
TODO: dit vind ik een erg onduidelijk stukje (ASR)
Before we continue with the next Entity, we want to give Perhaps you would like to have a bit more insight in the creation of relations in taxonomy type of knowledge bases. In the previous paragraph you have noticed that we created Entity-relations, paragraph 2.3.3.2 above and “normal” relations, paragraph 2.3.3.3 above. But why do we have two different methods?
You have three ways of adding and using relations:
- Adding an Entity relation to the Entity in a Taxonomy;
- Add a relation to the Knowledge Browser and connect it to a parameter in an Entity;
- Create a relation in the Knowledge Browser and let the modeler determine which relations to use to determine a parameter in an Entity. This is only facilitated when all parameters in the Entity will be determined by the modeler.
Three important remarks can be made about the use of the different relation types:
Above you encountered two different methods of adding relations to entities. Why are there two different methods?
- The general approach is to create entity relations in the taxonomy.
- The main reason to use normal (global) relations and connecting them to parameters in an entity is when you know that the relation will be used at more than one spot in the taxonomy. In that case you rather create one relation and connect it to the parameters in the relevant entities.
- Also, use normal relations if The general approach is to create Entity relations when you are developing a Taxonomy type of knowledge base.
Only used normal relations when you want to use the modeling/reasoning functionality of Quaestor. You might want to use the modeler when you want to execute complex models which make use of reasoning an advantage over a normal traditional fully hardcoded model (which a Taxonomy taxonomy is to some extent). This is the case when you want the structure (network of relations) of a model to be dependent on the choices made and input provided by the user. The main reason to use normal relations and connecting them to parameters in an Entity is when you know that the relation will be used on multiple positions in the Taxonomy. In that case you rather create one relation and connect it to the parameters in the relevant Entities.You then have a hybrid knowledge base (mix of taxonomy and classical).
| Note |
|---|
Use the ENTITY# function only in combination with |
...
entity relations |
...
! You can use this function in normal relations but this is not advisable. |
...
This is because the EntityID in the ENTITY# function will be renumbered when modifications are made to the |
...
taxonomy that cause |
...
entities to be renumbered. This renumbering |
...
will not take place for normal relations. |
...
Overview
Content Tools