Re: Property for linking from a graph to HTTP connection meta-data?

Dear Martin, All,

Just a reminder that you are looking at an old, outdated editors draft 
of the HTTP-in-RDF Vocabulary. The latest Public Working Draft is here:
  - <http://www.w3.org/TR/HTTP-in-RDF10/>

I seem to recall updates to the vocabulary that allow more flexibility 
to support uses as the one described below by Martin (though I did not 
check back specifically for that case).

Please note that the W3C/WAI Evaluation and Repair Tools Working Group 
welcomes comments and feedback on HTTP-in-RDF (despite the long passed 
deadline). Please send comments to <public-earl10-comments@w3.org>.

Best,
   Shadi


On 17.1.2011 20:23, Nathan wrote:
> William Waites wrote:
>> * [2011-01-17 16:39:27 +0100] Martin Hepp
>> <martin.hepp@ebusiness-unibw.org> écrit:
>>
>> ] Does anybody know of a standard property for linking a RDF graph to
>> a ] http:GetRequest, http:Connection, or http:Response instance? Maybe
>> ] rdfs:seeAlso (@TBL: ;- ))?
>>
>> If you suppose that the name of the graph is the same as the
>> request URI (it will not always be, of course) you can link
>> in the other direction from http:Request using http:requestURI.
>> I am not sure that http:requestURI has a standard inverse though.
>
> And remember of course, that the headers are split in to different
> groups which relate to different things, many relate to the message (in
> relation to the request), some relate to the server, some relate to the
> entity (an encoded version of the representation for messaging) a few
> (really not many) relate to the representation itself, and a couple
> relate to the resource itself, the resource being the thing the URI
> identifies.
>
> Best,
>
> Nathan
>
>

-- 
Shadi Abou-Zahra - http://www.w3.org/People/shadi/ |
   WAI International Program Office Activity Lead   |
  W3C Evaluation & Repair Tools Working Group Chair |

Received on Monday, 17 January 2011 20:23:10 UTC