Open ariutta opened 7 years ago
Fixed the links to go to WpRdf and WpTypes.
In terms of usage, for RDF queries on WP content, you should use the wp vocab. The queries look consistent to me if you stay within the wp vocab, i.e., wp:GeneProduct is a subclass of wp:DataNode, not gpml:DataNode. The inconsistent part seems to simply be the unnecessary prefix for gpml vocab, since it isn't used.
For this DataNode:
<DataNode TextLabel="BDKRB2" GraphId="f54f5" Type="GeneProduct">
<Attribute Key="org.pathvisio.model.BackpageHead" Value="BDKRB2 | bradykinin receptor B2"/>
<Graphics CenterX="759.3333333333333" CenterY="388.0" Width="60.0" Height="20.0" ZOrder="32768" FontSize="10" Valign="Middle"/>
<Xref Database="Entrez Gene" ID="624"/>
</DataNode>
I think these are the applicable types from the WP vocab:
rdf:type
is BOTH wp:DataNode
and wp:GeneProduct
gpml:type
is ONLY wp:GeneProduct
For wpTypes, it appears to not be used at present. Does that sound correct, @RyAMiller?
Two questions/problems:
gpml:Type vs.wpTypesBased on GPML2013a,
Type
is a property for elements likeDataNode
, with expected values likeGeneProduct
:Based on
rdf:type
, the type above would begpml:DataNode
, not. But when I query our sparql endpoint, it appears the type can bewp:GeneProduct
wp:DataNode
orwp:GeneProduct
but notgpml:DataNode
.Query for rdf:type wp:DataNode succeeds:
Query for rdf:type wp:GeneProduct succeeds
Query for rdf:type gpml:DataNode fails: