| Latest Newsletter | ||||
|
||||
Abstract
URIQA is a model for knowledge discovery both from authoritative sources, as well as from third party sources. It proposes an extension to present Web architecture to enable Semantic Web activity. This is done by communicating to the web server that it should resolve the specified URI in terms of knowledge (description) about the resource, rather than its representation.
The URI Query Agent Model
Introduction:
The present web is concerned about providing the representations of resources. This is fine for humans browsing the web who can deal with great amount of variety, inconsistency, and ambiguity.
But the semantic web agents can not deal with broad range of possible representations associated with the resource. Semantic web agents require information which is explicit and formally defined.
URIQA (URI Query Agent) is a model for knowledge discovery both from authoritative sources as well as from third party sources. It proposes extension to present web architecture to enable semantic web activity. This is done by communicating to the web server that it should resolve the specified URI in terms of knowledge (description) about the resource rather than its representation.
Semantic Web Methods for HTTP:
URIQA extends the present web architecture by introducing the following HTTP methods for interacting with semantic web server:
|
MGET |
Return a concise bounded description of the resource denoted by the request URI. E.g. MGET /foo HTTP/1.1 Host: example.com , <http://example.com/foo>. |
|
MPUT |
Add the statements contained in a concise bounded description of the resource, provided as input, to the (possibly empty) body of knowledge maintained about the resource denoted by the request URI. e.g. MPUT /foo HTTP/1.1 Host: example.com i.e. Add statements to the description of the resource denoted by <http://example.com/foo>. |
|
MDELETE |
Remove the statements contained in a concise bounded description of the resource, provided as input, from the existing knowledge maintained about the resource denoted by the request URI. If no description is provided as input, remove all statements asserted about the specified resource. e.g. MDELETE /foo HTTP/1.1 Host: example.com i.e. Delete statements from the description of the resource denoted by <http://example.com/foo>. |
The URIQA Semantic Web Service Interface :
The URIQA model defines a simple web service interface for accessing descriptions of resources by third parties other than the web authority of the URI denoting the resource and/or for resources denoted by URIs which are not meaningful to the HTTP protocol.
All URIQA service implementations must provide support for the following parameters:
|
Method |
Parameter |
Value |
Description |
|
GET, POST |
uri |
<URI> |
The URL encoded URI denoting the resource described. |
|
POST |
method |
MGET, MPUT, or MDELETE |
The URIQA method to be applied. |
e.g.:
GET /uriqa?uri=http%3a%2f%2fexample%2ecom%2fblargh HTTP/1.1 Host: example.com
Retrieve from example.com a description of the resource denoted by <http://example.com/blargh>
POST /uriqa?uri=http%3a%2f%2fwidgets%2eorg%2ffoo%23bar&method=MGET HTTP/1.1 Host: example.com
Retrieve from example.com a description of the resource denoted by <http://widgets.org/foo#bar>
The URIQA model also defines additional parameters which are relevant to GET requests. All the service parameters may also be specified as an HTTP message header. The header name for each parameter corresponds to the prefix "URIQA-" followed by service parameter name. To name a few:
- URIQA-uri:
- URIQA-format:
- URIQA-naming:
- etc.
Reference:
Impressum |
|
|
| Newsletters |
|
Webmaster
|