[STANBOL-556] LdPath processor for Entityhub Indexing

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.9.0-incubating
• Fix Version/s: entityhub-0.10.0-incubating
• Component/s: Entityhub
• Assignee: Rupert Westenthaler
• Reporter: Rupert Westenthaler
• Created: 28/Mar/12 09:57
• Updated: 10/Jul/12 10:58
• Resolved: 27/Apr/12 06:27

Description

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.

Sub-Tasks

• LDPath processor operating on the IndexingSource and Implementation for the JenaTDB based indexing source.: Closed
• LDPath processor operating on the IndexingDestination in the post-processing phase: Closed