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

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

From: Peter Williams <home_pw@msn.com>
Date: Fri, 30 Dec 2011 13:33:12 -0800
Message-ID: <snt0-eas8222C9E3A750CE7A9AAD8992920@phx.gbl>
To: Kingsley Idehen <kidehen@openlinksw.com>
CC: "public-xg-webid@w3.org" <public-xg-webid@w3.org>

Yes. And I ran into a second windows kernel limit. It enforces the http rfc, much like windows ssl enforces the pkix rfc re trust anchors.

Folks whin da Msft not doing standards. Now folks whine at Msft for doing what the standards say.

If webid at the validation agent should or must address "linked data nuances", I failed on 2 counts  (with native windows). The platform rigidly enforces the standards that prevent such nuancing (generally as they are attack vectors, being un spec'ed engineering).

Obviously once I built a socket listener, I dont have those issues. But neither do I have access to 500 man years of engineering know how...

All normal, as new requirements are identified and viewed as important enuf to induce ;slow) change in the baseline.

We have to show that unregistered self signed Certs and linked data nuances are really important, to justify such changes. The self signed cert falls right on the boundary of need, only important because it removes an old FBI/NSA/state/doc limit imposed on vendors, from a different crypto era.



> 
> Note, its now clear to me that Peter was attempting to implement a WebID verifier, and this modality sets him up for being responsible for URI de-reference and associated nuances re. Linked Data.
> 
> -- 
> 
> Regards,
> 
> Kingsley Idehen    
> Founder&  CEO
> OpenLink Software
> Company Web: http://www.openlinksw.com
> Personal Weblog: http://www.openlinksw.com/blog/~kidehen
> Twitter/Identi.ca handle: @kidehen
> Google+ Profile: https://plus.google.com/112399767740508618350/about
> LinkedIn Profile: http://www.linkedin.com/in/kidehen
> 
> 
> 
> 
> 
> 
Received on Friday, 30 December 2011 21:33:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 30 December 2011 21:33:56 GMT