Hi,
Am 10.06.2010 14:34, schrieb Nathan:
Christoph LANGE wrote:
2010-06-10 13:40 Christoph LANGE :
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
2010-06-10 14:01 Michael Hausenblas :
> Are you aware of the respective HTTPbis ticket [1]?
>
> [1] http://trac.tools.ietf.org/wg/httpbis/trac/ticket/43
Thanks, good to know – no, I didn't know that.
Cheers,
Christoph
--
Christoph Lange, Jacobs Univ. Bremen, http://kwarc.info/clange, Skype du
于 2010/6/11 5:41, Christoph LANGE 写道:
Hi Nathan,
thanks for your clarifying reply! That gave me the confirmation that we
were on the right track. Indeed I should not judge such issues from the
behavior of browsers that are not even RDF-aware.
During I was developing a PIM tool, I realiz
Hi Nathan,
thanks for your clarifying reply! That gave me the confirmation that we
were on the right track. Indeed I should not judge such issues from the
behavior of browsers that are not even RDF-aware.
Cheers,
Christoph
2010-06-10 14:24 Nathan :
> ...
>
> long:
> I've asked this questio
Christoph LANGE wrote:
2010-06-10 13:40 Christoph LANGE :
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 h
Christoph LANGE wrote:
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
, Galway
Ireland, Europe
Tel. +353 91 495730
http://linkeddata.deri.ie/
http://sw-app.org/about.html
> From: Christoph LANGE
> Organization: Jacobs University Bremen
> Date: Thu, 10 Jun 2010 13:40:42 +0200
> To: Linked Data community
> Subject: 303 redirect to a fragment what
2010-06-10 13:40 Christoph LANGE :
> 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/
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://exa
