1) adding to the knowledge base

2) querying the available objects to see if you can add to it

.......

There is probably more to add but at the moment thats what I have. It is all very good to give us access to query the server with the api ... but without the ability to add to the knowledge base with our own I don't think the api would reach its true potential. One of the problems I believe you would face in building a knowledge base is having to create transforms for the sources of information already out there .... e.g. wikipedia .... Although that is a good thing it would also be good to create a way for the community to add their information to the TK base as it gets added .... for example if I was mysql I would want to support my community by extending search with NLP I would add mysql related objects to TK. The best way to do this would be to provide mysql with an api where they could add objects etc which are related to their product. The benefits to TK would be twofold ...

1) Growing your knowledge base as you would have a larger number of contributors

2) Gaining market share in the number of companies and communities which would use your search on their site.

if your api provides enhanced error information like ... "mysql does not exist .... could you please categorize it for me " add this to a review process which could be accessible through the api and the worldwide community would be able to help build rich datasets with greater ease.

Anyways ... long story short .... only having an api which lets you access the data and not contribute limits the value of the api both to TK and the end user.

I will continue to look for ideas to add to the api...