It's about The Concepts
The BeliefNetworks service is about discovering concepts locked within data such as unformatted text documents, HTML documents, Word documents, PDF files, RSS feeds and XML representations dumped from databases. Itï¿½s this simple idea, coupled with automation, which provides a foundation for your next-generation, intelligent web application.
The discovery of concepts is fundamental to the BeliefNetworks service. If you are familiar with search text discovery, then consider a starting point of "I'm a little teapot". This, in turn, is the basis for ï¿½Finding Not Searchingï¿½.ï¿½ Keywords, in this context, have no relevance.
However, that's just scratching the surface. Once DataChasm has mined a document for concepts, or conceptually mapped its concepts, the document becomes a resource for richer search features enabled in applications powered by BeliefNetworks. Up until now, conceptually mapped documents were the potential endpoints of a search scenario, that is, a document to be discovered. However, BeliefNetworks applies an interesting twist by making the conceptually mapped document also the starting point of a search. For example, a conceptually mapped document can be the target of the statement "Find me all documents that are like this document". And, as soon as you consider that documents don't have to be literally documents, that they can actually be unstructured information that represents anything in your domain, then the possibilities begin to multiply.
Finding Not SearchingTM
Imagine youï¿½re trying to find all documents related to a document about "The History of Military Aircraft" using a straight-up search appliance. First, you read the document closely, extracting the concepts you believe represent the essence of the document, and then you start a search with those concepts as search keywords. We've already seen an example of the subtle differences between discovery of search keywords and the discovery of higher-level conceptual meaning. What can you expect? You'll probably find a lot documents about camels, for starters.
With a BeliefNetworksï¿½ application, that last step might actually be as simple as "pushing a button". The action of that button would extract concepts that you would otherwise be forced to do manually, and then search for other documents that represent similar concepts. With a BeliefNetworksï¿½ application, if you started with a document on the History of Military Aircraft, you might get results ranging from World War Aircraft and Classic Aircraft to Lethal Aircraft. Bingo.
Recommendations based on what you know.
That was a discovery scenario. Let's think about a recommendation scenario. Suppose you are building an application, the premise of which is that you can provide value to a user base by matching pet owners to pet service providers (groomers, walkers, stables, supplies vendors, etc). Both pet owners and pet service providers can register in your system, but they are two separate groups that are managed separately by your application.
There are affinities between the two groups that, if discovered, may lead to greater user satisfaction with your service, good buzz, more customers, and ultimately higher profits for you. For instance, obviously you don't recommend a stable to someone looking for a kennel, but a person looking for a kennel for Roscoe for the weekend may have some particular likes and needs that can be matched to the right kennel with minimal effort for Roscoe's owner.
In this case, the "documents" scanned for concepts are pet owner profiles they freely enter at registration time describing themselves and their pets (with appropriate confidence the details won't be sold or revealed). Profiles would be fed, as created, into the conceptual mapper. Meanwhile, pet service providers would fill out some forms describing their offerings that ultimately could be rendered as XML documents. As you can see, there are a number of approaches for each major actor in your application.
Now, imagine a pet-services discovery service powered by BeliefNetworks. The conceptual information for all pet owners is mapped and placed into one silo, and likewise another silo of conceptual information is built for all pet service providers. Finally, we return to Roscoe's owner who pushes a button on the BeliefNetworksï¿½ powered application to start searching for recommendations in the pet services silo based upon the conceptual information gleaned from their owner's profile.
It could also work another way. Suppose you offer anonymous direct marketing, something that would inform pet owners of goods and services but would not expose their personal data to the service providers. This approach would not be as annoying as a phone call, but could be a message on their customer page linking them to the service provider that they can click on if theyï¿½re interested. Conversely, the pet service provider, interested in buying a batch of push marketing, pushes a button and your service discovers pet owners most likely to be interested in their products and services by asking BeliefNetworks to match the pet service provider's profile to the most conceptually relevant profiles of pet owners.
The DataChasmTM Service
Version 1.0 of BeliefNetworksï¿½ DataChasmï¿½ web service provides RESTful programmatic conceptual discovery against two large data repositories - The World Wide Web and Twitter. No additional effort is required on the part of the programmer other than to make the call. These two data repositories are most useful for interesting search applications and mashups. As an example, the MashMeUp web application illustrates the functionality of concept discovery with Twitter and web site recommendations.
The DataChasm web service also provides the means to build your own silos of conceptual information, closely tuned to your own application business needs. Once built, those silos become the foundation for recommendation features, that until now, you've only wished you could have.
But, to use the APIs properly, some conceptual information should be introduced (pun intended).
Concepts, Concepts, Concepts
We started with concepts, and now we return to them. Concepts are key to successful use of the DataChasm service. We like to think of concepts as information thumbnails (actually, we consider them a higher cognitive learning process, but that is another discussion). The habit of pushing simple keyword search, while actionable by the APIs, isnï¿½t as successful as starting with a document that expresses and represents the concepts you are interested in discovering. You'll find many APIs accept a generic "text" parameter. This may refer to as little or as much text as you need to represent your concepts, or it can refer to a fully qualified URL which points to a document or resource on the web (think article, publication, XML output from some other API) that encapsulates the concepts. For instance, you may have better results pointing to an article on The Cramps for a punk band search than simply the text "The Cramps".
A recommendation is the relationship between your starting point (text or URL) and the haystack of information with which you wish to establish an affinity with that starting point in order i to discover the ï¿½needlesï¿½, sorted for relevance. What BeliefNetworks believes to be the most relevant possibilities are returned first; if you wish, you can go deeper into the stack with successive queries. For instance, when you ask for recommendations from Twitter, you are returned ongoing conversations considered most relevant to your conceptual starting point. We like to call that ï¿½tweaningï¿½; in other words, bringing meaning to tweeting.
"Weight" is the term we use for the degree of relevance a recommendation has to your chosen starting point. You'll see various weights returned for recommendations, and you can build logic around this such as sorting, cut-off, etc.
Our custom APIs allows you to build applications against your own business data. You can define silos of information by business need, seed them and maintain them with resources, and then query them for recommendations, just like you can with our Twitter and Web APIs. This is a powerful tool that allows you to discover conceptual relationships of the highest relevance against between your own repositories of business data.
One Corpus, Many Corpora
The "Corpora" referred to by BeliefNetworksï¿½ APIs are your information silos. You create a corpus to hold the results of resources that are related by conceptual consistency. For example, if you were Amazon, one corpus might hold Books, while another might hold Reviewers. A resource list is typically provided at creation time. The corpus resources are subsequently managed and updated as resources come and go. Every 24 hours, DataChasm crawls any new resources for addition to, and removes all those marked for deletion from, your corpus.
Once a corpus is created, you may begin to query it for recommendations.
The following is a list of how-to and tutorial content that matched your search term. ProgrammableWeb's how-to content comes from two sources; full-blown tutorials that we publish ourselves and other highly relevant tutorials that we find elsewhere on the Web. This list represents on combination of both tutorial types and if you go to ProgrammableWeb's API University, you'll not only be able to find more, they are organized based on your role (API providers or developers who consumes APIs). If you know of a tutorial that would be of interest to the ProgrammableWeb community, we'd like to know about it. Be sure to check our guidelines for making contributions to ProgrammableWeb.