api4kb_queries
====== Differences ====== This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
api4kb_queries [2012/10/08 12:24] hsolbrig |
api4kb_queries [2013/03/17 17:15] (current) admin |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| APIs for query support [[start|Link to API4KB Main Page]] | APIs for query support [[start|Link to API4KB Main Page]] | ||
| + | * Ask, tell ...? queries with side effects? what do you do with inferred knowledge based on the query (post it, not)? | ||
| + | * Read-only (boolean - can/can't satisfy, or extract if available) | ||
| + | * Read-write API (i.e. with side effects that can update the KB) | ||
| + | * Inform -- write something to the KB, but only commit if consistency is preserved (flag) | ||
| + | * Inform/reason/query -- write something to the KB, reason over the KB, query to get revised results | ||
| + | * Hypothetical reasoning -- inform/reason/query/rollback | ||
| + | * Or without rollback, meaning commit the results, but only if consistency is preserved | ||
| + | * Service discovery (e.g. query to a portal for services pertaining to a certain subject) | ||
| * Determining service capabilities | * Determining service capabilities | ||
| - | * Determine which "semantic profiles" (e.g. OWL 1.1 Full, EL, RL, QL, Common Logic, RDF Inference, ...) the service recognizes | + | * Determine which "semantic profiles" (e.g. OWL 1.1 Full, EL, RL, QL, Common Logic, %%RDF%% Inference, ...) the service recognizes |
| - | * Determine which formats the service recognizes (e.g. RDF/XML, RDF/N3, ...) | + | * Determine which formats the service recognizes (e.g. %%RDF%%/%%XML%%, %%RDF%%/N3, ...) |
| * Determine which query languages are recognized (e.g. SPARQL, graph query language, OWLQL, etc) | * Determine which query languages are recognized (e.g. SPARQL, graph query language, OWLQL, etc) | ||
| * Response should address which, if any capabilities are mandatory, optional | * Response should address which, if any capabilities are mandatory, optional | ||
| * Response should address consistent naming - declare which URIs will be used to identify capabilities | * Response should address consistent naming - declare which URIs will be used to identify capabilities | ||
| + | Most of these APIs may require various compliance levels, so that people can support read-only, or inform but not inform/reason/query, or not hypothetical reasoning ... etc. | ||
| + | |||
| + | ===== Questions ===== | ||
| + | * Enter questions here | ||
api4kb_queries.1349713444.txt.gz · Last modified: 2012/10/08 12:24 by hsolbrig
Page Tools
