W3C home > Mailing lists > Public > semantic-web@w3.org > June 2010

Describing Images (and similar), and Descriptor discovery.

From: Nathan <nathan@webr3.org>
Date: Wed, 09 Jun 2010 14:01:32 +0100
Message-ID: <4C0F90AC.6040602@webr3.org>
To: Linked Data community <public-lod@w3.org>, Semantic Web <semantic-web@w3.org>
Hi All,

I'm just wondering what approaches people are taking to describing non 
rdf/html resources, such as Images, PDFs and similar?

Given that we have a jpeg with the URL http://example.org/image.jpg 
would we:

give it the Identifier <http://example.org/image.jpg#this> and serve an 
RDF description via conneg

give it the Identifer <http://example.org/image#this> and again serve an 
RDF description via conneg - a possible issue introduced here is if you 
have an alternative SVG version with it's own fragments(?) (SVGTINY12[1])

give it a completely different Identifier 
<http://example.org/r/132#image> and 'link' from the descriptor to the 
image with..? (dcterms:hasFormat, sioc:link, uri:uri, link:uri, other?)

and on the reverse, how about descriptor discovery for images/PDFs etc, 
expose via the Link header (tight coupling to HTTP), or?

As a side but related question, do we see the Web Of Data as running 
autonomous to the Web of Documents, as in it is taken that rdf / linked 
data clients will purely run over the web of linked data and reference 
non rdf resources via links with no backwards discovery needed, or is 
the link from web of documents back to web of data needed by any 
specific use cases? does conneg suffice? what if the image is 
<ftp://example.org/image.jpg>?

Best,

Nathan

[1] http://www.w3.org/TR/2008/REC-SVGTiny12-20081222
Received on Wednesday, 9 June 2010 13:02:33 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 21:45:36 GMT