Why I should get a beta for Twine?
March 13, 2008
Nova Spivack asks the question and here is my response.
Readers of this blog know about my fascination with the structured, distributed web and open data, and the role the semantic web can play on that web. This fascination has reached a point where I ended up reversing a decision I made a few years ago about walking away from programming and honing my skills and knowledge in strategic concepts.
I have long felt that Twine occupies an important in the future of the Semantic Web. Unlike technology platforms like Freebase or Talis, Twine is an application that abstracts away the technology, an essential step in the widespread adoption of the Semantic Web. I have argued that in a perfect world, the end user does not really need know that they are functioning on the Semantic Web, but rather just feel the impact of a power powerful backend. However, in order for the developer (and investor) community to embrace that idea we need applications that are built on top of an RDF infrastructure and bring to people powerful functionality derived from the Semantic backend. Usability and functionality will be a key, and this is why so much rides on the success of Twine. It has mindshare, it has guns trained on it, and the last thing one wants is for Twine to fall into the Hype and Naysayers trap.
Plus, if I get into something (Lijit is an example), you won’t find too many people better to provide constructive criticism
Here are some recent posts about metadata, the Semantic Web and Twine
- Harnessing organizational intelligence
- The value of feature extraction
- Entity extraction
- Semantic Thoughts and Semantic Thoughts #2
Technorati Tags: Twine, Semantic Web, Nova Spivack



Add New Comment
Viewing 2 Comments
Thanks. Your comment is awaiting approval by a moderator.
Do you already have an account? Log in and claim this comment.
Do you already have an account? Log in and claim this comment.
Do you already have an account? Log in and claim this comment.
Add New Comment
Trackbacks
(Trackback URL)