- From: Richard Smith <richard@ex-parrot.com>
- Date: Wed, 12 Feb 2014 21:17:04 +0000 (GMT)
- To: Semantic Web <semantic-web@w3.org>
- Message-ID: <alpine.LRH.2.02.1402122100530.9417@sphinx.mythic-beasts.com>
Martynas Jusevičius wrote:
> HTTP Vocabulary in RDF 1.0?
>
> http://www.w3.org/TR/HTTP-in-RDF10/
I should have mentioned that I was aware of that. It's much
more a vocabulary for encoding whole HTTP messages, than for
metadata about the resource in the message body. So for
example, if <http://example.com/foo.jpg> is served with:
Content-Length: 514090
this translates to RDF as:
@prefix http: <http://www.w3.org/2011/http#> .
[ a http:Connection ;
http:connectionAuthority "example.com" ;
http:requests (
[ a http:Request ;
http:absolutePath "/foo.jpg" ;
http:headers (
[ a http:RequestHeader ;
http:hdrName
<http://www.w3.org/2011/http-headers#content-length> ;
http:fieldValue "514090" ] ) ] ) ] .
I dare say that has uses, but it's a long hugely
over-complicated for what I want.
I wondered whether it might be possible to extract from that
the following:
@prefix hdr: <http://www.w3.org/2011/http-headers#> .
<http://example.com/foo.jpg> hdr:content-length 514090 .
But it isn't, as hdr:content-length is declared an
http:HeaderName which is an rdfs:Class, not a subtype of
rdf:Property.
Richard
Received on Wednesday, 12 February 2014 21:17:27 UTC