Information Panopticon

Home » Articles posted by Ahren E. Lehnert (Page 2)

Author Archives: Ahren E. Lehnert

Taxonomy Blues

https://pixabay.com/photos/background-blue-close-up-craft-3628553/

“I got to keep movin’, I got to keep movin’/Blues fallin’ down like hail, blues fallin’ down like hail/Hmm-mmm, blues fallin’ down like hail, blues fallin’ down like hail.” – Robert Johnson, Hellhound on My Trail

I was laid off recently from a taxonomy position I very much enjoyed. Rather than wait for the smart to wear off, the day after, I sat with a not insignificant IBU IPA and doubled down on the mixed emotions rattling through me to expound on some common issues I see in the work world of taxonomists. Many of these challenges I’ve dealt with in my blogs in one form or another in the past, but the day after a layoff hits a little differently when there’s a bruised ego and a true feeling of loss at play.

Like emails sent in the heat of the moment, posting a blog to social media hot on the heels of a personally emotional layoff is probably not the best idea. I’ve had nearly some time to let reality set in and revisit this writing. Surprisingly, I didn’t have to alter much of the content.

It’s Just Business

Layoffs happen. If you think your company loves you, you may have never been laid off. If it has never happened to you, then I am genuinely happy that you’ve not gone through the experience. Personally, I think it’s ok to believe in your company, drink the Kool-Aid (actually, it was grape Flavor Aid), and embrace their mission, goals, and strategy. I also think it’s natural and in the interest of self-preservation to recognize that any company will unceremoniously dispose of you when necessary. Their commitment to you will never match your commitment to their goals. Short of creating your own company and working for yourself building something you strongly believe in, this is always going to be the case. I enjoyed my company, believed in their mission, but also wasn’t one bit surprised when I got laid off.

From a detached, objective position, layoffs are as much a part of doing business as hiring when times are good. Layoffs can be triggered by downturns in which an organization’s revenue drops enough to merit reducing headcount. They can be triggered by well-meaning attempts at reducing redundancy and bloat. They can also be triggered by poor strategic decisions. Whatever spurs the layoffs, they are not always conducted in a strategic and thoughtful manner. Or, perhaps, there is a thoughtful strategy, but not one that will clearly bring about success.

No matter the impetus for a layoff, in my experience they disproportionately affect contractors and, because of what I can see immediately around me, taxonomists. There’s often an overlap between the two groups. When staff is augmented with consultant, freelance, or contract taxonomists, expect those people to be higher on the list when it comes to reducing headcount. The business likely doesn’t understand the role a taxonomist plays or minimizes the skill set as something anyone can do. As a seasoned taxonomist with years of consulting engagements behind me, I can tell you not everyone can just be a taxonomist. Like any proficient role, taxonomists bring unique organizational and research skills to bear. Shifting this work to the technology organization or a business domain in the enterprise is a misappropriation of work.

You’re a Taxo-what-now?

From years in the industry and still having not yet quite perfected my elevator pitch explaining my job, I can tell you taxonomy is not well understood. Cue the taxidermy jokes, financial tax questions, and, if you had the “ontologist” title, interrogations about whether you know anything about cancer. Speaking metaphorically, I do, and that is the metastasizing misunderstanding of what taxonomy, ontology, and semantic technologies bring to the table. Hence, taxonomists are not just laid off singly, but en masse, eradicating entire capabilities from organizations which likely had a long and painful path to establishing an enterprise taxonomy capability in the first place. With one swift slice of the oncologist’s scalpel, an entire function is excised with no idea of how to replace the missing connective tissue.

I’m sure many people think their job is extremely important, if for no other reason than it keeps one motivated to show up every morning. As part of justifying your work to yourself, and, more importantly, to the chain of command above you, there needs to be definitive and clear expressions of why the work is too critical to eliminate. Expressing the necessity of taxonomy work is essential precisely because it is misunderstood. Taxonomy work is often seen as simply gathering terms and putting them in lists or hierarchies, but the deep work of information science is frequently unseen. An inexperienced, self-nominated taxonomist is going to be at a loss when confronted by a dedicated, commercial off-the-shelf taxonomy and ontology system backed by a standards-compliant RDF triple store. That leaves the amateur with two options: do “taxonomy” in a simpler, alternative tool or establish a taxonomy capability in the organization starting with hiring a trained taxonomist to build the taxonomies and lead the effort to evaluate and purchase a taxonomy and ontology management system.

Having worked in many organizations which have gone from zero to taxonomy capability, it is no small task and can take anywhere from months to years. Taxonomists can start as contractors building taxonomies in spreadsheets and then either transition to a full-time role him or herself or lead the effort to hire a full-time taxonomist and bring in a tool. Regardless, the effort it takes to convince upper management of the need for a taxonomy program and the long journey to making it an essential part of the business involves a tremendous amount of time and resources. Establishing such a program and cutting it demonstrates a lack of understanding, an irresponsible waste of company resources, and a phenomenal strategic error, especially in the rising tide of machine learning and generative AI.

Foundations

It is widely understood and communicated that clear, accurate foundational data is essential for a business to create meaningful analytics, support strategic decisions, and train machine learning models properly. Despite the monumental efforts corporations put into building and maintaining clean data, it’s not all that common to see it done well. Typically, the issue is years of legacy data, all created with good intentions but frequently in conflict across disparate systems, inaccurate due to the passage of time, or made obsolete by shifts in strategic direction. To use a worn expression, there is no magic bullet to solve this problem. Migrating all that data to a data lake is time-consuming and still results in redundant, conflicting data. Creating taxonomies, ontologies, and tying data together with semantic layers and knowledge graphs also assists with creating and building foundational data, but these methods too can result in disparities.

There is no simple plug-and-play solution, but pursuing multiple strategies and bringing them together is not impossible. Data lakes serve a purpose, just as taxonomies and ontologies do. They are not either/or solutions, but AND solutions: structured, relational data working with structured semantic data and both describing semi- and unstructured content across the organization.You can have one strategy without the other…but why? There are realistic barriers to pursuing multiple data strategies, including budgets, resources, data ownership, and governance. Barriers do not preclude building strong capabilities to address these different aspects. Completely eliminating one or more of these pillars makes it more difficult for the business to execute a clear and effective data strategy, only to return to rebuild that capability at a later date at a not insignificant effort.

I’ll Be Back

There is a bitter vengeance tale in my head that goes something like this: you laid me off and now I’m back as a consultant making money from you to fix what you broke. Cyborg, guns blazing, blasting all your crappy taxonomies straight to hell. Well, not very likely, but I always win this one in my head (aside: does anyone ever lose the self-righteous conversations in their head?). Yeah, ok, so maybe I’m not back and may never be. Maybe the story runs more like someone either “discovers” that taxonomy is useful or stumbles on the skeletal, ancient remains of a discarded taxonomy management system half-buried in the earth, sorely out of date, and filled with the eggs of xenomorphs. Some face-hugger plants the seed of understanding in the astronaut and they decide the organization needs to do taxonomy stuff. Maybe someone listens and they hire dedicated roles to do taxonomy stuff. Taxonomy stuff takes off, becomes seemingly essential, and then taxonomy stuff gets stuffed in a round of layoffs. Maybe taxonomists are all just Cylons.

Anyway, bitter, wounded emotions aside, eliminating an enterprise taxonomy capability does your organization a disservice. Taxonomy is foundational to well-structured, semantic, governed data. Taxonomy data should be feeding your website navigation and search, applied as metadata to content, data, and digital assets, and providing a semantic layer to your products to power personalized experiences and recommendation engines. I’ll say it bluntly: if you don’t get taxonomy, you’ll never get machine learning. Or, rather, your machine learning models will never be optimized. If you think your generative AI proof of concept will run without taxonomy, it will…at first. Then, when scaling is the next step, expect it to fall on its face. Large language models without the context of your domain, your organization, what makes you you—that is, what is modeled in taxonomies and ontologies—will give you the bland, contextless results that can only be delivered by models that don’t get who you are. Taxonomists get who you are, but, well, they’re gone.

I said bitter, wounded emotions aside. Scrap that. I am very passionate and emotional about quality data. Nerd or no nerd, this is true. And your organizational truth is going to suffer without the expertise a semantic expert can deliver. You might say this is shameless self-promotion in search of the next gig, and you might be right. What is also right is that whether I’m the taxonomist hero who saves your disintegrating semantics or it’s another capable taxonomist, I’ll applaud the result. Because truth in data. Because waste and redundancy. Because efficiency. Because user experience. Because…

I’m not going to skewer the company that laid me off and dissect what I see as their poor strategic decisions. And, honestly, I don’t know what their strategy is or will be going forward. But, I will say this: I think it was a mistake. Not for me, not for the team I really admired and enjoyed working with, but for the greater strategy of the organization. Revenge tales aside, the company is going to feel the lack of governed, semantic data built by seasoned, professional taxonomists. There are people who remain in the organization who will carry the torch, but they’ve been hobbled by indiscriminate layoffs subjected to, unfortunately, a misguided data strategy. Maybe there are other options the company will pursue to fill the gap. Maybe taxonomy will come back someday when the stock prices are more favorable, but, in the meantime, no decent data strategy is complete without semantics.

