W3C home > Mailing lists > Public > www-tag@w3.org > August 2007

Re: ISSUE-57: The use of HTTP Redirection

From: Xiaoshu Wang <wangxiao@musc.edu>
Date: Mon, 27 Aug 2007 12:31:01 +0100
Message-ID: <46D2B5F5.9080604@musc.edu>
To: Ed Davies <edavies@nildram.co.uk>
CC: Technical Architecture Group WG <www-tag@w3.org>

> Two mechanisms spring to mind.  One would be to add a new
> method to HTTP, GET-META perhaps, which either returns the
> metadata directly or its URI. (I'm not sure whether it would
> be best: to allow one, the other or either.)  Another would
> be to add a standard response header (SeeAlso:, perhaps)
> which could be used with normal GET or HEAD methods and which
> would contain the URI of the metadata.  However, maybe
> there's a less intrusive way to get this effect.
I think a less intrusive way is to give the RDF mimetype representation 
(application/rdf+xml, text/rdf+n3,...) a unique status.  Because RDF 
document always talk about something-else. 

So, GET (rdf) http://example.com/

do not need to 303 re-direct because the nature of the resource should 
be understood by the machine from the returned document.  If there is a 
description about a non-information resource that is a non-RDF mimetype, 
then do a 303 upon the dereference of the resource. 

The only question is if there be any real-word use case that needs to 
talk about the RDF documents as a text file but not as a model.  I 
cannot think any reasonable senario but someone might.... 

Received on Monday, 27 August 2007 11:31:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:17 UTC