Hi Grant,

in addition to what Ben mentioned, you can still get the required results using the following query:

   PREFIX dbpedia-owl: <http://dbpedia.org/ontology/>
   PREFIX dbpprop: <http://dbpedia.org/property/>
   PREFIX drugbank:
   <http://wifo5-04.informatik.uni-mannheim.de/drugbank/resource/drugbank/>
   PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
   PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
   PREFIX owl: <http://www.w3.org/2002/07/owl#>
   SELECT * WHERE{
        {
            SELECT * WHERE {
                SERVICE
   <http://wifo5-04.informatik.uni-mannheim.de/drugbank/sparql>
                {?modifiedDrug rdfs:label "Lepirudin";
   drugbank:affectedOrganism ?affectedOrganism}
            }
        }.
        {
            SELECT IRI(REPLACE(STR(?drug),
   "http://www4.wiwiss.fu-berlin.de";,
   "http://wifo5-04.informatik.uni-mannheim.de";)) AS ?modifiedDrug WHERE {
                SERVICE <http://dbpedia.org/sparql>
                {?a rdfs:label "Lepirudin"@en; owl:sameAs ?drug;
   dbpprop:routesOfAdministration ?routes.}
        }
        }

   }


Hope it helps.

On 03/06/2013 10:16 AM, Ben Companjen wrote:
Hi Grant,

When I click the link
<http://www4.wiwiss.fu-berlin.de/drugbank/resource/drugs/DB00001>  I
get redirected to
<http://wifo5-03.informatik.uni-mannheim.de/drugbank/resource/drugs/DB00001>
(3 instead of 4), so it looks like the "resource" URIs are not stable.
There is no <wifo5-03...> owl:sameAs <wifo5-04...> either so the
resources could be different. The redirect URI should be stable ("Cool
URIs don't change.").

In the page that is returned, I see owl:sameAs to DBpedia drugs, but
those URIs include "www." which I believe is incorrect.

I agree that shared URIs increase the value of different descriptions,
but the Drugbank could use some changes too:)
Besides, DBpedia extracts information from Wikipedia (only, AFAIK), so
changes should be made there. I hope I made my point that the Drugbank
uses inconsistent URIs, so if you do change Wikipedia, there may be
people not agreeing to your edits for this reason.

Regards,

Ben

On 5 March 2013 23:57, Smith, Grant M. (UMKC-Student)
<[email protected]>  wrote:
>PREFIX dbpedia-owl:<http://dbpedia.org/ontology/>
>PREFIX dbpprop:<http://dbpedia.org/property/>
>PREFIX drugbank:
><http://wifo5-04.informatik.uni-mannheim.de/drugbank/resource/drugbank/>
>PREFIX rdf:<http://www.w3.org/1999/02/22-rdf-syntax-ns#>
>PREFIX rdfs:<http://www.w3.org/2000/01/rdf-schema#>
>PREFIX owl:<http://www.w3.org/2002/07/owl#>
>SELECT * WHERE{
>{
>SELECT * WHERE {
>SERVICE<http://wifo5-04.informatik.uni-mannheim.de/drugbank/sparql>
>{?drug rdfs:label "Lepirudin"; drugbank:affectedOrganism ?affectedOrganism}}
>} .
>{
>SELECT ?drug ?routes WHERE {
>SERVICE<http://dbpedia.org/sparql>
>{?a rdfs:label "Lepirudin"@en; owl:sameAs ?drug;
>dbpprop:routesOfAdministration ?routes}}
>}}
>
>This query returns no results.  However, each subquery within it does return
>results.  The results of each subquery are not joinable by the variable
>?drug because the objects in the owl:sameAs relationships across dbpedia are
>not the actual resource URIs, that are used in other datasets such as
>drugbank.  These are the owl:sameAs values for
><http://dbpedia.org/resource/Lepirudin>
>
>http://pt.dbpedia.org/resource/Lepirudina
>http://fr.dbpedia.org/resource/Lépirudine
>http://www4.wiwiss.fu-berlin.de/dailymed/resource/ingredient/Lepirudin
>http://www4.wiwiss.fu-berlin.de/drugbank/resource/drugs/DB00001
>freebase:Lepirudin
>
>The actual resource URI used by drugbank is
><http://wifo5-04.informatik.uni-mannheim.de/drugbank/resource/drugs/DB00001>.
>Instead of using values that redirect to the resource, dbpedia should use
>the values used by other datasets to represent the resource.  Following such
>practices would make federated queries possible, and generally improve the
>quality of the Semantic Web.
>
>
>Grant Smith
>
>Grant Smith
>816-588-2004


--
Kind Regards
Mohamed Morsey
Department of Computer Science
University of Leipzig

------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Dbpedia-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion

Reply via email to