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 2012/04/24 19:55:33 UTC

[jira] [Created] (STANBOL-590) LDPath processor operating on the IndexingSource and Implementation for the JenaTDB based indexing source.

Rupert Westenthaler created STANBOL-590:
-------------------------------------------

             Summary: LDPath processor operating on the IndexingSource and Implementation for the JenaTDB based indexing source.
                 Key: STANBOL-590
                 URL: https://issues.apache.org/jira/browse/STANBOL-590
             Project: Stanbol
          Issue Type: Sub-task
          Components: Entity Hub
    Affects Versions: 0.10.0-incubating
            Reporter: Rupert Westenthaler
            Assignee: Rupert Westenthaler
             Fix For: 0.10.0-incubating


This LDPath processor would allow to use the full LDPath functionality based on the Data of the IndexingSource.
Configuration of such a processor would be also easy as the IndexingSource is already present for every indexing process.
This requires IndexingSurces to implement RDFBackend. This can be easily done for the Jena TDB based indexing source.

This feature would be very useful for calculating the "semantic context" of Entities. Such as following related Entities and indexing their labels with the current Entity. This information may be later used for similarity searches such as Solr MLT.

However the same feature might also be used materialize transitive, symmetric and/or inverse properties in indexed datasets.

Users need to NOTE that indexing time will increase if using those features as execution configured LDPath programms will cause a lot of additional requests to the IndexingSource. 

--
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-590) LDPath processor operating on the IndexingSource and Implementation for the JenaTDB based indexing source.

Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/STANBOL-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rupert Westenthaler resolved STANBOL-590.
-----------------------------------------

    Resolution: Fixed

implemented with revision #1330107
                
> LDPath processor operating on the IndexingSource and Implementation for the JenaTDB based indexing source.
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: STANBOL-590
>                 URL: https://issues.apache.org/jira/browse/STANBOL-590
>             Project: Stanbol
>          Issue Type: Sub-task
>          Components: Entity Hub
>    Affects Versions: 0.10.0-incubating
>            Reporter: Rupert Westenthaler
>            Assignee: Rupert Westenthaler
>             Fix For: 0.10.0-incubating
>
>
> This LDPath processor would allow to use the full LDPath functionality based on the Data of the IndexingSource.
> Configuration of such a processor would be also easy as the IndexingSource is already present for every indexing process.
> This requires IndexingSurces to implement RDFBackend. This can be easily done for the Jena TDB based indexing source.
> This feature would be very useful for calculating the "semantic context" of Entities. Such as following related Entities and indexing their labels with the current Entity. This information may be later used for similarity searches such as Solr MLT.
> However the same feature might also be used materialize transitive, symmetric and/or inverse properties in indexed datasets.
> Users need to NOTE that indexing time will increase if using those features as execution configured LDPath programms will cause a lot of additional requests to the IndexingSource. 

--
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