I’ll close with a call to action to taxonomists. You already know how difficult it can be to build and maintain a taxonomy capability in your organization. Once established, make it essential. Make it foundational to data work wherever it happens. Integrate the taxonomy system into important, enterprise-wide data systems and strategies. No job is impervious to layoffs, but cementing the capability will, hopefully, help you avoid the taxonomy blues.

Friction and Complexity

https://pixabay.com/illustrations/spiral-fractal-template-abstract-1167623/

“Without culture there can be no growth; without exertion, no acquisition; without friction, no polish; without labor, no knowledge; without action, no progress and without conflict, no victory.” – Frederick Douglass, Self-Made Men

I attended the three day Information Architecture (IA) Conference in Philadelphia, Pennsylvania May 1st through 3rd. Over the course of the event, speakers covered numerous IA and UX topics. Of the many topics, two stood out to me both in frequency and in potential personal and professional application. Let’s consider friction and complexity through the lens of taxonomy and ontology practice.

Friction

Friction is an interesting phenomenon in that it is both to be avoided and embraced. Friction is undesirable in machinery, requiring lubricants to keep engines running and avoid heat buildup. Friction in relationships is unpleasant and is avoided through tactful word choice and conversation topic selection. The friction of a space capsule entering the earth’s atmosphere can incinerate it and friction on the rink can stop a skater in his or her tracks. On the other hand, friction between rubber tires and the surface of a road is what keeps motor vehicles from spinning in circles in wet or icy conditions. Friction between the head of match and the striker produces the heat necessary to ignite a flame. Friction in negotiations can potentially lead to a better end solution than either party would have thought of in an uncontested proposition.

User experience (UX) friction is typically to be avoided because it can prevent the user from achieving their desired outcome, whether that be finding information or completing a purchase. The goal of a UX designer is to minimize friction so the user can achieve his or her goals without frustration or task abandonment. Is there good friction in a user experience? In some cases, friction slows the user’s actions for a more thoughtful and productive outcome. Friction may help a user from going down an incorrect navigational path or line of inquiry resulting in unexpected or inaccurate results. The friction is built in to avoid more friction. As one of the speakers pointed out, friction can be a hindrance, but, applied correctly, it can be a help. Specifically, people need friction in order to learn.

The topic of friction resonates with me as a taxonomist because taxonomy needs to be thoughtful and deliberately slowed to maximize the long-term intent and outcomes. Frictionless keyword and tag creation seems like a fantastic idea in the democratization of making information findable. However, as tag clouds, folksonomies, and cumbersome repositories of user-generated tags can attest to, a little friction can prevent a lot of garbage. The nature of taxonomy work is one of calculated friction in the form of strict governance and maintenance processes. Users are not allowed to enter concepts directly into taxonomies and, if they are, the taxonomist’s job is to research the concept thoroughly before adding it permanently to the semantic structure. Governed friction slows the taxonomy creation process to ensure it is accurate, consistent, and serves as a definitive source of information for the organization.

Coincidentally, the topic of friction came up as a common theme in both our work when my wife was describing building redundancies into safety procedures. In her work as a safety specialist, she described the need for two safety hatches when closing an underground water tunnel for maintenance. A single hatch can fail and the workers could drown. With two hatches, one can fail, flood a chamber between the failed hatch and the next, and still allow time for the workers to get to safety while working behind the second hatch. A double safety redundancy is a form of friction. The obstacle between one potential point of failure and another creates a necessary friction which can save lives.

In taxonomy work, there are probably not as many examples in which the wrong taxonomy term can put lives at risk, though they do exist. Wrongly tagged content offered as medical advice can cause risk to a patient. Incorrectly identified drawings based on metadata can result in a manufacturing error. Machine learning models offering suggestions or identifying criminals based on training data tagged from taxonomies must be correct. For many of us creating taxonomies, there may not be the risk of lost lives, but there is probably some kind of risk to a company’s legal compliance or reputation.

In one of the presentations at the IA Conference, the speaker noted that the more friction there is in a system, the less people are likely to share information. We can see this in what can be characterized as the oversharing nature of social media. It is extremely easy to post text, pictures, and videos in any emotional (or inebriated) state of mind, resulting in an outpouring of information which should not necessarily be shared. The lack of friction makes it easy to share information, for better or for worse. Similarly, there is risk of creating too much friction in the taxonomy governance process, resulting in a reluctance to contribute to or use taxonomies. Users may seek out other options as a workaround; less friction, but inherently less quality. It is precisely this balance which must be discovered within an organization: how much friction will end users tolerate without abandoning the use of taxonomy altogether?

Complexity

I believe people gravitate to either/or solutions and black and white thinking because it reduces complexity. While reducing complexity to simple binaries helps us to understand and categorize the world more easily, it also creates a false embodiment of complex systems. Like friction, reducing complexity in user experience is generally a guiding principle. Finding and displaying information should not be complex. The user should be able to find what they need and understand the results quickly…and if not quickly, then efficiently. However, avoiding or obfuscating complexity can have unintended consequences. In one conference session, the speakers explored the use of storytelling to build awareness about complexity, specifically citing the work of Dave Snowden. Storytelling can be used to clarify the information coming from systems. Reducing complex problems to simpler components in order to better analyze or solve them is a good tactic, but there is risk if those components are analyzed or presented as isolated and independent rather than a part of a more complex and nuanced whole. 

My own presentation at the IA Conference also dealt with complexity (based on a blog I wrote on this topic, Specialty Skills and the Risks of Hidden Complexity), specifically the potential complexity of enterprise taxonomies and ontologies and how they can be displayed and consumed to maximum effect without overwhelming end users. Like having too much or too little friction, showing or hiding too much complexity in the form of taxonomies and ontologies can have several risks.

First, the user may not understand what is being presented and the intent behind it. Building taxonomies and ontologies can seem like an esoteric, academic approach to information management when users have to understand why taxonomies are structured the way they are, why they have strict governance procedures, and why complex semantic structures are useful. When all a user wants is a dropdown to select a few metadata values, providing a full set of faceted taxonomies can appear to be an overly engineered solution to a simple problem. Likewise, since fewer people in an organization have backgrounds in information science, the time spent carefully curating semantic models can seem to be a hindrance rather than a help, slowing the path to a deliverable project.

Second, users can be overwhelmed by the sheer scope of enterprise taxonomy models, especially as they mature to cover multiple domains within an organization. For example, if a user needs to apply metadata to data or content, a typeahead dropdown pulling from all possible concepts in a taxonomy will likely be too much for the user to select from. A consequence of this is that with more tagging options, there will be more tagging inconsistency. A complex set of taxonomies bound by a semantically rich ontology will benefit the organization, but presenting everything everywhere all at once will be a frustrating experience.

Finally, hiding complexity to make it easier for end users can have unintended consequences. Taxonomy work can seem simplistic, easy to do, and within reach of any business user. Being too good at hiding semantic complexity can result in users taking up the work themselves, leading to disparate efforts and data sources. Additionally, without a coordinated and governed effort, the “simplicity” of taxonomy work typically results in products which aren’t much better than user-generated keywords, filled with misspellings, variant concepts describing the same thing, a mix of full concepts and acronyms, and a host of other inconsistencies. By hiding complexity, non-practitioners may believe taxonomy construction is easy and quick to complete.

Like calculated friction, it may be beneficial to find a path toward calculated complexity. Determine which user experiences require simple dropdown selections and which may benefit from displaying the entire taxonomy framework, either as a hierarchy or as a visualized graph showing all components of the structure. Somewhere between these two lies a spectrum of user experience options combining simple flat lists, hierarchies, tabbed information displays, graphical representations, hover menus, and a plethora of other displays which are fit-for-purpose to the user goals. Revealing complexity, where appropriate, can expose the range of domain coverage, but also the possibilities that semantic models can offer.

Friction and Complexity

Communicating the value and guiding principles of semantic models and their supporting technologies can be extremely difficult in an enterprise. There are many ways to solve business problems and making the case for what semantic technologies can do, the use cases to which they can be applied, and the advantages they bring can be challenging for taxonomists and ontologists to convey. Considering the nuanced balance between friction and flow, complexity and simplicity, can have application to user experiences and the way we present taxonomies and ontologies to end users. In turn, thoughtful presentations providing the correct amount of friction and complexity can influence adoption across the organization.

Nobody’s Alt but Mine

https://pixabay.com/vectors/creative-commons-derivatives-785336/

“A good ruler has to learn his world’s language, and that’s different for every world, the language you don’t hear just with your ears.” – Frank Herbert, Dune

Synonymy

