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

[Peter Williams]

http://preview.tinyurl.com/y8elsac tested fine in Mozilla for windows.

it's a "client mediated" resource. You cannot talk to directly. You have to
click the download button.

The regime sucks in my view (and is an example of what I don't like about
the way similar regimes in the openid space are going, as the
mega-corporations running that movement impose their "governance practices"
as intermediaries to the resource).

Even if you are authenticated to the IDP (live.com), the interceptor
"client" still kicks in as a mandatory (interactive) guard. I don't know if
I subscribed to a for-fee plan if the URL would resolve directly. I stopped
paying for my MSN service in about 1998 as they could not get the PPP over
ATM tunnel to work reliably).

The windows server toolkit allows anyone to take the live.com websso
assertion and consume it on their (windows) website as an websso
authenticator, then providing any service they like. The live.com openid
service will work similarly (we are assured). This could be a simple webdav
content management system using webdav verbs. I just don't happen to know of
any that (a) showcase such websso, and (b) offer me no-fee storage and
no-fee bandwidth. I just don't want any more usernames/passwords...


http://en.wikipedia.org/wiki/404_error show how the 80:20 web works.
Apparently skydrive makes a reasonable use of 404 (judged against community
norms and customary practice).



-----Original Message-----
From: hjs at bblfish.net [mailto:hjs at bblfish.net] On Behalf Of Story Henry
Sent: Friday, January 22, 2010 12:44 AM
To: Peter Williams
Cc: foaf-protocols at lists.foaf-project.org
Subject: Re: [foaf-protocols] foaf.me with https, vs http

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=YnkxLnB2dC1zdG9yYWdlLmxpdmUuY29tKjEsMzYyMDA5MDA2Njg
5MTE0OTc2LDAs; 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).