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: Tue, 27 Dec 2011 14:14:02 -0800
Message-ID: <SNT143-W180A1FC098F79076AC5E6592AF0@phx.gbl>
To: <henry.story@bblfish.net>
CC: "public-xg-webid@w3.org" <public-xg-webid@w3.org>

Ive reached screaming point, despite it sort of working: See http://tinyurl.com/7zjf77v


It only works in what I assume are "advanced validators" - those able to deal with proxying. Which is not to say that the advanced validators can use my own data source (and validated against it). But, assuming Kingsleys system SOMEHOW cleans up my data source (and turns it into a linked data set), putting the proxy URI in the SAN alongside the URI does make something work, in some places, sometimes.


I think I learned something, about where webid will get too. ANd, now, I can at least SEE/CONTEMPLATE the full power of the linke data model (as it relates to just webid, never mind the rest). Its rather BETTER than the X.500 subobject/instancing model, particularly if such as Henrys validator can cast its query to suit the linked data view (of my data source).


What this means for security I dont know; as the traditional notions of authority have gone out of the window.


Received on Tuesday, 27 December 2011 22:14:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:39:50 UTC