[comment HTTP in RDF ] More detailed Use cases needed

Hi,
This is a comment about 
http://www.w3.org/TR/2006/WD-HTTP-in-RDF-20061220/#use-cases

The use cases are interesting but they lead to the question "Are there real use cases?". 
For example, it is not clear how someone has access to the list of possible negotiated resources. Once the resource has been sent by the server, it is almost impossible to know what were the other representations. 
    Does that mean that "HTTP in RDF" must be used at a higher level in the HTTP server?
    Or recording only the details of the negotiated resource is enough?
Giving more details on the use cases would help to understand the technology.

  * What is the issue?
  * How HTTP in RDF solve the issue?
  * Preliminary implementations using this technique





Title: "HTTP Vocabulary in RDF"
URL: http://www.w3.org/TR/2006/WD-HTTP-in-RDF-20061220/
Date: 2007-01-17
Status: 1st WD

-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
   QA Weblog - http://www.w3.org/QA/
      *** Be Strict To Be Cool ***

Received on Wednesday, 17 January 2007 03:09:06 UTC