Difference between revisions of "CTS2 RDF Plugin"

From NCBO Wiki
Jump to: navigation, search
(Known Issues)
(Known Issues)
Line 18: Line 18:
 
</code>
 
</code>
  
Unbound predicate queries are expensive to execute on the triple store, and CTS2 requires all Properties of a given subject to be displayed. This will cause all CTS2 Read services to have a delay in returning results.
+
* Unbound predicate queries are expensive to execute on the triple store, and CTS2 requires all Properties of a given subject to be displayed. This will cause all CTS2 Read services to have a delay in returning results.
  
 
=== CodeSystemCatalogQuery ===
 
=== CodeSystemCatalogQuery ===

Revision as of 04:31, 7 June 2012

CTS2 REST Services

Known Issues

  • URI Mismatch: Certain portions of the RDF Plugin utilize the NCBO REST service for searching. Sometimes, the URIs returned by the NCBO REST service are not identical to those int the triple store. This will manifest on Entity Read by Name queries.
  • Jena Local Name Parsing: Jena is used in the background for parsing the returned RDF.

Given a URI like http://purl.bioontology.org/ontology/RCD/7K6Ax

Jena will parse the "local part" of this URI as 'K6Ax' (notice the missing '7'). This may be a Jena bug. The only known example is: http://informatics.mayo.edu/cts2/services/bioportal-rdf//codesystem/RCD/version/RCD-42295/entity/RCD:7K6Ax Notice how the 'name' part and the local part of the 'about' are out of sync.

  • All Read Services are executed by a SPARQL query similar to:

<http://some/uri...> ?p ?o

  • Unbound predicate queries are expensive to execute on the triple store, and CTS2 requires all Properties of a given subject to be displayed. This will cause all CTS2 Read services to have a delay in returning results.

CodeSystemCatalogQuery

CodeSystemCatalogRead

CodeSystemCatalogVersionQuery

CodeSystemVersionCatalogRead

EntityDescriptionQuery

EntityDescriptionRead

ValueSetCatalogQuery

ValueSetCatalogRead


ResolvedValueSetQuery


AssociationQuery