Linking non-RDF resources to the content they contain

• From: Stuart Sierra <the.stuart.sierra@gmail.com>
• Date: Fri, 7 Nov 2008 11:21:43 -0500
• To: semantic-web@w3.org
• Message-ID: <314ee0450811070821p3c683bebk92fca12739ed7181@mail.gmail.com>

Hello, list!

I'm working on a custom web crawler that uses the "HTTP in RDF"
vocabulary <http://www.w3.org/TR/HTTP-in-RDF/> as its output format.

I have a question:  Suppose I download a file from
<http://example.com/some/file>.  It's not an RDF resource, just some
file of arbitrary bytes.  Using the HTTP in RDF vocab, I get something
like this:

<:response1> a <http:Response>;
        http:body <:body1> .
<:body1> a <cnt:Base64> ;
        cnt:bytes "qouh3908t38hohfrf..."^^xsd:base64Binary .

Now suppose I want to refer to the content of that file as a resource.
 Which would be more correct:
1. To define a new property, like <http://example.com/some/file>
hasContent <:body1>
2. To equate the two resources, like <http://example.com/some/file>
owl:sameAs <:body1>

The latter seems more logical to me, but is a resource "the same as"
its content?

Thanks,
Stuart Sierra

Received on Friday, 7 November 2008 16:52:44 UTC