Allow configuration of Type Mappings for the KeywordLinkingEngine

The Type Mappings are used to determine the "dc:type" of the TextAnnotation based on the types of the suggested Entity. This mappings are already configurable in the EntityLinkerConfig [1] however currently there is no way to change the default configuration when creating an KeywordLinkingEngine instance.

Proposed Syntax:

{uri}
{source} > {target}
{source1}; {source2}; ... {sourceN} > {target}

The first variant is a shorthand for {uri}

>

{uri} and therefore specifies that the {uri}

should be used as 'dc:type' for TextAnnotations if the matched entity is of type

{uri}

. The second variant matches a

{source}

URI to a

{target}

. Variant three shows the possibility to match multiple URIs to the same target in a single configuration line.

Both 'ns:localName' and full qualified URIs should be supported.

The currently used default configuration is

dbp-ont:Person; foaf:Person; schema:Person > dbp-ont:Person
dbp-ont:Organisation; dbp-ont:Newspaper; schema:Organization > dbp-ont:Organisation
dbp-ont:Place; schema:Place; gml:_Feature > dbp-ont:Place
skos:Concept

This extension would allow to define additional mappings for types used in their ontologies e.g.

dailymed:organization > dbp-ont:Organisation

but it would also allow to define new dc:types used with fise:TextAnnotations e.g.

drugbank:drugs; dbp-ont:Drug; dailymed:drugs; sider:drugs; tcm:Medicine > drugbank:drugs
diseasome:diseases; linkedct:condition; tcm:Disease > diseasome:diseases

[1] http://svn.apache.org/repos/asf/incubator/stanbol/trunk/enhancer/engines/keywordextraction/src/main/java/org/apache/stanbol/enhancer/engines/keywordextraction/linking/EntityLinkerConfig.java