[foaf-protocols] foaf.me with https, vs http

[Story Henry]

The URL for your pdf does not seem to work:

$ curl -I http://cid-05061d4609325b60.skydrive.live.com/self.aspx/Public/Tying%20FOAF%20identity%20with%20the%20identity%20semantics%20of%20OpenID.pdf
HTTP/1.1 404 Not Found
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 19798
Content-Type: application/xhtml+xml; charset=utf-8
Expires: -1
Server: Microsoft-IIS/7.0
X-AspNetMvc-Version: 1.0
X-AspNet-Version: 2.0.50727
X-UA-Compatible: IE=7
Set-Cookie: mktstate=S=1935582920&U=&E=&P=&B=; domain=.live.com; path=/
Set-Cookie: mkt1=norm=; domain=.live.com; path=/
Set-Cookie: mkt2=ui=en-us; domain=skydrive.live.com; path=/
Set-Cookie: wlv=A|SDvx-t:a*_; domain=.live.com; path=/
Set-Cookie: _wlx_affinity_state_v4.0=YnkxLnB2dC1zdG9yYWdlLmxpdmUuY29tKjEsMzYyMDA5MDA2Njg5MTE0OTc2LDAs; domain=.live.com; expires=Fri, 29-Jan-2010 08:40:50 GMT; path=/
X-Powered-By: ASP.NET
Date: Fri, 22 Jan 2010 08:40:49 GMT

Perhaps a tinyurl would work better?

Henry

On 22 Jan 2010, at 03:13, Peter Williams wrote:

> 
> In
> http://cid-05061d4609325b60.skydrive.live.com/self.aspx/Public/Tying%20FOAF%
> 20identity%20with%20the%20identity%20semantics%20of%20OpenID.pdf page 6 we
> previous discussed how an RP might interact with an (openid) IDP not by
> redirecting simple messages by location header but by using sparql. I.e. the
> artifact binding would be sparql  protocol and customer queries (rather than
> using name value pairs or querystring values as a bearer for signals).