Semantic Proxy

It's been way to long ago. But I was invited to try SemanticProxy. ReadWriteWeb recently had a nice overview post on Semantic web applications and Calais was one of them. Calais is:

...a toolkit of products that enable users to incorporate semantic functionality within their blog, content management system, website or application.

Since launching the Open Calais API early this year, over 6,000 developers have registered with it and the service is doing more than 1 million transactions a day. We wrote about the launch of Calais' easiest-to-use service yet, called SemanticProxy, at the end of September. Version 3.0 was released earlier this month and version 4 is expected by January 09.

RWW verdict one year later: Calais has really blossomed over the past year and it is one of the most promising Semantic services around today. We can't wait to see what's next!

I finally had time to play around with SemanticProxy. I first tried the demo using the 'Knowledge Management' Wikipedia entry. The extraction of key phrases is impressive (also for the other entries I tried). It also categorizes the terms/phrases, distinguishing 'industry terms', 'technologies', etc. It didn't get the term in the 'organization' categorization right.

The demo is pretty limited (- it's beta, I know). I didn't go into the API stuff. But it's not hard to see this kind of smart functionality being useful in the near future. For instance, I'd love to use this semantic analysis to sifts through our internal document management systems, connect unconnected information together and build a network of information using tools like Semantic Proxy. I'm really curious if this will also work for the Web. Using this kind of technology inside the enterprise seems to be easier due to the limited data and term set.

Good luck, Semantic Proxy. I'll be following your steps and hope to experiment more internally with your tools as well. When I have results, I'll let you know.

Tags van Technorati: ,

Comments

Post a Comment

Please leave a comment! Just log in using one of the formats and if you want me to get back to you. Otherwise comment anonymously.

Popular posts

Keep the Intranet Small

Image
This tweet by Jonathan Phillips ( @digitaljonathan ) triggered to finalize this post, that's been burning in my draft box. I've always been intrigued by how unsuccessful many intranets are. And there are all kinds of good reasons for intranet failure. One of the things that is hardly ever mentioned is: Shouldn't the intranet be smaller? Usually intranets are huge. Lots and lots of pages with lots and lots of content. With complex navigation. The intranet  evaluation surveys almost always show employees only use the news page and people finder. But still we build and maintain nice big intranets. Not only stats point to smaller intranets. There are others reasons as well. I came up with a few. If you have more, just leave a comment. Here's my list: -            user requirements: users don't require large intranet -            search/navigation: searching and navigating a small intranet is easier than in a large intranet -            mobile: the content of the
Read more

Enterprise 2.0 Research

Image
There's not too much fundamental research on Enterprise 2.0. Deloitte recently published interesting research done on enterprise 2.0 implementations and their return-on-investment. In the EU research has also done as well. Study is being done for the European Commission and it was carried out by Tech4i2, IDC and Headshift. What was the goal of the study? Goals of the study To provide a clear definition of Enterprise 2.0 is, describe the market and the positioning of EU industry, also in comparison with US and Asia; To analyze the take-up of Enterprise 2.0, the organizational requirements, and the role on the transition to a knowledge based low-carbon economy; To collect evidence on its macro-economic impact, as a market opportunity for the European Software industry and as a productivity tool for European business; To identify and analyse both the direct and contextual challenges, including the need for Next Generation Access and the legal barriers; To analyse an
Read more

Innovation in Turbulent Times

Image
I love reading articles about innovation. And every now and then you read one that is very interesting. "Innovation in Turbulent Times" by Rigby, Gruver, Allen (in HBR, June 2009) is one of them. This article takes fashion companies as an example for continuous, year-by-year innovation. And how successful fashion companies are usually led by two people: a left-brainer and a right-brainer. "If you don't have highly creative people in positions of real authority, you won't get innovation. Most companies in other industries ignore this lesson." They extend this to show that successful non-fashion companies have the same kind of leadership. And this kind of leadership is usually also characterized by a long-term relationship. I think this concept can also be extended to teams and projects as well. More often than not, people are good at one or the other: thinking up great concepts or ideas, or, making them. In teams and projects we can learn from this as
Read more