Jun

Abundance of Information Often is a Liability

A massive change has occurred in the world during the last ten to twenty years. Until recently and throughout the history of mankind information was hard to access. Obtaining and sharing information was either a laborious process or impossible, and the underlying assumption was that information can never be enough.

Today, of course, we have the opposite picture. Not only information is easily available, it keeps pouring in from a growing number of sources, and we continuously find ourselves in situations when there is more information than we want or able to process.

A major task we, as species, are facing is therefore how to reduce or filter out relevant information. It is, to repeat, in direct opposition to the task we’ve been accustomed to during all previous centuries, which was how to obtain information.

Since this change took place only recently, within a lifetime of one generation, we didn’t have time to develop efficient set of procedures to address the new problem. But the work has started and will only accelerate with time.

Interested in reading more? Check out our other blogs:

Microsoft AI products

                                                 

Microsoft product strategy has always been and still remains that of ‘zero alternative’. Their ultimate policy is for their customers to have no choice but to embrace only Microsoft products. Consequently they created and are offering products and solutions in (almost) every segment of IT enterprise and consumer market, including, but certainly not limited to, their own data base, their own cloud services, operating system, office tools, programming language, and many more.

Not only do Microsoft offer wide variety of products, they tie them up together in a unified ecosystem that makes it easy for components to connect and interact. At the same time, this ecosystem is hostile to non-Microsoft products.

Microsoft strategy for the burgeoning, fast growing AI segment is similar:

Create products to address all parts of the AI market, add them to the ecosystem to ensure easy compatibility from within and difficulty of use from outside.

Currently the products on offer are:

- Microsoft AI engine, called LUIS. It is supposed to compete with other major industrial AI systems such as IBM Watson, and has similar training methodology. It offers webhook interfacing via endpoints.  

- Microsoft chatbot building platform, called, surprisingly, Microsoft Bot Platform. It addresses the popular demand for easy chatbot design and provides seamless connectivity with main user interfaces, such as web interface, SMS, mobile, and messaging platforms.

- In addition Microsoft offers their own messaging platform in Skype.

The main advantage of  using Microsoft AI products is the built-in connectivity with user interfaces.

The main disadvantage is in their ‘zero alternative’ policy - once you’ve chosen a Microsoft product you are likely will be forced to choose only Microsoft products for the duration of your project.

 

READ MORE

Beware the lure of crowdsourced data

Crowdsourced data can often be inconsistent, messy or downright wrong 

We all like something for nothing, that’s why open source software is so popular. (It’s also why the Pirate  Bay exists). But sometimes things that seem too good to be true are just that. 

Repustate is in the text analytics game which means we needs lots and lots of data to model certain  characteristics of written text. We need common words, grammar constructs, human-annotated corpora  of text etc. to make our various language models work as quickly and as well as they do. 

We recently embarked on the next phase of our text analytics adventure: semantic analysis. Semantic  analysis the process of taking arbitrary text and assigning meaning to the individual, relevant components.  For example, being able to identify “apple” as a fruit in the sentence “I went apple picking yesterday” but to  identify “Apple’ the company when saying “I can’t wait for the new Apple product announcement” (note:  even though I used title case for the latter example, casing should not matter)

READ MORE