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

Re: HTTP 200 instead of 303

From: Richard Cyganiak <richard@cyganiak.de>
Date: Fri, 5 Jun 2009 10:40:24 +0100
Cc: "public-lod@w3.org" <public-lod@w3.org>, Damian Steer <pldms@mac.com>, Andreas Radinger <andreas.radinger@unibw.de>, Kingsley Idehen <kidehen@openlinksw.com>
Message-Id: <DFFD9CCD-7C0E-4ADB-AE4B-799962D74BC2@cyganiak.de>
To: martin.hepp@ebusiness-unibw.org
Martin,

There's not enough context in your mail to really understand the  
situation. But Content-Location should be used when a content- 
negotiated URL is accessed, and it should give a URL for the specific  
variant that was chosen by the content-negotiation algorithm. For  
example, if </report> is available in plain text, PDF and HTML, and  
those three variants have the URLs </report.txt>, </report.pdf> and </ 
report.html>, and let's say an agent that prefers plain text accesses  
</report>, then the server should send the contents of </report.txt>,  
and should send a header "Content-Location: /report.txt" along with  
the response.

This is a recommended practice for content negotiation in general, and  
is orthogonal to any LOD issues.

Best,
Richard


On 5 Jun 2009, at 07:08, Martin Hepp (UniBW) wrote:

> Dear all,
>
> is this an acceptable practice from an LOD point of view or are  
> there technical concerns?
>
> Martin
>
> Damian Steer wrote:
>>
>> On 20 May 2009, at 18:54, Martin Hepp (UniBW) wrote:
>>
>>> Hi Damian:
>>> Thanks for your e-mail! I must admit that I don't get what exactly  
>>> you are proposing with
>>>
>>> <thought entertained="minimal">
>>> If the location header was set in the response I guess that might  
>>> help.
>>> </thought>
>>>
>>> Best
>>> Martin
>>
>> Hi Martin,
>>
>> Apologies. The perils of hasty emails :-)
>>
>> I meant setting the 'Content-Location' header, to indicate where  
>> the data came from. It's lighter than a redirect.
>>
>> Example:
>>
>> GET http://logs.jruby.org/jruby/latest
>> =>
>> HTTP/1.1 200 OK
>> ...
>> Content-Location: latest.txt
>>
>> Similarly you could try:
>>
>> GET http://openean.kaufkauf.net/id/EanUpc_0001067792600
>> =>
>> HTTP/1.1 200 OK
>> ...
>> Content-Location: EanUpc_range_xxxxxx
>>
>> GET http://openean.kaufkauf.net/id/EanUpc_0008811127923
>> =>
>> HTTP/1.1 200 OK
>> ...
>> Content-Location: EanUpc_range_xxxxxx
>>
>> Which seems like a reasonable way to indicate they have the same  
>> content.
>>
>> Damian
>>
>
> -- 
> --------------------------------------------------------------
> martin hepp
> e-business & web science research group
> universitaet der bundeswehr muenchen
>
> e-mail: mhepp@computer.org
> phone:  +49-(0)89-6004-4217
> fax:    +49-(0)89-6004-4620
> www:    http://www.unibw.de/ebusiness/ (group)
> 	http://www.heppnetz.de/ (personal)
> skype:  mfhepp
>
> Check out the GoodRelations vocabulary for E-Commerce on the Web of  
> Data!
> = 
> = 
> ======================================================================
>
> Webcast explaining the Web of Data for E-Commerce:
> -------------------------------------------------
> http://www.heppnetz.de/projects/goodrelations/webcast/
>
> Tool for registering your business:
> ----------------------------------
> http://www.ebusiness-unibw.org/tools/goodrelations-annotator/
>
> Overview article on Semantic Universe:
> -------------------------------------
> http://tinyurl.com/goodrelations-universe
>
> Project page and resources for developers:
> -----------------------------------------
> http://purl.org/goodrelations/
>
> Upcoming events:
> ---------------
> Full-day tutorial at ESWC 2009: The Web of Data for E-Commerce in  
> One Day: A Hands-on Introduction to the GoodRelations Ontology,  
> RDFa, and Yahoo! SearchMonkey
>
> http://www.eswc2009.org/program-menu/tutorials/70
>
> Talk at the Semantic Technology Conference 2009: Semantic Web-based  
> E-Commerce: The GoodRelations Ontology
> More information: http://www.semantic-conference.com/session/1881/
>
> Slides: http://tinyurl.com/semtech-hepp
>
>
> <martin_hepp.vcf>
Received on Friday, 5 June 2009 09:41:03 UTC

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