A savvy web user might have a profile for:

Yahoo! 360

The above comprises a list of great websites, but I would make the argument that the people search component of those sites is weak, very weak. None of those sites claim to be people search sites and they do not need to be, but a good people search would certainly add a nice new set of capabilities.

PeopleTM.com hopes to be the glue for the social web by providing a killer search engine for people.

Databases also play a great role in people search, pure keyword searches for people is limited. You can’t type into a box, “people who went to the University of Florida who now live in New York” and expect it to make sense of your query, only a database that can intercept many properties and handle the complex relationships of peoples lives can return anything relevant.


I always say that before understanding comes utter confusion. Attempting to organize all the data on the web is certainly confusing. I hope in the future that PeopleTM.com will meet its goal of making sense of the massive amount of content on the web by allowing people to contribute to the classification and ranking of the information. But for now I see the people search component of PeopleTM as the most important and best place to start.

Note: When I refer to database architecture in this post I am referring to the industry standard relational architecture.

The challenge to secure online banking systems, led me to develop a new way of dealing with data, which in turn led to the Lanxer Database Architecture and the Lanxer Database Engine.

Having limited money and working out of an off campus apartment, I created my own prospect management system for my security product and business needs. The system was called Liquid and stored all my business contacts and data.  I would frequently change the system as my real word relationships were changing.  Eventually I worked out a new way of dealing with data that could adapt to the everyday changes of complex real world data relationships.

Real world relationships can become extremely complex and can grow and adapt every second.  Take a book for example, the book is written by an author, reviewed by critics bought by thousands of people.  Those copies of books are then passed on by friends and taken out in libraries.  Quotes from the book might appear on television or radio and the book could even be sighted as a reference in a research paper.  The relationships of a book are not static but changes every second.

Anybody familiar with relational database architecture knows that all the relationships must be mapped on the database side before the application can store data. The power of Liquid is to be able to handle theses dynamically changing relationships in an elegant manner. Eventually I adapted the concepts of Liquid into the Lanxer Database Architecture and the Lanxer Database Engine.

The database industry also recognizes the drawbacks of current database architectures. They are slowly adding capabilities to handle XML data along side tabular data.

I certainly do not expect the Lanxer Database Engine to be adapted by industry any time soon.  My potential objective for PeopleTM.com would be that people utilize the engine as a primary source for complex data management.  While in its Beta stage PeopleTM will continue to improve its search capabilities.