W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > March 2009

Suggestion: Support Linking from all Query Responses

From: Leigh Dodds <leigh.dodds@talis.com>
Date: Fri, 6 Mar 2009 11:07:19 +0000
Message-ID: <f323a4470903060307t6335cee9x4984e67584afcdd8@mail.gmail.com>
To: public-rdf-dawg-comments@w3.org
Hi,

I'd like to make the following feature suggestion/raise an issue with the WG:

Feature: Support contextual links from all query responses

Feature Description

  The SPARQL XML Results format currently supports a <link/> element
allowing references to
  additional metadata to be included in the response. However this
feature is limited as there is
  no way for a client to select between the possible alternatives. A
"rel" attribute similar to HTTP
  would be one way to enable this, as would allowing additional
elements from extra namespaces
  to be included in the response.

  A typical example of using this feature would be to link back to the
original endpoint, or to licensing metadata
  associated with the request.

  However currently this feature has no equivalent for
CONSTRUCT/DESCRIBE queries. It is potentially
  legal for an endpoint to include additional statements that refer to
the response document, but it is more likely
  that clients will simply treat these statements as part of the
results, rather than separate metadata about
  the result document.

Example:

 Allow, e.g.:

 <link rel="license" href="..."/>

 and/or

 <rdf:Description rdf:about="...">
  ...statements about response document...
 </rdf:Description>

 ... query results ...

Example Implementations

 None that I'm aware of.

Use Cases

* Make the protocol more RESTful by allowing hypertext linking, from
all result formats
* Allow linking to, or embedding of license statements relating to the
data in the results
* Allow linking to a service description for the endpoint and/or VoiD
description of the dataset

Cheers,

L.

-- 
Leigh Dodds
Programme Manager, Talis Platform
Talis
leigh.dodds@talis.com
http://www.talis.com
Received on Friday, 6 March 2009 11:07:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 6 March 2009 11:08:00 GMT