Synonyms are “one of two or more words or expressions of the same language that have the same or nearly the same meaning in some or all senses” (Merriam-Webster). We can define synonyms when building taxonomies using the skos:altLabel field from semantic standards created by the W3C. The W3C defines skos:altLabel as “an alternative lexical label for a resource”, which, using the same words in the definition as in the label, isn’t as helpful as their example: “acronyms, abbreviations, spelling variants, and irregular plural/singular forms may be included among the alternative labels for a concept. Mis-spelled terms are normally included as hidden labels (see skos:hiddenLabel)” (W3C).

Synonymous concepts are part of what make taxonomies complete, clear, and demonstrate a consideration for each selected concept distinguishing between the chosen preferred label, the possible other languages for that preferred label, and other possible options which can be captured in the altLabel field. English may or may not have the most synonyms, but it certainly has many:

“The richness of the English vocabulary and the wealth of available synonyms means that English speakers can often draw shades of distinction unavailable to non-English speakers. Modern English has an unusually large number of synonyms or near-synonyms, mainly because of the influence of very different language groups: Germanic (Anglo-Saxon and Old Norse, the main basis of English), Romance languages (Latin, French), and Greek. There are many sets of triplet synonyms from Anglo-Saxon/Latin/Greek and also Anglo-Saxon/Norman French/Latin-Greek like cool-calm-collected and foretell-predict-prophesy” (Why other languages don’t use thesauruses like we do).

Synonymy is not as cut and dried as it would seem. Let’s consider the use of the skos:altLabel in practice.

ALTruism

According to the W3C, the altLabel field can, by definition, include acronyms, abbreviations, spelling variants, and even irregular plural or singular forms. If we use the “out of the box” set of SKOS labels, it simplifies the structural encoding of taxonomies and reduces the number of properties we need to maintain and manage. However, just as synonyms aren’t purely objective, there are a few disadvantages and risks involved with only using the skos:altLabel. First, the nuanced differences between acronyms, abbreviations, and spelling variants is lost. Second, the ability to separate these nuanced differences in systems consuming altLabels from a taxonomy and ontology management system becomes difficult, if not impossible. Finally, taxonomy consumers or viewers may or may not know what an altLabel is, what it includes, or why the values they are seeing in that field seem to differ.

Defining separate, clearly named taxonomy properties defined by the skos:altLabel type may help to solve this problem. Let’s consider a few examples.

Synonyms

Using the skos:altLabel field type but naming it synonym can make it clear for end users what values to expect. A field like this could include “true” synonyms like “shoelace” and “shoestring” and synonyms which an organization defines for their domain, like “footwear” and “shoes”. These are not truly synonymous, but for an organization which sells footwear of all types, they might be.

Acronyms

Acronyms may be a clearer example since an acronym is more narrowly defined. Even here, it depends on the taxonomy use case, altruistically considering the audience. One organization may use the preferred label “deoxyribonucleic acid” while another organization may use the preferred label “DNA”. In either case, defining shades of skos:altLabel can help. In one instance, “deoxyribonucleic acid”” is the preferred term while “DNA” is included in the acronym field. In the other instance, “DNA” is the preferred label while “deoxyribonucleic acid” is in the synonym field. Using fields in this way very clearly expresses the organization’s viewpoint on how they approach the domain.

Abbreviations

Using skos:altLabel as an abbreviation field also sets expectations for what is included. I live in California, and when I abbreviate the state name, I use “CA”. I remember, however, using longer state name abbreviations when I was younger (which is interesting, because the U.S. Post Office officially switched to two letters in 1963…and, well, I’m a little younger than that). In this case, we could include all of the historical abbreviations “Cal.”, “Calif.”, and “CALIF” in the abbreviations field.

Historical Label

If we want to add even more nuance in naming a skos:altLabel field, we could include something like historical label, more or less paralleling the skos:historyNote field. Using another California example, the historical label field could include “Oakland Raiders” and “Los Angeles Raiders” for the team “Las Vegas Raiders”. These terms are really synonymous, but we’ve added another layer of clarity by adding a time element. If a taxonomy and ontology system supports adding metadata to properties and relationships, you could use the synonym field and add date ranges for when the team was active with each name: “Oakland Raiders” (1960-1981, 1995-2019) and “Los Angeles Raiders” (1982-1994) with the option to add an open date range to “Las Vegas Raiders” or no date range at all.

Spelling Variants

The use of skos:altLabel for spelling variants is dependent on your use case, in my opinion. For taxonomies supporting search, it may be valuable to define a field called spelling variant. Likewise, despite W3C’s recommendation, there could be another field called misspellings. However, in practical application, maintaining spelling variants and misspellings is the work of the front-end search system, not the taxonomy. How you architect your taxonomy to support search may be a matter of your organization’s technical environment, so do what’s best for your use case.

Another Word for Thesaurus

You’ve probably heard the old joke, “What’s another word for thesaurus?” Well, the slippery nature of language is on display in that the Merriam-Webster online dictionary provides seven “Synonyms & Similar Words” for “thesaurus”. So, the answer is: dictionary, gloss, glossary, lexicon, nomenclature, vocabulary, or workbook. All of these, arguably, are not synonyms for the word “thesaurus”.
I’m not going to get into homonyms, homographs, or the use of the skos:closeMatch or skos:exactMatch relationships in this blog because, although all are similar concepts, they are not synonyms. What I will leave you with is adhering to the W3C standard is a good practice in taxonomy and ontology design, but creating nuanced flavors of the skos:altLabel might prove to be a useful alternative for your taxonomy audiences.

Taxonomies, the Eternal, and the Ephemeral

https://pixabay.com/illustrations/man-time-temporariness-sky-surreal-8768564/

Have you sped through fleeting customs, popularities?” – Walt Whitman, As I Sat Alone by Blue Ontario’s Shores

Taxonomists and ontologists are, quite reasonably, obsessed with the is-ness of things. We are, after all, classifiers, and what we classify must be able to conform to one or more categories. A significant factor in categorizing things is time. What is was is not necessarily what is is now.

Time-based categories impact taxonomy concepts in a number of ways, including defining is-ness and the maintenance and governance of is-ness as an ongoing practice.

Is-ness Terms, Business Terms

The subjectivity of is-ness is contextual. When navigating a website, categories are not always strictly semantic in their aboutness because our minds can fill in the blanks. If I navigate to Men’s > Shoes > Basketball, I know not to expect to find basketballs. I also know that basketballs aren’t shoes anymore than shoes are men. My mind fills in any missing words, which might be “Men’s Shoes” or “Shoes for Men”; “Basketball Shoes” or “Shoes for Playing Basketball”. In navigation, we don’t need to be so specific because, in this context, we are less concerned with is-ness than we are about navigational findability.

Even as we describe what things are, our terms may be subjective. What does it mean for a shoe to be a “Lifestyle” shoe? What lifestyle? Whose lifestyle? Similarly, what does it mean to be “Retro”? It depends on the product, the year, and the history of the item. These examples, most importantly, are commonly understood by people based on the immediate context; that is, they are time-based. Loosely speaking, “retro” tends to span 20-30 years…within the lifetime of the consumer. I wouldn’t expect to look for a “Retro” shoe and get a Roman solea (sandal) made of leather and woven papyrus leaves. Retro, for sure, but not what we commonly agree to being retro in the consumer product space.

What people know is slippery, but, somehow, we can commonly understand the difference between concepts with longevity and those which are ephemeral and trending.

The Ephemeral and The Trending

We live in a rapid age, arguably driven by a vast online sales force of young people created by capitalist organizations. Why spend countless millions and human resources on sales and marketing when pre-teens and teens can hype and distribute your product on online social media sites and sales platforms? Some of us have seen in our lifetimes the death of a salesman (that is, a door-to-door sales person) and the rise of the young, entrepreneurial sales people receiving free products, monetary compensation, and social compensation quantified by likes and follows. It’s ingenious, really.

The fast follow to fast following is the vaporous ephemerality of what’s popular and trending. But, hasn’t this always been the case? Weren’t people obsessed with trends and topics in fashion and the public sphere which were very quickly dropped and fell out of awareness in short order? Of course, but the nature of the online race to be ahead of what’s next–to be that trendsetter who identified and pushed the next big thing–is easier in an online world and has immediate social and financial consequences.

Here’s a fairly recent example from Google Trends. “Barbie pink” was a hot topic for several months around the release of the Barbie movie. The movie’s U.S. release date was July 9, 2023 (which, incidentally, is my birthday, and, depending on the source, the birth date of Nikola Tesla). Look at how neatly the searches rise to meet the weeks following the movie’s release and how that trend falls off by Christmas. Likewise, Oppenheimer was released July 17, 2023, and the trend pattern is nearly identical. And, of course, their juxtaposition as “Barbenheimer” follows a similar popularity graph.

