RE: slow down and organize

Ive given up on the FOAF+SSL code I did last year. There is no point working
on code nobody maintains.

 

Despite blog posts, zip files, it had zero people use it (aside from folks
doing FOAF+SSL).

 

I used dotNet/Win32 so that the vb crowd could be excited. But, they are all
more interested in the Microsoft alternative to RDF and lambda functions for
expressing searches: ORM and linq/f#

 

Ive moved onto using gnutls in the posix mode of NT as my pgoramming
platform; it's good ol C code. It reduced the client cert part of webid
protocol to almost no work (like 2h.). Just missing the rdf/sparql part now.
Ideally, id just make a call to a service..

 

 

From: public-xg-webid-request@w3.org [mailto:public-xg-webid-request@w3.org]
On Behalf Of Henry Story
Sent: Saturday, February 26, 2011 5:01 AM
To: peter williams
Cc: 'WebID Incubator Group WG'
Subject: Re: slow down and organize

 

 

On 26 Feb 2011, at 13:25, peter williams wrote:





That's fine. And I tend to agree about standard's structure (protocol first,
interfaces second)

 

Can I **as an implementor** please have access to that service? (think
webby! It's what make things take off.). It only has to work in the most
common cases, 80% of the time.

 

Im in dotNet land, which has a dirth of rdf/rdfs libraries. I'd MUCH rather
consume a remote service doing all the rdf/rdfs/sparql related validation
agent steps, than link to the dotNet libraries I used last year for local
rdf/rdfs/sparql validation agent steps.

 

Yes, on the other hand it would be good to have an open source dot net
implementation that we can give people to improve. Did you write up your dot
net work somewhere? If not that would be useful. I am sure there are people
on this list who can help you. Just try for something light weight that
people can build on.

 

I will try embedding that foafssl.org service so that it can be a default
component of Clerezza, so that there are as many such endpoints around as
possible. You can then decide who to trust... SPARQL endpoints or whatever
will surely be possible at some point too.

 

Henry

 

Social Web Architect
http://bblfish.net/