Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

KIM supports various model representations of the entity labels within its repository.

Currently, there are two basic models:

  • Aliases (default)
  • Labels

Aliases. The Aliases model representation allows adding supplementary metadata about the entity labels. For example, information about the source of the item can be added. However, this representation requires more statements to be stored within the semantic repository. Entities have two kinds of aliases - exactly one main alias and many secondary aliases. Aliases are connected to corresponding literals using the rdfs:label predicate.

Labels. This is the more simple model. It stores the connections between entities and labels directly. There can be two types of relations for each entity: exactly one main label and many secondary labels. The predicates used in this case are <> and rdfs:label.

In KIM 3.5, we have provided the capability of the administrator selecting custom predicates based on the Labels model representation. In order to select custom labels model, one have to set the to Custom and then enlist all required predicates as value of the (a comma-separated list).

A sample configuration:

As can be seen from the comments in this example, there is one predicate that is always added - the default Labels model predicate

Another improvement allows filtering the labels by their language (if such is provided within the literal object from the semantic repository). The user needs to set the property value to the desired list of language abbreviations. Check the example:

As can be seen, there are again default values that are always added to the list.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.