W3C home > Mailing lists > Public > public-xg-webid@w3.org > April 2011

RE: payswarm, webid and javascript SSL.

From: peter williams <home_pw@msn.com>
Date: Tue, 26 Apr 2011 06:42:33 -0700
Message-ID: <SNT143-ds15D4FCD160B09247AB0D5492990@phx.gbl>
To: "'Henry Story'" <henry.story@bblfish.net>
CC: <public-xg-webid@w3.org>
I don't have any interest in open source dynamics. Typically, I modify other
code examples to show an integration, or show just one use case as vibrant
and useful. It removes technical barriers, or shows where windows is
lacking. It's a repeatable experiment, only. What can a visual basic
programmer accomplish? I showed that such a programmer  can add webid to
their firms' legacy web methods, for example - without having to sell the
semantic web first. With any

 

Try to remember windows was originally for small firms with self taught
programmers and it admins, not giant corporations. For $100 *you* get 80% of
what ibm provides to the giant firms with a 100 staff, all with a masters in
computing. For me its better than spending 60 on a linux book, to navigate
the morass of open source technologies.

 

It will be fun to do javascript ssl, and then see what ssl protocol tweaks
can influence payments. There were lots of ideas that didn't quite make it
in 2000, that today's tooling may now re-approach. The tool I have, for
example, is webid cert validation.a simple interface to the semweb world.

 

From: public-xg-webid-request@w3.org [mailto:public-xg-webid-request@w3.org]
On Behalf Of Henry Story
Sent: Monday, April 25, 2011 11:29 PM
To: peter williams
Cc: public-xg-webid@w3.org
Subject: Re: payswarm, webid and javascript SSL.

 

If you can, put up your code on some open source repository: github,
mercurial or such, and make the licence clear. That

will make it easier for people to help you out and contribute.

 

Henry

 

On 26 Apr 2011, at 07:15, peter williams wrote:





Having dominated what I need to know to applying WIF and modern websso on
windows and .NET 4.0 (and doing webid helped force the issues on certs,
consuming sparql, working with naming authority), I think I will move on in
terms of coding. The platform is stuck on 2000 era SSL, and is resisting
innovation with SSL. I need source (and GNUTLS is not mature enough for my
needs).

 

If anyone is interested in classical webid work, one might look further at
http://identity.thinktecture.com/stsce/docs/configuration/userMappings.confi
g.htm. Its an STS, with openid bridge, that does client certs for https too,
and addresses identity delegation. Sounds like a great platform on which to
build a more advanced webid prototype looking at the more involved flows,
including authorization lookups.

 

Im going to have a look at the micro-payments world again, assuming the
semantic web added something to the work done in 2001/2002 type period. This
will hopefully enable me to at least get the tool skills to build that
javascript ssl client library, and see how it can fit into the usual windows
eco-system of tools and cloud, etc. Hopefully, this can add something to the
final phase of this incubator, as it rounds out its "applicability and uses"
type of considerations. Getting a real client in javascript, with a UI and
trust stores built using javascript (not browser vendors) sounds like
nirvana!

 

Social Web Architect
http://bblfish.net/

 
Received on Tuesday, 26 April 2011 13:43:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:24 UTC