Re: 303 redirect to a fragment ­ what should a linked data client do?

Christoph,
 
Are you aware of the respective HTTPbis ticket [1]?

Cheers,
      Michael

[1] http://trac.tools.ietf.org/wg/httpbis/trac/ticket/43

-- 
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: Christoph LANGE <ch.lange@jacobs-university.de>
> Organization: Jacobs University Bremen
> Date: Thu, 10 Jun 2010 13:40:42 +0200
> To: Linked Data community <public-lod@w3.org>
> Subject: 303 redirect to a fragment   ­ what should a linked data client do?
> Resent-From: Linked Data community <public-lod@w3.org>
> Resent-Date: Thu, 10 Jun 2010 11:40:31 +0000
> 
> Hi all,
> 
>   in our setup we are still somehow fighting with ill-conceived legacy URIs
> from the pre-LOD age.  We heavily make use of hash URIs there, so it could
> happen that a client, requesting http://example.org/foo#bar (thus actually
> requesting http://example.org/foo) gets redirected to
> http://example.org/baz#grr (note that I don't mean
> http://example.org/baz%23grr here, but really the un-escaped hash).  I
> observed that when serving such a result as XHTML, the browser (at least
> Firefox) scrolls to the #grr fragment of the resulting page.
> 
> But what should an RDF-aware client do?  I guess it should still look out for
> triples with the originally requested subject http://example.org/foo#bar, e.g.
> <rdf:Description rdf:about="http://example.org/foo#bar">, or (assuming
> xml:base="http://example.org/foo") for <rdf:Description rdf:ID="bar">.  Is my
> assumption right?
> 
> Thanks in advance for any help,
> 
> Christoph
> 
> -- 
> Christoph Lange, Jacobs Univ. Bremen, http://kwarc.info/clange, Skype duke4701

Received on Thursday, 10 June 2010 12:02:01 UTC