If you produce products in pink–any products in pink–you are going to want to jump on that trend and ride the wave until it disappears. When one considers what this means, the ramp-up and execution is significant. Identify all of your pink products and create landing pages so people can find all of those pink products. Make sure these pages can be found with the search term “Barbie pink” without using the word “Barbie”, because you are likely not licensed to do so. Ensure you have enough product to deliver on the increased popularity while also ensuring you are not stuck with a warehouse full of unsold product when the trend tapers off. Logistics of this nature requires foresight, and, most importantly, the infrastructure to deliver on trends.

As for Oppenheimer, it seems there was no fire sale on atomic weapons.

Longevity

The concept of “literary warrant” is an important one in taxonomy creation and maintenance. Literary warrant is the justification for indexing or classifying based on the content of existing literature; literature, in the modern context, extended to electronic and physical writings of all kinds. When we use sources like Google Trends, we can say that this is user warrant: we see what concepts people are actually using and consider adding them to taxonomies.

Taxonomies are never finished. They constantly grow and are governed to maintain currency. Out of date concepts or phrases are deprecated or updated with newer terms. Terms of art may evolve, new areas of study may arise, or social trends may push terminology into or out of use. Taxonomists consider these factors when deciding whether a concept should be added to taxonomies. In general, the goal is to include terms that represent the domain but that also have some stability and aren’t changing rapidly.

Practically speaking, maintaining stability is important because taxonomies which are constantly in flux aren’t very useful. When terms change frequently, there is greater chance that the same or similar content will be tagged using different concepts. Additionally, frequently changing tags on content can be difficult to manage and result in sporadic and chaotic retrievability. From the end user perspective, not knowing which terms to search for or use can result in lower use of taxonomies for metadata application.

So, if trending, ephemeral concepts are useful and taxonomies with stable terms with longevity are also useful, how do we maximize the use of both?

The Ephemeral and The Eternal

For textual problems like trending concepts, machine learning (ML) models are a practical and effective means for identifying and routing terms. Using ML models against sources like user search terms on an organization’s properties, general user search terms across the Internet, user reviews, social media channels, and the like can generate terms which may be useful. Some of these terms are so fleeting, they could feasibly be tagged immediately to content for findability. As the trend wanes, the tag remains, but no longer is critical for retrieving the content. Other terms will have a longer lifespan and may be considered for inclusion in taxonomies.

The main questions to ask are

  • What is the term source?
  • How and why was it proposed by the ML model?
  • Did the ML model compare the term to existing concepts in the taxonomy?
  • Did the ML model use only exact match when comparing new concepts to those already in the taxonomy or did it also perform near match or other similarity vectors?
  • How is it reviewed for potential inclusion in taxonomies?
  • How does the ML model receive and process positive and negative review feedback to improve the model?
  • How does the taxonomist know whether to add the term to the taxonomy or not?

Developing a process in which ML models identify ephemeral and trending concepts quickly and can route and act upon these as metadata can speed an organization’s response to trends. Human-in-the-loop reviewers can include subject matter experts for product or content tagging. Importantly for taxonomists, including them as human-in-the loop reviewers for potential candidate taxonomy concepts can help expand taxonomies and maintain their currency.

Maintaining the semantic integrity of taxonomies while also responding quickly to trending topics can improve an organization’s overall reaction to the market while also maintaining clean, quality data. Popular and timely.

Who Owns the Taxonomy?

https://pixabay.com/illustrations/ai-generated-home-ownership-house-9104189/

“Ownership is not a vice, not something to be ashamed of, but rather a commitment, and an instrument by which the general good can be served.” – Václav Havel

In my experience, when a business begins building a taxonomy program, two related questions arise: where does the taxonomy program live in an organization and who owns it?

There are at least two paths that lead to these questions. The first, and the most common from what I’ve seen, is that a taxonomy has arisen organically in the organization based on a real business need requiring a solution. An example of this might be the development of a marketing taxonomy used for planning or for tagging assets such as product copy or images. In this case, a part of the organization has covered a narrow domain of knowledge and there is a recognition that it needs to expand and grow to serve the greater needs of the business.

The second, and less common, is that an organization recognizes the importance of an enterprise taxonomy where none has existed before and makes a calculated decision to start one. From the scattered remains of glossaries and metadata schemas, consultants or a hired taxonomist builds a new enterprise taxonomy from the ground up and sets the foundation for a taxonomy program. Because an organization must requisition for a consulting budget and new positions, a decision must be made as to where this position will sit in the organization and to whom this individual, or taxonomy team, will report.

Who Should Not Own Enterprise Taxonomy

Let me start by saying who I think should not own the taxonomy. Although I myself have worked in taxonomy in a technical group, I would advise against ownership by any group called Information Technology (IT) or some similar variant. In fact, I would actually be surprised if anyone in a technical organization disagreed with this assessment. Technology exists to serve the needs of the business and it is the business who should define those needs and requirements. Even when a technology organization leads the business in best practices for tooling, the business needs to define how and in what capacity the technology supports business processes and activities. While technologists such as information architects may be adept at building metadata models and schemas, including taxonomies, it is the business who must decide what values those metadata models include.

Now that I have stated the business should own the taxonomy, I’ll now go further and say that no one business domain within the organization should be the owner. Marketing should not dictate enterprise taxonomy needs, but should own marketing taxonomy needs. The same goes for any other specific domain within an organization, as any functioning company will be made up of multiple domains all working together to achieve common goals.

Where Does Taxonomy Live?

Following on the idea that no one business domain should own the enterprise taxonomy, so too should the taxonomy not live in a technology solution supporting one part of the business. While digital asset management (DAM) systems absolutely require metadata, the use case of applying taxonomy to describe assets is too narrow to act as a centralized repository for other business needs. Similarly, content management systems (CMS) are not the best place to store data that could also be described by taxonomy metadata. Using the business glossaries in data catalogs is valuable for describing the data living in or passing through that system, but is not the right tool to house business terms which should be applied in other repositories or, again, in a separate CMS. While any of these systems can house a taxonomy, none of them is purpose-built to provide enterprise taxonomy services.

As a former taxonomy and ontology management (TMS) software product manager, there is truth in the positioning of these tools as centralized, agnostic, metadata repositories for many (but maybe not all) enterprise use cases. Centralizing taxonomies in a tool allows for building enterprise taxonomies that can serve multiple use cases and multiple systems. Because the tool stands alone, it is less subject to changing business directions and domain imperatives. On the flip side, making the case for purchasing a standalone system that “only” houses taxonomies and ontologies can be challenging. I have written about this in my former position in a blog called Running a Successful Taxonomy Campaign.

So, Who Owns the Taxonomy?

An independent, centralized, enterprise taxonomy team should ultimately own the enterprise taxonomy and the TMS it lives in. The taxonomy team owns the taxonomy and ontology models they build, but what they build is always in the service of use cases defined by the business. Having a centralized team allows them to be in a position in which they can serve any and all business domains and work with technology groups to fulfill use cases in enterprise and domain-specific technologies. I’ve seen taxonomy teams reporting up to enterprise knowledge management or learning organizations which serve the same enterprise-wide function.

Some of the business use cases are truly enterprise while others may be for specific domains which in turn serve the enterprise. For example, values from the taxonomy used in navigation and search typeahead on the company’s website is where the taxonomy ROI is realized. Tagging product images and copy in a DAM serving the front end are also enterprise. The metadata from the taxonomies is used on assets which are likely going to live in multiple downstream systems and channels in which products are presented and sold.

Other use cases may be specific to a domain requiring metadata values which may or may not be shared with other domains and systems. However, centralizing these values also supports interoperability and business continuity should the domain decide to switch technology platforms. Rather than migrate metadata from the old to new system, the metadata can still be pulled from a centralized taxonomy management system using common GUIDs used across the enterprise.

The real key here is finding the owners within the business who will be accountable for the concept values, properties, and relationships needing to be maintained in the taxonomy. Taxonomists are usually generalists who can build and maintain taxonomies across a variety of domains. They are taxonomy subject matter experts, not domain subject experts (though they may become so over time). In this way, the business SMEs who know the subject matter can be accountable for adding new concepts and identifying concepts which need to be deprecated over time. The business owners are essential to the ongoing governance and sustainability of the taxonomy and, of course, are the people who know the business needs the best.

The working relationship with technology groups is the same. There are product managers owning technology platforms serving the business. Each of these tools can be integrated via APIs to a centralized TMS to consume all or part of the taxonomy and ontology graph for the appropriate use case.

A standalone, independent, enterprise taxonomy program will allow for service to any and all business domains without bias…except for those shared business goals at the enterprise level. The ability for all business domains to have ownership and stake in the shared enterprise taxonomies also allows for cross-team collaboration and innovation with shared metadata use.

The Path to Taxonomist

https://pixabay.com/illustrations/maze-labyrinth-solution-lost-1804499/

“And you may ask yourself, “Well, how did I get here?” – The Talking Heads, Once in a Lifetime

