You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (Created) (JIRA)" <ji...@apache.org> on 2012/03/15 13:21:37 UTC
[jira] [Created] (STANBOL-536) Allow configuration of Type Mappings
for the KeywordLinkingEngine
Allow configuration of Type Mappings for the KeywordLinkingEngine
-----------------------------------------------------------------
Key: STANBOL-536
URL: https://issues.apache.org/jira/browse/STANBOL-536
Project: Stanbol
Issue Type: New Feature
Components: Enhancer
Reporter: Rupert Westenthaler
Assignee: Rupert Westenthaler
Priority: Minor
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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (STANBOL-536) Allow configuration of Type Mappings
for the KeywordLinkingEngine
Posted by "Fabian Christ (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabian Christ updated STANBOL-536:
----------------------------------
Fix Version/s: 0.9.0-incubating
> Allow configuration of Type Mappings for the KeywordLinkingEngine
> -----------------------------------------------------------------
>
> Key: STANBOL-536
> URL: https://issues.apache.org/jira/browse/STANBOL-536
> Project: Stanbol
> Issue Type: New Feature
> Components: Enhancer
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Priority: Minor
> Fix For: 0.9.0-incubating
>
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (STANBOL-536) Allow configuration of Type
Mappings for the KeywordLinkingEngine
Posted by "Rupert Westenthaler (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-536.
-----------------------------------------
Resolution: Fixed
implemented with #1301339
> Allow configuration of Type Mappings for the KeywordLinkingEngine
> -----------------------------------------------------------------
>
> Key: STANBOL-536
> URL: https://issues.apache.org/jira/browse/STANBOL-536
> Project: Stanbol
> Issue Type: New Feature
> Components: Enhancer
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Priority: Minor
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira