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: Kingsley Idehen <kidehen@openlinksw.com>
Date: Wed, 28 Dec 2011 13:05:24 -0500
Message-ID: <4EFB5A64.80106@openlinksw.com>
To: public-xg-webid@w3.org
On 12/28/11 12:37 AM, Peter Williams wrote:
> The built in openid server (that uses a webid challenge) is confusing. I dont know if the webids and profiles that it vouches for are limited to those in an ODS profile, in a proxy profile, or are for any other public webid (for which a proxy profile is immediately created).

The relations have to be reflected in the description graph. By default 
the WebID made by ODS is the primary subject of the description graph to 
which said WebID resolves.

If you want to make co-reference claims to other WebIDs, you can use the 
"synonym" feature of the ODS profile to make such claims which result in 
owl:sameAs relations. You can even use a variety of URI schemes in those 

ODS is about making a data space on a Network (e.g., InterWeb) where 
your WebID is a superkey .

We have an old 2000 cruddy UI (yes, that's how old ODS is) that is a 
distraction. That's being addressed. What isn't obvious though,  is the 
underlying support of REST patterns as an alternative interaction mechanism.



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 Wednesday, 28 December 2011 18:05:51 UTC

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