- From: Lee Feigenbaum <lee@thefigtrees.net>
- Date: Fri, 06 Jun 2008 14:34:19 -0400
- To: Alan Ruttenberg <alanruttenberg@gmail.com>
- CC: Phil Archer <parcher@icra.org>, SWIG <semantic-web@w3.org>
Alan Ruttenberg wrote: > > I would think you do know the color. The 302 says the resource can be > found elsewhere for the moment. So it is supposed to be the same > resource. However, once the server stops responding with a 302 to this > address, or the caching information says it is stale, all bets are off. > -Alan I hope that's not the case. If 302 implies owl:sameAs then I can't make separate statements about two different URLs representing two formats of the same resource (I know I'm messing up the terminology here) accessed via content negotiation. <http://thefigtrees.net/id> a foaf:PerosnalProfileDocument . 302's based on Accept: headers to either http://thefigtrees.net/id.n3 http://thefigtrees.net/id.rdf What if I wanted to include an ex:mimeType triple about the latter ones? <http://thefigtrees.net/id.rdf> a foaf:PerosnalProfileDocument ; ex:mimeType "application/rdf+xml" . Or are you suggesting that this is some strange one-way equivalence? (If X -- 302 --> Y and X p q then Y p q?) Lee > > On Jun 6, 2008, at 4:57 AM, Phil Archer wrote: > >> >> Suppose I have this triple >> >> <http://example.org/> ex:colour "red" >> >> and when I dereference the URI I get a 302 redirect to >> http://www.example.org/home.asp. >> >> Do I know what colour http://www.example.org/home.asp is? >> >> I'm pretty sure the answer's no, but has anyone else grappled with the >> joys of redirects in this way? >> >> Phil. >> >> -- >> Phil Archer >> Chief Technical Officer, >> Family Online Safety Institute >> w. http://www.fosi.org/people/philarcher/ >> >> >> >> > > >
Received on Friday, 6 June 2008 18:35:01 UTC