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 (JIRA)" <ji...@apache.org> on 2015/04/16 08:23:58 UTC

[jira] [Updated] (STANBOL-1417) Create Language Annotation for parsed "Content-Language" header

     [ https://issues.apache.org/jira/browse/STANBOL-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rupert Westenthaler updated STANBOL-1417:
-----------------------------------------
    Summary: Create Language Annotation for parsed "Content-Language" header  (was: Clreate Language Annotation for parsed "Content-Language" header)

> Create Language Annotation for parsed "Content-Language" header
> ---------------------------------------------------------------
>
>                 Key: STANBOL-1417
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1417
>             Project: Stanbol
>          Issue Type: Improvement
>          Components: Enhancement Engines
>    Affects Versions: 0.12.0
>            Reporter: Rupert Westenthaler
>            Assignee: Rupert Westenthaler
>            Priority: Minor
>             Fix For: 1.0.0, 0.12.1
>
>
> Stanbol supports parsing the language of the content by using the "Content-Language" header since STANBOL-660. However currently only the `dc:language` property is set for the ContentItem.
> However based on the specification of STANBOL-613 this information is only used as fallback if no language annotation is present in the ContentItem. So as soon as any Language Identification Engine is present in the Chain the "Content-Language" as parsed by the User will get ignored. This is not the intention of a user explicitly parsing the language.
> To force Stanbol to use the parsed language a Language Annotation with the confidence 1.0 needs to be added to the metadata of the ContentItem instead. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)