W3C home > Mailing lists > Public > public-lod@w3.org > June 2010

Re: Describing Images (and similar), and Descriptor discovery.

From: Michael Hausenblas <michael.hausenblas@deri.org>
Date: Wed, 09 Jun 2010 14:31:40 +0100
To: <nathan@webr3.org>
CC: Linked Data community <public-lod@w3.org>, Semantic Web community <semantic-web@w3.org>
Message-ID: <C835564C.114C5%michael.hausenblas@deri.org>

Nathan,

>From the TAG, related, maybe helps you a bit [1].

Cheers,
      Michael

[1] http://lists.w3.org/Archives/Public/www-tag/2010Feb/0000.html

-- 
Dr. Michael Hausenblas
LiDRC - Linked Data Research Centre
DERI - Digital Enterprise Research Institute
NUIG - National University of Ireland, Galway
Ireland, Europe
Tel. +353 91 495730
http://linkeddata.deri.ie/
http://sw-app.org/about.html



> From: Nathan <nathan@webr3.org>
> Organization: webr3
> Reply-To: <nathan@webr3.org>
> Date: Wed, 09 Jun 2010 14:01:32 +0100
> To: Linked Data community <public-lod@w3.org>, Semantic Web community
> <semantic-web@w3.org>
> Subject: Describing Images (and similar), and Descriptor discovery.
> Resent-From: Linked Data community <public-lod@w3.org>
> Resent-Date: Wed, 09 Jun 2010 13:02:35 +0000
> 
> 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:32:27 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:27 UTC