When people ask me what I do for a living, I usually say something like “information management” because it’s an easy way to simplify the explanation of my work. If people dig deeper, they may ask me, first, what is a taxonomist? Then, what does a taxonomist do? And, if we get through those questions, the next is usually, how did you become a taxonomist?

How does one become a taxonomist? Let me share with you my path to becoming a taxonomist through a combination of chronology, and, of course, categories. I’ll also sprinkle in what I think is also a more common path to getting a role as a taxonomist currently.

Background

If you asked me what I wanted to be when I was young, I probably would have said I wanted to be a writer. Even in high school, I knew that one did not simply become a writer. There was starving and sacrifice to be done, and I am cursed with a little too much pragmatism to go through all that.

My first decision which led to a life of taxonomy was determining the best way to become a writer was to embrace what I loved and teach it. As we all know, teachers have plenty of leisure time and summers off to write their to-be-famous tomes. Well, it turns out that’s not what happens when you are a teacher, which I quickly learned when I was a teacher myself. I went to Eastern Michigan University in Ypsilanti, Michigan and got a Bachelor of Arts in English Literature and Language. I also became certified to teach in the Secondary Education program, adding an entire year to my undergraduate studies. I minored in history. The dual program allowed me to take courses in literature, composition, linguistics, and in my history minor. All of those courses turned out to be important later.

After teaching for a few years at the high school level after graduation, I was driven to get my Masters after a rather unsuccessful year as a middle school teacher. I graduated with a Masters degree in English Literature from the State University of New York at Stony Brook, a school known for…well, not English literature. The content of my degree soon became irrelevant, as the important takeaway was having a masters with even more literature and linguistics classes as well as a good dose of literary theory.

With my Masters, it was difficult for me to find full-time employment as a teacher in the New York area. The available positions for an English teacher were limited, the best school districts weren’t often hiring, and the worst only reminded me of what I hadn’t done well as a middle school teacher. After a few years of cobbling together several adjunct teaching positions at several different community colleges, I decided living on the economic edge just wasn’t for me anymore. I wanted some stability, and I was already seeing teaching wasn’t going to remain my passion for many more years.

My decision to leave teaching was as much about the pragmatic ability to have a full-time job with benefits as it was a recognition I would not be fulfilled with a career in education. While seeking a new career path, I applied for a job whose description I didn’t even understand at the Modern Language Association International Bibliography. In retrospect, I probably shouldn’t have mentioned in the interview that I didn’t understand what an Associate Thesaurus Editor did, but I somehow got the job anyway. Later, I was told I was hired because of my diverse background in language, literature, history, and education. Since the MLA indexed articles in all of those humanities areas, having knowledge and experience in them was helpful for reviewing content. In addition, I don’t believe they hired anyone without a Masters degree, so having an MA probably led directly to getting that role.

Everything I ever needed to learn about controlled vocabularies I learned at the MLA. It provided me with a firm foundation in the world of controlled vocabularies and indexing. The more I learned there, the more I realized the timing couldn’t have been better.

Timing (Luck)

I got my job at the MLA in 2002. In 2005, Gartner released its annual Hype Cycle with Taxonomy sitting at the Peak of Inflated Expectations on the curve. Businesses were clamoring for taxonomies. They didn’t really understand what they were or what they did, but they knew they had to have one.

Not only was I learning what it takes to maintain and govern a thesaurus of more than 56,000 terms in a flat list managed in an Access database, I was also making coincidental connections with people in market research and special libraries. The more I understood what they did, the more I began to understand the role of information in the corporate world. The corporate world, mind you, I knew nothing about with my two academic degrees and non-profit academic job. The intersection of my understanding of controlled vocabularies, learning more about market research content, and researching what taxonomists and special librarians did led me to understand that to grow in my career, I would have to make the jump into the business environment.

Strategy (Timing)

I often tell people I couldn’t have planned my career better if I had planned it. The fact is, I didn’t know I would be a good taxonomist until I became one. Sure, I had always been very organized (perhaps borderline OCD), lining up my Matchbox toy cars alternately by color or size as a child. I had also been interested in many different topics, but I never knew there was such a job as working with language that wasn’t linguistics, writing, or teaching some combination of those fields.

I often put more emphasis on my background and timing than on my ability to think strategically, but I did in fact have ideas and insights that proved to be true over time. So, in hindsight, I made some very strategic decisions that just so happened to work out.

The first was contacting people in the world of controlled vocabularies to understand better what they did, how they got there, and what I could do to advance my career in the field. I spoke to two people from the Getty Research Institute about their work on the Getty Vocabularies and how people got into those roles. I also spoke to a well-known taxonomy consultant who, when I told him what I was doing and asked what I should do next, replied, “Be a consultant.”

Back to timing. Since organizations knew they needed taxonomies but not what for or how to build them, they often hired consultancies to show them the way. Before there were taxonomy jobs at many of these companies, there were consultants telling them they needed to create a taxonomy job and hire a taxonomist. I started a two-pronged search for taxonomist or librarian roles and taxonomy consulting jobs. Traditionally, most taxonomists have a Masters in Library and Information Science. It is in this course of study they learn about taxonomies and then choose a path of becoming a librarian, becoming a taxonomist, or becoming a librarian who later becomes a taxonomist. Without an MLIS and no business background, I wasn’t having luck inserting myself into librarian jobs, especially corporate librarian roles.

Consulting companies, however, are always looking for fresh graduates to hire on as junior consultants. Despite being almost ten years out of my undergraduate degree, I did have enough on my resume to work in taxonomies, a niche and uncommon skill set for anyone looking for jobs in the corporate world. I landed a job at BearingPoint, a now defunct consulting company with a great reputation and a strong team in content and information analysis, organization, and discovery. Despite coming in at a junior level, the overall compensation package seemed incredible after years in education and non-profit. I was probably severely lowballed, but it was more than I had been making and gave me several years of additional background in content and records management, search, business analysis, process mapping, user experience design, and a host of other tasks thrown at junior consultants with an explanation something along the lines of, “Here, go become an expert in this.” And, of course, there was the taxonomy for business work that I had been seeking.

So, at the intersection of timing and strategy, I launched a career. I went on to work at several more consulting roles–some for others and one for myself during the economic downturn in 2008–in-house taxonomy roles, and once for a taxonomy and ontology management software vendor. The perfect trifecta: consultant, in-house practitioner, and vendor. With every passing year after breaking into the industry with my first thesaurus job, I learned more and was able to apply those learnings, with varying degrees of success, at the next job.

Takeaways

I believe we are at a moment as pivotal for taxonomy work, if not moreso, than the peak of taxonomy expectations back in 2005. In a field in which the Semantic Web has mostly failed to deliver, artificial intelligence and machine learning models have filled some of the gaps in automating and connecting existing content. What is widely accepted is that these technologies need clean data and taxonomies and ontologies provide foundational structures for classifying and connecting content. They are the semantic underpinnings that should have been the publically accessible and connected Semantic Web. I believe, now more than ever, experts in taxonomies and ontologies are necessary and valuable roles in an organization.

I’ve already laid out a path to becoming a taxonomist that didn’t require an MLIS, getting on-the-job training at an important moment in taxonomy evolution as a required business need. Aside from my initial Masters, which I got in order to get full-time teaching jobs at the college level, I never had to return to school to get the additional skills I needed to become a taxonomist. I learned in my work roles and researched information on my own, with a few certificate courses along the way to round out my education.

Will this still work today? Possibly, but getting your first taxonomy job without an MLIS is probably more difficult now than in the past. I do believe, though, the skills remain about the same as they were over 20 years ago. Therefore, you may find that you have the right skills and knowledge through a combination of your degree and work experience, as I did.

Things you need to know and skills you need to have:

  1. How to do research…in any field. The ability to research is inherent to the core tasks of defining preferred labels and discovering concept definitions.
  2. The ability to interact with others and negotiate. Taxonomy work is only enabled through work with other business and technical colleagues. It is often necessary to convince people of the value of taxonomies and there are often compromises to be made.
  3. Taxonomy and ontology best practices following standards and guidelines like the ANSI/NISO Z39.19-2005 (R2010) Guidelines for the Construction, Format, and Management of Monolingual Controlled Vocabularies, ISO 25964-1:201, W3C SKOS, W3C RDF, W3C OWL, and any industry-specific standards and available taxonomies and ontologies applicable to your area.
  4. Taxonomy and ontology management software vendors and their capabilities, like Access Innovations (Data Harmony), Graphifi (Graphologi), Progress (Semaphore), Stanford’s Protégé, Synaptica (Graphite), TopQuadrant (TopBraid EDG), and others which may be tangential to the functionalities of dedicated software platforms. Understanding how these systems work, even basically, informs how taxonomies are built and delivered to the business.

