- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Wed, 21 Dec 2011 09:46:41 -0500
- To: public-xg-webid@w3.org
- Message-ID: <4EF1F151.6070000@openlinksw.com>
On 12/21/11 8:58 AM, Kingsley Idehen wrote: > Is a WebID verifier supposed to be a Linked Data consumer ? > Is a WebID verifier supposed to be an RDF consumer? > > Please understand that RDF != Linked Data. It's just one of the > options for creating and publishing Linked Data. > > In addition: > > Is a WebID verifier supposed to be an HTTP client? > Is a WebID verifier supposed to be able to leverage HTTP content > negotiation? > > Right now, WebID verifiers are very inconsistent re. the above, thus I > encourage we bring clarity to this very important manner. > > Remember, if we are going to tout WebID as leveraging Web > Architecture, we have to actually comply with said architecture. For the record, I am re-posting due to critical typo fix. I meant to say: Is a WebID verifier supposed to be a Linked Data consumer ? Is a WebID verifier supposed to be an RDF consumer? Please understand that RDF != Linked Data. It's just one of the options for creating and publishing Linked Data. In addition: Is a WebID verifier supposed to be an HTTP client? Is a WebID verifier supposed to be able to leverage HTTP content negotiation? Right now, WebID verifiers are very inconsistent re. the above, thus I encourage we bring clarity to this very important *matter*. Remember, if we are going to tout WebID as leveraging Web Architecture, we have to actually comply with said architecture. -- 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, 21 December 2011 14:47:09 UTC