- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 19 May 2014 09:48:11 -0400
- To: public-webid@w3.org
- Message-ID: <537A0B9B.4000805@openlinksw.com>
On 5/19/14 8:41 AM, Timothy Holborn wrote: > What (if any) are the barriers to updating the spec? The process. > Creating a version 2, perhaps starting with use-case scenarios (again?) > > Timh. > We certainly need interop testing across current implementations otherwise we'll just be vulnerable to speculative looping about what feasible vs whats infeasible. This remains one of the biggest problems with specs associated with Semantic Web related technology. Imagine a functional Linked Open Data cloud without DBpedia. We got DBpedia going on the basis of implementing something rather than being distracted by speculation. The Read-Write Web (RWW) dimension of the Web will only bootstrap by way of actual spec implementations and interop testing, combined with the discipline of not being distracted by speculation or cumbersome processes -- associated with spec construction and publication. BTW -- decoupling WebID-Profile from FOAF is a good thing too. That way, FOAF doesn't leak into what WebID, WebID-Profile, and Web-TLS are about. Ditto WebACLs. -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Monday, 19 May 2014 13:48:34 UTC