Things you may need to know and skills you may need to have:

  1. A background in library science (an MLIS degree), English (or other literature), or linguistics.
  2. Project work in text analytics, search, content, digital asset, and/or records management, user experience, or other fields or applications in which taxonomy features.
  3. Decent spreadsheet skills. I’ve never met a taxonomist who didn’t start their taxonomies in spreadsheets.
  4. Knowledge of triplestore graph databases on the market, including AllegroGraph, Amazon Neptune, OntoText GraphDB, Stardog, Neo4j, and others.
  5. Awareness of and interaction with taxonomy practitioners and consultancies, including Dovecot Studio, Enterprise Knowledge, Semantic Arts, Straits Knowledge, Taxonomy Strategies, taxonomy and ontology management software vendors, and others.

Things you really don’t need to know or have the skills to do yourself:

  1. Speak more than one language. If working in the United States, the primary language of an organization is probably English. If you are doing multilingual taxonomy work, it may help to speak one or more languages, but many organizations use translation services. Of course, an understanding of other languages helps because taxonomy is all about words.
  2. Programming and formatting languages, including XML, JSON, SPARQL, and SHACL. You may need to write these yourself, but there are frequently vendor or in-house resources to do this if you’ve already gone far enough to need them.
  3. How machine learning models work. There are people who do this as their core competency. A taxonomist isn’t expected to know how these models work under the covers, but it does help to have an understanding of how models will use taxonomies.

This is not an exhaustive list and these are my opinions after working in taxonomy for over 20 years. People, companies, or products not mentioned here is likely an oversight and does not indicate a negative opinion or lack of endorsement. I also didn’t provide a list of excellent taxonomy resources, including websites and books, because there are so many and they are already pretty well documented. A few quick searches should set you on the right path to find your own resources.

Having frequently been asked how I became a taxonomist and what I had to do, know, or learn to become one, I hope this blog helps others on their path!

Taxonomies and Turnover, or Johnny Pneumonic

https://pixabay.com/vectors/bookshelves-books-reading-learning-1751334/

“In any given culture and at any given moment, there is always only one ‘episteme’ that defines the conditions of possibility of all knowledge, whether expressed in theory or silently invested in a practice.” – Michel Foucault, The Order of Things: An Archaeology of the Human Sciences

When the movie Johnny Mnemonic came out in 1995, I often heard people mispronounce the word “mnemonic” as “pneumonic”. I speculated at the time, rightly or wrongly, that more people knew the term “pneumonia” than “mnemonic” or maybe one was simply easier to say. Strangely enough, I’ve now associated the concepts of memory and sickness because of the similarity, and confusion, of those two concepts. Maybe a pneumomic device helps you remember something…or maybe it helps your lungs function properly. Are we concerned about another pneumonic plague or a pending mnemonic plague? Who can say?

The Mnemonic Plague

If we live in a knowledge zeitgeist, it may someday later be defined as the death of knowledge. Or, more accurately, the death of the belief in knowledge and expertise in favor of opinion and belief. The results of successful misinformation campaigns include a skepticism of expertise and knowledge, feelings that opinions are equal to or supersede knowable facts, or even the inability to know anything at all. Postmodern philosophy has concerned itself with the idea that there is no objective truth, either foreshadowing the imminent knowledge paradigm or driving it. Baudrillard has predicted, quite accurately, that simulations and simulacra will become so prevalent that all meaning will be meaningless.

Add to this another sociological trend, the current workplace generational turnover from a larger, knowledgeable, older generation to a younger generation buried in and swept up by these currents of skepticism. With reality changing so quickly, and so many people being distrustful of what reality is anyway, are we on the cusp of a mnemonic plague? A plague in which no one remembers anything? A plague in which we all doubt the ability to remember it correctly? A plague in which we are convinced by others that reality is not reality, facts are not facts, and that memory is susceptible to convincingly reality-sounding alternative histories?

Johnny Pneumonic

When we began the great shift from paper to electronic documentation, the speed at which we would be able to create, store, and access information grew exponentially. Imagine a library which could feasibly contain all knowledge from human history across all countries, languages, ethnicities, and religions. An electronic library that would make the Library of Alexandria, the Library of Congress, and the Bodleian Library look like corner news stands. One library to rule them all. That happened, sort of, with the expansion of the World Wide Web. Vast troves of information were digitized and made available online even as people continued to create informational web pages and create documents which were born digital, never seeing the pulpified remains of a tree. In parallel, all the other kinds of news, information, and entertainment were also being born digitally and, in the great democratization of the Internet, anyone anywhere could theoretically have access to the ability to view and create information assuming they had some kind of device and network or satellite infrastructure.

Imagine the possibilities! Imagine how knowledgeable we could all become! Imagine knowing anything, anywhere, at any time, at the moment you need to know it! And some of that is true. What is also true is that people create patently false information reflecting their personal beliefs and agendas. There are millions of mediums, channels, and formats available to anyone to tell us what magical healing herbs will make us live longer and with fewer wrinkles; entire video libraries dedicated to documenting the horrors of vaccines and Western medicine; travel logs with erroneous anecdotes and false facts with the only verification being the person who created the content; videos of lizard-people trafficking human children; videos of directors faking the moon landing. All of this available to anyone, anywhere who wants to be an audience.

Whether an individual or a state actor, whether the content creator believes their own content or not, whether we can decipher what is true and what is not, all of this information is there for us to consume and form our own opinions about. That is freedom. That is democracy. That is the democratization and platform of eight billion voices. We no longer have to be slaves to a single narrative; no, we can write our own narratives and gather our own followers, forming fragmented communities in a new-world Splinternet in which we can all, finally, show everyone else a picture of what we had for lunch.

The Codification of Memory

I could say things were better back in the good old days, whenever those were and for whomever they were good, but that’s also an opinion, not a fact. The genie is out of the bottle. The train has left the station. The die is cast. We have crossed the Rubicon. The horse has left the barn. We now live in a world of snowclones, memechés, and information of dubious provenance. Compounding the intersection of easily creatable and accessible information, skepticism of expertise, and generational turnover is the ever-improving use of AI tools to generate very impressive, lifelike, and believable images to support textual messages. Don’t believe we faked the moon landing? Here’s a photo! Didn’t that famous Hollywood actor appear in a porno? Here’s the video!

And now for something completely different. Or, rather, here is me now getting to the point for my target audience of information professionals: what do we do in the face of all this misinformation? Our jobs…the best we can.

I’ve been working on taxonomies for over 20 years. At various times–sometimes from one year to the next and other times one hour to the next–I have experienced that overwhelming sense of doom, frustration, or hopelessness in the face of shockingly ignorant misinformation and opinions. I have long since abandoned any hope for the Semantic Web’s promise that real, verified meaning could be captured in logical, formalized, human and machine-readable structures like taxonomies and ontologies. Despite the acknowledgement, both philosophical and practical, that there is no Truth with a capital “t” and that all facts are context-dependent, I still try to build semantic structures that codify the truth of my organization at the moment we are building it.

In the context of any moment, there are truths we can build and verify. We can create preferred concepts and connect them with human-readable, sensible relationships and build taxonomies into interconnected graphical knowledge bases applied to a variety of content vetted by subject matter experts. Verified and vetted content may no longer be true in a week or a year or a decade. The relationship between two concepts may quickly become outdated. A preferred concept may fall out of use or fashion. Despite all of this, codifying knowledge in taxonomies and ontologies is not an act of futility; it is an act of capturing truth and memory at a moment. We can document these changes over time and look back over the history to see what was true versus what is true now.

These semantic structures are a way we can document organizational knowledge and pass this knowledge on to the next employee, the next generation, the next iteration of a company. Creating good historical records in semantic models serves a knowledge management function in being one way we can enable knowledge handover from one person to the next, one team to the next, one project to the next.

The organizational book of knowledge as written in taxonomies is often edited and changed, but it is still a book to which we can refer with confidence that what we tried to build was accurate and true to the best of our abilities. Taxonomies are the new black. Ontologies are the mother of all semantic structures. In space, no one can hear you taxonomize…but your work is still valuable.

KMWorld Themes and Trends

https://pixabay.com/illustrations/cyborg-hand-human-robot-contact-9091910/

“At a certain level of machine-ness, of immersion in virtual machinery, there is no more distinction between man and machine.” – Jean Baudrillard, Violence of the Virtual and Integral Reality

I attended the KMWorld and co-located conferences held in Washington, D.C., November 18th – 21st. Across the conferences and sessions that I attended and the conversations between sessions, there were several themes which resonated. I’ll detail some of those themes and highlight any talks in particular I thought inspired or captured those trends. I couldn’t attend everything, so please forgive me if I’ve overlooked great talks, of which there were many.

Taxonomies as an Enterprise Strategy

