Re: neither FCNS nor FOAFSSL can read a new foaf card (hosted in Azure). RDFa validators at W3C and RDFachecker say its fine...

On 30 Dec 2011, at 18:28, Kingsley Idehen wrote:

> On 12/30/11 3:55 AM, Mo McRoberts wrote:
>> On 30 Dec 2011, at 02:08, Kingsley Idehen wrote:
>> 
>>> Yes, if you didn't perform the HTTP GET using IE with proxies in the mix. The problem is IE (and it seems) bits of Windows still sending Fragment Identifiers over the wires.
>> Under what circumstances does this happen? I’ve got IE behind a proxy (Squid) right here (standard BBC desktop build is IE8, Active Directory, no routable Internet access so everything goes through an HTTP or SOCKS proxy) — does it always happen when IE is behind a proxy and it's just the case that my proxy is filtering it out behind forwarding, or is it only certain kinds of proxy? …or am I misunderstanding?
>> 
>> M.
>> 
> Mo,
> 
> Here is one reference to this IE6 anomaly: http://jamespreston.co.uk/Articles/RedirectingIE6ToUrlWithFragmentIdentifier.html .
> 
> Remember, I said, this is why DBpedia ended up using slash URIs since the goal what for DBpedia to "just work" re. Linked Data exploitation from any browser.

Aha, thanks for the link — that's much clearer.

M.

-- 
Mo McRoberts - Technical Lead - The Space,
0141 422 6036 (Internal: 01-26036) - PGP key CEBCF03E,
Project Office: Room 7083, BBC Television Centre, London W12 7RJ

Received on Saturday, 31 December 2011 00:23:12 UTC