You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on rdf:type, the type above would be gpml:DataNode, not wp:GeneProduct. But when I query our sparql endpoint, it appears the type can be wp:DataNode or wp:GeneProduct but not gpml:DataNode.
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.
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:
The text was updated successfully, but these errors were encountered: