- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Wed, 28 Dec 2011 13:05:24 -0500
- To: public-xg-webid@w3.org
- Message-ID: <4EFB5A64.80106@openlinksw.com>
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 claims. 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. -- 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
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Wednesday, 28 December 2011 18:05:51 UTC