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

http://yorkporc.wordpress.com/2011/12/26/making-azure-web-role-host-a-foaf-card/ please run a debugger, and figure what sensitivity Im triggering. The graph now present on the mentioned endpoint is a variant of that documented, as I played another hour after writing up my failure case. My new graph is a a variant of Henrys foafssl card, rather than the minimal card in the spec. It still validates, but still cannot be read by either FCNS or FOAFSSL. FCNS hangs around before failing (as if timing out, when passing through teh URI collection in the cert), whereas FOAFSSL has a fast rejection. Once this works, Ill swap out the MVC3 project I built and substitute it with a Best Practices MVC3 site that leverage Azure STS (talking to openid). That will allow me to then properly expose something that has (a) claims-based patterns (b) semantic markup (c) can talk to a webid IDP (via openid auth protocol) using the Azure/ACS STS gateway.