Great questions. Let me see if I can provide some insight. Taxonomy integration is metadata binding to your content at build time or at run time (dynamically). This timing depends on how you are delivery your content to your customers. Taxonomy integration gives you more options for your writers and your customers to find and use your content. It provides your customers with a unified experience when it comes to content. At a high level, here are some of the benefits that you could implement if you had taxonomy support:

• Navigation and discovery of your content - customer intuitive product groupings
• Search - indexing preferred terms, type ahead (classification driven recommendations), non-preferred terms
• Indirect implied tagging and late binding - tagging content with features that represent large data sets of products
• Contextual filtering - customer content is modeled and captured by the Ontology Semantics, content Conditional rendering using Taxonomy values/IDs, content rendered to the customer's specific product context and profile

What taxonomy does is coordinate the user experience. You gain classification, navigation, search, and controlled vocabulary in your content. KC 2016 was recently released so we have customers who are in process of evaluating its use and implementation.

What SDL has built in KC 2016 is a connector to the SmartLogic SES taxonomy system.