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

Rupert Westenthaler resolved STANBOL-556.
-----------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.10.0-incubating

as of Revision #1330107 users can now

* perform any LDpath program on the IndexingSource (if it does implement 
RDFRepository).
* perform any LDpath program on the IndexingDestination within the new 
post-processing phase
* perform local LDpath programs (e.g. for adv. filters on properties) as an 
EntityProcessor

Note also that the Jena TDB indexing source now implements RDFRepository

                
> LdPath processor for Entityhub Indexing
> ---------------------------------------
>
>                 Key: STANBOL-556
>                 URL: https://issues.apache.org/jira/browse/STANBOL-556
>             Project: Stanbol
>          Issue Type: New Feature
>          Components: Entity Hub
>            Reporter: Rupert Westenthaler
>            Assignee: Rupert Westenthaler
>            Priority: Minor
>             Fix For: 0.10.0-incubating
>
>
> This will allow to use simple LDPath statements for property mappings during 
> the indexing of datasets.
> While the default mapping language supports a lot of use cases for mapping, 
> converting and filtering of properties it is by far not as capable as 
> [LDpath](http://code.google.com/p/ldpath/). Because of that the indexing 
> tools has also support for using LDPath to process entities by using the 
> "LdpathProcessor". 
> A typical usage example of the LdpathProcessor processor are type specific 
> mappings such as
>     skos:prefLabel = .[rdf:type is diseasome:genes]/rdfs:label;
> This specifies that only for entities of the type "diseasome:genes" the 
> rdfs:label is mapped to skos:prefLabel. rdfs:labels of Entities with other 
> types will not be mapped to skos:prefLabel by this rule.

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

        

Reply via email to