Re: Java Framework for Content Negotiation

Angelo,

> I might have a non-information resource http://example.org/resource/foo
> 
> I could place a REST-Webservice there and do content negotiation with
> @GET / @Produces Annotations. But this seems not correct to me, because
> it is a non-information resource and not a html or rdf/xml document. So
> it should never return html or rdf/xml but do a 303 redirect to an
> information resource instead, doesn't it?

This is a recurring pattern and people tend to confuse things (conneg and
303), in my experience. I assume you've read [1], already ? ;)

Without more detailed knowledge about what you want to achieve it is hard
for me to tell you anything beyond what has been discussed in various
forums.

Can you give me a more concrete description of your setup and goals? How
does your data look like? What's the task you try to solve? Etc.

Cheers,
      Michael

[1] http://www.w3.org/TR/cooluris/

-- 
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: Angelo Veltens <angelo.veltens@online.de>
> Date: Thu, 20 May 2010 14:38:53 +0200
> To: Linked Data community <public-lod@w3.org>
> Subject: Re: Java Framework for Content Negotiation
> Resent-From: Linked Data community <public-lod@w3.org>
> Resent-Date: Thu, 20 May 2010 12:39:34 +0000
> 
> On 20.05.2010 12:18, Michael Hausenblas wrote:
>>> There's also Jersey [1]  ...
>>>      
>> +1 to Jersey - had overall very good experience with it. If you want to have
>> a quick look (not saying it's beautiful/exciting, but might helps to
>> kick-start things) see [1] for my hacking with it.
>> 
>> Cheers,
>>        Michael
>> 
>> [1] http://bitbucket.org/mhausenblas/sparestfulql/
>>    
> 
> Mmh, i have been thinking about using REST-Webservice already, but there
> is one thing i'm quite unsteady with:
> 
> I might have a non-information resource http://example.org/resource/foo
> 
> I could place a REST-Webservice there and do content negotiation with
> @GET / @Produces Annotations. But this seems not correct to me, because
> it is a non-information resource and not a html or rdf/xml document. So
> it should never return html or rdf/xml but do a 303 redirect to an
> information resource instead, doesn't it?
> 
> Kind regards,
> Angelo
>

Received on Thursday, 20 May 2010 13:39:48 UTC