Re: query language

> What functionality do you need that is not currently offered?

Actually a query language will be needed by automated REST clients.
Just to make an example. I am a REST client, and I want to look for a
service with certain application state transformation capabilities.
For example I want to transform my application state (having 10$) to
another one (having a pizza). What can I do when I don't know the IRI
of a service with such capabilities? I can use a service discovery
mechanism, for example a search engine (google) to find it. So I use
the query language (English) poorly supported by that search engine
and find the service I need (Pizza Hut). After that I can use that
service and evaluate the quality of the results. Another possible
solution to construct the intended transformation step by step using
my transformation knowledge graph if I am a client with artificial
intelligence (homemade pizza).

Now currently we have much lower abstraction level problems, like
defining a standard service interface and this query language problem
might be solved by SPARQL.

Received on Friday, 19 September 2014 10:25:37 UTC