The importance of taxonomies and ontologies as a foundational business and technical program was particularly evident at Taxonomy Boot Camp, but the theme also came up in talks in the other conferences as well. I presented on the topic in my session, “Stand Still Like the Hummingbird: Enterprise Taxonomy Strategy When Nothing Stands Still”. Likewise, Thomas Stilling in his Monday keynote, “Be the Change: Your Taxonomy Expertise Can Help Drive Organizational Transformation”, emphasized metadata as an organizational strategic asset and discussed how to position taxonomy to align with strategic objectives. Similarly, Lindsay Pettai’s session, “Empowering Your Enterprise With a Dynamic Taxonomy Program”, discussed the importance of having an enterprise taxonomy program.

These are just a few examples. Throughout the conferences, the notion that taxonomies and ontologies provide structured, source of truth values for navigation, search, and content tagging was prevalent. The main theme, however, was how taxonomies and ontologies are critical to the success of machine learning (ML) model training and program success. In talk after talk, artificial intelligence (AI) and ML were top topics and various ways to approach projects to make them viable and successful included what needed to be in place. Taxonomies and ontologies were among those foundational requirements.

As a 16-year veteran of KMWorld associated conferences–my first being Enterprise Search Summit West in 2008–I have seen the more recent embrace and understanding of enterprise taxonomies and ontologies beyond simple use cases like navigation. Even just a few years ago, taxonomies seemed to be misunderstood or undervalued by many conference attendees. Now, talk of their use as enablers of AI was ubiquitous.

Artificial Intelligence Is Here to Stay

I don’t believe I saw a talk which didn’t include the keywords “artificial intelligence”, “machine learning”, “AI”, or “ML”. I was unable to attend KMWorld last year, but in years past, any conversation on the role of AI/ML was frequently met with scoffs, eyerolls, or fear. In KMWorld’s Thursday Keynote, KM, Experts & AI: Learning From KM Leaders, Kim Glover and Cindy Hubert captured something important when they said that AI is driving a lot of emotions. Some of these emotions are excitement, skepticism, and fear. Addressing these emotions is going to be essential in addressing the technologies. 

The overarching theme is that AI/ML is here to stay, so what are you going to do about it? Continue to reject it and fall behind the curve? Embrace it without question? Embracing ML models, including LLMs, with guidance and guardrails seemed to be the message most were conveying. While many organizations are still in the proof of concept (PoC) project stage, adoption seems to have already arrived or is pending, so get ready to embrace the change to be successful.

The exponential growth in ML has been fueled by cheaper storage, faster technologies, more robust and accessible models such as ChatGPT, and built-in technologies like Microsoft Copilot. Not only are these tools more accessible, they are more accurate than they have ever been in the past…for the right use cases. And this was another big takeaway: AI/ML is here to stay, but use these technologies for the right use cases. Document summarization and generative AI text generation are big winners while tools used for critical decision making are still improving and must be approached with caution.

Human-in-the-Loop, Cyborg, or Sigh…Borg?

Overwhelmingly across sessions, the consensus was the importance of the human in the use of AI/ML technologies. For both the input and the output, to avoid garbage in and garbage out, human beings need to curate and review ML training sets and the information that an ML model outputs. As noted above, document summarization may be low risk depending on the industry, but decision-making in areas like law and medicine are high-risk and require humans-in-the-loop.

In his session, Evolving KM: AI, Agile, & Answers, the inestimable Dave Snowden discussed storytelling–or, rather, talked about storytelling through the art of storytelling–as an intimately human activity. He noted the deeply contextual nature of human knowledge and the need for knowledge management to generate knowledge rather than store it as codified data. If knowledge can not be fully codified as data, therefore, it is difficult or impossible to transfer that level of human knowing into machines and their models. The connectivity to knowledge and deep metaphor was evident in my three takeaways from his session: his notion of a tri-opticon integrating knowledge between three areas of an organization and the connection to Welsh Triads; forming teams or roles of threes, fives, or sevens, Welsh Rugby, and the number of people on a rugby sevens team; and assemblages, mycorrhizae, and rhizomatic networks in Deleuze and Guattari’s, “A Thousand Plateaus”. These kinds of connections are weak use cases for machine learning and emphasize the importance of human knowledge and inclusion in AI technologies.

And, speaking of human knowledge, of course knowledge retention and transfer were key topics in an era when both age and work-from-home job mobility are creating more job turnover than ever. While human knowledge is difficult to capture, using AI agents to capture knowledge and ML models to parse textual information will assist in ramping up the sheer scale and increasing pace necessary to retain and transfer knowledge.

The human-in-the-loop, the cyborg, and, sigh…Borg, are all going to rely on knowledge and ethics in order to create a human-machine interactive paradigm. If humans don’t use our own ethical boundaries to curate machine content, then bad data, and bad ethics, will spread throughout our information systems.

While there was some fear and loathing in D.C., there was a stronger current of hope, optimism, and curiosity in the many ways we can use taxonomies and ontologies, AI/ML, and human knowledge management together to guide us toward a brighter future of technology use.

Specialty Skills and the Risks of Hidden Complexity

https://pixabay.com/photos/statue-camouflage-hidden-discreet-2393168/

The Cube is, at the same time, a symbol of simplicity and complexity.” – Ernő Rubik

Taxonomists and ontologists–sometimes separate but more often one and the same role I’ll simply call a “taxonomist”–are frequently underappreciated for their work in modeling and representing complex domains. Taxonomists do not simply suggest term forms and put them in a list; they research and consider each concept, carefully map out its relationships to other concepts, and consider how new additions and changes impact the overall semantic model. The nature of taxonomy work is often misunderstood, or, worse, trivialized as work that anyone in the organization might perform. Several expert taxonomists discussed this topic as a pain point in communicating the value of taxonomy at the Henry Stewart Semantic Data 2024 Conference in New York this week.

Taxonomies and ontologies need to be clear, transparent, and wholly visible and available where appropriate. Serving different use cases drives user experience decisions which lean toward simplifying the display of complex semantic models so users can more easily understand and use them. While hiding complexity is a service for end users, it can communicate the result of taxonomy work as simplified dropdown lists, shallow hierarchical structures, or simple concept values without additional properties and relationships. The complexity of semantic models, including the taxonomist’s work in building them, can be hidden and thus misunderstood.

Hidden Work

Semantic models are frequently hidden from users due to their complexity and necessarily strict governance models. The overall semantic structure, potentially composed of many taxonomies connected by robust ontologies, is not always available for the end user to view as a whole or to interact with directly. Hiding the complexity of semantic models can simplify user experiences, but they can also present fractured, contextless concept values. Worse, the art and science of semantic modeling conducted by highly skilled and knowledgeable taxonomists is also hidden…or at least potentially misrepresented.

The implications of this hidden work are manyfold. Because the skilled work of taxonomists is simplified, so too does the portrayal of semantic work seem simple. The result is inexperienced employees taking on taxonomy and ontology modeling tasks, potentially in parallel to ongoing enterprise taxonomy efforts. The fragmentation of taxonomy work in turn impacts the success of the overall taxonomy program as an enterprise strategy.

Additionally, the value of taxonomy work in supporting a variety of use cases is also undercut. Taxonomy is reduced to simple hierarchies to use in navigation or flat lists used in content tagging. The true value of complex, interrelated concepts with additional property metadata is lost. End users, or potential end users, don’t know the art of the possible or even what to ask for from enterprise taxonomists.

Exposing Semantic Models in the UI

Systems consuming taxonomy values are an abstracted layer, presenting concepts in navigational structures, as typeahead values in search boxes, or as limited flat lists for tagging content or assets. Because of this, the additional value of ontological relationships and property metadata is stripped away. Of course, designing user experiences to meet the use case and deciding when it is appropriate to display taxonomy values, how many, what type, and what is possible are all aimed at organizational efficiency and clarity. Sometimes too much is just too much.

However, consideration is not always given to what else from a semantic model may be displayed, and in what way, so that users get more contextual value from taxonomy concepts shown out of context. How much information associated to a taxonomy concept should be exposed and in what context? Concept definitions or synonyms might be valuable to expose to end users so they understand the label and what else it may represent. These could be displayed in a hover menu so they are available but unobtrusive.

Similarly, taxonomies need not always be displayed as flat lists or hierarchies. Taxonomies are natural candidates for graphical visualizations to display interconnected values and associated metadata. Many existing taxonomy and ontology tools include APIs or widgets meant to display taxonomies in just this way external to the tool. Publicly available visualization libraries can be used in custom, in-house built UIs to display and navigate graphs. A graphical user experience can display the complexity of semantic models, including hierarchical and associative relationships, while easing their presentation and navigation.

Taxonomies and ontologies are foundational components in the training and refining of machine learning models, including their use as a source for tagging machine learning training sets and as institutional reference for large language models. Graphical displays have the benefit of exposing the full scope of semantic models for more complex use cases like serving data to machine learning models. 

Another way to expose the full scope of semantic models is to provide partners with read-only access to taxonomy and ontology management systems. These tools typically have few editing licenses which should be reserved for members of the taxonomy team to maintain proper model governance. Read access, when available, should be reserved for business partners who understand, or are willing to be trained, how to navigate complicated platforms.

