...

• Create a new class alongside Dimensions and call it General.
• Create the following parameters (all are values) within the Knowledge Browser:

• Next drag and drop the parameters: Lpp, Boa, Cb, Displacement, Rho, T_design and Volume from the Knowledge Browser into the entity Hydrostatics.

...

2    Creating a drop down box Image Added

Because their there will only be two possible values for parameter Rho (1.025 or 1.000 [t/m³]), it is useful to create a dropdown box. This can be done by providing a special reference.

• Select the Parameter tab of the Properties window for Rho.
• In the Reference field type the following:

Density of water. Select water type;
1.025<EQ>Saltwater
1.000<EQ>Freshwater

3    Creating entity relations Image Added

In the Hydrostatics entity, calculations need to be performed based upon information from Main Dimensions and some relation. In order to achieve this, you have to create so called entity-relations. The first entity-relation to create will be for parameter Boa in entity Hydrostatics: the value of Boa in entity Hydrostatics should be equal to the value of Boa in entity Main Dimensions.

...

• Enter the following relation and click Save.

Boa = ENTITY#(12).Boa

This means Boa is equal to (will copy the value of) the Boa of the entity with QEntityID = 12.

...

• Create an entity relation for Lpp in entity Hydrostatics in the same way. This parameter must be equal to the value of Lpp in Entity Main Dimensions:

Lpp = ENTITY#(12).Lpp

Finally, relations must be provided to calculate Displacement and Volume in entity Hydrostatics. The following calculations should be made:

Displacement = Cb * Lpp * Boa * T_design * Rho

Volume = Cb * Lpp * Boa * T_design

• Create an entity relation for Volume in the same way. Delete ENTITY#()in the editor and enter the expression above.

...

4    Connecting existing relations to entities Image Added

By adding the relation to the Knowledge Browser, you can connect it several times to various parameters in various entities, saving a lot of time.

...

To connect the relation, in the Workbase, select the parameter Displacement in entity Hydrostatics. Then, select the right mouse button menu Taxonomy>Choose/create relation or relation or press Ctrl+T. A window will open showing the available relations for the selected parameter in the Knowledge Browser.

You can browse through the available relations and select the relation you want to use to compute the parameter, see Figure 67below. In this case select the relation you have just created. The same method can be used to include any available relation for any selected parameter.

...

5    Strategy for adding relations in taxonomy type knowledge bases

TODO: dit vind ik een erg onduidelijk stukje (ASR)

Image Added

Perhaps you would like to have a bit Before we continue with the next Entity, we want to give 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:

1. Adding an Entity relation to the Entity in a Taxonomy;
2. Add a relation to the Knowledge Browser and connect it to a parameter in an Entity;
3. 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?

1. The general approach is to create entity relations in the taxonomy.
2. 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.
3. 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).

...

...

...

...

...

...

...

Back to content | << Previous | Next >>