W3C home > Mailing lists > Public > www-tag@w3.org > February 2009

RE: Question on the boundaries of content negotiation in the context of the Web of Data

From: Williams, Stuart (HP Labs, Bristol) <skw@hp.com>
Date: Fri, 13 Feb 2009 13:56:04 +0000
To: Ian Davis <me@iandavis.com>
CC: Michael Hausenblas <michael.hausenblas@deri.org>, "www-tag@w3.org" <www-tag@w3.org>
Message-ID: <233101CD2D78D64E8C6691E90030E5C8293C5894AF@GVW1120EXC.americas.hpqcorp.net>

________________________________
From: Ian Davis [mailto:me@iandavis.com]
Sent: 13 February 2009 13:01
To: Williams, Stuart (HP Labs, Bristol)
Cc: Michael Hausenblas; www-tag@w3.org
Subject: Re: Question on the boundaries of content negotiation in the context of the Web of Data


On Fri, Feb 13, 2009 at 12:24 PM, Williams, Stuart (HP Labs, Bristol) <skw@hp.com<mailto:skw@hp.com>> wrote:

Sure... but we're punning here on the word document (representation or resource sense). The bits that came over the wire are awww:representation of a graph and of an image that either depict or describe a common subject (a house), but neither graph nor the picture are that subject - and neither are their awww:representations awww:representations of the same thing... one is an awww:representation of a graph whilst the other is of a picture.


Would you agree that by that logic an SVG representation that reproduces exactly the pixels of the image cannot be used in content negotiation for that resource? The SVG document is a representation of an xml infoset

Ian

:-)

Nope...

You'll see from other messages in the thread that I there is a mention of a graph using some appropriately grounded vocabulary to encode the same image - in which case I could be persuaded that (at least for the purpose of rendering an image to a user) a turtle representation and PNG representation could be equivalent. Point is there can me be many different descriptions/depictions of the same thing - that what they describe or depict is the same doesn't make them the same. Things are also constrained such that any fragmentIds that resolve in multiple representations should be referring to the same thing regardless of representation - though not all frag Ids need to resolve in all representations [1]

Stuart
--
[1]  http://www.w3.org/TR/webarch/#media-type-fragid
Received on Friday, 13 February 2009 14:00:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:12 GMT