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 2011/12/05 23:02:40 UTC

[jira] [Created] (STANBOL-409) LDPath RDFBackend implementations for the Entityhub

LDPath RDFBackend implementations for the Entityhub
---------------------------------------------------

                 Key: STANBOL-409
                 URL: https://issues.apache.org/jira/browse/STANBOL-409
             Project: Stanbol
          Issue Type: Sub-task
          Components: Entity Hub
            Reporter: Rupert Westenthaler
            Assignee: Rupert Westenthaler


LDPath requires the implementation of the RDFBackend interface so that it can query data within an entity source. The plan is to provide implementation of this interface for the following Entityhub Interfaces:

* Yard: This is mainly interesting because Yard implementations typically do not require an OSGI environment.
* ReferencedSite
* ReferencedSiteManater: to use LDPath over all referenced sites
* Entityhub


--
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-409) LDPath RDFBackend implementations for the Entityhub

Posted by "Rupert Westenthaler (Resolved) (JIRA)" <ji...@apache.org>.

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

Rupert Westenthaler resolved STANBOL-409.
-----------------------------------------

    Resolution: Fixed

With Revision #1210685 RDFRepository for Yard, ReferencedSite, ReferencedSiteManager and Entityhub where added. In addition an implementation that can use Representations already retrieved by a query was added.

For Examples how to use the new API see the UnitTest "BackendTest":

Especially the new possibility to follow inverse properties is interesting because it allows to select inverse properties for Entities:

The unit test uses an Example for the DBPedia Category "Category:Harvard_University_alumni"

LDPath Program:

    name = rdfs:label :: xsd:string;
    parent = skos:broader :: xsd:anyURI;
    childs = ^skos:broader :: xsd:anyURI;
    members = ^<http://purl.org/dc/terms/subject> :: xsd:anyURI;

The Representation as stored in the Entityhub

    skos:broader:[dbpedia:Category:Harvard_University_people, 
        dbpedia:Category:Alumni_by_university_or_college_in_Massachusetts, 
        dbpedia:Category:Ivy_League_alumni]
    rdfs:type:[http://www.w3.org/2004/02/skos/core#Concept]
    entityRank:[0.66937166]
    rdfs:abel:[Harvard University alumni@en]
    skos:prefLabel:[Harvard University alumni@en]

As one can see members and child categories are not stored with categories. However the "^{property}" statement of LDPath allows to retrieve them.

    name: [Harvard University alumni]
    parent: [dbpedia:Category:Harvard_University_people, 
        dbpedia:Category:Alumni_by_university_or_college_in_Massachusetts, 
        dboedia:Category:Ivy_League_alumni]
    childs: [dbpedia:Category:John_F._Kennedy_School_of_Government_alumni, 
        dbpedia:Category:Harvard_Law_School_alumni, 
        dbpedia:Category:Harvard_Medical_School_alumni, 
        dbpedia:Category:Harvard_Business_School_alumni]
    members: [dbpedia:Edward_Said, dbpedia:Norman_Mailer, dbpedia:John_Lithgow, 
        dbpedia:John_Quincy_Adams, [.. and manny more ..]

                
> LDPath RDFBackend implementations for the Entityhub
> ---------------------------------------------------
>
>                 Key: STANBOL-409
>                 URL: https://issues.apache.org/jira/browse/STANBOL-409
>             Project: Stanbol
>          Issue Type: Sub-task
>          Components: Entity Hub
>            Reporter: Rupert Westenthaler
>            Assignee: Rupert Westenthaler
>
> LDPath requires the implementation of the RDFBackend interface so that it can query data within an entity source. The plan is to provide implementation of this interface for the following Entityhub Interfaces:
> * Yard: This is mainly interesting because Yard implementations typically do not require an OSGI environment.
> * ReferencedSite
> * ReferencedSiteManater: to use LDPath over all referenced sites
> * Entityhub

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