The Benefits

There are several benefits to getting creative about how and what to expose from semantic models.

The main benefit is discrete, visual communication and training of the complexity and possibilities of semantic models. Good UIs don’t simply provide a way of interacting with machines, they also educate and train the end user on common principles such as clicking on a button to perform an action, pinching in and out to view content, and, in this case, how to traverse hierarchies and graphs. From this, end users may come to their own realizations about how semantic models may be used in their projects.

Another benefit is increasing end user awareness and the visible profiles of the taxonomists and taxonomy program. Knowing how information is provided to consuming systems and who is responsible for creating, modeling, and maintaining that information provides a point of contact for end users who can field their questions. Since consumers don’t always know the full range of possible semantic model use cases, they are provided a path to get modeling advice. Taxonomists increase their visibility and can act as internal consultants on a range of organizational projects. In turn, their valuable skills are employed in many areas of information management, improving the overall health of information best practices.

In sum, don’t hide your taxonomists or their work. Get creative about how to expose what they do and the results of their professional skills.

Modeling a Moving Target

https://pixabay.com/illustrations/ai-generated-pipes-industrial-9043429/

Like a wave in the physical world, in the infinite ocean of the medium which pervades all, so in the world of organisms, in life, an impulse started proceeds onward, at times, may be, with the speed of light, at times, again, so slowly that for ages and ages it seems to stay, passing through processes of a complexity inconceivable to men, but in all its forms, in all its stages, its energy ever and ever integrally present.” – Nikola Tesla

Some of the most thorough, authoritative, and well-constructed controlled vocabularies have been built and curated over the course of decades. The NASA Thesaurus was first published in 1967. The Library of Congress Subject Headings can be traced back to its roots in 1898. The MLA Thesaurus was modernized in 1981 based on previous classification methods. The Getty Art & Architecture Thesaurus was started in the late 1970s. There are many more examples of well-established controlled vocabularies, some older and some newer.Maybe there’s something to the adage “with age comes wisdom” in the longevity and authority of these vocabularies.

Many of these longstanding vocabularies serve the academic system and do not necessarily “move with the speed of business”. In a business environment, the emphasis is typically on speed, agility, and efficiency. None of these qualities are in opposition to the typical development of good controlled vocabularies, but a fast-paced organizational environment can certainly be difficult to support with vocabulary development that can’t keep up.

In my experience, product vendors talk about how to speed up taxonomy and ontology development while semantic practitioners (librarians, taxonomists, ontologists, etc.) regularly have to strike a balance between maintaining quality semantic models and serving the business needs. The speed at which semantic models need to be developed in a business setting often leads to the extension of inappropriate taxonomy use cases in order to support and facilitate immediate business priorities. We need to step back and ask ourselves how we can as taxonomists effectively support the business while addressing what should be modeled in taxonomies and what should not.

In this blog, I’m going to focus on two closely related cases of data which I think are not appropriately modeled or maintained in a semantic model but are often brought up as examples of serving the business quickly.

Processes & Sequences

A business problem I’ve seen in my roles as a taxonomy management platform product manager for a vendor and as a taxonomy practitioner is the modeling of processes as taxonomies.

There are several difficulties with modeling processes as taxonomies, and why I tend to discourage their inclusion as part of the overall enterprise taxonomy and ontology semantic framework. First, steps in a process aren’t usually semantically hierarchical. For example, say you are asked to support a step-by-step process for submitting a ticket in a request tool such as those offered by ServiceNow or Atlassian in a centralized taxonomy. An IT service ticket can be opened, assigned, reassigned, resolved, closed, and reopened. Building these steps as a hierarchical taxonomy doesn’t convey their true relationship to each other. You can build these steps as a flat list, which addresses that problem, but then you have a sorting issue of making sure the steps are displayed in the proper order in the consuming system. Since the actual ticket requests live in a consuming ticketing system while the controlled values naming each step in the process live in a taxonomy management system, this may not be a problem at all. The ticket is an object that is simply tagged with a new value at each stage in its lifecycle, regardless of the flat or hierarchical structure in the taxonomy. So, the first problem may be solvable, but it needs to be addressed.

The second issue is that processes are rarely progressive steps from beginning to end. The stages of a ticket may move up and down a flat list or hierarchy, often skipping steps in between and moving back to a previous step. Again, if the ticket is tagged from a flat list which is properly ordered for display, this may not be an issue. If the consuming system must follow the flat list or tree order, however, there may be challenges in changing the value to a previous step. Where this gets complicated, however, are processes in which the same steps are repeated by different groups in the organization. A contract, for example, can go through contract review by the vendor, by the business team representatives, by legal, and again by the vendor’s legal. Modeling a process like this taxonomically often means that these repeated processes are either appended with the team or entity conducting the process step (business review, legal review, etc.) or repeating the steps as children under organizational group headings, creating a polyhierarchical nightmare. 

The final and most difficult challenge with modeling a process is that they often change. In another example, modeling the customer journey from start to finish is much like stages in an IT ticketing process. The customer rarely moves neatly from each step to the next. More importantly, however, is that marketing processes frequently are overhauled with changing values anytime there are changes in business strategy. Even when the values don’t change, their ordering of the process does and these orders are often reflected as navigational structures represented as filters on the front end. Representing a customer journey based on filterable values is challenging because of the numerous ways a customer may enter the UX pipeline. In retail apparel, for example, they may start looking for products at Gender (Men’s, Women’s, Children), then apparel type, then size, then filtering by material or color. Or, the customer may start with color, then apparel type, then size. There is a process here, but one with multiple entry and end points. Trying to represent this as a taxonomy is incredibly difficult.

A similar problem I’ve come across in taxonomy modeling is using lists or hierarchies to indicate sequence. Most processes have steps that are in sequence, but in this case I’m talking about strictly fixed sequential order. Examples can include the order of books or films (by date or by narrative order), the list of U.S. Presidents in order, or events by date.

The fundamental issue for most taxonomy management systems, and for many systems relying on taxonomy data for that matter, is the default to alphabetical display in lists. For most taxonomy hierarchies, alphabetical is the preferred display order, with each cascading branch also alphabetized. On most front end websites, navigational taxonomies are ordered by use with the most prevalent ways to access information listed first. Front end website platforms are built for this type of information display because the hierarchies do not necessarily follow what I would call semantic or “is a” taxonomy practices; parent child relationships are based on filtered drilldowns, not by strict contextual meaning. Where this becomes an issue is when an organization, quite rightly, wants to consume centralized taxonomy concepts for the front end experience.

Even when using the larger graph underlying taxonomy and ontology structures, conveying order can be challenging without the right functionality to support it or the ability to leverage the model in consuming systems that can only handle flat lists or shallow hierarchies.

Modeling Options

Modeling sequences isn’t out of the question in taxonomy management systems assuming that 1) the taxonomy and ontology management system includes functionality supporting modeling options, or 2) downstream systems can effectively handle or transform concepts received from a centralized taxonomy.

To model steps in a process or to capture sequences, there are a few options. If you are using a tool supporting RDF and core SKOS elements, you can consider using skos:OrderedCollection. An ordered collection is exactly what it sounds like: a collection of concepts put in a specified order. Using an ordered collection for a list of concepts in a branch of taxonomy allows listing those items in the order desired. There may be no other indicators of why those concepts are in that order if stripped from their contextual parent, but it will force sort a group of concepts. This assumes, of course, that the consuming systems don’t simply revert to alphabetical order once received.

A more flexible and sustainable way to model a process is to model semantically using “is a” rules and then leveraging a true ontological structure and a graph to map the journey. This means modeling concepts in their one best location in one or more taxonomies as part of a larger domain model. Modeling this way leans into the strengths of an ontology by using associative relationships between entities to make a graphical representation of the order while also connecting the entities to their owners. So, for example, books or films may have relationships like is followed by / is preceded by and then can be connected to their authors, directors, and actors as part of a greater graph.

Another option is to include a property on each concept. The property could be a field which indicates a numerical value listing its placement in the list. While this metadata field could be useful in the taxonomy user experience, whether or not these property values could be used in consuming systems to order items is still problematic. Furthermore, it gets complicated if it’s necessary to order multiple sets, all of them including the same numbers as an ordering property.

In advanced graph-based taxonomy and ontology management systems, there may be an option to use reification or RDF* to support metadata on triples. In this way, the ordering is embedded on the edges themselves. For example, books and films could include relationships with a release date. This could look something like “James Bond film” has release date [20061117] “Casino Royale” in addition to a broader/narrower relationship between the two concepts. There are several modeling options to make use of associative relationships with added metadata on the relationship edge.

In sum, it’s not impossible to model processes and sequences in taxonomies, but it requires thoughtful modeling in the context of other existing business taxonomies likely sharing the same overarching business ontology. Moreover, thoughtful modeling may not move with the speed at which an organization wants to move, but slowing down and getting it right the first time can save a lot of painful rework later.