<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-4592106281625729711</id><updated>2012-02-16T07:37:22.571-05:00</updated><category term='Faceted Taxonomy'/><category term='Mapping'/><category term='Authorial Perspective'/><category term='Banyan'/><category term='HIPPA'/><category term='Solutions'/><category term='Starting'/><category term='video game'/><category term='Comparables'/><category term='parsing'/><category term='meta-terms'/><category term='Oracle'/><category term='Domain'/><category term='hiercarhy'/><category term='Trade Books'/><category term='social networking'/><category term='Taxonomy'/><category term='trees'/><category term='Synonyms'/><category term='Thesaurus'/><category term='Prioritization'/><category term='Software'/><category term='Diwali'/><category term='Query'/><category term='Concepts'/><category term='Hierarchical'/><category term='Classification'/><category term='Rules Sets'/><category term='Parent Child relationship'/><category term='multi-faceted taxonomy'/><category term='Cloud Computing'/><category term='Christmas'/><category term='Business Space'/><category term='Eid'/><category term='Auto-Classification'/><category term='Pecking Order'/><category term='Search'/><category term='Polyhierarchy'/><category term='Categorization'/><category term='multi-dimensional'/><category term='Winter Solstice'/><category term='Business'/><category term='Hanukkah'/><category term='Classes'/><category term='Microtargeting'/><category term='Saturnalia'/><category term='Evolution'/><category term='HIMS'/><category term='Multidimensional'/><category term='cross links'/><category term='NAICS'/><category term='Channel'/><category term='Mergers and Acquisitions'/><title type='text'>Business Taxonomy</title><subtitle type='html'>Follow the exploration on how to build a better taxonomy for business. I believe current taxonomies are currently lacking. Using a spatial concept of taxonomy, our team has built a taxonomy that is used to power research into Comparables for Mergers &amp;amp; Acquisitions in the evolving sector of Information, Software and Media, and I would like to share our thoughts on how to build a better taxonomy.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>23</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-5843041334470123189</id><published>2012-01-25T15:29:00.001-05:00</published><updated>2012-01-25T15:29:30.519-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Search'/><category scheme='http://www.blogger.com/atom/ns#' term='Auto-Classification'/><category scheme='http://www.blogger.com/atom/ns#' term='Comparables'/><category scheme='http://www.blogger.com/atom/ns#' term='parsing'/><category scheme='http://www.blogger.com/atom/ns#' term='multi-dimensional'/><category scheme='http://www.blogger.com/atom/ns#' term='meta-terms'/><title type='text'>Coining Phrases - Reverse Auto-Classification</title><content type='html'>Recently, I have been talking with some software folks who have created&amp;nbsp;parsers&amp;nbsp;for auto-classification. These engines will take a text or website, scan the contents and see how it matches to a given taxonomy. These parsers use a variety of techniques including statistics, semantics, word location to see how a given document matches a taxonomy. These are very impressive, and I hope to use one of these for our taxonomy to classify our content.&amp;nbsp;One of the unique traits of our taxonomy is that is multidimensional, and we use those dimensions to show the different ways that businesses operate in our economy. We have been able to leverage this to find buyers, sellers and comparables for Mergers and Acquisitions. One of the problems with this approach is that users who are searching our database need to have a fairly in depth knowledge of the taxonomy in order to find what they need. To solve this problem, we decided we needed to create meta-terms or coined phrases that would represent different search criteria to apply to our taxonomy. Instead of, going from &lt;i&gt;text &lt;/i&gt;to &lt;i&gt;taxonomy &lt;/i&gt;we are going from &lt;i&gt;taxonomy &lt;/i&gt;to &lt;i&gt;text&lt;/i&gt;.&amp;nbsp;We also use all the synonyms for all the nodes in our taxonomy. So instead of having users select their criteria from a series of drop-down boxes, they can type in a&amp;nbsp;Google-like text box and the software will auto-fill matches against the table of coined phrases generated from our taxonomy.&lt;br /&gt;&lt;br /&gt;I have a live sample on our MandAsoft site here:&amp;nbsp;&lt;a href="http://mandasoft.com/segments/searchlob.aspx"&gt;http://mandasoft.com/segments/searchlob.aspx&lt;/a&gt;. A good example is &lt;i&gt;accountant software&lt;/i&gt;&amp;nbsp;which is a coined phrase that will search for &lt;i&gt;software &lt;/i&gt;for &lt;i&gt;accountants&lt;/i&gt;. Here are the results for that search&amp;nbsp;&lt;a href="http://mandasoft.com/segmentview.aspx?SearchID=LOB99"&gt;http://mandasoft.com/segmentview.aspx?SearchID=LOB99&lt;/a&gt;.&lt;br /&gt;Tell me what you think.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-5843041334470123189?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/5843041334470123189/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2012/01/coining-phrases-reverse-auto.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/5843041334470123189'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/5843041334470123189'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2012/01/coining-phrases-reverse-auto.html' title='Coining Phrases - Reverse Auto-Classification'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-4800436083642885791</id><published>2012-01-17T13:28:00.001-05:00</published><updated>2012-01-17T13:38:08.152-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Auto-Classification'/><category scheme='http://www.blogger.com/atom/ns#' term='Evolution'/><category scheme='http://www.blogger.com/atom/ns#' term='Categorization'/><category scheme='http://www.blogger.com/atom/ns#' term='Taxonomy'/><title type='text'>Taxonomy Evolution Conundrum</title><content type='html'>Our team has been developing our taxonomy for almost ten years now. Our goal is to classify businesses by looking at how they operate, who they serve, and what they do, and our focus has been on media and software businesses. Needless to say over the last ten years, there have been major changes to the media and software industries with the introduction of smart phones, tablet computers, cloud computing, SaaS, virtualization, etc. To handle this evolution of the content we are classifying, we need to make sure our framework was solid and that the taxonomy could change with abilities to add nodes, merge nodes, link nodes, and to make sure our classifications migrated with the changes. However, change is never apparent when it happens. When we saw the first business operating in Social Networking, we originally had them classified basically as forums of user generated content, as opposed to editorial content. But as the business and technology took off, and showed itself to be a new business model, we realized we had to add the term &lt;i&gt;Social Networking&lt;/i&gt;&amp;nbsp;to our taxonomy. Now our problem was that we had to go back&amp;nbsp;and re-evaluate our companies that were classified as forums and see if they were really Social Networks. One way to fix this problem is to have an auto-classifier, and you set up a new set of rules to recognize &lt;i&gt;Social Networking.&lt;/i&gt;&amp;nbsp;Then &amp;nbsp;you re-run the auto-classifier on those companies. But here is the conundrum, we noticed this evolution in business models because we had human eyes seeing the trend. How can you expect an auto-classifier to see that? What are your thoughts on this problem?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-4800436083642885791?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/4800436083642885791/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2012/01/taxonomy-evolution-conundrum.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/4800436083642885791'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/4800436083642885791'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2012/01/taxonomy-evolution-conundrum.html' title='Taxonomy Evolution Conundrum'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-4369673906230323141</id><published>2012-01-09T14:29:00.000-05:00</published><updated>2012-01-09T14:29:47.640-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='social networking'/><category scheme='http://www.blogger.com/atom/ns#' term='Taxonomy'/><category scheme='http://www.blogger.com/atom/ns#' term='multi-dimensional'/><title type='text'>A Multi-Dimensional Quandary - Social Networking</title><content type='html'>Today our team had an interesting issue come up. As our taxonomy tries to model business, we try to keep on top of how business models evolve, and we find we have to reconsider terms and what they mean. The term that gave us pause today was &lt;i&gt;Social Networking. &lt;/i&gt;We use a multi-dimensional&amp;nbsp;taxonomy, where we have four distinct trees that model different aspects of a business and each one roughly answers the following questions: 1) who is the clientele of a business, 2) how does a company do business, 3) what problems does a business solve or subject area it specializes in, and 4) what channel does the business use to reach customers. So our problem was that we had&amp;nbsp;&lt;i&gt;Social Networking &lt;/i&gt;defined in our business solution tree, but then we found that &lt;i&gt;Social Networking &lt;/i&gt;started to morph&amp;nbsp;into something beyond Facebook, Twitter and LinkedIn. Shopping sites started to&amp;nbsp;incorporate&amp;nbsp;&lt;i&gt;Social Networking &lt;/i&gt;into their businesses, and then &lt;i&gt;Social Networking, &lt;/i&gt;no longer seemed like an "end: but a "means to an end". So our solution, which is far from the only solution was to add &lt;i&gt;social networking &lt;/i&gt;to our channel tree, where it sits along with &lt;i&gt;mobile &lt;/i&gt;and &lt;i&gt;online &lt;/i&gt;&amp;nbsp;terms. I hate having the same term in multiple trees, but the term is now used in multiple contexts, and we do have repeated terms for different contexts. What are your thoughts?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-4369673906230323141?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/4369673906230323141/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2012/01/multi-dimensional-quandary-social.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/4369673906230323141'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/4369673906230323141'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2012/01/multi-dimensional-quandary-social.html' title='A Multi-Dimensional Quandary - Social Networking'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-5545421335498765404</id><published>2012-01-05T15:40:00.001-05:00</published><updated>2012-01-05T15:41:02.484-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Classification'/><category scheme='http://www.blogger.com/atom/ns#' term='Categorization'/><category scheme='http://www.blogger.com/atom/ns#' term='Mapping'/><title type='text'>Taxonomy Mapping Engine in Use</title><content type='html'>Our team is in&lt;i&gt; Annual Trends Report&lt;/i&gt; Mode. Yesterday we published our first of seven Trends Reports tracking Mergers &amp;amp; Acquisitions in the Media and Software Sectors. This &lt;a href="http://www.berkerynoyes.com/publication/trend-report/2011/full-year/media.aspx"&gt;report&lt;/a&gt;&amp;nbsp;is for the media space. One part of the report is to collect the deals that for this space. We use an auto-population algorithm that fills the lists many times a day. We then use an &lt;i&gt;Industry Map&lt;/i&gt; and&lt;i&gt; rules set&lt;/i&gt; that maps the categorized deals into a simple flat taxonomy just used for this report. We can then compare sub-segments of the Sector to see which segments are performing better or worse. Note we do this for 7 different reports each with its own&lt;i&gt; Industry Map&lt;/i&gt; and&lt;i&gt; rules set.&lt;/i&gt; We never have to categorize a deal more than one time. The mapping engine puts the deals into the appropriate bins for that report. Check it out &lt;a href="http://www.berkerynoyes.com/publication/trend-report/2011/full-year/media.aspx"&gt;here&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-5545421335498765404?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/5545421335498765404/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2012/01/taxonomy-mapping-engine-in-use.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/5545421335498765404'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/5545421335498765404'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2012/01/taxonomy-mapping-engine-in-use.html' title='Taxonomy Mapping Engine in Use'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-1314612654443214850</id><published>2012-01-04T16:54:00.000-05:00</published><updated>2012-01-04T16:54:12.955-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Hierarchical'/><category scheme='http://www.blogger.com/atom/ns#' term='Classification'/><category scheme='http://www.blogger.com/atom/ns#' term='Taxonomy'/><category scheme='http://www.blogger.com/atom/ns#' term='Starting'/><title type='text'>Flying a Kite - Starting a Taxonomy</title><content type='html'>For Christmas, I got this wonderful book about the Brooklyn Bridge. It is called "The Great Bridge" by David McCullough. One part, he wrote about the first bridge to cross the Niagara Gorge built by Charles Ellet. The way Ellet started the bridge was to offer five dollars the first American boy who could fly a kite over to the Canadian side of the gorge. The bridge span was 1,010 feet, and young Homer Walsh won the prize. Ellet took the kite string that spanned the gorge, and tied successively heavier cords and pulled them across the gorge until he had a heavy cable spanning the gorge and from that he built his bridge.&lt;br /&gt;&lt;br /&gt;This story reminded me of our team's first efforts of building a business taxonomy. We started with a simple flat set of categories, and then added a second set of categories. After that we migrated to hierarchical trees, and then to banyans, and today we are ever adding features and complexity to our business taxonomy. But we could not have gotten to where we are today, unless we had first tried our first simple solution to span our own problem.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-1314612654443214850?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/1314612654443214850/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2012/01/flying-kite-starting-taxonomy.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/1314612654443214850'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/1314612654443214850'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2012/01/flying-kite-starting-taxonomy.html' title='Flying a Kite - Starting a Taxonomy'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-7658050754454844965</id><published>2011-12-23T15:22:00.001-05:00</published><updated>2011-12-23T15:22:48.131-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Eid'/><category scheme='http://www.blogger.com/atom/ns#' term='Hanukkah'/><category scheme='http://www.blogger.com/atom/ns#' term='Winter Solstice'/><category scheme='http://www.blogger.com/atom/ns#' term='Saturnalia'/><category scheme='http://www.blogger.com/atom/ns#' term='Christmas'/><category scheme='http://www.blogger.com/atom/ns#' term='Diwali'/><title type='text'>Winter Solstice Taxonomy</title><content type='html'>A friend of mine has his own business, and he recently had an interesting problem. He sent out to his client list a generic holiday email which did not mention Christmas or any specific holiday. One of the people who got the email replied very negatively about how Christmas is never mentioned specifically by name, and was very upset. My friend happens to have been raised by parents who come from two different religious traditions, and so he not surprisingly wants to wish everyone well. So how can his&amp;nbsp;dilemma be solved by Taxonomy? As I mentioned earlier our team uses multiple dimensions to classify businesses. He could create a taxonomy of holidays. For instance, you could have a category for the midwinter holiday, and you could code each instance to given religious audience: Christian, Jewish, Muslim, Hindu, Pagan, Agnostic, Atheist, etc. which would give us imagery and words for Christmas,&amp;nbsp;Hanukkah, Eid, Diwali, Saturnalia, Winter Solstice, etc. You could then continue this for the major fall, spring and summer holidays. My son's school, interestingly enough, only celebrates the equinoxes and solstices.&lt;br /&gt;&lt;br /&gt;In all seriousness, I wish you all a Happy New Year!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-7658050754454844965?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/7658050754454844965/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/winter-solstice-taxonomy.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/7658050754454844965'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/7658050754454844965'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/winter-solstice-taxonomy.html' title='Winter Solstice Taxonomy'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-87708147036318724</id><published>2011-12-21T16:02:00.001-05:00</published><updated>2011-12-21T16:23:38.473-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Auto-Classification'/><category scheme='http://www.blogger.com/atom/ns#' term='Classification'/><category scheme='http://www.blogger.com/atom/ns#' term='Thesaurus'/><title type='text'>Challenges of Classifying a Business</title><content type='html'>One of the biggest challenges our team has building a taxonomy of businesses is the actual classifying of a business. The process at best is semi-automated. Our classifiers generally have to look at the website of a given business and try to determine what they do. The website, generally speaking, is not written to describe how a business operates, but rather to sell the business's products and services. Each website has its own content, and we used to concentrate on the "About Us" page where the business defines itself.&amp;nbsp;Unfortunately, the "About Us" page is usually some sort of vague mission statement. We&amp;nbsp;even&amp;nbsp;looked at our own website, and found the wording written by our Marketing guy was so general that you would not know what we did! So our classifiers have learned to scan around many pages of a businesses site to learn what they do, how they do it and who they sell to. We have built some scrapers, but our results have been mediocre. We are now currently looking at ways to scrape company websites and intelligently gather info data to further automate the classification. The big problem we saw was that matching words on the website against words in our thesaurus gave us too many false positives. We are now looking at weighting the value of words in our thesaurus and how they matched in the past with verified classifications. Anyone explore these types of auto-classification.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-87708147036318724?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/87708147036318724/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/challenges-of-classifying-business.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/87708147036318724'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/87708147036318724'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/challenges-of-classifying-business.html' title='Challenges of Classifying a Business'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-7235284318933560883</id><published>2011-12-20T16:45:00.001-05:00</published><updated>2011-12-20T16:59:20.007-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Taxonomy'/><category scheme='http://www.blogger.com/atom/ns#' term='Concepts'/><category scheme='http://www.blogger.com/atom/ns#' term='Parent Child relationship'/><category scheme='http://www.blogger.com/atom/ns#' term='Classes'/><title type='text'>Classes versus Concepts Taxonomies</title><content type='html'>As I also post these entries on LinkedIn as well as other social media, sometimes a discussion will take off on one of the social media sites, and is not shown here on this blog. One of the most interesting responses to the &lt;a class="GMUUXGEDPB" href="http://businesstaxonomy.blogspot.com/2011/12/true-relationship-between-parent-and.html" kind="edit" style="border-bottom-width: 0px; border-color: initial; border-image: initial; border-left-width: 0px; border-right-width: 0px; border-style: initial; border-top-width: 0px; color: #1155cc; font-family: Arial, Helvetica, sans-serif; font-size: 13px; margin-bottom: 0px; margin-left: 0px; margin-right: 10px; margin-top: 0px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-left; text-decoration: none; vertical-align: baseline;"&gt;True relationship between parent and child&lt;/a&gt;post was on LinkedIn and covered what is the nature of nodes in one's taxonomy. Does each node represent a &lt;i&gt;class&lt;/i&gt; or a &lt;i&gt;concept&lt;/i&gt;? Denise B. of Kent State University raised this thought, and said that often one needs two taxonomies one where the nodes are &lt;i&gt;classes &lt;/i&gt;and another where the nodes are &lt;i&gt;concepts.&lt;/i&gt;&amp;nbsp;The nature of your taxonomy will then define the nature of the parent-child relationship. In a class based taxonomy, the child is a subclass of the parent where the child has all the kinds of attributes of the parent and then has some special attributes specific to the child class. With a concept based taxonomy, we would then see each node embodies a concept and hence the relationship to a child node is not so strict. Thanks to Denise on the response.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-7235284318933560883?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/7235284318933560883/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/classes-versus-concepts-taxonomies.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/7235284318933560883'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/7235284318933560883'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/classes-versus-concepts-taxonomies.html' title='Classes versus Concepts Taxonomies'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-5974867478153025789</id><published>2011-12-16T13:48:00.001-05:00</published><updated>2011-12-16T17:49:07.159-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Search'/><category scheme='http://www.blogger.com/atom/ns#' term='Taxonomy'/><category scheme='http://www.blogger.com/atom/ns#' term='Software'/><category scheme='http://www.blogger.com/atom/ns#' term='Parent Child relationship'/><category scheme='http://www.blogger.com/atom/ns#' term='Oracle'/><title type='text'>True relationship between parent and child</title><content type='html'>I recently had to make a change to our taxonomy search. Our previous search would match a selected node and all its children. However, we found a need to search and just match a node and not any of its child nodes. I have seen this feature in many other systems, but we never found the need to implement it in our system till recently. This highlights a deeper question of what do we expect the relationship between parent and child nodes. When we first developed our taxonomy, we had long heated discussions on this issue for our industry tree. Let's take an example of a well known software company, Oracle. Under our software category we have operating systems, business applications, desktop applications, database systems, email systems, graphics applications, etc. Oracle is a big software company that makes all kinds of software, but does not create all the types of software under our software category, but they do most. One of our team members suggested that if a company is categorized as something then it must do all the subcategories. His suggestion was to categorize multiple times for each type of product it does exactly. However, it starts get ugly when a company like Oracle is operating in most of the subcategories but not all. Our general consensus was to categorize a company in the parent category if it covers a good portion of the subcategories, but not all. If the company covers a few of the subcategories, then we will have multiple categorizations. The real key is consistency. We take the approach (and near cliche) that the parent is something different than the sum of its children. &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-5974867478153025789?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/5974867478153025789/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/true-relationship-between-parent-and.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/5974867478153025789'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/5974867478153025789'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/true-relationship-between-parent-and.html' title='True relationship between parent and child'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-8102306102369642718</id><published>2011-12-14T11:35:00.000-05:00</published><updated>2011-12-14T16:52:53.401-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Hierarchical'/><category scheme='http://www.blogger.com/atom/ns#' term='Classification'/><category scheme='http://www.blogger.com/atom/ns#' term='Business Space'/><category scheme='http://www.blogger.com/atom/ns#' term='Banyan'/><category scheme='http://www.blogger.com/atom/ns#' term='Polyhierarchy'/><title type='text'>Banyan provides an interesting view on our data.</title><content type='html'>The folks at &lt;a href="http://ongig.com/"&gt;Ongig.com&lt;/a&gt;, a new video enhanced job site, asked for some of our data to see who are the top 25 most efficient Tech companies based on profit per employee. The winner is SanDisk followed by Google and Apple.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://ongig.com/blog/wall-street/profit-per-employee-tech#more-1399"&gt;http://ongig.com/blog/wall-street/profit-per-employee-tech#more-1399&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;We were able to easily provide this because our chief taxonomist had created a top level node in our industry tree called &lt;i&gt;Information Technology &lt;/i&gt;which has child nodes for &lt;i&gt;Computer Manufacturers, Software Companies, Electronic Information, &lt;/i&gt;and &lt;i&gt;IT Consultants.&lt;/i&gt;&amp;nbsp;All these nodes have other parents elsewhere in the tree, but the Banyan helps pull it all together.&lt;br /&gt;&lt;br /&gt;I would also like to add a comment by Leo Meerman from LinkedIn. He mentioned that what I call a "Banyan Tree" is better known as a "Polyhierarchy".&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-8102306102369642718?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/8102306102369642718/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/banyan-provides-interesting-view-on-our.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/8102306102369642718'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/8102306102369642718'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/banyan-provides-interesting-view-on-our.html' title='Banyan provides an interesting view on our data.'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-4215101868740041971</id><published>2011-12-13T09:54:00.003-05:00</published><updated>2011-12-13T09:54:19.361-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Classification'/><category scheme='http://www.blogger.com/atom/ns#' term='video game'/><category scheme='http://www.blogger.com/atom/ns#' term='hiercarhy'/><category scheme='http://www.blogger.com/atom/ns#' term='Categorization'/><category scheme='http://www.blogger.com/atom/ns#' term='trees'/><category scheme='http://www.blogger.com/atom/ns#' term='cross links'/><category scheme='http://www.blogger.com/atom/ns#' term='Banyan'/><title type='text'>The Banyan Tree - a new hierarchy</title><content type='html'>&lt;div class="separator" style="clear: both; text-align: left;"&gt;Most taxonomies are set up in a hierarchical tree format. Our team consists of four distinct trees for each facet of how a business operates. Developing the taxonomy and software over the last 8 years, we found at some point that the tree structure became too strict. There were certain categories that did not want to be under just one parent category. A prime example of this situation is &lt;i&gt;video game&lt;/i&gt; companies. These companies make software for entertainment purposes. As this industry has matured, it has become closely link with the big entertainment companies, and they employ teams of artists, writers as well as programmers. Historically, these businesses should be software, but they are also so tied closely to entertainment companies it seems odd that when searching for entertainment companies that these would not turn up in our search results. One solution is to move &lt;i&gt;video game studios&lt;/i&gt;&amp;nbsp;to under the&amp;nbsp;&lt;i&gt;entertainment &lt;/i&gt;category,&amp;nbsp;but then we lose the &lt;i&gt;software &lt;/i&gt;aspect of the business. Our team's solution was to change the nature of our trees. We now allow nodes to have multiple parents, and create what I call the "Banyan" tree, which is a tree from India that has multiple trunks to the ground.&lt;i&gt;&amp;nbsp;&lt;/i&gt;&lt;/div&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://www.paradiseearth.com/Plant%20Articles/Banyan%20Tree.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="241" src="http://www.paradiseearth.com/Plant%20Articles/Banyan%20Tree.jpg" width="320" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;Looking at the&amp;nbsp;Wikipedia&amp;nbsp;&lt;a href="http://en.wikipedia.org/wiki/Banyan"&gt;article&lt;/a&gt;, we see that the banyan tree name comes from the Gujarti word for merchant, because merchant markets were often located under these great trees. It seems appropriate for a business taxonomy.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-4215101868740041971?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/4215101868740041971/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/banyan-tree-new-hierarchy.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/4215101868740041971'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/4215101868740041971'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/banyan-tree-new-hierarchy.html' title='The Banyan Tree - a new hierarchy'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-4114276578271275509</id><published>2011-12-12T09:26:00.001-05:00</published><updated>2011-12-12T09:53:01.529-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Search'/><category scheme='http://www.blogger.com/atom/ns#' term='Synonyms'/><category scheme='http://www.blogger.com/atom/ns#' term='Multidimensional'/><category scheme='http://www.blogger.com/atom/ns#' term='Categorization'/><category scheme='http://www.blogger.com/atom/ns#' term='Taxonomy'/><category scheme='http://www.blogger.com/atom/ns#' term='Query'/><category scheme='http://www.blogger.com/atom/ns#' term='meta-terms'/><category scheme='http://www.blogger.com/atom/ns#' term='Business Space'/><title type='text'>Challenges of Searching a Complex Taxonomy</title><content type='html'>As I have noted, our team has developed a very complex multi-faceted taxonomy which give a very exact categorization of any given business. The complexity we have created comes with a price. It creates challenges for users searching for businesses. A company is categorized by who their clientele is, what business needs they fulfill and by how they fill those needs, and what channels they use. A typical user does not think of businesses in such a manner. For instance, a typical search would be I would like all businesses that sell &lt;i&gt;education software&lt;/i&gt;. In early versions of our application, users would have to savvy enough to enter in the search criteria&amp;nbsp;&lt;i&gt;education &lt;/i&gt;for&amp;nbsp;the clientele and to enter&amp;nbsp;&lt;i&gt;software&lt;/i&gt; for industry (the "how a business operates"). Needless to say, users had to be trained to use the system, and hence the system was only used by our in house taxonomist who would get search requests and he would then give them results in a handy report. This was not ideal, because our taxonomist has many other things to do. The challenge for us was to make our taxonomy search as easy as Google. Nobody has to be trained to use Google, and we found that if training was involved generally that part of our application was not used unless the payback was great. In addition, since we were already fielding queries, our users found it much easier to send an email to our team, rather than run the search on their own. So how did we simplify our search. Well, in an earlier post, I mentioned we found that were phrases that users wanted in our taxonomy that would not fit in a single tree or dimension of our taxonomy. I called these phrases, "Meta-Terms". The example I gave was&amp;nbsp;&lt;i&gt;Trade Magazines &lt;/i&gt;which&amp;nbsp;are B2B magazines. In our taxonomy we then map this term to&amp;nbsp;&lt;i&gt;magazines&amp;nbsp;&lt;/i&gt;in our Industry tree and&amp;nbsp;&lt;i&gt;B2B&lt;/i&gt;&amp;nbsp;in our Clientele tree. So the key to simplifying our search was to use&amp;nbsp;"Meta-Terms" as a model for&amp;nbsp;Google&amp;nbsp;like search, Users can now type into a text box and it will see if it matches an existing "Meta-Term" or what I call an implicit "Meta-Term". Implicit "Meta-Terms" are created &amp;nbsp;by synthesizing synonyms from our different trees' vocabularies. There are over a million possible combinations from the trees, but some of the combinations are unlikely to exist like (&lt;i&gt;e-discovery software for teenagers&lt;/i&gt;). So we have created a list of synthesized terms from the companies we have already categorized (numbers around 23,000). From these categorized companies and all the synonyms, we get a list of about 200,000 implicit meta-terms. Our "Google" search box then matches the user input to our list of terms and runs a query on how that meta-term maps to our multiple dimensions. This is still in testing, but shows tremendous promise.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-4114276578271275509?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/4114276578271275509/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/challenges-of-searching-complex.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/4114276578271275509'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/4114276578271275509'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/challenges-of-searching-complex.html' title='Challenges of Searching a Complex Taxonomy'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-6372532680499556956</id><published>2011-12-09T09:09:00.001-05:00</published><updated>2011-12-09T09:29:32.802-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Taxonomy'/><category scheme='http://www.blogger.com/atom/ns#' term='Rules Sets'/><category scheme='http://www.blogger.com/atom/ns#' term='Mapping'/><category scheme='http://www.blogger.com/atom/ns#' term='Pecking Order'/><category scheme='http://www.blogger.com/atom/ns#' term='Prioritization'/><title type='text'>The Pecking Order - Rules Sets for Mapping</title><content type='html'>Continuing from the last post, let us look at how mapping from one taxonomy to another can be used. I had used the analogy of mapping rules sets as a camera where the rules sets will collapse the multi-dimension taxonomy to a single dimension taxonomy just as a camera takes a three dimensional space and collapses it to a two dimensional image. I also mentioned the the mapping rules in the rules set are prioritized. Going back to our camera, we know the objects in front will block objects in the back of our image. So with our taxonomy camera, mapping rules at the top of the order will override or block rules lower in the order. Now let us look around at how our businesses are run. Most businesses have a sales team. At our business, the sales team are managing directors and they do much more than just sales. Sales teams are given jurisdictions so as to keep them from stepping on each others toes. Depending on what a businesses product is, a business can define these sales jurisdictions by geography or by specialty based on domain knowledge. Taxonomies will not help define geographic sales territories, but if your business defines sales jurisdictions based on &lt;i&gt;what &lt;/i&gt;the clients are (as opposed to &lt;i&gt;where &lt;/i&gt;they are), you can use Mapping Rules Sets. Our team has defined a simplified taxonomy which describes the different practice groups, and then a mapping rules set that maps from our multi-dimensional taxonomy onto the simplified taxonomy. As anyone might know, the agreed upon rules for defining sales territories can be quite intricate and often contested, and using prioritized rules sets will help to define as broadly or narrowly any businesses sales territories. This pecking order of rules can be used to allocate leads to our sales teams in a consistent and efficient manner.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-6372532680499556956?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/6372532680499556956/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/pecking-order-rules-sets-for-mapping.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/6372532680499556956'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/6372532680499556956'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/pecking-order-rules-sets-for-mapping.html' title='The Pecking Order - Rules Sets for Mapping'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-8904974268414303791</id><published>2011-12-08T08:32:00.001-05:00</published><updated>2011-12-09T16:32:44.871-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Business'/><category scheme='http://www.blogger.com/atom/ns#' term='Multidimensional'/><category scheme='http://www.blogger.com/atom/ns#' term='Taxonomy'/><category scheme='http://www.blogger.com/atom/ns#' term='Mapping'/><category scheme='http://www.blogger.com/atom/ns#' term='Authorial Perspective'/><title type='text'>A One Way Street to Clarity and Simplicity - More on Mapping a taxonomy to a taxonomy</title><content type='html'>In my last post, I did not elaborate too much on rules sets that contain the logic to map from one space to another. These rules sets are interesting in that usually when you map from a complex multi-dimensional taxonomy space to a simpler domain specific taxonomy space it is a one way mapping. A good way to think of it is to think about how photography works. A camera has a lens that focuses an image of a three dimensional space onto a two dimensional piece of film. Needless to say, there is a loss of information when the camera takes a picture because the resulting image is just a single view of a three dimensional image. Can we recreate the three dimensional space from our two dimensional photo? Not really, though I have seen some software that guess. Nevertheless, we still love photography. I was just looking at my wedding pictures last night, and in a way photography gives us a clearer vision of our shared reality from an authorial viewpoint.Great portraits or landscapes captures a moment and gives it clarity.&lt;br /&gt;&lt;br /&gt;Let's get back to our idea of rules sets (our taxonomy camera), and how they map from&amp;nbsp;from a complex multi-dimensional taxonomy space to a simpler domain specific taxonomy space. We develop the simpler taxonomy to give us a perspective of a domain which gives us vision of clarity and simplicity. We use it to give an authorial view of certain business sectors in a way that our more general purpose taxonomy can not do.&lt;br /&gt;&lt;br /&gt;For those with a mathematical bent, I can say that our rules sets are prioritized rules and the fact that we have rules with greater priority than other rules makes these rules sets one way, and collapse the information to a simpler view. If we ran our rules sets on companies classified using the complex taxonomy to get the simpler classification, and then ran the rules sets in reverse on the simple taxonomy to get the categorizations in the complex taxonomy, the original complex classification will not be the same as the derived categorizations.&lt;br /&gt;&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-8904974268414303791?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/8904974268414303791/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/one-way-street-to-clarity-and.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/8904974268414303791'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/8904974268414303791'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/one-way-street-to-clarity-and.html' title='A One Way Street to Clarity and Simplicity - More on Mapping a taxonomy to a taxonomy'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-8122326901065201555</id><published>2011-12-07T14:30:00.001-05:00</published><updated>2011-12-07T15:08:48.795-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Mergers and Acquisitions'/><category scheme='http://www.blogger.com/atom/ns#' term='Business'/><category scheme='http://www.blogger.com/atom/ns#' term='Multidimensional'/><category scheme='http://www.blogger.com/atom/ns#' term='Taxonomy'/><category scheme='http://www.blogger.com/atom/ns#' term='Mapping'/><category scheme='http://www.blogger.com/atom/ns#' term='meta-terms'/><title type='text'>Mapping a taxonomy to a taxonomy</title><content type='html'>In my last post, I talked about "meta-terms" which mapped a commonly used expressions to nodes in multiple trees. This concept could be taken much further. When our team built our four dimensional taxonomy, our goal was to be able to classify any business, and to find similarities between companies even though traditionally they &amp;nbsp;would be considered to be operating in different arenas. My favorite example is to look at &lt;i&gt;Intuit &lt;/i&gt;which creates financial software for the consumer, and compare it to &lt;i&gt;H.R. Block&lt;/i&gt; which provides a financial services for consumers. In the tax arena, they both provide help to people doing their taxes, and compete directly. Our taxonomy categorizes Intuit as a &lt;i&gt;consumer software &lt;/i&gt;company for &lt;i&gt;taxes, &lt;/i&gt;while H.R. Block is a &lt;i&gt;consumer&lt;/i&gt; &lt;i&gt;service &lt;/i&gt;company for &lt;i&gt;taxes&lt;/i&gt;. As you see these companies overlap on what they do, and who they do it for, but not on &lt;b&gt;how &lt;/b&gt;they do it. Interestingly enough, Intuit started offering a professional help service and H.R. Block started offer a software package.&lt;br /&gt;&lt;br /&gt;What this brings up is that our taxonomy is complicated. Our team produces reports on Merger and Acquisition activity in a variety of segments (&lt;a href="http://mandasoft.com/"&gt;http://mandasoft.com&lt;/a&gt;), and each of these business segments like to break down using their own taxonomies specific to their domain. How do we reconcile the need for a taxonomy with nodes that can be used cross multiple domains, while needing to have easy to understand domain specific terms in a given domain? &amp;nbsp;The way I like to see this problem is that we have a vocabulary that works great when looking at the business world at the 50,000 foot level, but when we get down into trenches, the terms start to look vague and confusing at the lower altitudes. The way we solved this was by building a system to create 50 ft level simple taxonomies for specific domains (e.g. &lt;i&gt;healthcare media and software&lt;/i&gt;). We then categorize each business using the&amp;nbsp;50,000 foot level taxonomy, and we then have rules sets that map from 50,000 ft level taxonomy to the 50 ft level taxonomy. The utility is especially noted when we create multiple domains with their own rules sets&amp;nbsp;&amp;nbsp;(e.g.&amp;nbsp;&lt;i&gt;healthcare media and software&lt;/i&gt;, and&lt;i&gt; &amp;nbsp;Cloud Computing&lt;/i&gt;) and a business which may reside in both domains, only needs to be categorized once at the&amp;nbsp;50,000 ft level taxonomy. We can create as many domains as we need and not have to reclassify companies as our domain views evolve!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-8122326901065201555?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/8122326901065201555/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/mapping-taxonomy-to-taxonomy.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/8122326901065201555'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/8122326901065201555'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/mapping-taxonomy-to-taxonomy.html' title='Mapping a taxonomy to a taxonomy'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-1613952300738878681</id><published>2011-12-06T16:31:00.001-05:00</published><updated>2011-12-06T22:28:39.417-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Trade Books'/><category scheme='http://www.blogger.com/atom/ns#' term='multi-faceted taxonomy'/><category scheme='http://www.blogger.com/atom/ns#' term='HIMS'/><category scheme='http://www.blogger.com/atom/ns#' term='Synonyms'/><category scheme='http://www.blogger.com/atom/ns#' term='meta-terms'/><title type='text'>"Meta-terms" in a multi-faceted taxonomy</title><content type='html'>Most taxonomies have synonyms for their nodes. A good example may be if you have a node for &lt;i&gt;hospitals. Hospitals &lt;/i&gt;also could be known as &lt;i&gt;Medical Centers, Clinics, Surgery, Health Service&lt;/i&gt;, etc. These are the synonyms typical of any given taxonomy. In the&amp;nbsp;multi-faceted taxonomy, our team uses we have such synonyms, but sometimes we find certain key industry terms that actually span across multiple dimensions. For instance, &lt;i&gt;Trade Books, Trade Magazines, HIMS (Healthcare Information and Management Systems) &lt;/i&gt;are terms that can be like a synonym except, they point to nodes in multiple trees.&amp;nbsp;&lt;i&gt;Trade Books&amp;nbsp;&lt;/i&gt;are books for consumers. In our taxonomy we then map this term to&amp;nbsp;&lt;i&gt;books&amp;nbsp;&lt;/i&gt;in our Industry tree and&amp;nbsp;&lt;i&gt;consumer&lt;/i&gt;&amp;nbsp;in our Clientele tree.&amp;nbsp;&amp;nbsp;&lt;i&gt;Trade Magazines&amp;nbsp;&lt;/i&gt;are B2B magazines. In our taxonomy we then map this term to&amp;nbsp;&lt;i&gt;magazines&amp;nbsp;&lt;/i&gt;in our Industry tree and&amp;nbsp;&lt;i&gt;B2B&lt;/i&gt;&amp;nbsp;in our Clientele tree.&amp;nbsp;We call these special terms "Meta-terms", and they act as little mini-maps in our taxonomy, and expands our vocabulary like synonyms do. Later I will describe how we can build more complicated maps and rule sets to build mini-taxonomies that can use new sets of key words to define &amp;nbsp;new ontologies which set on top of our main taxonomy. &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-1613952300738878681?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/1613952300738878681/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/meta-terms-in-multi-faceted-taxonomy.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/1613952300738878681'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/1613952300738878681'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/meta-terms-in-multi-faceted-taxonomy.html' title='&amp;quot;Meta-terms&amp;quot; in a multi-faceted taxonomy'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-1656689680056020871</id><published>2011-12-05T09:08:00.001-05:00</published><updated>2011-12-05T12:42:37.849-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Multidimensional'/><category scheme='http://www.blogger.com/atom/ns#' term='Categorization'/><category scheme='http://www.blogger.com/atom/ns#' term='Taxonomy'/><category scheme='http://www.blogger.com/atom/ns#' term='Business Space'/><title type='text'>Spheres of Competition</title><content type='html'>Last week I spoke of looking at a business taxonomy in new way. Generally, people think of taxonomies as a vocabulary with perhaps a hierarchical structure of categories and sub-categories. However when you build a multi-dimensional taxonomy as our team has, you can now start to think of it as a spatial topology. There are four trees and each one defines a dimension in our business taxonomy space. This thought is analogous to the special theory of&amp;nbsp;relativity from&amp;nbsp;physics where you have the x, y, z dimensions plus the time dimension. An "event" is a point in the space time continuum is defined by those four dimensions. In our business taxonomy space, a "company" is a point in the spatial topology defined by our four dimensions. If you draw a small sphere around a given company's point in our taxonomy, you will get all the competitors of that company. We have seen as you widen the sphere the outlying companies are less likely to be competitors. The key to making this work is to define the distances between points in a given dimension's tree. We generally realize that the distance between parent and child is shorter the deeper you get into the tree, and the distance between siblings is slightly more than that between parent and child. We also realize that you may define siblings where some&amp;nbsp;siblings&amp;nbsp;are closer in meaning than others. Our distance&amp;nbsp;algorithm&amp;nbsp;has to take all these things into consideration. Our work has been experimental, but has returned interesting results. We have use this in our drill-down feature on &lt;a href="http://mandasoft.com/"&gt;mandasoft.com&lt;/a&gt;. &amp;nbsp;The space defined has to be tweaked, and I may leverage algorithms similar to Einstein's general relativity where actual data defining company revenue at a point in our topology could warp the spatial distances, just like physical mass warps physical space. Any thoughts?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-1656689680056020871?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/1656689680056020871/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/spheres-of-competition.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/1656689680056020871'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/1656689680056020871'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/spheres-of-competition.html' title='Spheres of Competition'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-4341871336838328942</id><published>2011-12-02T09:10:00.001-05:00</published><updated>2011-12-02T09:42:28.264-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Mergers and Acquisitions'/><category scheme='http://www.blogger.com/atom/ns#' term='Comparables'/><category scheme='http://www.blogger.com/atom/ns#' term='Categorization'/><category scheme='http://www.blogger.com/atom/ns#' term='NAICS'/><category scheme='http://www.blogger.com/atom/ns#' term='Faceted Taxonomy'/><category scheme='http://www.blogger.com/atom/ns#' term='Microtargeting'/><title type='text'>Why is a multi-dimensional faceted taxonomy better for Business?</title><content type='html'>&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;As we have seen, we can more closely describe a company and how they operate by using four different hierarchical trees to categorize their clientele, their methodologies, their solutions and their channels. This faceted taxonomy definitely gives us a better view of any particular business, but at what cost. &amp;nbsp;Our team has definitely found using this taxonomy has been challenging to categorize a given company. The taxonomist must research thoroughly a&amp;nbsp;given business, and then be able to abstract that understanding into the four different dimensions. Another challenge we found in our first search tool, was that the user using the search tool needed to understand how to abstract the kinds of businesses they were looking for into the four different dimensions. These two issues makes us wonder whether it is worth it. (Currently, we are working on software&amp;nbsp;algorithms&amp;nbsp;to make the search more user friendly and to make suggestions from web scraping to help the categorization.)&amp;nbsp;&lt;/span&gt;&lt;br /&gt;&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;We find it is worth it. The reason why is that, unlike NAICS codes, our taxonomy allows us to dig into micro-market views. NAICS is good for broad markets, but not for close views of a given market segment. Looking back to the 2004 Presidential Election, we see that President Bush's team was able to efficiently direct resources by using &lt;a href="http://en.wikipedia.org/wiki/Microtargeting"&gt;Microtargeting&lt;/a&gt;. The impetus of our taxonomy is Mergers &amp;amp; Acquisitions, and an important part of that process is valuation. To find the potential target company of an acquisition, investment bankers search for recent comparable deals. A task that is impossible using NAICS codes.&amp;nbsp;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;&amp;nbsp;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;With our taxonomy, we can do this.&lt;/span&gt;&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;&amp;nbsp;The reason is because we have moved away from the traditional way of viewing "Business" which is in terms of a vocabulary. &amp;nbsp;Instead, we now can view "Business" as a multi-dimensional space where we can define "Spheres of Competition" to determine "comparables". Stay tuned for more.&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-4341871336838328942?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/4341871336838328942/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/why-is-multi-dimensional-faceted.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/4341871336838328942'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/4341871336838328942'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/why-is-multi-dimensional-faceted.html' title='Why is a multi-dimensional faceted taxonomy better for Business?'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-2321865755330746936</id><published>2011-12-01T16:52:00.001-05:00</published><updated>2011-12-01T17:04:23.577-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Hierarchical'/><category scheme='http://www.blogger.com/atom/ns#' term='Multidimensional'/><category scheme='http://www.blogger.com/atom/ns#' term='Domain'/><category scheme='http://www.blogger.com/atom/ns#' term='Channel'/><category scheme='http://www.blogger.com/atom/ns#' term='Faceted Taxonomy'/><title type='text'>Requirements for a better Business Taxonomy Part 4</title><content type='html'>&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;My last post talked about how we can categorize a company in three different ways: &amp;nbsp;1) Who their customers or audience are. 2). How they serve their clientele. 3). What business need do they fulfill for their clientele. This is what I have heard called a faceted taxonomy. But I prefer it to be called a multidimensional taxonomy. Now we must ask ourselves are there anymore dimensions which could be useful. Our team has found one which is a little goofy. This is what I call the channel dimension. A company will provide a service, but with all these new means of reaching clients via mobile or internet. Maybe we can have a small domain which defines these different ways of reaching people. So for our example of &lt;i&gt;healthcare EMR software&lt;/i&gt;, this company could channel their services through licensed software installed at the client, or via a subscription of hosted software also known as Software as a Service (SaaS). Could anyone think of another useful dimension for a Business Taxonomy?&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-2321865755330746936?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/2321865755330746936/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/requirements-for-better-business.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/2321865755330746936'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/2321865755330746936'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/12/requirements-for-better-business.html' title='Requirements for a better Business Taxonomy Part 4'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-7384223938108057701</id><published>2011-11-30T14:22:00.000-05:00</published><updated>2011-11-30T14:22:02.429-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Search'/><category scheme='http://www.blogger.com/atom/ns#' term='Multidimensional'/><category scheme='http://www.blogger.com/atom/ns#' term='Taxonomy'/><category scheme='http://www.blogger.com/atom/ns#' term='Solutions'/><title type='text'>Requirements for a better Business Taxonomy Part 3</title><content type='html'>&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;Having discussed that we can have multiple&amp;nbsp;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;dimensions&amp;nbsp;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;for a detailed Business Taxonomy, lets see what&amp;nbsp;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;dimensions&amp;nbsp;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;we might want to have. The first two dimensions we discussed about described 1) Who is the company's clientele (for media we should look at the audience) 2)How the company services their clientele. I suggest we also give a dimension for 3)What business need the company accomplishes for their clientele. For instance, our hypothetical &lt;i&gt;healthcare software &lt;/i&gt;could accomplish a particular process. A big new push in &lt;i&gt;healthcare &lt;/i&gt;is &lt;i&gt;Electronic Medical Records (EMR)&lt;/i&gt;. If we have this third dimension, we can now classify a&lt;i&gt;&amp;nbsp;Healthcare&lt;/i&gt;&amp;nbsp;&lt;i&gt;Consulting &lt;/i&gt;company specializing in &lt;i&gt;EMR. &lt;/i&gt;Now, if we search for businesses providing &lt;i&gt;EMR &lt;/i&gt;solutions, we will get results for any company who are working in that space weather they are software or a consultant. Most taxonomies that "solve" this problem by searching on a mix of keywords and their tree structure. This third dimension gives a way to tie in companies that are working on related subjects but using different methodologies. Look at HR Block and Intuit. One is a service company and one is a software company, but both provide tax solutions. We will look at more dimensions in the next post.&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-7384223938108057701?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/7384223938108057701/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/11/requirements-for-better-business_30.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/7384223938108057701'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/7384223938108057701'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/11/requirements-for-better-business_30.html' title='Requirements for a better Business Taxonomy Part 3'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-9022612213452831113</id><published>2011-11-29T09:54:00.000-05:00</published><updated>2011-11-29T11:49:12.307-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Multidimensional'/><category scheme='http://www.blogger.com/atom/ns#' term='Categorization'/><category scheme='http://www.blogger.com/atom/ns#' term='Taxonomy'/><title type='text'>Requirements for a better Business Taxonomy Part 2</title><content type='html'>&lt;span class="Apple-style-span" style="font-family: Arial, Tahoma, Helvetica, FreeSans, sans-serif;"&gt;&lt;span class="Apple-style-span" style="line-height: 18px;"&gt;Following my previous post, we see that a business can be classified in a parent child hierarchical taxonomy, but sometimes one could create a sub-category which is really expressing a not a sub-type of the parent category, but rather a different aspect of the business. As in &lt;i&gt;healthcare software &lt;/i&gt;is not really a sub-category of &lt;i&gt;software&lt;/i&gt;. &lt;i&gt;Healthcare &lt;/i&gt;defines the customer base or subject matter of the &lt;i&gt;software&lt;/i&gt;. A true sub-type of&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;i style="font-family: Arial, Tahoma, Helvetica, FreeSans, sans-serif; line-height: 18px;"&gt;software &lt;/i&gt;&lt;span style="font-family: Arial, Tahoma, Helvetica, FreeSans, sans-serif; line-height: 18px;"&gt;would be &lt;i&gt;infrastructure software &lt;/i&gt;or &lt;i&gt;business application software.&lt;/i&gt;&amp;nbsp;An improved business taxonomy would then categorize a company in multiple ways or dimensions. For instance you could have, a dimension to describe the clientele or market that. So our&amp;nbsp;&lt;/span&gt;&lt;i style="font-family: Arial, Tahoma, Helvetica, FreeSans, sans-serif; line-height: 18px;"&gt;healthcare software&lt;/i&gt;&lt;span style="font-family: Arial, Tahoma, Helvetica, FreeSans, sans-serif; line-height: 18px;"&gt;&amp;nbsp;company would have its clientele be set to &lt;i&gt;healthcare.&lt;/i&gt;&amp;nbsp;Another dimension would describe how the company solves the business problems in the case of our&amp;nbsp;&lt;/span&gt;&lt;span style="font-family: Arial, Tahoma, Helvetica, FreeSans, sans-serif; line-height: 18px;"&gt;&amp;nbsp;&lt;/span&gt;&lt;i style="font-family: Arial, Tahoma, Helvetica, FreeSans, sans-serif; line-height: 18px;"&gt;healthcare software &lt;/i&gt;&lt;span style="font-family: Arial, Tahoma, Helvetica, FreeSans, sans-serif; line-height: 18px;"&gt;the company would be categorized as &lt;i&gt;software.&lt;/i&gt;&amp;nbsp;In my next post we will discuss other possible dimensions for a business taxonomy.&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-9022612213452831113?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/9022612213452831113/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/11/requirements-for-better-business_29.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/9022612213452831113'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/9022612213452831113'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/11/requirements-for-better-business_29.html' title='Requirements for a better Business Taxonomy Part 2'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-2331689832106341342</id><published>2011-11-28T09:26:00.000-05:00</published><updated>2011-11-28T09:26:33.455-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Hierarchical'/><category scheme='http://www.blogger.com/atom/ns#' term='HIPPA'/><category scheme='http://www.blogger.com/atom/ns#' term='Taxonomy'/><category scheme='http://www.blogger.com/atom/ns#' term='Cloud Computing'/><title type='text'>Requirements for a better Business Taxonomy Part 1</title><content type='html'>Most business taxonomies, I have seen, are hierarchical with parent and child relationships. A good example may be cloud computing. The term is new and kind of vague, but it can be divided into various sub categories like cloud computing hosting like Amazon Web Services or Microsoft Azure which will host virtual machines on the cloud, or cloud computing infrastructure services like cloud based backup services or antivirus services. However, if you see a cloud application that is specially oriented towards a given vertical like Healthcare which has special requirements like HIPPA, do you want to create a cloud subcategory for healthcare. What if there is a licensed software which manages Electronic Medical Records and is HIPPA compliant but does not run in the cloud. Do you create a subcategory for Healthcare under licensed software too? Then how do you find all the HIPPA compliant solutions? It seems that you need to categorize businesses in multiple ways. In effect, you should have a multi-dimensional hierarchical taxonomy to be able to better categorize and hence find businesses in any database. More on what these categories should be in my next post!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-2331689832106341342?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/2331689832106341342/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/11/requirements-for-better-business.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/2331689832106341342'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/2331689832106341342'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/11/requirements-for-better-business.html' title='Requirements for a better Business Taxonomy Part 1'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4592106281625729711.post-4299640241576163504</id><published>2011-11-23T10:53:00.000-05:00</published><updated>2011-11-23T10:53:21.444-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Classification'/><category scheme='http://www.blogger.com/atom/ns#' term='Business'/><category scheme='http://www.blogger.com/atom/ns#' term='NAICS'/><category scheme='http://www.blogger.com/atom/ns#' term='Taxonomy'/><title type='text'>Why the North American Industry Classification System (NAICS) is no good?</title><content type='html'>&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;When navigating a database of businesses, you need a taxonomy in order to find companies in an industry you are interested in. You would think that the NAICS would be ideal, however in practice none of the commercial databases use it. The reason is found on the US Census web site.&lt;/span&gt;&lt;br /&gt;&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;As stated on US Census web site, "The North American Industry Classification System (NAICS) is the standard used by Federal statistical agencies in classifying business establishments for the purpose of collecting, analyzing, and publishing statistical data related to the U.S. business economy." and "NAICS was developed under the auspices of the Office of Management and Budget (OMB), and adopted in 1997 to replace the &lt;a href="http://www.osha.gov/pls/imis/sic_manual.html" title="Standard Industrial Classification (SIC) system"&gt;Standard Industrial Classification (SIC) system&lt;/a&gt;. It was developed jointly by the &lt;a href="http://www.census.gov/eos/www/naics/development_partners/devpartners.html" title="U.S. Economic Classification Policy Committee (ECPC)"&gt;U.S. Economic Classification Policy Committee (ECPC)&lt;/a&gt;, &lt;a href="http://www.statcan.ca/english/concepts/industry.htm" title="Statistics Canada"&gt;Statistics Canada&lt;/a&gt; &lt;img alt="This link to a non-federal Web site does not imply endorsement of any particular product, company, or content." src="http://www.census.gov/eos/www/naics/img/offsite.gif" /&gt;, and Mexico's &lt;a href="http://www.inegi.org.mx/prod_serv/contenidos/espanol/biblioteca/Default.asp?accion=1&amp;amp;upc=702825023614&amp;amp;s=est&amp;amp;c=14680" title="Instituto Nacional de Estadistica y Geografia"&gt;Instituto Nacional de Estadistica y Geografia&lt;/a&gt; &lt;img alt="This link to a non-federal Web site does not imply endorsement of any particular product, company, or content." src="http://www.census.gov/eos/www/naics/img/offsite.gif" /&gt;, to allow for a high level of comparability in business statistics among the North American countries."&lt;/span&gt;&lt;br /&gt;&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;&lt;span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"&gt;The reason that it is not useful is that it is used to track broad trends. When you need to analyze business segments of our market you will see that a finer grained and richer taxonomy is needed. I have started this blog to explore this issue as my team and I continue to tackle the issues. Stay tuned.&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4592106281625729711-4299640241576163504?l=businesstaxonomy.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://businesstaxonomy.blogspot.com/feeds/4299640241576163504/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/11/why-north-american-industry.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/4299640241576163504'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4592106281625729711/posts/default/4299640241576163504'/><link rel='alternate' type='text/html' href='http://businesstaxonomy.blogspot.com/2011/11/why-north-american-industry.html' title='Why the North American Industry Classification System (NAICS) is no good?'/><author><name>Keith Lubell</name><uri>http://www.blogger.com/profile/15607292657392016011</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/-TPvre4liwLw/Ts0Te7ORlBI/AAAAAAAAALw/8lvJYh0-S8g/s220/PreWeddingDump%2B054.JPG'/></author><thr:total>0</thr:total></entry></feed>
