tag:blogger.com,1999:blog-90947315961690969922024-03-19T07:38:13.736-04:00The Accidental TaxonomistTopics related to information management taxonomies posted by the author of the book, The Accidental Taxonomist.Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.comBlogger155125tag:blogger.com,1999:blog-9094731596169096992.post-7250774007504551422024-02-24T19:41:00.021-05:002024-02-26T13:45:46.276-05:00Faceted Classification and Faceted Taxonomies<p></p><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">I have argued before that a taxonomy is not the same
as a classification system, despite the original meaning of the word taxonomy
as a system for classification. (See the blog post </span><span><span lang="EN-CA"><a href="https://accidental-taxonomist.blogspot.com/2020/02/classification-systems-vs-taxonomies.html"><span>Classification Systems vs. Taxonomies</span></a></span><span lang="EN-CA">.) Modern taxonomies that are used to
support information management and findability are more similar to information
retrieval thesauri and subject heading schemes than they are to classification
systems. Another type of classification, the method of “faceted classification,”
however, does apply to types of taxonomies. I would not consider “faceted
classification” as exactly a synonym, though, to “faceted taxonomy,” though, as
not all faceted taxonomies are the same. </span></span></span><p></p>
<h2 class="MsoNormal" style="text-align: left;"><span style="font-family: inherit; font-size: large;"><span lang="EN-CA">What is faceted classification? </span></span></h2>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA"></span></span></p><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: right; margin-left: 1em; text-align: right;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhR2w_F5FBs79QqZl9cr6-OATAT_3XKWmEnXDFTIT5wNNJ8a0pXGKTQ8iDxCSwZttXP6ViA0zeOpVMYVHSa5OGyyT-VZMIGYyqiXKbk2zvgDus09b_0b89lBFKjZjkcZCONAZgLw8IFEx_YG4WPCqubo6BqvaKSs49thSjQR7nX5NzUn4qkPCcqERmobBM/s634/job%20facets.jpg" style="font-family: inherit; margin-left: auto; margin-right: auto;"><img border="0" data-original-height="634" data-original-width="262" height="465" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhR2w_F5FBs79QqZl9cr6-OATAT_3XKWmEnXDFTIT5wNNJ8a0pXGKTQ8iDxCSwZttXP6ViA0zeOpVMYVHSa5OGyyT-VZMIGYyqiXKbk2zvgDus09b_0b89lBFKjZjkcZCONAZgLw8IFEx_YG4WPCqubo6BqvaKSs49thSjQR7nX5NzUn4qkPCcqERmobBM/w192-h465/job%20facets.jpg" width="192" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><i style="font-family: inherit;">Facets for jobs</i><span style="font-family: inherit;"><br /></span></td></tr></tbody></table><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Facet means face, side, dimension, or aspect. In this
sense, facets are meant to mean aspects of classification. A diamond, an
object, or a digital content item is multi-faceted. A digital content item
(text document, presentation, image, video, etc.) has multiple informational dimensions
or aspects to it and thus multiple ways to be classified.</span></span>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Classification is about putting an item, such as a
content item (document, page, or digital asset) into a class or category. If
it’s a physical object (a book) it goes into a shelf of its class. In faceted
classification, an item cannot physically be in more than one place, but it can
still be “assigned to” more than one class. So, while the book itself can be on
only one shelf, the record <i>about</i> the book can be assigned to more than
one class. </span></span></p>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Faceted classification assigns classes/categories/terms/concept
from each of multiple facets to a content item, allowing users to find the item
by choosing the concepts from any one of the facets they consider first.
Different users will consider different classification facets first. Users then
narrow the search results by selecting concepts from additional facets in any
order they wish, until they get a targeted result set meeting the criteria of
multiple facet selections. The user interface of faceted classification is
sometimes referred to as faceted browsing.</span></span></p>
<h2 class="MsoNormal" style="text-align: left;"><span style="font-family: inherit; font-size: large;"><span lang="EN-CA">History of faceted classification</span></span></h2>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">The idea of faceted classification as a superior alternative
to traditional hierarchical classification, whereby an item (such as book or
article) can be classified in multiple different ways instead of in just a
single classification class/category, is not new. The first such faceted
classification was developed and published by </span><span>mathematician/librarian S.R. Ranganathan in
1933, as an alternative to the Dewey Decimal System for classifying books, called <a href="https://www.isko.org/cyclo/colon_classification">C</a></span><span lang="EN-CA"><a href="https://www.isko.org/cyclo/colon_classification">olon Classification</a> (since
the colon punctuation was originally used to separate the multiple facets). In
addition to subject categories, it has the following facets: </span></span></p>
<ol start="1" style="margin-top: 0in;" type="1"><li class="MsoNormal" style="margin-bottom: 0in; mso-line-height-alt: 1.2pt; mso-list: l0 level1 lfo2; tab-stops: list .5in;"><span style="font-family: inherit; font-size: medium;"><span><i><span>Personality</span></i><span> – topic or orientation</span></span></span></li><li class="MsoNormal" style="margin-bottom: 0in; mso-line-height-alt: 1.2pt; mso-list: l0 level1 lfo2; tab-stops: list .5in;"><span style="font-family: inherit; font-size: medium;"><span><i><span>Matter</span></i><span> – things or materials</span></span></span></li><li class="MsoNormal" style="margin-bottom: 0in; mso-line-height-alt: 1.2pt; mso-list: l0 level1 lfo2; tab-stops: list .5in;"><span style="font-family: inherit; font-size: medium;"><span><i><span>Energy</span></i><span> – actions</span></span></span></li><li class="MsoNormal" style="margin-bottom: 0in; mso-line-height-alt: 1.2pt; mso-list: l0 level1 lfo2; tab-stops: list .5in;"><span style="font-family: inherit; font-size: medium;"><span><i><span>Space</span></i><span> – places or locations</span></span></span></li><li class="MsoNormal" style="margin-bottom: 0in; mso-line-height-alt: 1.2pt; mso-list: l0 level1 lfo2; tab-stops: list .5in;"><span style="font-family: inherit; font-size: medium;"><span><i><span>Time</span></i><span> – times or time periods</span></span></span></li></ol>
<p class="MsoNormal" style="margin-bottom: 0in; mso-line-height-alt: 1.2pt;"><span style="font-family: inherit; font-size: medium;"><span>Although it was not adopted widely internationally due
to its complexities in the pre-digital era, colon classification has been used
by libraries in India.</span></span></p>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">In the late 20<sup>th</sup> century, digital library research
systems based on databases enabled faceted classification and search, with
different fields of a database record represented in different search facets. Users
interacted with through an “advanced search” form of multiple fields. Faceted
classification and browsing gained widespread adoption with the advancement of interactive
user interfaces on websites and in web applications in the late 1990s and early
2000s. Thus, facets started being displayed in more user-friendly ways that
were no longer “advanced.”</span></span></p>
<h2 class="MsoNormal" style="text-align: left;"><span style="font-family: inherit; font-size: large;"><span>Structure of facets</span></span></h2>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span>It’s not necessary to follow Ranganathan’s
suggested five facets, but that’s a good way to get thinking about faceted
classification. Another way to look at faceted classification is to consider a
facet for each of various question words: What, Who, Where, When</span></span></p>
<ul style="text-align: left;"><li>
<span style="font-family: inherit; font-size: medium;"><span><i><span>What</span></i><span>
kind of thing is it – content type</span></span></span></li><li><span style="font-family: inherit; font-size: medium;"><span><i><span>What</span></i><span>
is it primarily about - subject</span></span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span><i><span>Who</span></i><span> is
it for or concerns – audience or user group</span></span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span><i><span>Where</span></i><span>
is it for/applicable, or where it depicts (media) – geographic region</span></span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span><i><span>When</span></i><span> it
is about – event or season (not date of creation, which is administrative
metadata, instead of a taxonomy concept)</span></span></span></li></ul>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span>The additional question words of “why” and “how”
are relevant in some cases, but less common. An individual content item typically
does not address all of these questions, but usually addresses more than one. When
creating facets, most of the facet types should be applicable to most of the
content types. <span> </span></span></span></p>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span>Another good way to think about faceted
classification is to put the word “by” after each facet, to suggest
classification and filtering “by” the aspect type. A logical and practical
number of facets tends to be in the range of three to seven.</span></span></p>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span>A standard feature of facets is that they are
mutually exclusive. A concept/type belongs to only one facet. This is typical
practice for the design of classification systems. The difference is that in <i>faceted</i>
classification it is merely the concept/type/term that belongs to just one
facet, not the content item or thing itself that would belong to only one
classification in traditional classification systems.</span></span></p>
<h2 class="MsoNormal" style="text-align: left;"><span style="font-family: inherit; font-size: large;"><span lang="EN-CA">When a faceted taxonomy is not for classification </span></span></h2>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">The design, implementation and use of facets to
construct or refine searches has become so popular that it is no longer used just
for classification aspects. Rather, a faceted taxonomy design may be used for
any faceted grouping of concepts for search or metadata types that are relevant
for the content and users.</span></span></p>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Faceted classification is intended to classify things
that share all the same facets. For example, all technical documentation
content has a product, feature, issue, and content type, so these are faceted
classifications. But with more heterogeneous content, facets are not universally
shared. While the facets may still be useful tool, it would be best not call it
faceted classification when facets are applicable to only some content types. </span></span></p>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">While faceted classification tends to be quite limited
in the number of its facets, non-classification faceted taxonomies, whether
based on subject types or separate controlled vocabularies, could result in a
rather large number of facets. </span></span></p>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Faceted taxonomies that would not be considered
faceted classification include those where multiple facets are created for
organizing and breaking down subjects or when multiple facets are created for
reflecting multiple different controlled vocabularies. These faceted taxonomies
stretch the meaning of “facet,” since the facets are not necessarily faces,
dimensions, or aspects, but simply “types” suitable for filtering.</span></span></p>
<h3 class="MsoNormal" style="text-align: left;"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Facets for organizing subjects</span></span></h3>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">In faceted classification we assign an object or
content item to multiple different classes. However, for classification, these
classes are relevant to the content item as a whole. This contrasts with
indexing or tagging for subjects or names of relevance that occur <i>within</i>
a text or are depicted <i>within</i> a media asset. These names and subjects
can be grouped into facets for filtering/limiting search results, without being
about the “classification” of the content item. <span> </span>This is common for specialized subject areas. Faceted
taxonomies provide a form of guided navigation and are easier to browse and use
than deep hierarchical taxonomies, so a large “subject” taxonomy could be
broken down into specific subject-type facets.</span></span></p>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Examples of specific subject-type facets include:</span></span></p><ul style="text-align: left;"><li><span style="font-family: inherit; font-size: medium;"><span>Organization types</span></span></li><li><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Product
types</span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Technologies</span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Activities</span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Industries</span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Disciplines</span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Job
roles</span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Event
types</span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Topics</span></span></li></ul>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">The “Topics” facet is then used for the leftover
generic subject concepts that do not belong in any of the other specialized
facets. Unlike faceted classification, each facet is applicable to only some
content items.</span></span></p>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Any content item could be tagged with any number of
concepts from any number of these facets. The facets make it easier for user to
find taxonomy concepts and combine them. But the facets are not for
“classifying” the content.</span></span></p>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">While faceted taxonomies should also ideally be
mutually exclusive, in contrast to the principle of faceted classification, the
occasional exception of a concept belonging to more than one subject-type facet
(question word of “What”) does not create a problem in search. For example, the
same concept Data catalogs, could be in the facet Product Types and
Technologies, as long as this type of polyhierarchy is kept to a minimum to
avoid confusion. This would not be considered a case of classic polyhierarchy, because
it’s not simply a matter of different broader concepts, but rather different facets
or concept schemes. It is an attempt to address a different focus or approach
to the topic that results it being in more than one facet, offering an
additional starting point for searchers.</span></span></p>
<h3 class="MsoNormal" style="text-align: left;"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Facets for organizing controlled vocabularies</span></span></h3>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Faceted filters/refinement may be based on different
controlled vocabulary types: one or more of term lists, name authorities, and
subject thesauri/taxonomies. The “facets” are based on how the set of multiple
controlled vocabularies is organized rather than based on “aspects” of the
content. </span></span></p>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Facets could be used for any controlled vocabulary
filters that are logical, such as:</span></span></p>
<ul style="text-align: left;"><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Named people (mentioned/discussed)</span></span></li><li><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Organizations
(mentioned/discussed)</span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Products/brands
(mentioned/discussed)</span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Divisions,
departments, units (mentioned/discussed)</span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Named
works/document titles (mentioned/discussed)</span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Places
(mentioned/discussed)</span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Topics
(mentioned/discussed)</span></span></li></ul>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Because these facets reflect controlled vocabularies
of concepts used to tag content for relevant occurrences of the subject/name
and not for classification of the content, this kind of faceted taxonomy would
not be considered faceted classification. There could, however, be additional faceted
classification types, such as content type.</span></span></p>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">The Topics facet could contain a large hierarchical
taxonomy or thesaurus. As such, this faceted search/browse structure, may not
even be considered a “faceted taxonomy,” but rather merely a faceted search
interface to a set of taxonomies. Thus, there is even a nuanced difference between
a faceted browse UI that utilizes at taxonomy (among other controlled vocabularies),
and a “faceted taxonomy.”</span></span></p>
<h3 class="MsoNormal" style="text-align: left;"><span style="font-family: inherit; font-size: medium;"><b><span lang="EN-CA">Facets for heterogeneous content</span></b></span></h3>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Finally, whether a faceted taxonomy is considered an
implementation of faceted “classification” or not may depend on the context and
type of content. If the content is homogeneous and all items share the same
facets, then it may be considered faceted classification, but if the content is
heterogeneous, and the facets are only relevant to some content, then it would
not be considered classification. </span></span></p>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Consider the following example of specialized
subject-based facets for the field of medicine:</span></span></p>
<ul style="text-align: left;"><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Diseases or conditions</span></span></li><li><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Body parts (anatomy)</span></span></li><li><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Sign
and symptoms</span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Treatments</span></span></li><li>
<span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Patient
population types</span></span></li></ul>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">If all the content comprised just clinical case
studies, then these facets actually could be considered faceted classification,
since they all apply to nearly all the content and are aspects of the content. The
content is classified by these facets. On the other hand, if the content dealt
with all kinds of documents that had something to do with health or medicine,
then these facets would not be for classification of the content but rather
just for grouping of subjects for search filters.</span></span></p>
<p class="MsoNormal"><span style="font-family: inherit; font-size: large;"><b><span lang="EN-CA">When faceted classification is not a taxonomy</span></b></span></p>
<table cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: left; margin-right: 1em; text-align: left;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhDJ6JkPVpVW4ll3cWH-ZtlNE6qrwBX02TAWzH8gQFVB00hCmq8Hx_A4hcq2AUzyRi6yApZ745NW_B5abVPb64vExF9T71_OIN42n0btSuXqrBvS6N0sXJLDqIdM2eHDE7Ear-y4dL5D7n25ppmh-k8VGZPxLc-vJDmuE1PPKY9kTyBVDUEHrFzqd-II2s/s941/computer%20attributes.jpg" style="clear: right; font-family: inherit; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img border="0" data-original-height="941" data-original-width="302" height="700" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhDJ6JkPVpVW4ll3cWH-ZtlNE6qrwBX02TAWzH8gQFVB00hCmq8Hx_A4hcq2AUzyRi6yApZ745NW_B5abVPb64vExF9T71_OIN42n0btSuXqrBvS6N0sXJLDqIdM2eHDE7Ear-y4dL5D7n25ppmh-k8VGZPxLc-vJDmuE1PPKY9kTyBVDUEHrFzqd-II2s/w225-h700/computer%20attributes.jpg" width="225" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><i style="font-family: inherit;">Attributes for computers</i><span style="font-family: inherit;"><br /></span></td></tr></tbody></table><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Finally,
I would not consider all faceted structures to be faceted <i>taxonomies</i>. <br /></span></span>
<p class="MsoNormal"><span style="font-family: inherit; font-size: medium;"><span lang="EN-CA">Taxonomies
are primarily for subjects and may include named entities. Content types/document
types may also be included in the scope of taxonomy. There exists additional
metadata that may be desired for filtering/refining searches that is out of
scope of a definition of taxonomy. This includes date published/uploaded, file
format, author/creator, document/approval status, etc. If it is important to the
end users, these additional metadata properties could be included among the browsable
facets and be considered classification aspects.</span></span></p>
<p><span style="font-family: inherit; font-size: medium;"><span>Attributes are a form of faceted classification, but a set of
attributes is not really a faceted taxonomy. Often ecommerce taxonomies are
presented as examples of faceted taxonomies. In fact, ecommerce taxonomies tend
to be hierarchical, as they present categories and subcategories of types of
products for the users to browse. At lower, more specific levels of the
hierarchy, the user then has the additional option to narrow the results
further by selecting values from various attributes that are shared among the
products within the same product category. These include color, size/dimensions,
price range, and product-specific features. I would not consider numeric values
to be a taxonomy, but some attributes, such as for features, are more within the
realm of taxonomies. Whether these should be called facets or attributes is a
matter of debate. More about attributes is discussed in my past blog post
“<a href="https://accidental-taxonomist.blogspot.com/2021/11/attributes-in-taxonomies.htm">Attributes in Taxonomies</a>.”</span></span></p>
<p><span style="font-family: inherit; font-size: large;"><b>Conclusions</b></span></p>
<p style="mso-line-height-alt: 1.2pt;"><span style="font-family: inherit; font-size: medium;"><span>Not all faceted taxonomies are faceted classifications, but some
are. Not all faceted classifications are taxonomies, but some are. The
differences are nuanced, and end-users may not care nor need to know these
naming distinctions, as long as the taxonomist should. Having a deep understanding of
facets helps taxonomists and information architects design the facets better. The goal is to serve the
users with the most suitable faceted design to serve their needs and
accommodate the set of content</span></span><span style="font-family: inherit;">.</span></p>
Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-47811899547537640742024-01-14T13:20:00.007-05:002024-01-15T10:35:07.199-05:00Learning to Create Taxonomies<p style="text-align: left;"><span style="font-size: medium;"><span lang="EN-CA">Knowledge of what taxonomies are, what they
are for, and how they are used is quite widespread, even if there are
uncertainties and disagreements around the definition of “taxonomy.” People who
often look up digital information are familiar with various presentations of
taxonomies for selecting terms linked to content. These include hierarchical
trees of topic and subtopics to browse, scroll boxes of controlled terms, type-ahead
or search-suggest terms that appear below a search box after the first few
letters are typed into the box, and terms or named entities grouped by various
aspect types (facets) in the left margin to select from in order to limit/refine/filter
search results.</span></span></p>
<h2 class="MsoNormal" style="text-align: left;"><span style="font-size: large;"><span lang="EN-CA">Why Learn Taxonomy Creation</span></span></h2>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span lang="EN-CA">There is a big difference, however, between
being able to<i> use</i> taxonomies and being able to <i>create</i> taxonomies.</span></span></p>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span lang="EN-CA">While it is usually best to leave taxonomy
creation to the experts, taxonomists are not always available, or the needed
taxonomy may be small or apparently “simple,” so it may not be economical to
hire a contract taxonomist or a consultant. In other situations, the taxonomy
subject may be quite technical, and it would seem preferable to have subject
matter experts, rather than an external taxonomist, create the taxonomy. <span> </span>Thus, people who are not professional taxonomists
often create taxonomies. </span></span></p>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span lang="EN-CA">Generative AI now makes it easier for
anyone to “generate” a taxonomy. However, the knowledge of taxonomy principles
is needed to make necessary corrections and edit the taxonomy to achieve a decent
level of quality. Generative AI should not be used to fully create a taxonomy (which
could in fact be extracting published taxonomies violating their copyright),
but rather it may be a used as a tool facilitate parts of the taxonomy creation
process. (See my post “<a href="https://accidental-taxonomist.blogspot.com/2023/05/taxonomies-and-chatgpt.html">Taxonomies and ChatGPT</a>.”)
The technology thus makes it easier to create taxonomies for those who are not
taxonomists and have limited time for taxonomy creation tasks. </span></span></p>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span lang="EN-CA">There is also the matter of taxonomy
maintenance. After a contract taxonomist or consultant creates a taxonomy and leaves,
the taxonomy still needs to be kept up to date, with new concepts added and
others changed, and over time expanded. While documentation and guidelines
written by a taxonomy consultant are helpful, a good understanding of taxonomy
creation principles is also needed by anyone responsible for expanding or maintaining
a taxonomy.</span></span></p>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span lang="EN-CA">Finally, taxonomy creation is a collaborative
effort, involving stakeholders in various roles (project management, content management,
digital asset management, information technology tagging, research, user
experience, search, etc.) who are invited to contribute their perspectives. Stakeholders
can provide better insights to a taxonomy if they have a better understanding
of taxonomy principles. Taxonomy project managers in particular need to
understand taxonomy creation even if they are not doing the actual taxonomy creation
work. </span></span></p>
<h2 class="MsoNormal" style="text-align: left;"><span style="font-size: large;"><span lang="EN-CA">How to Learn Taxonomy Creation</span></span></h2>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span lang="EN-CA">Fortunately, there are many resources to
learn the principles and standards of taxonomy design and creation. There is,
of course, my book, <i><a href="http://www.hedden-information.com/accidental-taxonomist" target="_blank">The Accidental Taxonomist</a></i>, <span></span>which, as the name implies, is intended
for anyone who finds themselves, perhaps by “accident” in a position that
requires them to create, edit, or manage taxonomies. </span></span></p>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span lang="EN-CA"></span></span></p><div style="text-align: left;"><span style="font-size: medium;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiLTB9oLY2ltTIpz9u84HXpCAdDFa7gn-K_sAjEJgTZbGiFGk_E2tJHjtqF5MruXvKly2xfjIsiUs8KFRJU5ggAmtMqmZ58FeQAJfeWVJaeo0FSCYZmNc0UxBzFeWGCVs1UaOZ905XoClSCTJErCqwKVrfBgSHyJKqAorxe-65gWrb1hMbejopnJ4S4gLM/s5040/804A4623-heather-hedden.jpg" style="clear: left; margin-bottom: 1em;"></a><span style="font-size: medium;"><span lang="EN-CA"><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-RhsPUFmowN_xdMjsamRkRTMXlqhyw3l5G0B7b1GGaLVO8Dju6IztKLjbKtl7sqtSneXGkgr-N5QZ9093_Uk8gklJypndE1vDrSB84n8oouhtqHOhrf4DPt63KRpb0gn0iCNUAeKjhHuiAOVA8e1KC7rZYRs7LGrLT-mqJ-fd93jlCYXk8-LOHPq33QM/s5040/804A4623-heather-hedden.jpg" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img alt="Heather Hedden delivering a taxonomy workshop" border="0" data-original-height="3360" data-original-width="5040" height="213" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-RhsPUFmowN_xdMjsamRkRTMXlqhyw3l5G0B7b1GGaLVO8Dju6IztKLjbKtl7sqtSneXGkgr-N5QZ9093_Uk8gklJypndE1vDrSB84n8oouhtqHOhrf4DPt63KRpb0gn0iCNUAeKjhHuiAOVA8e1KC7rZYRs7LGrLT-mqJ-fd93jlCYXk8-LOHPq33QM/w320-h213/804A4623-heather-hedden.jpg" title="Heather Hedden delivering a taxonomy workshop" width="320" /></a></div>There are also various half-day and
full-day workshops at conferences, virtual short courses through professional
associations and other organizations, and asynchronous online training. These
usually involve some exercises for practice and provide the appropriate amount
of training for getting started with creating taxonomies. I’ve offered various
kinds of training, both independently and through other organizations, over the
years. My current <a href="http://www.hedden-information.com/courses-workshops/" target="_blank">course offerings</a> are on my website </span></span><br /></span></div><p></p>
<h2 class="MsoNormal" style="text-align: left;"><span style="font-size: large;"><span lang="EN-CA">Upcoming Taxonomy Course</span></span></h2>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span lang="EN-CA">The next live (virtual) course I will offer
is a new course called “<a href="https://www.henrystewartconferences.com/events/controlled-vocabularies-and-taxonomies" target="_blank">Controlled Vocabularies and Taxonomies</a>”
offered through <a href="https://www.henrystewartconferences.com/events/courses" target="_blank">HS Events</a>,
on GoToWebinar over four weekly sessions from February 29 though March 27. I
will teach this course live (with ample time for Q&A) just once, after which
it will become available as a recording for purchase. </span></span></p>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span lang="EN-CA">HS (Henry Stewart) Events are best known
for their dominance in the field of digital asset management (DAM), but the
course I will teach is not limited to DAM professionals. Actually, this course
is most appropriate for the expanding scope of HS Events, which will introduce
a Semantic Data conference event, which includes the subject of taxonomies, co-located
with its DAM conferences in <a href="https://henrystewartconferences.com/events/semantic-data-2024">London</a> and New York in 2024. </span></span></p>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span lang="EN-CA">The subject of taxonomies fits nicely into
four sessions. The first session is an introduction to the definitions, types,
uses, benefits, and standards for taxonomies. The second deals with project
management side of planning and researching for creating controlled
vocabularies and taxonomies. The third session gets into the details of creating
terms and relationships. Finally, the fourth session takes up design and
implementation issues.</span></span></p>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span lang="EN-CA">This course is most similar to the course
"Metadata and Taxonomies" which I had taught through the Rome,
Italy-based training company Technology Transfer S.r.l from 2019 to 2023, and
which I decided to discontinue offering. The scheduling is now better: Instead
of two consecutive days of four hours/day it is spread out over four weekly
shorter sessions with a dedicated encouraged Q&A time. Also, the sessions
start two hours later than the Rome-based course (10:00 am instead of 8:00 am
EST). I have also updated the content, which was getting a little stale after
several years, and I added more new graphics. Finally, the registration fee is
considerably lower than the Technology Transfer course. You can also take advantage of a 20% discount (code JANUARY20) if you register before January 31.</span></span></p>
Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-62678479437451251942023-12-31T13:47:00.006-05:002024-01-13T20:50:04.351-05:00IT and Taxonomies<p><span style="font-family: times;"><span style="font-size: medium;"></span></span><span style="font-family: times;"><span style="font-size: medium;">Taxonomies are related to many fields of work, including knowledge management, information architecture, website design, website marketing at SEO, document management, terminology management, publishing, product management (for information products), content management and strategy, digital asset management, machine learning for classification, natural language processing for auto-tagging, data management, library and information management, and information technology. Information technology is relevant to the implementation of all taxonomies.</span></span></p><h2 style="text-align: left;"><span style="font-family: times;"><span style="font-size: large;">Why is IT involved in taxonomies?</span></span></h2>
<div class="separator" style="clear: both; text-align: left;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhByv7fLmDUnN-xXmDzjeuOSVtyx5DPM2wRXTQMSIYti_rZqSTijcF7i-HQK0mx52UKjaJAs_UWOjKcwwTjctAWJg8J1tJxqqf0m7AQgKxlVxUNVdi0ykCCNviIQZNGtVRSXH8nhYHD0HMMs-dmXQ1p7lQPnwFKv7nklYSuQRFhtI9cSZ8EACLYHiasS9U/s800/Devices%20for%20IT.png" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="512" data-original-width="800" height="205" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhByv7fLmDUnN-xXmDzjeuOSVtyx5DPM2wRXTQMSIYti_rZqSTijcF7i-HQK0mx52UKjaJAs_UWOjKcwwTjctAWJg8J1tJxqqf0m7AQgKxlVxUNVdi0ykCCNviIQZNGtVRSXH8nhYHD0HMMs-dmXQ1p7lQPnwFKv7nklYSuQRFhtI9cSZ8EACLYHiasS9U/s320/Devices%20for%20IT.png" width="320" /></a>
<span style="font-size: medium;"><span style="font-family: times; font-size: medium;">Taxonomies link users to content (and taxonomies extended into ontologies also link users to data), but this linking relies on technology. The technology could be a kind of software, such as a content management system that supports the tagging and retrieval of content by taxonomies along with the feature of taxonomy management. Often, however, additional technology is needed to link multiple software systems together, with APIs, and to move data across systems, with extract-transform-load (ETL) tools. Taxonomies are increasingly built in the SKOS (Simple Knowledge Organization System) standard/data model, which enables taxonomies and other knowledge organization systems to be machine-readable and not just human readable.</span></span><p></p><p><span style="font-family: times; font-size: medium;">Taxonomies are a concern of information technology professionals as they are the owners of, and often also the developers of, the systems in which taxonomies are implemented. The systems could be completely internally developed, or they could be licensed software that typically requires some customization or integration with other systems. In my experience as a taxonomy consultant, I have typically engaged in conversations with those in IT as key stakeholders of the taxonomy. However, the degree of the involvement of IT professionals in the taxonomy itself can vary.</span></p><p><span style="font-family: times;"><span style="font-size: medium;">In custom taxonomy implementations, such as in an information service/product or in an ecommerce business, IT professionals are usually not involved in the actual design of the taxonomy, but taxonomists or others who create that taxonomy need to collaborate with IT professionals to understand the system’s capabilities and limitations and may impose requirements. Taxonomists are concerned with how the taxonomy will be displayed to the users, how the users can interact with the taxonomy, how tagging is done, and how the search functions. Custom software development has great flexibility in how it supports a taxonomy.<br />In implementations of taxonomies in licensed software, there may still be some development work for the IT professionals, but there are limits to what can be done or changed.</span></span></p><p><span style="font-family: times;"><span style="font-size: medium;">Commercial content management systems (CMS) that allow for the custom development of the user interface, referred to as “headless” CMSs, however, are becoming more common. The user interface in particular is very significant to how a taxonomy is designed and how it functions.</span></span></p><h2 style="text-align: left;"><span style="font-family: times;"><span style="font-size: large;">Who in IT is involved in taxonomies?</span></span></h2><p><span style="font-family: times;"><span style="font-size: medium;">Those who work in IT departments with involvement taxonomies could be in roles doing development or support for systems that manage and consume taxonomies, or they could be in systems integration roles. Additionally, there are taxonomy/metadata/ontology specialists who work within the IT department of an enterprise, especially if a knowledge/information management department does not exist in the organization.</span></span></p><p><span style="font-family: times;"><span style="font-size: medium;">In a <a href="http://www.hedden-information.com/accidental-taxonomist/taxonomist-survey/">survey of taxonomists</a> I conducted in January 2022 for the 3rd edition of<i> The Accidental Taxonomist</i> book, of 162 people who do taxonomy work for their employers, which are not consultancies creating taxonomies for others, a multiple-choice question asked what area they work in. Information technology ranked 4th out of 11 choices, with 17% of the responses, following the areas of knowledge management, content management/strategy, and product development/management, yet ahead of the specialties of library, user experience, marketing, and others.</span></span></p><p><span style="font-family: times;"><span style="font-size: medium;">The survey also asked all respondents to provide their job titles, and some of those working in taxonomies have job title that are closely associated with information technology. These included titles of IT Data Analyst, Data and Technology Platform Products, SharePoint Product Owner, Senior Solutions Consultant, Implementation Project Manager, Data Architect, Senior Manager - Graph Solutions, Enterprise Architect, Staff Engineer - Systems, Information Governance Engineer, Head of Technical Services, and Director of Solutions Delivery.</span></span></p><h2 style="text-align: left;"><span style="font-family: times;"><span style="font-size: large;">What does IT do with taxonomies?</span></span></h2><p><span style="font-family: times;"><span style="font-size: medium;">From my experience as a taxonomy consultant, I have observed that those working in IT, in their efforts to facilitate the adoption of new software and features that make use of taxonomies, may include starter taxonomies within the tool, whether selected from offerings of software vendor or created by the IT staff themselves. For example, IT professionals might create simple controlled vocabularies in the SharePoint term store, such as for document types, departments, locations, etc., so that users can start using the search refinements right away, and there is also an example of the functionality of taxonomy, which can be improved upon and expanded by someone else later.</span></span></p><p><span style="font-family: times;"><span style="font-size: medium;">Then there is enterprise taxonomy/ontology management software, which should be connected to search systems, content management systems, and tagging systems (if not using a tagging module of the taxonomy management system). In my experience working for a taxonomy software vendor, the IT department was often involved in the software purchasing process, if not actually leading the decision-making. Representatives from the IT department attend pre-sales demos of the tool, ask questions, and compile and compare system requirements when requesting a proposal.</span></span></p><p><span style="font-family: times;"><span style="font-size: medium;">That taxonomy is actually an area concern of IT, was also made clear when I saw that taxonomies were mentioned in a section within a chapter on knowledge management-related systems in my son’s introductory Management Information Systems textbook for a required course for his B.S. in Information Technology.</span></span></p><p><span style="font-family: times;"><span style="font-size: medium;">In sum, IT professionals who support enterprise knowledge or information management systems need to have a basic understanding of taxonomy principles, standards, benefits, and uses. My <a href="http://www.hedden-information.com/">website</a> contains various taxonomy resources. Some IT professionals may even want to go further and design and create small taxonomies (lacking the time to create large taxonomies), and they may want to read my book or attend my <a href="http://www.hedden-information.com/courses-workshops/">workshops or online courses</a>. </span><br /></span></p></div>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-69010523778143605202023-11-30T18:04:00.036-05:002023-12-31T17:33:04.375-05:00Generative AI at Taxonomy Boot Camp Conference<p><span lang="EN-CA" style="font-family: times; line-height: 107%;"><span style="font-size: medium;">Generative AI and
large language models (LLMs), the technology behind ChatGPT, have been topics of presentations, keynotes, and
attendees’ conversations at all the varied conferences I had the fortune to attend this year,
including the <a href="https://taxonomybootcamp.com/2023/default.aspx" target="">Taxonomy Boot Camp</a> conference
held November 6-7, in Washington, DC. Taxonomy Boot Camp is the only conference
dedicated to taxonomies. </span></span></p>
<h3 style="margin: 0in; text-align: left;"><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjL9bq3sSFsjaVEKasDKgYFHCKUqn87ERikhph97UHdGu174VZ2xv2ksx9pKK6tTMEgHL4T0CCncFS0mGNGgGIl6viRRaHo8OEjCjGsPkLz_gbZLbdV4ZFBCCVEY1zasNQdtwZH7DEtJzpsFR88LZF2u-r9o3r3YwCIl1UoTlGT3D2FJnHXY_HE84_jB3Q/s1887/20231204_174057.jpg" style="font-family: times; margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1392" data-original-width="1887" height="295" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjL9bq3sSFsjaVEKasDKgYFHCKUqn87ERikhph97UHdGu174VZ2xv2ksx9pKK6tTMEgHL4T0CCncFS0mGNGgGIl6viRRaHo8OEjCjGsPkLz_gbZLbdV4ZFBCCVEY1zasNQdtwZH7DEtJzpsFR88LZF2u-r9o3r3YwCIl1UoTlGT3D2FJnHXY_HE84_jB3Q/w400-h295/20231204_174057.jpg" width="400" /></a></div></h3><h2 style="text-align: left;"><span style="font-family: times;">Opening
and Keynotes</span></h2>
<p style="margin: 0in;"><span style="font-family: times;"> </span></p>
<p style="margin: 0in;"><span style="font-family: times; font-size: medium;">Right
from the beginning in the opening welcome, the conference chair <a href="https://www.dovecotstudio.com/team/stephanie-lemieux/">Stephanie Lemieux</a>
mentioned uses of ChatGPT for taxonomy creation, such as asking prompts: <span style="color: black;">What is a category for a following list of terms</span>?, What
label for a concept might be better for scientists, or better for parents?,
and What are alternative labels for a specific content? It has become clear
that generative AI is a tool to assist taxonomists with specific tasks of a
project but is not appropriate for automating the entire creation of a taxonomy.
Thus, the Taxonomy Boot Camp theme this year, “Humans in the Loop,” was quite
apt for the new era of generative AI, even if not specific to it.</span></p>
<p style="margin: 0in;"><span style="font-family: times; font-size: medium;"><span style="color: black;"> </span></span></p>
<p style="margin: 0in;"><span style="font-family: times; font-size: medium;"><span style="color: black;">The Taxonomy Boot Camp opening keynote, “<a href="https://conferences.infotoday.com/documents/440/0910_Allemang.pptx" target="_blank">Ontologies in the New Age of AI</a>”</span><span style="color: black;">
by Dean Allemang, was on this subject. Dean is more of an ontologist than a
taxonomist, hence the title, but he discussed both taxonomies and ontologies. Allemang
made the statement that Generative AI “understands” why we need a taxonomy</span>
(even if managers do not). He explained that Schema.org has put RDF on many
websites, which ChatGPT “reads.” Allemang has found that ChatGPT also
performs perfectly on SPARQL queries, the query language for data, including
taxonomies, that is in RDF. Allemang gave ChatGPT query examples, such
as “Return all the claims we have by claim number, open date, and close date,”
and “What is the total loss of each policy where loss is the sum of loss payment,
loss reserve, expense, payment, and expense reserve amount?” Allemang
advised taxonomists to identify uses for taxonomies that have not been fully
delivered on and use generative AI to deliver it, and if people argue that generative
AI does not understand their language, taxonomists should<span lang="EN-CA" style="color: black;"> build in a link to the taxonomy that makes generative
AI understand it.</span></span></p><p style="margin: 0in;"><span style="font-family: times; font-size: medium;"><span lang="EN-CA" style="color: black; font-weight: normal;"> </span></span></p><p style="margin: 0in;"><span style="font-family: times; font-size: medium;"><span lang="EN-CA" style="color: black; font-weight: normal;">On the
second day, Taxonomy Boot Camp registrants <span> </span>attend the same shared keynote presentations
with all of the KMWorld co-located conferences, and this year these mostly dealt
with generative AI, including the opening keynote by Dion Hinchcliffe “</span><span style="font-weight: normal;"><a href="https://taxonomybootcamp.com/2023/program.aspx#16235" target="_blank">Tech-Driven Enterprise Thrills & Chills: The Future of
Work</a></span>.” </span></p><div style="text-align: left;"><span style="font-family: times; font-size: medium;"><br /></span></div><div style="text-align: left;"><h2 style="text-align: left;"><span style="font-family: times;">Regular Sessions <br /></span></h2></div>
<p style="text-align: left;"><span style="color: black; font-family: times; font-size: 12pt; font-weight: normal;"></span></p>
<p style="text-align: left;"><span style="font-family: times; font-size: medium;"><span style="color: black; font-weight: normal;">In addition to being mentioned in various talks,
generative AI was also the subject of a session, “</span><a href="https://taxonomybootcamp.com/2023/program.aspx#16205"><span style="font-weight: normal;">ChatGPT, Taxonomist: Opportunities & Challenges in
AI-Assisted Taxonomy Development</span></a>,”
which comprised two separate presentations.</span></p>
<p style="text-align: left;"><span style="font-family: times; font-size: medium;"><span style="color: black; font-weight: normal;">In this session, Xia Lin presented in “<a href="https://conferences.infotoday.com/documents/440/1345_Lin.pptx">Chat GPT and Generative AI for Taxonomy Development</a>”
in which he discussed the steps involved in using ChatGPT in two case studies. In
one, a taxonomy for data analytics projects of a small business was developed
by providing ChatGPT with the scope of the first level of the taxonomy and then
asking ChatGPT to expand individual categories by adding subcategories and then
to add definitions of terms and categories. The results were reviewed and
revised by experts. But Lin did not stop there. He showed the results of asking
ChatGPT to provide stakeholder interview questions around a category, and (for
those more technically inclined) how to create a ChatGPT plug-in for various
defined functions of taxonomy creation, using ChatGPT’s APIs. </span></span></p><p style="text-align: left;"><span style="font-family: times; font-size: medium;"><span style="color: black; font-weight: normal;">Also in “<a href="https://conferences.infotoday.com/documents/440/1345_Kotula.pptx">ChatGPT and Generative AI for Taxonomy Development</a>”
Marjorie Hlava and Heather Kotula jointly presented on issues of the use of
ChatGPT to create taxonomies and in general. They explained the risks of bias, plagiarism,
ethics, data quality, matching the generated taxonomy to the content, and the
amplification of errors upon repeating a prompt. In plagiarism, for example, if
you ask ChatGPT to return a complete taxonomy on a subject domain in may return
a copyrighted taxonomy that cannot be reused without a license.</span></span></p><p style="text-align: left;"><span style="font-family: times; font-size: medium;"><span style="color: black; font-weight: normal;">Generative AI also impacts the topics of other presentations.
For example, in the presentation “</span><span style="font-weight: normal;"><a href="https://conferences.infotoday.com/documents/440/1330_Griffin.pptx">In Taxonomy We Trust: Building Buy-In for Taxonomy Projects</a>,” Bonnie Griffin mentioned the importance of “<span class="description">continually
re-introducing the value of taxonomy, as generative AI captures attention</span>.”
It was also the subject of a debate question in somewhat humorous closing
sessions “</span><span style="font-weight: normal;"><a href="https://taxonomybootcamp.com/2023/program.aspx#16209">Taxonomy Showdown—Point/Counterpoint With Taxonomy Experts</a>.”</span></span></p><p style="text-align: left;"><span style="font-family: times; font-size: medium;"><span style="font-weight: normal;"> </span></span><br /></p><h2 style="text-align: left;"><span style="font-family: times;">More on Taxonomies and AI<br /></span></h2><p style="text-align: left;"><span style="font-family: times; font-size: medium;">Of
course, there is more to AI than just generative AI. Other sessions dealt with
machine learning for auto-categorization. These included presentations by each Bob
Kasenchak and Rachael Maddison in the session “<a href="https://taxonomybootcamp.com/2023/program.aspx#16200">Machine Learning Is Coming forYour Taxonom</a>y,” (link to
<a href="https://conferences.infotoday.com/documents/440/1515_Kasenchak.pptx">Bob’s slides</a>)
and Wytze Vlietstra’s presentation of “<a href="https://taxonomybootcamp.com/2023/program.aspx#16201">Vision for Modular Taxonomy Product at Elsevier</a>,” in which the program
included<span class="description"> “shared infrastructure supported by AI-based
decision support tools</span>.” In fact, AI has been a theme of Taxonomy
Boot Camp in the past, in 2018. It is generative AI based on large language models
that is new. </span></p><p style="text-align: left;"><span style="font-family: times; font-size: medium;">For some more details on how this technology may be used for taxonomy
development, see my prior blog post this spring </span><span style="font-family: times; font-size: medium;">“</span><span style="font-family: times; font-size: medium;"><a href="https://accidental-taxonomist.blogspot.com/2023/05/taxonomies-and-chatgpt.html">Taxonomies
and ChatGPT</a>.</span><span style="font-family: times; font-size: medium;">”</span><span style="font-family: times; font-size: medium;"> <span>To get another perspective on this conference, check out the recent blog post by Taxonomy Boot Camp speaker Mary Katherine Barnes </span></span><span style="font-family: times; font-size: medium;">“</span><span style="font-family: times; font-size: medium;"><span><a href="https://www.icpnet.com/resources/blog/ai-taxonomy-bootcamp">Integrating AI: Insights from KMWorld 2023.</a></span></span><span style="font-family: times; font-size: medium;">”</span></p>
Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-33519179273749243382023-10-31T23:25:00.012-04:002024-02-24T19:59:55.996-05:00Taxonomies for Learning and Training Content<p></p><div class="separator" style="clear: both; text-align: center;"><span style="font-size: medium;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgE5y1s9ku8eUxphb5nZOQxN0fg7BinYw5ZO3HVOQcF5yIwV3E0LvJ_PP0D7O6env_PGDQL7V13m3ayE5fZaF4_DalYSxbwt8wLNnbM1QnKrUQOgdSTX6WlpXiBCVdEiVV2jJI4PkQsO63fOgEU4EVdmfXg-I6I6Xm-r7dkjiDyQFNI5vYQ_sxF7ykUITA/s766/Training%20image.jpeg" style="clear: left; float: left; font-family: times; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="550" data-original-width="766" height="230" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgE5y1s9ku8eUxphb5nZOQxN0fg7BinYw5ZO3HVOQcF5yIwV3E0LvJ_PP0D7O6env_PGDQL7V13m3ayE5fZaF4_DalYSxbwt8wLNnbM1QnKrUQOgdSTX6WlpXiBCVdEiVV2jJI4PkQsO63fOgEU4EVdmfXg-I6I6Xm-r7dkjiDyQFNI5vYQ_sxF7ykUITA/s320/Training%20image.jpeg" width="320" /></a></span></div><p style="text-align: left;"><span style="font-family: times; font-size: medium;">Taxonomies are primarily for tagging digital content to make it more easily found when users search or browse on taxonomy concepts. Content can be of various kinds: articles and research reports, policies and procedures, technical documentation, product information, contracts and other legal documents, marketing content, etc. A growing area of digital content is instructional or training content, especially corporate training for employees.</span><span style="font-family: times; font-size: medium;"> </span><span style="font-size: medium;"><span style="font-family: times;"><br /></span></span></p><h2 style="text-align: left;"><span style="font-family: times; font-size: large;">The need for taxonomies for training content</span></h2><p><span style="font-family: times; font-size: medium;">When an organization offers its employees a large number of training courses, it can be difficult for employees to find desired training. Having the training content tagged with controlled terms from a taxonomy makes it easier to find.</span></p><p><span style="font-family: times; font-size: medium;">The training content may come from different sources and thus may come with different, inconsistent metadata already applied to it. An organization may have generic training (such as on diversity and information security) produced by a corporate training company, industry-specific training (such as anti-money laundering for financial services and retail industries) produced by a different training company, and company-specific training which is internally produced. An organization may also subscribe to an offering of business skills and technical skills training offered by one ore more third party, such as LinkedIn Learning. It may be very difficult to search across all these different sources.</span></p><p><span style="font-family: times; font-size: medium;">Furthermore, simply searching on words in training course titles might not be effective, if topics are broad or the course titles are vague. For example, a search on “communication” may yield far too many results to sort through. A search on “writing” might miss a training course with a title of “Bringing out Your Voice” or “Use Plain Language.” Tagged with the concept of “Writing,” these courses can then be found.</span></p><h2 style="text-align: left;"><span style="font-family: times; font-size: large;">Faceted taxonomies for training content</span></h2><table cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: left;"><tbody><tr><td style="text-align: center;"><span style="font-size: medium;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi2thvvxvxGLLCCHpDEKqGBgkrjuAal8mCaVmK4Ivm2EkSqHvljjug0gTscybICkDREYUoEWTLFXFne4Z5eK-pZ3GgsZc_8KZQdZ3hoAXqKa21i6xYUWgf7RVwoSQTXXlwHFV5GgciOZcSFVvkEPoPFmDzmY2cfiYqHVaXIAfOrLb7DjVJTmnopPYLTagw/s828/learning%20taxonomy.png" style="clear: left; font-family: times; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img border="0" data-original-height="828" data-original-width="376" height="587" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi2thvvxvxGLLCCHpDEKqGBgkrjuAal8mCaVmK4Ivm2EkSqHvljjug0gTscybICkDREYUoEWTLFXFne4Z5eK-pZ3GgsZc_8KZQdZ3hoAXqKa21i6xYUWgf7RVwoSQTXXlwHFV5GgciOZcSFVvkEPoPFmDzmY2cfiYqHVaXIAfOrLb7DjVJTmnopPYLTagw/w266-h587/learning%20taxonomy.png" width="266" /></a></span></td></tr><tr><td class="tr-caption" style="text-align: center;"><span style="font-size: medium;"><span style="font-family: times;"><i>Sample faceted taxonomy for<br />training content in <a href="https://www.poolparty.biz/" target="_blank">PoolParty</a></i><br /></span></span></td></tr></tbody></table><span style="font-size: medium;"><span style="font-family: times;">For the complexities of training content, a single topical taxonomy is
not enough. There could be ambiguity as to the skill level or between
training topic and training format. For example, the topic of “Manager
training” is not clear as to whether it is for new managers or all
managers. The topic of “Presentation slides” is not clear as to whether
it is training on how to create presentation slides or if presentation
slides is the training format/medium. This is where a faceted taxonomy
can help. Facets are different aspects of content which can be combined
as search filters.</span></span><p><span style="font-size: medium;"><span style="font-family: times;">Training content is especially well suited for facets. Examples of
possible facets for training content are: Content type, Level, Role,
Skill, Training Program, and Topic. An example of taxonomy terms in
each facet are as follows:<br />• Content type: Video training<br />• Level: Intermediate<br />• Role: Customer support<br />• Skill: Written communication<br />• Training program: Upskilling<br />• Topic: Timeliness</span></span></p>
<p><span style="font-size: medium;"><span style="font-family: times;">It’s important to keep in mind that facets should be mutually
exclusive, so the same concept, such as “Customer support,” cannot exist
in both the Role and the Skill facets. Distinguishing a role and a
skill can sometimes be difficult. It important to separate out Role,
though, because then there is the possibility to recommend training
courses based on one’s Role.</span></span></p>
<p><span style="font-size: medium;"><span style="font-family: times;">Taxonomy facets are based on metadata properties, but there likely
exist many more metadata properties than needed for the end-user to
filter train content searches. Additional, administrative metadata
properties should not be implemented on the front-end for course
searches. These might include Organizational unit, Original source,
Region, Access Level, etc.</span></span></p><h2 style="text-align: left;"><span style="font-family: times; font-size: large;">Skills taxonomy sources and challenges</span></h2><p><span style="font-family: times; font-size: medium;">Developing a skills taxonomy facet has its own challenges. First of all, there are multiple goals of skills taxonomies. Enabling employees or their managers to find appropriate training is just one goal. Other purposes may be to describe job openings to found by candidates with matching skills, to find an expert with a desired skill to ask question of or have work on a project, or to map roles and skills to identify gaps and improve human resources strategies and professional development programs.</span></p><p><span style="font-family: times; font-size: medium;">There are also varied sources for skills taxonomies. Managers and subject matter experts would list certain skills, which might differ from a list of skills proposed by human resources staff. A taxonomist, metadata specialist, or information architect working on a taxonomy would come up with a slightly different list of skills, probably not as detailed. Finally, there are external sources, but these might not be appropriate to a specific organization. The largest, best known published taxonomy of skills is <a href="https://esco.ec.europa.eu/en" target="_blank">ESCO (European Skills, Competences, Qualifications, and Occupations)</a>, but with 13,890 skills, it is much too large and detailed for any one organization. It might be best to start with any skills list that the HR department has and build it out further with recommendations from managers, but not as detailed as some subject matter experts might suggest. External sources could be consulted to fill in some gaps.</span></p><p><span style="font-family: times; font-size: medium;">There is the potential to get too detailed in creating a hierarchy of skills, and some of the narrower concepts may end up being specific topics and not exactly skills. For example, a skill of project management could get narrower concepts for different project management methodologies and then various components of each methodology. This is would not be appropriate for a skills taxonomy, although, if important, these narrower concepts could be included in a Topics facet instead.</span></p><h2 style="text-align: left;"><span style="font-family: times; font-size: large;">Presentations on taxonomies for corporate training content</span></h2><p><span style="font-family: times; font-size: medium;">My most recent conference presentation and my next conference presentation are both about taxonomies for corporate training content. On October 16, I presented at the<a href="https://lavacon.org/" target="_blank"> LavaCon</a> content strategy conference in San Diego “<a href="http://www.hedden-information.com/wp-content/uploads/2023/10/LavaCon-2023-Leveraging-Semantics-to-Provide-Targeted-Training-Content.pdf" target="_blank">Leveraging Semantics to Provide Targeted Training Content: A Case Study</a>,” which was jointly presented with <a href="https://www.poolparty.biz/" target="_blank">PoolParty</a> software proof-of-concept project customer Esther Yoon of Google gTech. In addition to some of the issues described in this blog post, I also discussed how facets can be customized and how roles and skills can be linked for recommendation, and Esther presented how the POC improved the discovery of training content for those in roles related to customer support. <br /></span></p><p style="text-align: left;"><span style="font-family: times; font-size: medium;">On November 6, at <a href="https://taxonomybootcamp.com/2023/default.aspx" target="_blank">Taxonomy Boot Camp</a> conference in Washington, DC, I will present “<a href="http://www.hedden-information.com/wp-content/uploads/2023/11/TBC-Taxonomies-for-Learning-Development.pdf" target="_blank">Challenges in Creating Taxonomies for Learning & Development</a>,” which will be jointly presented with Amber Simpson of Walmart’s Walmart Academy, also a PoolParty software customer. In addition to issues described here, I will also provide specific examples of challenges in creation a Skills taxonomy facet. The slides will also be made available afterwards.</span></p><span style="font-size: medium;"><span style="font-family: times;"><br /></span></span>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-67049168757464429312023-09-30T17:30:00.069-04:002023-12-30T17:22:38.901-05:00SEMANTiCS Conference 2023: Taxonomies, Knowledge Graphs, and LLMs<div style="text-align: left;"><span style="font-family: inherit;"><div style="text-align: center;"><span style="font-size: medium;"><br /></span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" dir="rtl" style="clear: both; text-align: left;"><span style="font-size: medium;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2SHTyUAAKqtc8DysnqCG6k0HkFSyNAXiUDasLX4i9ZjDe1W3cJ5klCa9JfR-gjUOSSggzNr7Nnkr3et5uuDfpAWqniOVmMyPNdQ-ZqWXPxxn7z8xRsNVvg6rO9E43sO8_8LD1-AXacS5dGzH-Y5Ny6wv_L8nOnNDCMmcUG6xaBSWnfOeRCuM14WZ1E1Q/s4608/B6A9D38E-72D8-43C7-AF08-322DCC526AC4.jpeg" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="3456" data-original-width="4608" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2SHTyUAAKqtc8DysnqCG6k0HkFSyNAXiUDasLX4i9ZjDe1W3cJ5klCa9JfR-gjUOSSggzNr7Nnkr3et5uuDfpAWqniOVmMyPNdQ-ZqWXPxxn7z8xRsNVvg6rO9E43sO8_8LD1-AXacS5dGzH-Y5Ny6wv_L8nOnNDCMmcUG6xaBSWnfOeRCuM14WZ1E1Q/s320/B6A9D38E-72D8-43C7-AF08-322DCC526AC4.jpeg" width="320" /></a></span></div><p style="text-align: left;"><span style="font-size: medium;">The most recent conference I participated in was <a href="https://2023-eu.semantics.cc" target="_blank">SEMANTiCS</a>, September 20-22, in Leipzig Germany. This was the 19th year of this European conference focused on the application of semantic technologies and systems. This was also my fourth year presenting a workshop/tutorial on taxonomies and ontologies at the conference. The widespread value of taxonomies across different areas of specialization is indicated by the fact that taxonomy workshops are repeatedly a part of conferences on various subjects, including semantics, knowledge management, library and information science, information architecture, content strategy, and digital asset management.</span></p><p style="text-align: left;"><span style="font-size: medium;"><br /></span></p></div></span></div><h2><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><h3 style="text-align: left;"><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">Semantics and taxonomies</span></h3></span></h2><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><div><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"></span></div></span><p style="text-align: left;"><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"></span></p><p dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><span>Semantics means “meaning,” so semantic systems utilize standards to support the encoding of meaning of things/resources and their relations, making the semantics machine-readable. Various standards, guidelines, and data models for semantic systems were developed for what is called the Semantic Web. The Semantic Web goes beyond the simple hyperlinks of the World Wide Web to label shared metadata, specify the kinds of relations. This supports linked data, and the linking of taxonomies to other taxonomies and ontologies and their tagged content or data, which are stored on different servers. </span></span></span></p><br /><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><p dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><span>Just as World Wide Web protocols have been adapted within enterprises (“behind the firewall”), so have Semantic Web standards. You don’t have to share your data publicly to reap the benefits of the Semantic Web: open standards to enable the migration of taxonomies and related data between systems, sharing of data with partners, extracting and transforming data from within silos across the enterprise into a standard format, and the ability to link to data on the Web to bring in new content even if not sharing content out on the Web.</span></span></p></span><br /><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><p dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><span>Taxonomies, as controlled vocabularies, have always been about concepts, each with unique understood meaning, not just words or strings of text. So, using taxonomies is using semantics. The Semantic Web standard SKOS (Simple Knowledge Organization System) specifies a data model to make taxonomies and other knowledge organization systems (thesauri, classification systems, etc.) machine-readable and interchangeable on the Web. Semantic Web standards also cover ontologies with RDF-Schema and OWL. By following Semantic Web Standards, taxonomies can easily be linked to and extended with ontologies, and then by linking to data stored in a graph database, knowledge graphs can be built.</span></span></p></span><p></p><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><br /></span><h2><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><h3 style="text-align: left;"><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">The SEMANTiCS conference</span></h3></span></h2><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><div><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"></span></div></span><p style="text-align: left;"><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"></span></p><p dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><span>The SEMANTiCS conference is somewhat unique by being semi-academic and semi-industry. It has separate academic track and industry track chairs and additional tutorials and workshops. It’s good to bring academia and industry together in a field like this, where research topics can be applied and partnerships can be developed. The location of the conference varies, and it partners with a local higher education institution for logistical support, with graduate students volunteering to help in exchange to getting access to sessions. </span></span></span></p><br /><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><p dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><span>This was the second year that SEMANTiCS combined its conferences with the Language Technology Industry Association, which organized a Language Intelligence track, dealing with technologies for the management of terminology, multilingual content, and machine translation. The conference also includes a one-day track focused on DBpedia, which is not the same first day as the tutorials and workshops. The entire conference lasts three full days, and has a social event one evening, and a dinner on the second evening. </span></span></p></span><br /><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><p dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><span>The conference has industry vendor sponsors, about eight of which were exhibiting, and a few more which did not exhibit. There are also slightly more organizations which are “partners,” including DBpedia, The Alan Turing Institute, and a number of institutes of higher education in Europe which have programs in semantic technologies. Additional organizers include Semantic Web Company, Institut für Angewandte Informatik and the Vjije Universities Amsterdam, representing the three countries where SEMANTiCS has been taking place: Austria, Germany, and Netherlands. </span></span></p></span><p></p><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><span><br /></span></span><h2><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><h3 style="text-align: left;"><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">SEMANTiCS 2023</span></h3></span></h2><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><p dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><span></span></span></p></span><p style="text-align: left;"><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"></span></p><p dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><span>The 2023 conference was held September 20-22 in Leipzig, Germany, under the leadership of a new chair Sahar Vahdati of Technical University Dresden. There were about 285 participants in person and about one-third as many online. The conference has been hybrid since 2021. There were often six simultaneous sessions. Themed tracks or sessions of multiple speakers included Knowledge Graphs, Reasoning & Recommendation, Natural Language Processing and Large Language Models, Legal & Data Governance, Ontologies Data Management, and Environmental-Social-Governance (ESG). While there was not a life sciences track like last year, there was a themed subject track on cultural heritage. LLMs and ESG were both new topics this year. Poster presentations also covered the range of topics. </span></span></span></p><br /><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><p dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"><span><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">Knowledge graphs is a regular theme at this conference, but this time there was the addition of LLMs. The opening keynote was “Generations of Knowledge Graphs: The Crazy Ideas and the Business” presented by Xin Luna Dong of Meta. </span><span face="Helvetica, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">She spoke of three generations of knowledge graphs: entity-based knowledge graphs, text-rich knowledge graphs, and dual neural knowledge graphs, using an ontology and LLMs. The second day’s keynote was “Knowledge Graphs in the Age of Large Language Models,” presented by Aiden Hogan of the University of Chile.</span><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"> LLMs and AI topics were also presented in the Knowledge Graphs track, such as in Andreas Blumauer’s talk “Responsible AI and LLMs.” Finally, the moderated closing panel was “Large Language Models and Knowledge Graphs: Status Quo - Risks - Opportunities” with panelists, Andreas Blumauer and Jochen Hummel from software vendors and Kristina Podnar, a digital policy consultant, who were not completely in agreement.</span></span></p></span><br /><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><p dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><span>In addition to my 3-hour tutorial, “Knowledge Engineering of Taxonomies and Ontologies,” only slightly updated from last year, I also contributed, along with Lutz Krüger, to Andreas Blumauer’s new 3-hour tutorial “They Key to Sustainable Enterprises: ESG, KNowledge Graphs, and Digitalization.” Adopting an ESG program and complying with upcoming ESG directives requires connecting a lot of information and data and aligning it with requirements and disclosure categories, and this is where a knowledge graph can be extremely helpful. Other tutorials and workshops dealt with data spaces, ontology reasoning, healthcare NLP, NLP for knowledge graph construction, and FAIR ontologies. </span></span></p></span><p></p><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><br /></span><h2><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><h3 style="text-align: left;"><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">Past and future</span></h3></span></h2><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><div><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"></span></div></span><h2><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium; font-weight: normal;"><p style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: left;"><span face="Arial, sans-serif" style="font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><span>Semantic technologies were very new when the conference was first launched in 2005 by <a href="https://semantic-web.com/semantics-conference/">Semantic Web Company</a>, even before launching its product PoolParty Semantic Suite. But it’s never been a vendor product-based conference. The main purpose was and still is to promote the understanding and advancement of semantic technologies. Competitor software vendors sponsor and exhibit, and Semantic Web Company has stepped back from a lead organizational role. The conference is not one where sponsors make business in selling their products or services, but rather for raising awareness, making and reinforcing partnerships, exchanging ideas, and general networking, including looking for work. It is more of a community conference than anything else, but it is an open welcoming community, with new people coming every year.</span></span></p></span></h2><span id="docs-internal-guid-c55b8c68-7fff-770b-7f37-85d05ab11329" style="font-family: inherit; font-size: medium;"><div class="separator" style="clear: both; text-align: left;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjBOcjbvbxOPTy3ECBFdOZj93_sLzO0yB4IcAqkbHRHmXSiNZe2czq7UmkdHaSEhbQ1b94_BPq6Iotz-DaefuJYze9nKR6GIF-5bs4y5qa3YNjfR7b2VzdABTxyNwsrThj9x3m-p12L_dmfgz990RUFnyVtWzYmxFmnayAaEwu3BYicVwO5Y0Bst0gdBlw/s4052/SEMANTiCS%20group.jpeg" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="2143" data-original-width="4052" height="338" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjBOcjbvbxOPTy3ECBFdOZj93_sLzO0yB4IcAqkbHRHmXSiNZe2czq7UmkdHaSEhbQ1b94_BPq6Iotz-DaefuJYze9nKR6GIF-5bs4y5qa3YNjfR7b2VzdABTxyNwsrThj9x3m-p12L_dmfgz990RUFnyVtWzYmxFmnayAaEwu3BYicVwO5Y0Bst0gdBlw/w640-h338/SEMANTiCS%20group.jpeg" width="640" /></a></div><div class="separator" style="clear: both; text-align: left;"><span><br /></span></div><div class="separator" style="clear: both; text-align: left;"><span face="Arial, sans-serif" style="white-space: pre-wrap;"><span>The next SEMANTiCS, celebrating its 20th year, will be September 16 - 18, 2024, in Amsterdam.</span></span></div></span><span style="font-family: inherit;"><span style="font-size: medium;"><br /></span><br class="Apple-interchange-newline" /></span>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-15075749188140057522023-08-24T23:23:00.015-04:002023-12-31T21:44:35.716-05:00Taxonomies for Digital Asset Management (DAM)<p></p><p style="text-align: left;"><span style="font-family: inherit; font-size: medium;"><span style="background: white; color: black; line-height: 107%;"></span></span></p><div class="separator" style="clear: both; text-align: center;"><span style="font-family: inherit; font-size: medium;"><span style="background: white; color: black; line-height: 107%;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEipWbEN3AWzQDBQIl2sKcNL--r9bqyXMANMGR-7M2h5b1YbVbO8YR0-C0jgCym05bujTYxhSW3eJzFXhJXtOiXe3oCDKP7lPOU3D4XVRrVfkIBtav0j2hPJsuYXp5c3pfeeS2oVgxC2shC_CaYaectuOgquG0akYI0lcZ4Kri5TZtW7KpQzZoNW0PxFRTQ/s351/DAM%20file%20types.jpg" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img alt="Icons for file types" border="0" data-original-height="247" data-original-width="351" height="226" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEipWbEN3AWzQDBQIl2sKcNL--r9bqyXMANMGR-7M2h5b1YbVbO8YR0-C0jgCym05bujTYxhSW3eJzFXhJXtOiXe3oCDKP7lPOU3D4XVRrVfkIBtav0j2hPJsuYXp5c3pfeeS2oVgxC2shC_CaYaectuOgquG0akYI0lcZ4Kri5TZtW7KpQzZoNW0PxFRTQ/w320-h226/DAM%20file%20types.jpg" width="320" /></a></span></span></div><p style="text-align: left;"><span style="font-family: times;"><span style="font-size: medium;"><span style="background: white; color: black; line-height: 107%;">Taxonomies, with their origin in thesauri and library subject heading
systems, have traditionally been associated with the tagging and retrieving of <i>text</i>
content. The management and retrieval of <i>multimedia</i> content (images, video,
audio, or other graphics files), on the other hand, has traditionally been
served by metadata schema, reflecting the various attributes of the content,
including digital rights. </span></span><br /><span style="font-size: medium;"><span style="background: white; color: black; line-height: 107%;">Metadata for text content has become increasingly important to
make it “structured” and easier to manage. Meanwhile, taxonomies, with their
richness in topical detail, hierarchical structure, and synonyms, have become
increasingly important in making multimedia content, especially digital assets,
easier to identify and retrieve.</span></span></span></p><p style="text-align: left;"></p><p style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; line-height: 107%;"><span style="font-family: times;">However, the features and uses of taxonomies and descriptive
metadata have somewhat converged, now that faceted taxonomies have become
common. A facet is an aspect or attribute, by which the user may limit, filter,
or refine a search or initiate a search selection. (Several of my past blog posts discuss facets, including "<a href="https://accidental-taxonomist.blogspot.com/2020/10/customizing-taxonomy-facets.html">Customizing Taxonomy Facets</a>.")</span><span style="font-family: inherit;"> </span></span></span></p><p style="text-align: left;"><span style="font-family: inherit; font-size: medium;"><span style="background: white; color: black; line-height: 107%;"><br /></span></span></p>
<h2 class="MsoNormal" style="text-align: left;"><span><span style="background: white; color: black; font-family: inherit; font-size: large; line-height: 107%;">Why taxonomies for multimedia content and digital assets</span></span></h2>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; font-family: times; line-height: 107%;">There is considerable overlap between multimedia content and digital
assets, although they are not identical. A digital asset is something that is
created and stored in a digital form that has <i>value</i>. The word “asset”
implies it has value. So, not everything that is in digital form is an asset. Creative
works in digital form, whether by in-house producers or licensed, are
considered digital assets. Multimedia content tends to have value, so it tends
to be considered as digital assets. If it needs to be managed and made
available for retrieval and reuse, it can probably be considered a digital
asset. If it needs to be managed and made available for retrieval and reuse,
then assigning metadata and taxonomy terms is probably important.</span></span></p>
<h3 style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; font-family: times; line-height: 107%;">1. Growing volume of digital assets</span></span></h3>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; font-family: times; line-height: 107%;">The main reason to move beyond simple controlled lists of terms/values in metadata properties (such
as Type, Location name, Location type, Event/Occasion, Person type, Season,
etc.) and include relatively large topical taxonomies for digital assets is to provide
the ability to better limit search results in large volumes of content. The
number of digital assets owned or managed by organizations has grown immensely,
as varied media sources have become more common, not just for brand content but also
for marketing, instructional, and technical content. Limiting search results from only a few broad topic categories is often not sufficient, and too many digital assets are retrieved. </span></span></p>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; font-family: times; line-height: 107%;">A taxonomy provides further granularity of subjects which a digital
asset depicts or describes. A granular hierarchical taxonomy could provide the
terms for a single metadata property, such as “Subject,” or there could detailed
taxonomies in more than one metadata property, to also include “Activity,” “Product
category,” or “Occasion,” depending on the use case. </span></span></p>
<h3 style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; font-family: times; line-height: 107%;">2. Varied audience for digital assets and the use of synonyms</span></span></h3>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; font-family: times; line-height: 107%;">Another reason to use taxonomies for digital assets is to better suit a
varied audience of users. While it is digital asset managers who rely on
metadata to manage the digit assets, various other users need to find the same
assets: product and brand managers, web content editors, art designers, partnership
and licensing specialists, and perhaps even customers. Assets are most valuable
when they have wider uses, but in order to be reused by different people and
departments, a detailed taxonomy helps. </span></span></p>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; font-family: times; line-height: 107%;">A taxonomy is not only more detailed than a list of a few categories,
but it is also usually enriched with synonyms (also called alternative labels
or variant terms). This way, different people who may describe the same thing
by different names will find the same concept and its tagged content. For
example, synonyms could be “Bridal” and “Wedding”; “Infant” and “Baby”; “Botanical”
and “Plants”; “DIY” and “How to.” Internal users and external users often have
different preferred names for things.</span></span></p>
<h3 style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; font-family: times; line-height: 107%;">3. Connecting both text and multimedia content across the enterprise</span></span></h3>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; font-family: times; line-height: 107%;">Applying a taxonomy to tag digital assets can also allow digital assets
to be retrieved along with other content, text content, in other content management systems (CSMs). This would require that the taxonomy be a centrally managed enterprise taxonomy, and not
just a siloed taxonomy within a single DAM system, and that more than one system are connected
to each other (such as through APIs or integrations) or that a dedicated
front-end enterprise search application is linked to content in
their source repositories. <span> </span></span></span></p>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; font-family: times; line-height: 107%;">While users often look only for digital assets that they know are
located within a specific DAM system, other times users want to conduct a more exhaustive search on a
subject. While most images and videos are expected to be in the DAM, along with
some PDF files, other PDF files, presentations, and documents, and even some
images and videos from other sources may be located in other systems. Taxonomies
that can be linked to each other or a single master taxonomy managed centrally
in a dedicated taxonomy management system, such as <a href="https://www.poolparty.biz/">PoolParty</a>, serving as
"middleware," connected to the content in each of the systems, can enable comprehensive
search and retrieval across the organization, especially if all the data is
managed in a knowledge graph (explained in my last blog post "<a href="https://accidental-taxonomist.blogspot.com/2023/07/knowledge-graphs-and-taxonomies.html">Knowledge Graphs and Taxonomies</a>").</span></span></p>
<h2 style="text-align: left;"><span><span style="background: white; color: black; font-family: inherit; font-size: large; line-height: 107%;">Tagging or keywording multimedia content and digital assets</span></span></h2>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; font-family: times; line-height: 107%;">Finally, there is the tagging component of taxonomies, which is often called keywording with respect to images. Digital asset
managers must assign descriptive metadata to the assets they manage, which is
not difficult if the controlled lists of available values are short. A taxonomy, however, may be large, so it can be a challenge to determine which subject
terms to tag. </span></span></p><p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; font-family: times; line-height: 107%;">For text-only content, the technologies of text analytics, including
entity extraction and natural language processing, can be applied to enable
auto-tagging. Image, video, and audio content had previously been considered unsuitable
for auto-tagging, and thus less suitable for large taxonomies, but this is no
longer the case. </span></span></p>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; font-family: times; line-height: 107%;">There are new technologies and methods to enable auto-tagging of digital
assets. Audio-to-text technologies enable transcripts to be created from
audio and video files, and these texts can automatically analyze and tagged.
Improvements in image recognition technology can enable images to be auto-tagged
for their subjects. Human review of auto-tagging is still recommended, but that’s
easier than tagging from scratch.</span></span></p>
<h2 class="MsoNormal" style="text-align: left;"><span><span style="background: white; color: black; font-family: inherit; font-size: large; line-height: 107%;">Taxonomy is what powers DAM</span></span></h2>
<p class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="background: white; color: black; font-family: times; line-height: 107%;">DAM systems do support taxonomies, so you should not hold back from creating
a suitable taxonomy for your DAM content. To learn more about creating taxonomies for digital assets, attend the
session “<a href="https://www.henrystewartconferences.com/events/dam-new-york-2023/session/events-dam-new-york-2023-day-1-track-4-taxonomy-what-powers-dam">Taxonomy is What Powers DAM</a>” on September 14, 2023, at the HS Events <a href="https://www.henrystewartconferences.com/events/dam-new-york-2023" target="_blank">DAM New York</a> conference. I will join three other
panelists to discuss taxonomies for digital asset management: what taxonomies
are, how to develop a taxonomy, how to do research for a taxonomy, and how to
manage a taxonomy, especially for DAM applications. <a href="https://www.henrystewartconferences.com/events/dam-new-york-2023/pricing">Register</a> with the code SPEAKER100 for $100 off.</span></span></p>
<p class="MsoNormal" style="text-align: left;"><span><span style="background: white; color: black; font-family: times; font-size: medium; line-height: 107%;"> </span></span></p>
Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-11332666513975719782023-07-31T21:00:00.004-04:002023-11-09T15:20:16.729-05:00Knowledge Graphs and Taxonomies<p><span lang="EN-CA">Knowledge graphs have recently emerged as an
additional and growing use of taxonomies. A knowledge graph comprises data extracted
and stored typically in a graph database with an ontology to semantically link types of
data, but usually a knowledge graph also includes a taxonomy, thesaurus, or set
of controlled vocabularies to provide consistent labeling. As a result of this
combination, people involved in knowledge graphs are taking an interest in
taxonomies, and people involved in taxonomies are taking an interest in
knowledge graphs. </span></p>
<p class="MsoNormal"><span lang="EN-CA">The traditional and still primary use of
taxonomies is to consistently and comprehensively tag and retrieve <i>content</i>,
whereas the focus of knowledge graphs is to access and make connections among disparate
<i>data</i>. Content tagged and retrieved with taxonomies includes pages in
websites, intranets, content management systems; documents in document
management systems; and images and video files in digital asset management
systems. Knowledge graphs link together data which includes records in
databases, customer relationship management systems, product information
management systems, and other enterprise systems, and the values in cells in
spreadsheets, referenced by their row and column headers. By integrating a
taxonomy into a knowledge graph, users can then retrieve both content and data
on the same subject together.</span></p>
<p class="MsoNormal"><span lang="EN-CA">What
is a knowledge graph? The first
non-sponsored definition that pops up today with a Google search not
from a vendor is from the the Alan Turning Institute, the U.K. national
institute for data science and
artificial intelligence, which provides the following explanation on its
<a href="https://www.turing.ac.uk/research/interest-groups/knowledge-graphs" target="_blank">Knowledge graphs interest group</a> page:<br /></span></p>
<p class="MsoNormal"><span lang="EN-CA"></span></p><blockquote><p class="MsoNormal"><i><span lang="EN-CA">Knowledge graphs (KGs) organise data from
multiple sources, capture information about entities of interest in a given
domain or task (like people, places or events), and forge connections between
them. In data science and AI, knowledge graphs are commonly used to:</span></i></p><ul style="text-align: left;"><li class="MsoNormal"><i><span lang="EN-CA">Facilitate access to and
integration of data sources;</span></i></li><li><i><span lang="EN-CA">Add context and depth to other,
more data-driven AI techniques such as machine learning; and</span></i></li><li><i><span lang="EN-CA">Serve as bridges between humans
and systems, such as generating human-readable explanations, or, on a bigger
scale, enabling intelligent systems for scientists and engineers.</span></i></li></ul></blockquote>
<p class="MsoNormal"><span lang="EN-CA">From the taxonomy perspective, a knowledge
graph is a combination of controlled vocabularies or a taxonomy with the semantic
layer of an ontology, which adds custom semantic relations and attributes, plus
specific instance data, which is stored in a graph database. <span style="mso-spacerun: yes;"> </span>A knowledge graph thus extends the use of a
taxonomy beyond content to also include data. From the graph data perspective,
a knowledge graph is the gathering of disparate data, which has been extracted,
transformed, and loaded (ETL) into a graph database, where it is linked with
semantic relations provided by an ontology and described by terms in a taxonomy,
and it can be queried and analyzed all in one place. </span></p><div class="separator" style="clear: both; text-align: center;"><div class="separator" style="clear: both; text-align: center;"><table cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: left; margin-right: 1em; text-align: left;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8ZLR4jqZdn5foAn1zUzjp1aLCbwk_iCMKw821rXQBSZmOTcoKUOIwxERd4qIj0vwyTiC_aHdqblmzH3HQe59Z7kAKMuEP68jfjPcABaCccn9Vol6c3R8WnD0aliVQpmMlIlNk12onbIgCtmf8AXksbMxbj1B10q1Tfmol_rPvKYc7ODk1b2VuJ7BiYa0/s1561/ESG-KG.jpg" style="clear: left; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img alt="GraphViews of SWC ESG Knowledge Graph" border="0" data-original-height="782" data-original-width="1561" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8ZLR4jqZdn5foAn1zUzjp1aLCbwk_iCMKw821rXQBSZmOTcoKUOIwxERd4qIj0vwyTiC_aHdqblmzH3HQe59Z7kAKMuEP68jfjPcABaCccn9Vol6c3R8WnD0aliVQpmMlIlNk12onbIgCtmf8AXksbMxbj1B10q1Tfmol_rPvKYc7ODk1b2VuJ7BiYa0/w640-h320/ESG-KG.jpg" title="GraphViews of SWC ESG Knowledge Graph" width="640" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><i>GraphViews of SWC ESG Knowledge Graph</i></td></tr></tbody></table><div style="text-align: left;"><span lang="EN-CA">It is an important to the definition of a
knowledge graph to include its purpose and not just its components. The purposes
include providing a unified view of data, easy availability of information,
easy integration of new data, secure interoperability, visualization of
entities and relations, the possibility of discovery and insights through
semantic relations, and the support for complex multi-part queries with quick
results. With inclusion of a taxonomy, a knowledge graph can bring together
both data and content on in and organization.</span></div><div style="text-align: left;"><span lang="EN-CA"> </span></div><div style="text-align: left;"><span lang="EN-CA">With such lofty goals, knowledge graphs
should be an area of interest not just of data scientists and ontologists, but
also of information professionals (including taxonomists) and knowledge
managers. This is gradually becoming the case. Knowledge graphs emerged in the
2010, and became popularized with the Google Knowledge Graph introduced in 2012.
Knowledge graphs were first introduced at the KMWorld (Knowledge Management)
conferences in 2017 as "semantic knowledge graphs,” and were also first
mentioned at the Taxonomy Boot Camp conference that year. This November, the
<a href="https://www.kmworld.com/Conference/2023/Program.aspx">KMWorld conference</a> has more talks on knowledge graphs than before. When I
proposed multiple topics for this spring’s Information Architecture Conference,
the conference chair chose the presentation on an introduction knowledge
graphs. I also delivered a similar presentation this year to the joint Special
Libraries Association and Medical Libraries Association conference.</span></div></div></div><p></p>
<p class="MsoNormal"><span lang="EN-CA">I will be giving an updated version of
those talks, “<a href="https://www.poolparty.biz/events/webinar_knowledge_graphs_for_information_professionals/">Knowledge Graphs for Information Professionals</a>” as a free PoolParty webinar
on Thursday, August 17, 11:00 – 12:00 EDT, after which the recording will also
be available. </span></p>
<br /><br /><br />Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com3tag:blogger.com,1999:blog-9094731596169096992.post-68510131020377680632023-06-30T22:00:00.006-04:002023-12-09T11:34:32.943-05:00Taxonomies for Technical Documentation<div><p><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val="Cambria Math"/>
<m:brkBin m:val="before"/>
<m:brkBinSub m:val="--"/>
<m:smallFrac m:val="off"/>
<m:dispDef/>
<m:lMargin m:val="0"/>
<m:rMargin m:val="0"/>
<m:defJc m:val="centerGroup"/>
<m:wrapIndent m:val="1440"/>
<m:intLim m:val="subSup"/>
<m:naryLim m:val="undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="false"
DefSemiHidden="false" DefQFormat="false" DefPriority="99"
LatentStyleCount="376">
<w:LsdException Locked="false" Priority="0" QFormat="true" Name="Normal"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 1"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 2"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 3"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 4"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 5"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 6"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 7"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 8"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 9"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 9"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 1"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 2"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 3"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 4"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 5"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 6"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 7"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 8"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 9"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footnote text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="header"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footer"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index heading"/>
<w:LsdException Locked="false" Priority="35" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="caption"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="table of figures"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="envelope address"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="envelope return"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footnote reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="line number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="page number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="endnote reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="endnote text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="table of authorities"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="macro"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="toa heading"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 5"/>
<w:LsdException Locked="false" Priority="10" QFormat="true" Name="Title"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Closing"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Signature"/>
<w:LsdException Locked="false" Priority="1" SemiHidden="true"
UnhideWhenUsed="true" Name="Default Paragraph Font"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Message Header"/>
<w:LsdException Locked="false" Priority="11" QFormat="true" Name="Subtitle"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Salutation"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Date"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text First Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text First Indent 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Heading"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Block Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Hyperlink"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="FollowedHyperlink"/>
<w:LsdException Locked="false" Priority="22" QFormat="true" Name="Strong"/>
<w:LsdException Locked="false" Priority="20" QFormat="true" Name="Emphasis"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Document Map"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Plain Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="E-mail Signature"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Top of Form"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Bottom of Form"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal (Web)"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Acronym"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Address"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Cite"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Code"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Definition"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Keyboard"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Preformatted"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Sample"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Typewriter"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Variable"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal Table"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation subject"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="No List"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Contemporary"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Elegant"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Professional"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Subtle 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Subtle 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Balloon Text"/>
<w:LsdException Locked="false" Priority="39" Name="Table Grid"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Theme"/>
<w:LsdException Locked="false" SemiHidden="true" Name="Placeholder Text"/>
<w:LsdException Locked="false" Priority="1" QFormat="true" Name="No Spacing"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading"/>
<w:LsdException Locked="false" Priority="61" Name="Light List"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 1"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 1"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 1"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 1"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 1"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 1"/>
<w:LsdException Locked="false" SemiHidden="true" Name="Revision"/>
<w:LsdException Locked="false" Priority="34" QFormat="true"
Name="List Paragraph"/>
<w:LsdException Locked="false" Priority="29" QFormat="true" Name="Quote"/>
<w:LsdException Locked="false" Priority="30" QFormat="true"
Name="Intense Quote"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 1"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 1"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 1"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 1"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 1"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 1"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 1"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 1"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 2"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 2"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 2"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 2"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 2"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 2"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 2"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 2"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 2"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 2"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 2"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 2"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 2"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 2"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 3"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 3"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 3"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 3"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 3"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 3"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 3"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 3"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 3"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 3"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 3"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 3"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 3"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 3"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 4"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 4"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 4"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 4"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 4"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 4"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 4"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 4"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 4"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 4"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 4"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 4"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 4"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 4"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 5"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 5"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 5"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 5"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 5"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 5"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 5"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 5"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 5"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 5"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 5"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 5"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 5"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 5"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 6"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 6"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 6"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 6"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 6"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 6"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 6"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 6"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 6"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 6"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 6"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 6"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 6"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 6"/>
<w:LsdException Locked="false" Priority="19" QFormat="true"
Name="Subtle Emphasis"/>
<w:LsdException Locked="false" Priority="21" QFormat="true"
Name="Intense Emphasis"/>
<w:LsdException Locked="false" Priority="31" QFormat="true"
Name="Subtle Reference"/>
<w:LsdException Locked="false" Priority="32" QFormat="true"
Name="Intense Reference"/>
<w:LsdException Locked="false" Priority="33" QFormat="true" Name="Book Title"/>
<w:LsdException Locked="false" Priority="37" SemiHidden="true"
UnhideWhenUsed="true" Name="Bibliography"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="TOC Heading"/>
<w:LsdException Locked="false" Priority="41" Name="Plain Table 1"/>
<w:LsdException Locked="false" Priority="42" Name="Plain Table 2"/>
<w:LsdException Locked="false" Priority="43" Name="Plain Table 3"/>
<w:LsdException Locked="false" Priority="44" Name="Plain Table 4"/>
<w:LsdException Locked="false" Priority="45" Name="Plain Table 5"/>
<w:LsdException Locked="false" Priority="40" Name="Grid Table Light"/>
<w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark"/>
<w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful"/>
<w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 1"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 1"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 1"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 1"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 1"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 2"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 2"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 2"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 2"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 2"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 3"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 3"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 3"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 3"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 3"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 4"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 4"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 4"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 4"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 4"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 5"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 5"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 5"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 5"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 5"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 6"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 6"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 6"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 6"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 6"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="46" Name="List Table 1 Light"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark"/>
<w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful"/>
<w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 1"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 1"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 1"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 1"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 1"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 2"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 2"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 2"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 2"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 2"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 3"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 3"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 3"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 3"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 3"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 4"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 4"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 4"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 4"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 4"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 5"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 5"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 5"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 5"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 5"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 6"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 6"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 6"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 6"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 6"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Mention"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Smart Hyperlink"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Hashtag"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Unresolved Mention"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Smart Link"/>
</w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:8.0pt;
mso-para-margin-left:0in;
line-height:107%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
mso-font-kerning:1.0pt;
mso-ligatures:standardcontextual;}
</style>
<![endif]-->
</p><p class="MsoNormal"><span lang="EN-CA">Taxonomies are primarily for tagging content
for what is about so that precise content can easily be found by users, who browse
or search on the taxonomy terms. The types of content tagged and
implementations of taxonomies are numerous. One growing area of taxonomy use is
technical documentation. </span></p>
<p class="MsoNormal"><span lang="EN-CA">Technical documentation describes and
explains the use or design of products or services. We refer to “documentation,”
rather than “documents,” because the format can vary, including book-length manuals,
multi-page PDF files such as white papers, content for printed product inserts
or brochures, public website pages, and internal content management system
pages. <span style="mso-spacerun: yes;"> </span>Technical documentation has existed
for a long time. It used to be published only in print, especially as manual,
like books, so the tools of information findability were the table of contents
and the index at the back of manual. Now that technical documentation is most
often consumed online and always managed digitally, an alphabetical browsable
index is not practical to create, maintain, or use. Furthermore, indexes also
cannot serve multiple-use (multi-channel) content well.</span></p>
<h3 class="MsoNormal" style="text-align: left;"><span lang="EN-CA">Taxonomies for content tagging and
retrieval</span></h3>
<p class="MsoNormal"><span lang="EN-CA">In contrast to creating an alphabetical
index of terms referencing page numbers or linked to content sections, tagging
content with a taxonomy, has several benefits. </span></p>
<p class="MsoNormal"><span lang="EN-CA"></span></p><span lang="EN-CA">Taxonomies provide a better user experience
than indexes. While an index requires the user to browse a long alphabetical
list of terms until the desired term is found, the browsing of taxonomies does
not require the user to already know the name of the desired term. Taxonomies that
are arranged in hierarchical trees allow the user to drill down from broad categories
to a specific topic. Taxonomies that are arranged as facets allow the user to
select displayed terms (often listed by frequency of tagged usage) grouped by
various facets (aspects) to limit the search results. </span></div><div><span lang="EN-CA"><div style="text-align: center;"><a href="https://help.poolparty.biz/?lang=en" target="_blank"><span style="clear: right; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img alt="PoolParty help documentation facets" border="0" data-original-height="971" data-original-width="799" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi5eLN2tHKQHFSOw817NcHLyWWFQ_oSV4rv7qrmdReNVM2Ron1ZIpk5BwvlICTpcy9RRVRj1wCD0XVbctXr1_JMWw43M9TwtzzUmrMYzWszc9-awdSEBn-aw9NkcdRU1uCIVy3ZrCEcg-sS7zYDSRI4qiUWvFcYG6HsiOxL4jrfMqQaS3mFQZoOAvxNGgU/w526-h640/PPHelpFacets.jpg" title="PoolParty help documentation facets" width="526" /></span></a></div></span></div><div><span lang="EN-CA"> </span></div><div><span lang="EN-CA"> Facets for technical documentation
could be:</span><p></p>
</div><ul style="text-align: left;"><li><span lang="EN-CA">User audience</span></li><li><span lang="EN-CA">Content type</span></li><li><span lang="EN-CA">Product (name or module)</span></li><li><span lang="EN-CA">Feature or function</span></li><li><span lang="EN-CA">Topic</span></li></ul>
<p class="MsoNormal"><span lang="EN-CA">The process of tagging with a taxonomy or
other controlled vocabulary is also simpler than creating an index. Creating a back-of-the-book
index involves not only determining important concepts, but also giving them
names as terms, determining subentries if any, and creating cross-references. Only
trained indexers can do this well. Tagging with a taxonomy, especially if the
taxonomy is already well-designed, is not so challenging. Since the terms and
their synonyms or cross-references have already been established, it’s just a
matter of looking up the term that describes to concept. Technical content now
tends to be managed in component content management systems (CCMSs), so the unit
of content to be tagged is already designated as a component. (See my <a href="https://accidental-taxonomist.blogspot.com/2023/04/taxonomies-for-content-components.html">April blog post</a>.) Thus, content
managers, editors, and writers can competently do tagging themselves. Tagging
with a taxonomy can also be automated. </span></p>
<p class="MsoNormal"><span lang="EN-CA">An index is tied to a specific document or collection.
The same taxonomy, on the other hand, can be used for more than just technical
documentation but across the enterprise, such as for website and other
marketing content, product information, and research and development. Consistent
terms support more efficient and comprehensive information gathering, sharing,
and analysis.</span></p>
<h3 class="MsoNormal" style="text-align: left;"><span lang="EN-CA">Taxonomies to serve technical documentation’s
diverse users</span></h3>
<p class="MsoNormal"><span lang="EN-CA">Taxonomies are a useful information finding
tool when content is being used by different kinds of users. The same, or parts
of the same, technical documentation often have diverse users: product customers,
prospective customers, technical support agents, consultant staff, product managers,
engineers, etc.</span></p><ul style="text-align: left;"><li><span lang="EN-CA">Taxonomy concepts have synonyms or alternative labels to reflect the preferred wording of different groups of users. Matches to even these synonyms can be displayed after a search string is entered into a search box.</span><br /><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto;"><tbody><tr><td style="text-align: center;"><a href="https://help.poolparty.biz/?lang=en" target="_blank"><span style="margin-left: auto; margin-right: auto;"><img alt="https://help.poolparty.biz documentation search on taxonomy concepts" border="0" data-original-height="492" data-original-width="654" height="313" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEipuwbFAojqUeaHnYKesTIhkenYFt7SfeAo32gEez42ecniU7mrps-CMnH2oAirZ30RSWKDzWJvJJWLr11u70DM1idsKJ5WmUeJOQvHuDUXCympEKmTvRG7uHePpU_n_3dIZr0h8CLuGaq4x_HaXOoORyprh7cSxdW2e5Lr0YB-jhP1psdvPDfRyLFM-lU/w415-h313/2023-07-01%20(3).png" title="https://help.poolparty.biz documentation search on taxonomy concepts" width="415" /></span></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><a href="https://help.poolparty.biz/?lang=en" target="_blank"><span lang="EN-CA"><i>https://help.poolparty.biz documentation search on taxonomy concepts<br /></i></span></a></td></tr></tbody></table><br /></li><li><span lang="EN-CA"> The same taxonomy can be adapted to different user groups with different user interfaces. For example, exposing more metadata in an “advanced search” or displaying just a subset of a larger set of facets.</span></li><li><span lang="EN-CA">Taxonomy concepts can be managed with labels in multiple languages, supporting the tagging and retrieval of multilingual content for users of different languages.</span></li></ul><h3 class="MsoNormal" style="text-align: left;"><span lang="EN-CA"> <br />Events on taxonomies in technical documentation</span> <br /></h3><p>I have found increasing interest in taxonomies at technical documentation events. While I have been writing and speaking about taxonomies for a long time, in the past year I have been invited to talk about taxonomies at several events and programs more focused on technical documentation.</p><div>Recent past events focusing on technical documentation, at which I spoke, with recordings available:<br /><ul style="text-align: left;"><li>“<a href="https://www.stc.org/education/live-webinar/" target="_blank">Indexes, Search, and Taxonomies: Paths to Findability</a>” Society for Technical Communication webinar, June 2023 (recording available for purchase in late July)</li><li>“<a href="https://www.brighttalk.com/webcast/9273/557969" target="_blank">Taxonomy For Delivering Targeted Technical Content</a>” BrightTALK webinar, April 2023 <br /></li><li>“<a href="https://convex.infomanagementcenter.com/recordings/" target="_blank">From Document Search to Document Understanding</a>” presented by Helmut Nagy, ConVEx, April 2023 (The recording of my presentation on knowledge hubs, is only available for conference registrants.)</li></ul>Upcoming presentations of mine focusing on taxonomies and technical documentation:<br /><ul style="text-align: left;"><li>“<a href="https://www.stc.org/course/taxonomy-creation-for-content-tagging/" target="_blank">Taxonomy Creation for Content Tagging</a>” online workshop, Society for Technical Communication Tuesdays, July 18, July 25, and August 1, 4:00 – 5:30 EDT (Registration is still open.) <br /></li><li><a href="https://ideas.infomanagementcenter.com/agenda-23" target="_blank">Taxonomy panel</a>, ConVEx Ideas online conference, July 19, 12:00 – 1:30 pm EDT <br /></li><li>“<a href="https://lavacon.org/speaker/heather-hedden/" target="_blank">Leveraging Semantics to Provide Targeted Training Content: A Case Study</a>” LavaCon content strategy conference, San Diego and hybrid online, October 16, 1:30 – 3:00 pm PDT <br /></li></ul><p class="MsoNormal"><span style="mso-ansi-language: EN-US; mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin; mso-fareast-font-family: "Times New Roman"; mso-font-kerning: 18.0pt; mso-ligatures: none;"> </span></p>
<p class="MsoNormal"><span lang="EN-CA"> </span></p>
</div>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-55462399854864143042023-05-29T18:04:00.005-04:002023-05-30T12:30:28.943-04:00Taxonomies and ChatGPT<p>ChatGPT, generative AI, and large language models (LLMs) are hot topics of interest in fields of data, information, and knowledge management. LLMs dominated the keynote presentations at the networking conversations at <a href="https://www.knowledgegraph.tech">Knowledge Graph Conference</a> in New York and were also discussed in presentations and panels of this conference and <a href="https://www.dbta.com/DataSummit/2023/default.aspx">Data Summit</a> in Boston, both of which I attended this month. The technology is relevant to taxonomies as well. <br /><br /><a href="https://openai.com/blog/chatgpt" target=""></a></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhJRgSkAyAr7_Fx_wKggxwDKI8VcmF4b6F95zhqKcKDZMaHZy0oAYP051byMrkOcL_Q2R2WitOeo_h7D1d7EN-KwaomV_qjk5W86AoZWJ76Y34srgEcFSgRchgEwf7BDFxQqykncQ_s_ciPdmugU-eGB5HvGtvYD5jqHZhChSaQvABG4zYfv0r9IjN-/s1280/OpenAI_Logo-green.jpeg" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="853" data-original-width="1280" height="213" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhJRgSkAyAr7_Fx_wKggxwDKI8VcmF4b6F95zhqKcKDZMaHZy0oAYP051byMrkOcL_Q2R2WitOeo_h7D1d7EN-KwaomV_qjk5W86AoZWJ76Y34srgEcFSgRchgEwf7BDFxQqykncQ_s_ciPdmugU-eGB5HvGtvYD5jqHZhChSaQvABG4zYfv0r9IjN-/s320/OpenAI_Logo-green.jpeg" width="320" /></a></div><a href="https://openai.com/blog/chatgpt" target="">ChatGPT</a> is the user interface application on top of GPT (Generative Pre-Trained Transformer), a publicly available LLM developed by <a href="https://openai.com/" target="">OpenAI</a>, which is now in version 4. ChatGPT is thus a form of generative AI, in how it generates answers. There are many other LLMs (Neural network-based AI, trained with deep learning on very large volumes of text), including those which are proprietary, restricted, or for non-commercial research, but only some have generative AI user interfaces. Although we may think of generative AI for providing answers to questions, it can do a lot more, including tasks related to taxonomies. <br /><br /><p></p><h3 style="text-align: left;">Organizing terms into hierarchies</h3><p style="text-align: left;">Building a taxonomy is a combination of top-down design (identifying the top concepts or facets) and bottom-up building (identifying specific concepts from content analysis). The top-level of a taxonomy is designed to serve user needs and thus should be based on stakeholder interviews, surveys, and brainstorming workshops, which is not something ChatGPT can do. The bottom-up building a taxonomy, based on terms extracted content or search log terms, may benefit from some AI involvement. <br /><br />I have made a few test requests of ChatGPT for “Put the following list of terms into a hierarchical taxonomy…,” and the results are bulleted lists with indented narrower concepts. ChatGPT can also generate a taxonomy in a machine-readable SKOS in a requested RDF serialization format, as Bob DuCharme explained in his May 20 blog post “<a href="https://www.bobdc.com/blog/chatgpttaxonomy/" target="">Getting ChatGPT to turn a flat vocabulary list into a hierarchical taxonomy</a>.” <br /><br />Like card sorting exercises, you can specify the top categories/concepts (like a “closed card sort”), or you can let ChatGPT create the top categories (like an “open card sort”). In any case, better results are with context, of course, so you should also tell ChatGPT what the subject domain or context is. Asking for a hierarchical taxonomy results in a third level of hierarchy sometimes, and not just a single level of grouping. Near duplicates usually appear next to each other in the list, and the taxonomist can then decide if and how to merge them into a single concept. <br /><br />It is particularly for long lists of terms, where automated methods can save the taxonomist’s time. If a taxonomist comes up with terms based on manual content analysis, stakeholder interviews, or submitted lists from subject matter experts, the term lists tend not to be very long, and even the process of coming up with the terms tends to include some thoughts toward categorization at the same time. Longer term lists (such several hundred) are derived from automated term extraction (using text analytics technologies) across a corpus of dozens or hundreds of documents and from search log reports. ChatGPT is practical for putting these long lists of terms into draft hierarchies. There are inevitably some taxonomic errors in the results, which should be obvious to any taxonomist. For example, I have seen duplicated terms on different levels of the hierarchy. <br /><br />In both lists of extracted terms and search log lists, terms occur that are not suitable as concepts for a taxonomy, such as verbs and adjectives or vague words. ChatGPT understands grammatical rules, so my prompt also says “Include in the taxonomy only nouns and noun phrases and omit the other terms.”<br /><br /></p><h3 style="text-align: left;">Generating alternative labels (“synonyms”) for concepts</h3><p style="text-align: left;"></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhFROpW5v5brOQD4FHQxQ3XUjUL2RYwtw914QXxD13szRCXMzfU-jYbwdESfAaC1u0UmZG400_pSKUuIHwL82pyPdhUhpwmKy7ZXBVmfmwpy_MDZFswude4s3lkEuUZJzD3VtX2nd3VMjfU-OFxNlH2LXrR-13u9zBSOT_CxxK6z3Qmel3vyHMPK8K1/s456/Screen%20Shot%202023-05-29%20at%205.57.48%20PM.png" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" data-original-height="289" data-original-width="456" height="203" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhFROpW5v5brOQD4FHQxQ3XUjUL2RYwtw914QXxD13szRCXMzfU-jYbwdESfAaC1u0UmZG400_pSKUuIHwL82pyPdhUhpwmKy7ZXBVmfmwpy_MDZFswude4s3lkEuUZJzD3VtX2nd3VMjfU-OFxNlH2LXrR-13u9zBSOT_CxxK6z3Qmel3vyHMPK8K1/s320/Screen%20Shot%202023-05-29%20at%205.57.48%20PM.png" width="320" /></a></div>Asking ChatGPT to “provide a list of synonyms for…” a given term can also be helpful for coming up with alternative labels for taxonomy concepts. Alternative labels should be customized for the context of the content and users, so alternative labels for a concept will vary from one taxonomy to another, and an external source, such as ChatGPT should not relied upon as the only source for alternative labels, but merely as a supplemental source of suggestions to be considered. <p></p><p style="text-align: left;">Again, context can help and should be provided. I asked “Provide a list of synonyms for “healthcare” and got 20 terms. But then when I asked “Provide a list of synonyms for health care, meaning the industry,” I received a slightly more focused list of 15 terms. Interestingly, the two-word variant “health care” was not on the list, so “synonyms” is understood by ChatGPT to mean different words with the same meaning and not orthographic variations. Nevertheless, even 15 terms are too many, and the taxonomist should select from the list of suggestions. It might be a good idea to then test search the suggested alternative labels in the content and system being used. <br /><br />Although by strict definition a “synonym” is a single word with the same meaning as another word, ChatGPT provides acceptable synonyms for terms which are multi-word phrases, or synonymous multi-word phrases, such as “Chemical manufacturing and distribution” provided as a synonym for “chemical industry.”</p><br /><h3 style="text-align: left;">Other taxonomy-related uses of ChatGPT</h3><p>Getting help in designing an ontology (a more complex, yet high-level semantic model with defined classes of concepts, customized relationships, and attributes) is also possible with ChatGPT or other LLMs. Again, submitting the request multiple times with slight variations will yield multiple different responses for the ontologist to consider and select ideas from. Ontologies are not expressed in simple text, though, so the prompt request should specify it, such as RDF TTL. Dean Allemang, author of <i><a href="https://workingontologist.org/">Semantic Web or the Working Ontologist</a></i>, has written multiple articles (<a href="http://medium.com/@dallemang">medium.com/@dallemang</a>) recently on ChatGPT and ontologies/knowledge graphs.<br /><br />ChatGPT can also be used for comparing lists of terms, data conversion, and basic coding, which may be useful for taxonomists who lack coding skills. It can convert taxonomy or ontology data from one data format to another (although taxonomy/ontology management software also imports/exports in multiple formats). Taxonomies and ontologies in their raw data format are most commonly expressed in the RDF (Resource Description Framework) data model which has various serialization format: RDF/XML, JSON, JSON- LD, .ttl (Turtle), etc., and ChatGPT can convert data from one to another. Data extraction can also be done with ChatGPT. For example, knowledge management professional Camille Mathieu recently shared in a <a href="https://www.linkedin.com/posts/camillemathieu_chatgpt-python-activity-7067921553958572032-gy91?utm_source=share&utm_medium=member_desktop">LinkedIn post</a> how she used ChatGPT to write a Python script to extract text & metadata from PDFs.<br /><br />Perhaps what is most intriguing as a future implementation of taxonomies and ChatGPT is to go in the other direction and have knowledge organization systems, such as taxonomies, support the creation and use of queries (as called “prompts”) for generative AI, to obtain better results. This requires some back-end development, though, and is not merely a matter of putting a taxonomy into a prompt. Since a taxonomy is created for a specific subject domain, the questions need to be confined to the domain of the taxonomy. Semantic Web Company has developed a simple publicly accessible demo “<a href="https://www.poolparty.biz/pp-meets-chatgpt">PoolParty Meets Chat GPT</a>,” whereby you can compare the results of questions you ask in the subject area of ESG (Environmental, Social, and Governance) that are submitted directly to ChatGPT and with those which are filtered through an ESG taxonomy and knowledge graph (managed in PoolParty software) so that the questions are enriched before being sent to ChatGPT. The semantically enriched questions generate answers that have more detail, better accuracy, and even web links to definitions and other articles. <br /><br /></p><h3 style="text-align: left;">Conclusions</h3><p>While it’s arguable whether ChatGPT alone is a good way to obtain “facts,” there is no doubt that it is a good way to get suggestions and ideas. These suggestions can support the work of taxonomists and ontologists, and taxonomies and ontologies in turn can support the results of ChatGPT and other LLMs. Because there will be errors from ChatGPT, it should not be used to generate taxonomies by those who are not already knowledgeable with taxonomy requirements and best practices, nor should it be used as a substitute for the expertise of taxonomists. <br /><br />I hope to experiment more with ChatGPT for taxonomies and share additional details in future blog posts.<br /><br /></p>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-72242072492673103392023-04-30T22:31:00.038-04:002023-05-01T08:58:29.891-04:00Taxonomies for Content Components<div style="text-align: left;"></div><p style="text-align: left;"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val="Cambria Math"/>
<m:brkBin m:val="before"/>
<m:brkBinSub m:val="--"/>
<m:smallFrac m:val="off"/>
<m:dispDef/>
<m:lMargin m:val="0"/>
<m:rMargin m:val="0"/>
<m:defJc m:val="centerGroup"/>
<m:wrapIndent m:val="1440"/>
<m:intLim m:val="subSup"/>
<m:naryLim m:val="undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="false"
DefSemiHidden="false" DefQFormat="false" DefPriority="99"
LatentStyleCount="376">
<w:LsdException Locked="false" Priority="0" QFormat="true" Name="Normal"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 1"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 2"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 3"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 4"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 5"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 6"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 7"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 8"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 9"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 9"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 1"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 2"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 3"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 4"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 5"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 6"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 7"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 8"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 9"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footnote text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="header"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footer"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index heading"/>
<w:LsdException Locked="false" Priority="35" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="caption"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="table of figures"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="envelope address"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="envelope return"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footnote reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="line number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="page number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="endnote reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="endnote text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="table of authorities"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="macro"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="toa heading"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 5"/>
<w:LsdException Locked="false" Priority="10" QFormat="true" Name="Title"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Closing"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Signature"/>
<w:LsdException Locked="false" Priority="1" SemiHidden="true"
UnhideWhenUsed="true" Name="Default Paragraph Font"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Message Header"/>
<w:LsdException Locked="false" Priority="11" QFormat="true" Name="Subtitle"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Salutation"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Date"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text First Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text First Indent 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Heading"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Block Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Hyperlink"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="FollowedHyperlink"/>
<w:LsdException Locked="false" Priority="22" QFormat="true" Name="Strong"/>
<w:LsdException Locked="false" Priority="20" QFormat="true" Name="Emphasis"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Document Map"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Plain Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="E-mail Signature"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Top of Form"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Bottom of Form"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal (Web)"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Acronym"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Address"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Cite"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Code"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Definition"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Keyboard"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Preformatted"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Sample"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Typewriter"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Variable"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal Table"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation subject"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="No List"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Contemporary"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Elegant"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Professional"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Subtle 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Subtle 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Balloon Text"/>
<w:LsdException Locked="false" Priority="39" Name="Table Grid"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Theme"/>
<w:LsdException Locked="false" SemiHidden="true" Name="Placeholder Text"/>
<w:LsdException Locked="false" Priority="1" QFormat="true" Name="No Spacing"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading"/>
<w:LsdException Locked="false" Priority="61" Name="Light List"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 1"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 1"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 1"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 1"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 1"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 1"/>
<w:LsdException Locked="false" SemiHidden="true" Name="Revision"/>
<w:LsdException Locked="false" Priority="34" QFormat="true"
Name="List Paragraph"/>
<w:LsdException Locked="false" Priority="29" QFormat="true" Name="Quote"/>
<w:LsdException Locked="false" Priority="30" QFormat="true"
Name="Intense Quote"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 1"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 1"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 1"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 1"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 1"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 1"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 1"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 1"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 2"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 2"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 2"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 2"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 2"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 2"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 2"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 2"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 2"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 2"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 2"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 2"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 2"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 2"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 3"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 3"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 3"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 3"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 3"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 3"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 3"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 3"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 3"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 3"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 3"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 3"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 3"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 3"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 4"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 4"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 4"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 4"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 4"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 4"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 4"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 4"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 4"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 4"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 4"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 4"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 4"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 4"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 5"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 5"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 5"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 5"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 5"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 5"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 5"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 5"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 5"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 5"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 5"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 5"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 5"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 5"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 6"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 6"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 6"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 6"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 6"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 6"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 6"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 6"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 6"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 6"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 6"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 6"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 6"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 6"/>
<w:LsdException Locked="false" Priority="19" QFormat="true"
Name="Subtle Emphasis"/>
<w:LsdException Locked="false" Priority="21" QFormat="true"
Name="Intense Emphasis"/>
<w:LsdException Locked="false" Priority="31" QFormat="true"
Name="Subtle Reference"/>
<w:LsdException Locked="false" Priority="32" QFormat="true"
Name="Intense Reference"/>
<w:LsdException Locked="false" Priority="33" QFormat="true" Name="Book Title"/>
<w:LsdException Locked="false" Priority="37" SemiHidden="true"
UnhideWhenUsed="true" Name="Bibliography"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="TOC Heading"/>
<w:LsdException Locked="false" Priority="41" Name="Plain Table 1"/>
<w:LsdException Locked="false" Priority="42" Name="Plain Table 2"/>
<w:LsdException Locked="false" Priority="43" Name="Plain Table 3"/>
<w:LsdException Locked="false" Priority="44" Name="Plain Table 4"/>
<w:LsdException Locked="false" Priority="45" Name="Plain Table 5"/>
<w:LsdException Locked="false" Priority="40" Name="Grid Table Light"/>
<w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark"/>
<w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful"/>
<w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 1"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 1"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 1"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 1"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 1"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 2"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 2"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 2"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 2"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 2"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 3"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 3"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 3"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 3"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 3"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 4"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 4"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 4"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 4"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 4"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 5"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 5"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 5"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 5"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 5"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 6"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 6"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 6"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 6"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 6"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="46" Name="List Table 1 Light"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark"/>
<w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful"/>
<w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 1"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 1"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 1"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 1"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 1"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 2"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 2"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 2"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 2"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 2"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 3"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 3"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 3"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 3"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 3"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 4"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 4"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 4"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 4"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 4"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 5"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 5"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 5"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 5"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 5"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 6"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 6"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 6"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 6"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 6"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Mention"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Smart Hyperlink"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Hashtag"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Unresolved Mention"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Smart Link"/>
</w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:8.0pt;
mso-para-margin-left:0in;
line-height:107%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
mso-font-kerning:1.0pt;
mso-ligatures:standardcontextual;}
</style>
<![endif]-->
</p><p class="MsoNormal" style="text-align: left;"><span lang="EN-CA">The primary purpose of taxonomies is to support
consistent topical tagging (indexing) of content and full and accurate content retrieval
based on the tagged taxonomy concepts that the end-user selects. The unit of
content that is tagged makes a difference in the retrieval results and user
experience. <span style="mso-spacerun: yes;"> </span>Users want to find specific
content, such as a paragraph, a captioned image, a timestamp section within an
audio or video file. This is not always possible. The traditional method of tagging
is to tag the entire file, document, or web page, even if the specific topic
with the desired information is only part of the larger file, such as a few
sentences within a web page or document of multiple paragraphs. The user then
spends time (or wastes time) trying to find the desired information in the
larger file.</span></p>
<h3 class="MsoNormal" style="text-align: left;"><span lang="EN-CA">Content components</span></h3>
<p class="MsoNormal" style="text-align: left;"><span lang="EN-CA">Fortunately, there are methods to tag and retrieve
content at smaller units, such as a text section identified with a heading,
within a longer document. These methods depend on having “structured” content, where
sections are marked off using a markup language, most commonly Extensible
Markup Language (XML). As XML is rather generic, there have emerged standards specifically
for XML-based component-based content management, including <a href="https://www.dita-ot.org/">DITA</a> (Darwin
Information Typing Architecture).</span></p><p class="MsoNormal" style="text-align: left;"></p><table cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: left;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgyoT50B0rVSIJulspfRqJSL3TUbOAdt8tvd7Fg2vT-UQXl6D8XwTSNGG4fb1qSF4oJ-6vXOSiqZStF1pL9HBEsBgU7Y8fsMIVx3jZtIns94m2f8QKfz50FvO4xaWpzro_sVW1p-5o4-6_HlXOhltZH03cNxLBBZPyZoEq4hubzQXa2IhEt755u6Bid/s365/2023-04-30%20(2).png" style="clear: left; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img alt="DITA publishing graphic" border="0" data-original-height="365" data-original-width="280" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgyoT50B0rVSIJulspfRqJSL3TUbOAdt8tvd7Fg2vT-UQXl6D8XwTSNGG4fb1qSF4oJ-6vXOSiqZStF1pL9HBEsBgU7Y8fsMIVx3jZtIns94m2f8QKfz50FvO4xaWpzro_sVW1p-5o4-6_HlXOhltZH03cNxLBBZPyZoEq4hubzQXa2IhEt755u6Bid/w245-h320/2023-04-30%20(2).png" title="https://www.dita-ot.org/" width="245" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><a href="https://www.dita-ot.org/">www.dita-ot.org</a></td></tr></tbody></table><span lang="EN-CA">Structuring content was not originally
developed for the purpose of detailed topical tagging/indexing and retrieval, though,
but rather for the purpose of creating (authoring) and publishing content,
especially to the web, more efficiently. Originally, the focus of structured
content was on marking up the document style and supporting keyword tags for
the entire document. The first content management systems (CMSs) were developed
shortly after the web in the 1990s to facilitate the publishing of web pages,
although later a distinction emerged be web content management systems and enterprise
content management systems. </span><p></p><p style="text-align: left;"></p>
<p class="MsoNormal" style="text-align: left;"><span lang="EN-CA">By the early 2000s, component content
management systems (CCMSs) emerged, whereby content is managed in units
(components) smaller and more specific than an entire document. CCMSs enable content
publishing to be more modular and flexible, supporting content reuse, and
making it easier to update content, by updating only the relevant components,
instead of the entire document. CCMSs are especially used for creating technical
documentation, but they are not limited to that use. Examples of CCMSs include Adobe
FrameMaker, Documentum, Hereto, Kontent.ai, Quark, Paligo, Sanity, and Tridion
Docs. While more precise tagging was not the original goal of CCMSs, it is a
beneficial outcome. </span></p>
<h3 class="MsoNormal" style="text-align: left;"><span lang="EN-CA">Taxonomies and component content management</span></h3>
<p class="MsoNormal" style="text-align: left;"><span lang="EN-CA">CCMSs, along with all CMSs, have come to support
taxonomies and tagging better over the years. This includes both support for more
taxonomy features, such as hierarchies and synonym (alternative labels), and
support for importing and exporting taxonomies in standard interoperable
formats. With respect to CCMSs, taxonomies can be built out to a greater level
of detail, with concepts specific to the component topics of CCMS. However, whoever
is creating the taxonomy should remember not to create concepts that are so
specific that a concept is applicable to only a single component topic. A
single taxonomy concept should retrieve multiple results.</span></p>
<p class="MsoNormal" style="text-align: left;"><span lang="EN-CA">CCMSs, along with all CMSs, can also connect
to or integrate with taxonomies managed in dedicated taxonomy management
systems, such as <a href="https://www.poolparty.biz/">PoolParty</a>. Since organizations tend to have multiple CMSs,
each for different kinds of content and purposes, they are likely to end up
creating multiple, separate (siloed) taxonomies with similar or overlapping
concepts. Therefore, the best strategy for enterprise taxonomy management is to
manage taxonomies centrally, either as a single master taxonomy or with
multiple taxonomies linked together in dedicated taxonomy management software,
which can connect to CMSs with APIs (application programming interfaces) to
push the taxonomy out to the CMSs, including CCMSs. Additionally, prebuilt
integrations of taxonomy management systems and CCMSs, such as <a href="https://www.poolparty.biz/poolparty-powertagging-integrations-sharepoint-adobe-experience-manager-tridion">PoolParty and Tridion Docs</a>, are becoming more common.</span></p>
<p class="MsoNormal" style="text-align: left;"><span lang="EN-CA">There is also a growing interest in
taxonomies at conferences dealing with component content management. Last October
I attended the <a href="https://lavacon.org/">LavaCon</a> conference for content strategy for the first time, where
my pre-conference workshop on taxonomies was well attended. Two weeks ago, I
participated in the <a href="https://convex.infomanagementcenter.com/">ConVEx</a> conference, where there is more focus on component
content management than at LavaCon. (ConVEx was formerly the DITA North America
conference.) In contrast to LavaCon’s two presentations on taxonomies, ConVEx
had a track with the “taxonomy” theme and five presentations focused on
taxonomies and another three presentations with topics related to taxonomies. </span></p>
<p class="MsoNormal" style="text-align: left;"><span lang="EN-CA">Component content management enables more targeted
topic tagging and opens up more possibilities for rich taxonomies. Thus, as a
taxonomist, I look forward to learning more about CCMSs and how they taxonomies
can best be applied in these systems.</span></p>
<p style="text-align: left;"></p>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-86485447882791533092023-03-31T23:30:00.000-04:002023-05-01T07:49:59.765-04:00Taxonomy and Information Architecture Compared<p style="text-align: left;"><span style="font-family: inherit;"><span>There is considerable overlap between the fields of information taxonomies and information architecture. Both involve information organization, labeling, search, and findability. In some organizations the job roles and titles are combined. I previously blogged on “<a href="http://accidental-taxonomist.blogspot.com/2013/11/information-architecture-and-taxonomies.html ">Information Architecture and Taxonomies</a>,” observing that “information architecture” in name seemed to be declining while aspects of its practice continued to be strong, since it was an underlying theme in several of the talks at major taxonomy conference, Taxonomy Boot Camp in 2013.</span></span></p><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: right; margin-left: 1em; text-align: right;"><tbody><tr><td style="text-align: center;"><img alt="Photo of Information Architecture Conference opening: welcome on the screen and a jazz band playing" border="0" data-original-height="984" data-original-width="1392" height="226" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhkD-YUoi04qnUI9VZkwRl0NcqIt_zHIIxM0xQU7bZUsEtD1zHwKH0JqwMStioIkgwUo7YyqVyR0n0Y0BHMzANJxXKGK4_sYfwQuAxcGm8L6uy5q3eq65BB6EizIIz743XZMY9O4gcZFxjILh5ZkycyA7pHnRGFINjbl7GLmWTYrX7Zuyi4pixVBbvp/w320-h226/IAC%20welcome.png" style="margin-left: auto; margin-right: auto;" title="Information Architecture Conference opening. Photo credit: Marisela Meskus" width="320" /></td></tr><tr><td class="tr-caption" style="text-align: center;">Information Architecture Conference opening. <i>Photo <a href="https://www.linkedin.com/in/meskus/" target="_blank">Marisela Meskus</a></i></td></tr></tbody></table><p></p><p style="text-align: left;"><span style="font-family: inherit;">This week, for the first time, I am attending in person the </span><a href="https://www.theiaconference.com" style="font-family: inherit;">Information Architecture Conference</a><span style="font-family: inherit;">, being held in New Orleans March 28 - April 1, so it’s been interesting to hear how information architects consider taxonomies.</span></p><h3 style="text-align: left;"><span style="font-family: inherit;"><span style="font-kerning: none; font-size: small;">How Information Architecture and Taxonomy Overlap</span></span></h3><span style="font-family: inherit;"><span style="font-kerning: none;"><p style="text-align: left;"><span style="font-family: inherit;">The fields of information architecture and taxonomy are related beyond the stated shared practices of information organization, labeling, search, and findability. </span></p></span><span style="font-kerning: none;">When I give an introduction to taxonomies, I explain that a taxonomy is an intermediary between users and content to connect users to content by means of terms that the users understand and by the display of the terms in hierarchies, facet-filters, or type-ahead suggestions, which enable users to explore and interact with the taxonomy. This is clearly an aspect of information architecture. </span></span><p></p><p style="text-align: left;"><span style="font-family: inherit;"><span style="font-kerning: none;">In my own career path, I discovered taxonomy and information architecture at the same time. I had been working as a “controlled vocabulary editor” and had the opportunity to work on an interdisciplinary team for a newly design information product. A user interface for school library research database included both a hierarchical taxonomy that was designed to fit with a particular user interface. </span></span></p><p style="text-align: left;"><span style="font-family: inherit;"><span style="font-kerning: none;">At the Information Architecture Conference, I asked for a raise of hands of my session audience of how many had worked with taxonomies, and it seemed to be over 80%. At the conference, I met information architects who specialized in taxonomies, and taxonomists who had an interest and done some work in information architecture. Even though I identify as a taxonomist, I already knew a number of speakers at the Information Architecture conference due to the overlapping communities.<br /></span></span></p><h4 style="text-align: left;"><span style="font-family: inherit;"><span style="font-kerning: none;">How Information Architecture and Taxonomy Differ</span></span></h4><span style="font-family: inherit;"><span><p style="text-align: left;"><span style="font-family: inherit;">Information architecture is a discipline and a profession that is larger and more established than that of taxonomies. Although taxonomy work is growing, there are still more college courses on information architecture than on taxonomies, more books on information architecture than on taxonomies, and more people with “information architect” than “taxonomist” as a job title (based on LinkedIn searches). </span></p></span><span>Listening to sessions at the Information Architecture Conference and having discussions with participants, I began to see a clearer picture on how the fields of information architecture and taxonomies differ.</span></span><p></p><p style="text-align: left;"><span style="font-family: inherit;"><span>The Information Architecture Conference brings together a community of professionals who share ideas and experiences. There is no comparable taxonomist community as taxonomy work, compared to information architecture work, tends to be done by those with different professional backgrounds: information architects, librarians, content managers, metadata architects, indexers, ontologists, etc. It’s telling that there is not just one conference at which I present about taxonomies but multiple. (Knowledge management, content strategy, knowledge graphs, and data science are the fields of conferences at which I have spoken about taxonomies in the past year.) The only conference about taxonomies, Taxonomy Boot Camp, is more of specialized track within the KM World conference, and aims to provide taxonomy best practices and case studies to managers and directors of content, product, or knowledge management. It is not really a forum for taxonomists to discuss topics of their profession, as the Information Architecture Conference is.</span></span></p><p style="text-align: left;"><span style="font-family: inherit;">It seems that information architecture is more of a discipline and a field, whereas taxonomy is more of tool or system (although a very important one). In addition to information architects in organizations in various industries and consultants, the Information Architecture Conference includes professors and students in the field. By contrast taxonomy is not a field of study, research, or focus in academia. It is a focus area only in industry and consulting. Information architecture seems to allow more room for theory than does the taxonomy field. <br /></span></p><h4 style="text-align: left;"><span style="font-family: inherit;"><span style="font-kerning: none;">How Information Architecture and Taxonomy Are Related</span></span></h4><span style="font-family: inherit;"><span style="font-kerning: none;"><p style="text-align: left;"><span style="font-family: inherit;">From a "taxonomic" perspective, which is broader? For information architects, taxonomy is narrower than information architecture. There is no doubt that information architecture is broader in various ways, including content/information organization, design, user experience, and even organization of non-digital information spaces. For example, information architects are concerned not only with taxonomies to support searching and browsing for information, but also with content organization and navigation menu structuring in websites and in software user interfaces. </span></p></span></span><p></p><p style="text-align: left;"><span style="font-family: inherit;"><span style="font-kerning: none;">Taxonomists, on the other hand, do not consider taxonomies as a sub-field of information architecture, but rather consider the two fields as adjacent and closely related. This is because the taxonomies that information architects create tend to be small, such as term lists for metadata properties or facets or as hierarchies to model menu navigation or site maps. Professional taxonomists tend to work on large dynamic taxonomies or thesauri that are used to tag/index and retrieve content or data in one or more systems, often where the user interface is already prescribed.</span></span></p><p style="text-align: left;"><span style="font-family: inherit;"><span style="font-kerning: none;">The related fields or disciplines are also different. Information architecture has a closer relationship with fields of design, user experience, sociology, and psychology. Taxonomy has a closer relationship with indexing/tagging, natural language processing, ontologies, Semantic Web technologies, and knowledge management. One related field shared by both information architecture and taxonomy is structured content, which was also a subject of presentations at this year's Information Architecture conference and the field of my next conference.</span></span></p>
<p style="font-feature-settings: normal; font-kerning: auto; font-optical-sizing: auto; font-size-adjust: none; font-stretch: normal; font-style: normal; font-variant-alternates: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; font-variant: normal; font-variation-settings: normal; line-height: normal; margin: 0px;"></p>
<p style="font-feature-settings: normal; font-kerning: auto; font-optical-sizing: auto; font-size-adjust: none; font-stretch: normal; font-style: normal; font-variant-alternates: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; font-variant: normal; font-variation-settings: normal; line-height: normal; margin: 0px; min-height: 12px;"><span style="font-family: inherit;"><span style="font-kerning: none;"></span></span></p>
<p style="font-feature-settings: normal; font-kerning: auto; font-optical-sizing: auto; font-size-adjust: none; font-stretch: normal; font-style: normal; font-variant-alternates: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; font-variant: normal; font-variation-settings: normal; line-height: normal; margin: 0px; min-height: 12px;"><span style="font-family: inherit;"><span style="font-kerning: none;"></span></span></p>
<p style="font-feature-settings: normal; font-kerning: auto; font-optical-sizing: auto; font-size-adjust: none; font-stretch: normal; font-style: normal; font-variant-alternates: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; font-variant: normal; font-variation-settings: normal; line-height: normal; margin: 0px; min-height: 12px;"><span style="font-family: inherit;"><span style="font-kerning: none;"></span></span></p>
<p style="font-feature-settings: normal; font-kerning: auto; font-optical-sizing: auto; font-size-adjust: none; font-stretch: normal; font-style: normal; font-variant-alternates: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; font-variant: normal; font-variation-settings: normal; line-height: normal; margin: 0px; min-height: 12px;"><span style="font-family: inherit;"><span style="font-kerning: none;"></span></span></p>
<p style="font-feature-settings: normal; font-kerning: auto; font-optical-sizing: auto; font-size-adjust: none; font-stretch: normal; font-style: normal; font-variant-alternates: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; font-variant: normal; font-variation-settings: normal; line-height: normal; margin: 0px; min-height: 12px;"><span style="font-family: inherit;"><span style="font-kerning: none;"></span></span></p>
<p style="font-family: "Helvetica Neue"; font-feature-settings: normal; font-kerning: auto; font-optical-sizing: auto; font-size-adjust: none; font-stretch: normal; font-style: normal; font-variant-alternates: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-position: normal; font-variant: normal; font-variation-settings: normal; line-height: normal; margin: 0px;"><span style="font-kerning: none;"><br /></span></p>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-10773113699579311962023-02-25T22:29:00.014-05:002023-03-12T20:29:51.917-04:00Related Concepts in Taxonomies<p></p><table cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: left;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjHx9ufhAlFbYVVipXBAdPb0RftTRw_LL8ZUj5yWj1GeHz_QyVyhXd7tvy7-lzmJDoKsL3T7i2R8fGEF0QlThli1nb40gcWMsu0SBzjWw6d0SSsBSau7R5nUmgcIz73-kO8gEsRlr0BrrZ5RpAThrPsL7GTYB_-tb51nUPjeGkJYF2HGSQvTxSorFP6/s728/Related%20relationship%20graphic.jpg" style="clear: left; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img alt="Related concepts in a taxonomy" border="0" data-original-height="401" data-original-width="728" height="220" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjHx9ufhAlFbYVVipXBAdPb0RftTRw_LL8ZUj5yWj1GeHz_QyVyhXd7tvy7-lzmJDoKsL3T7i2R8fGEF0QlThli1nb40gcWMsu0SBzjWw6d0SSsBSau7R5nUmgcIz73-kO8gEsRlr0BrrZ5RpAThrPsL7GTYB_-tb51nUPjeGkJYF2HGSQvTxSorFP6/w400-h220/Related%20relationship%20graphic.jpg" title="A and B are related; C and D are related" width="400" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><i>A and B are related; C and D are related.</i></td><td class="tr-caption" style="text-align: center;"><br /></td></tr></tbody></table><span lang="EN-CA">Taxonomies and thesauri are characterized
by having hierarchical relationships linking their terms. The associative
relationship (or related concept, Related Term, or RT), on the other hand, is
a fundamental feature of thesauri, but it is merely an optional feature of
taxonomies. </span><p></p><p></p><p><span lang="EN-CA">An over-simplistic distinction between taxonomies and thesauri is
the presence of associative relationships, although I would disagree, because taxonomies
can have associative relationships, and there are other structural design
differences between taxonomies and thesauri. (See my past blog posts <a href=" http://accidental-taxonomist.blogspot.com/2014/01/taxonomies-vs-thesauri.html">Taxonomies vs. Thesauri</a>
and <a href="https://accidental-taxonomist.blogspot.com/2016/06/taxonomies-vs-thesauri-practical.html">Taxonomies vs. Thesauri: Practical Implementations</a>)</span></p><p><span lang="EN-CA">The associative (related) relationship is a generic, nonhierarchical, symmetrical (same in both directions), reciprocal relationship between pairs of terms/concepts in a thesaurus or taxonomy. "Related concept" actually refers to a kind of relationship, not a kind of concept. The following figure illustrates that <b>Data protection</b> and <b>Privacy</b> are related. <br /></span></p><p class="MsoNormal"></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiagvFylzkSy4O1CRYNX22RJvwWLGI2VRjw3DHxOyeK5yCcYf4zvipRNjbToC0T-qWeoEFjhUmcDdwlXUjDbYfBREC1XtXOUEVBtu7YSlxwTxsTOeOlwBwXNv-ED-3TVA2YmJ_GAkR_hdIShQEz0tHM7_8PAzo1QYE8nQzCrBzgbyNIV5E02wLe7dlf/s648/Related%20relationship%20graphic.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="182" data-original-width="648" height="113" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiagvFylzkSy4O1CRYNX22RJvwWLGI2VRjw3DHxOyeK5yCcYf4zvipRNjbToC0T-qWeoEFjhUmcDdwlXUjDbYfBREC1XtXOUEVBtu7YSlxwTxsTOeOlwBwXNv-ED-3TVA2YmJ_GAkR_hdIShQEz0tHM7_8PAzo1QYE8nQzCrBzgbyNIV5E02wLe7dlf/w400-h113/Related%20relationship%20graphic.png" width="400" /></a></div><br /><span lang="EN-CA">It is true that many taxonomies do not have
associative relationships. This is for various reasons. The function of the
taxonomy in the user interface may not require the support of related concepts,
such as when the taxonomy is displayed only as facets for refining results or only as
type-ahead taxonomy term suggestions when a user enters a search string into a
search box. The taxonomy may be implemented in a system (such as a commercial
off-the-shelf content management system or SharePoint) that does not support
the links/navigating to related concepts in the user interface. A taxonomy may be
too small to make beneficial use of associative relationships if most of the
taxonomy can quickly be browsed and seen. Finally, and perhaps of the greatest
potential significance, is that relationships across different types of
concepts can instead be
better supported with customized semantic relationships based on custom schema
and ontologies, which can be applied to a taxonomy. For example, having <b>Physicians</b><i> practice</i> <b>Medicine </b>and <b>Medicine </b><i>isPracticedBy</i> <b>Physicians</b>, instead of <b>Physicians</b> <i>related</i> <b>Medicine</b>.<br /></span><p></p>
<p class="MsoNormal"><span lang="EN-CA">It is not so much the <i>presence </i>but rather
the <i>extent </i>of associative relationships that also distinguishes thesauri
from taxonomies.<span style="mso-spacerun: yes;"> </span>In a traditional
thesaurus, associative relationships are as prolific as hierarchical
relationships, and perhaps even more so, and they occur between terms of all
different kinds and different types of relatedness. The thesaurus standards
(ANSI/NISO Z39.19 and ISO 25964-1) provide a list of possible types of
associative relationships (process and agent, action and target, cause and
effect, object and property, object and origins, and discipline and object,
among many others). When taxonomies have associative relationships, they tend
to be limited to only certain categories, facets, or concept schemes of the taxonomy.</span></p>
<h3 class="MsoNormal" style="text-align: left;"><span lang="EN-CA">Related Concepts and SKOS Concept Schemes</span></h3>
<p class="MsoNormal"><span lang="EN-CA">Most taxonomies these days, if they are of
any significant size (hundreds or thousands of concepts) and intended for use
in more than one application, are created in the <a href="https://www.w3.org/2009/08/skos-reference/skos.html" target="_blank">SKOS</a> (Simple Knowledge Organization
System) data model. (Smaller taxonomies might be created in a spreadsheet and
imported into a content management system.) The highest level of organizational
structure in SKOS is the concept scheme. SKOS-based taxonomy management
software will group and display multiple concept schemes together in a single
“project” or “knowledge model,” which is intended for a single business use, set
of content, user audience, or implementation (with some overlap of multiple use
cases acceptable). While SKOS does not provide any recommendation on what you
should use concept schemes for, it has become common practice to designate a
concept scheme for a taxonomy facet or a metadata property/field.<span style="mso-spacerun: yes;"> </span>Even when concept schemes are not currently
implemented as facets, they might be in the future, so it is good practice to
created concept schemes to represent facets. The structure of concept schemes representing
facets is also is also a good organizing principle for constructing any
taxonomy. Concept schemes also tend to reflect top-level “classes” of
ontologies (although not the very esoteric top class of “Thing”).</span></p>
<p class="MsoNormal"><span lang="EN-CA">SKOS permits the creation of related
concept relationships both within and between concept schemes. SKOS also has
mapping relationships called matching properties, including relatedMatch, for
use between concept schemes, whether they are in the same “project” (sharing
the same, initial, domain part of a URI) or not. The option to use either
related or relatedMatch across concept schemes of the same project can be a
source of confusion.</span></p>
<h3 class="MsoNormal" style="text-align: left;"><span lang="EN-CA">Best Practices for SKOS Related Concepts</span></h3>
<p class="MsoNormal"><span lang="EN-CA">If you are implementing concept schemes
each as a facet/filter/refinement in a user interface, then it is best practice
not create associative (related) relationships between concepts in different
concept schemes. Facets function as mutually exclusive aspects or dimensions of
content items and queries. Any “relatedness” is implicit based on the search
results, but not from the taxonomy itself, which should be flexible to allow
any combination of concepts from facets and not prescribe relatedness. For
example, a user may want to filter a search on movies by which movies meet
selected criteria (facets) of a chosen genre, actor, director, topical theme, and
country of production, and the result set will implicitly indicate in which movies
where these aspects are related. </span></p>
<p class="MsoNormal"><span lang="EN-CA">Enriching a taxonomy with the semantics of
an ontology, in addition to supporting additional data attributes (such as
movie production year, actor nationality and birth date, etc.), supports
connections across concept types that can be utilized in a front-end
application. The user can search not only for movies, but also search for other
entities, such as actors (who appear in movies of a certain genre directed by a
certain director), or directors (who directed movies on certain themes from
certain countries), etc. <span style="mso-spacerun: yes;"> </span>This involved
creating customized, semantic relationships between classes which correspond to
the concept schemes: <b>Actor</b> <i>performsIn</i> <b>Movie title</b> and <b>Movie
title</b> <i>hasActor</i> <b>Actor</b>, <b>Movie title</b> <i>isProducedIn</i> <b>Country</b>
and <b>Country</b><i> isOriginOf</i> <b>Movie title</b>, etc. These semantic
relationships, of course, make any generic SKOS related relationships across
the concept schemes unnecessary, redundant, and rather meaningless.</span></p>
<p class="MsoNormal"><span lang="EN-CA">Thus, regardless of the use of your concept
schemes, the related concept relationship is best not used between concepts in
different concept schemes. Rather, the related concept relationship is better
used between concepts <i>within</i> a concept scheme, especially topical
(subject) concepts, for example, relating the concepts <b>Data quality</b> and <b>Quality
management</b>. Relatedness between named entities within a concept scheme, on
the other hand, such as concept schemes for People, Organizations, and
Geographic places, is best left to be implicit from the retrieved content and
not prescribed in a taxonomy, which may be dependent on the content, change
over time, and be too subjective.</span></p>
<p class="MsoNormal"><span lang="EN-CA">Even if the current end-user application of
a taxonomy does not support user interaction with related links, associative
relationships can support tagging, both manual and automated. Finally, a taxonomy
typically has a longer life than a single application, so incorporating in
related concept relationships while the taxonomy is being built and regularly
maintained is a good practice for the future use of the taxonomy. </span></p>
<p></p>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-23022369939482401352023-01-31T21:56:00.013-05:002023-02-08T12:52:57.594-05:00Taxonomies vs. Ontologies<p><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">The question often comes up: how are
taxonomies and ontologies different? While there are some short simple answers
(such as: taxonomies are hierarchies, and ontologies are semantic networks), it
is understandable that the distinction is not that clear. There is considerable
overlap. Ontologies may contain taxonomies, and taxonomies can be semantically
enriched to become ontology-like. The same software tools, for example <a href="https://www.poolparty.biz/" target="_blank">PoolParty</a>, support the creation
of both. </span></span></span>
</p><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">One of the trends in
data/information/knowledge management in the convergence of systems, methods,
and technologies, including the convergence of taxonomies and ontologies. It’s
gotten to the point that some people will refer to taxonomies and ontologies
almost interchangeably, as if they are essentially the same thing. They are
not, although they are increasingly combined.<span style="mso-spacerun: yes;"> </span>It’s interesting that one of the most active
discussion channels within the <a href="https://lnkd.in/euERXyvC" target="_blank">Taxonomy </a><a href="https://lnkd.in/euERXyvC" target="_blank">Talk community</a> on Discord is on
ontologies. </span></span></span></p><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"></span></span></p><div class="separator" style="clear: both; text-align: center;"><span style="font-size: small;"><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjNanBl19ZWiyl7-2b77hIy-09YLarFGo7Jgta1iyYaTz-EcJ4Kax3xNEAjdTKkF_aPOz2XckRVrOWwXkWuCJYZzGjt2TVo0TT1EtVvG6SUtZ4aH9wL0yojI174nipd0jOzLMZ1zgvcPz5DPvolTx2PyqaXYaWNoDpPL_tsgmEEZUEDXps9CSb7NedY/s993/Taxonomy-vs-ontology.png" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="686" data-original-width="993" height="276" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjNanBl19ZWiyl7-2b77hIy-09YLarFGo7Jgta1iyYaTz-EcJ4Kax3xNEAjdTKkF_aPOz2XckRVrOWwXkWuCJYZzGjt2TVo0TT1EtVvG6SUtZ4aH9wL0yojI174nipd0jOzLMZ1zgvcPz5DPvolTx2PyqaXYaWNoDpPL_tsgmEEZUEDXps9CSb7NedY/w400-h276/Taxonomy-vs-ontology.png" width="400" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><span style="font-size: small;"><span style="font-family: inherit;"><i style="font-family: inherit;">Taxonomy vs. Ontology (</i></span></span><a href="https://graphviews.poolparty.biz/GraphViews" target="_blank"><span style="font-size: small;"><span style="font-size: small;"><span style="font-family: inherit;"><i style="font-family: inherit;">https://graphviews.poolparty.biz/GraphViews</i></span></span></span></a><span style="font-size: small;"><span style="font-family: inherit;"><i style="font-family: inherit;">)<br /></i></span></span></td></tr></tbody></table><br /><span style="font-family: inherit;"></span></span></div><span style="font-size: small;"><span style="font-family: inherit;"></span></span><p></p><h3 class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="font-family: inherit;"><span lang="EN-CA" style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;">Uses</span></span></span></h3><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA" style="color: black; mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;">Although both taxonomies and
ontologies are kinds of knowledge organization systems, which support access to
information, their specific uses tend to differ. The primary use of information
taxonomies is for consistent tagging and accurate and comprehensive retrieval
of <i>content </i>items. These could be documents, components (sections) of
documents, web or intranet pages, or digital assets (image, audio, video files,
etc.). Ontologies, with their inclusion or linkages to instances/individuals, with
their various attributes, are more focused on the specifics of <i>data</i>:
data retrieval, data comparison, and data analysis. Taxonomies are </span><span lang="EN-CA">primarily for what a content item is <i>about</i> (although
content/document types may also be part of taxonomy), as in “get me all the
information resources about…,” or “get me a list of products with…” and specifying
set of features and price range as filters. Ontologies, on the other hand, can
support more complex, multistep queries, such as “get me a list of products
with…” a set of features and price range, whose vendors are located in Canada and
have a minimum annual revenue of CAD $50 million. </span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">In comparing retrieval of content and data,
for example, taxonomies can retrieve a spreadsheet file, whereas ontologies can
retrieve data from individual cells in the spreadsheet. Ontologies can traverse
data in a database. While this could be a relational database, increasingly ontologies
are used with graph databases, since ontologies are also structured as graphs.</span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><h3 class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="font-family: inherit;"><span lang="EN-CA">Origins</span></span></span></h3><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">Another major difference between taxonomies
and ontologies is their origins. Information taxonomies (not biological
taxonomies) originated in the discipline of library science. Specifically, I would
say that taxonomies have evolved as a kind of flexible hybrid of classification
systems and thesauri. Ontologies, on the other hand, (when not in philosophy)
tend to be taught and researched as a part of computer science. Again, there
has also been convergence of library science and computer science in the field
of information science. Nevertheless, library/information science and
computer/information science are different approaches. </span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">Taxonomies have also become an area of
interest in information architecture, user experience design, content
management, and digital asset management. Taxonomies are also related to
terminology management and information search and retrieval. Ontologies, on the
other had, have become an area of interest in data science, data engineering,
and graph data management. Ontologies also borrow concepts from set theory in
mathematics and logic from philosophy.</span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">Taxonomies and ontologies follow different
standards, but the standards have also converged in a way. Taxonomies have no
standard of their own but follow the thesaurus standards (ANSI/NISO
Z.39.19 and ISO 25964) for recommended best practices. Ontologies are based on
W3C standards of <a href="https://www.w3.org/RDF/" target="_blank">RDF</a>, <a href="https://www.w3.org/TR/rdf-schema/" target="_blank">RDF-Schema</a>, and the formal language of <a href="https://www.w3.org/TR/owl2-overview/" target="_blank">OWL</a> (Web Ontology Language). The W3C then
published a recommendation for taxonomies, thesauri, and other knowledge
organization systems called <a href="https://www.w3.org/2004/02/skos/" target="_blank">SKOS</a> (Simple Knowledge Organization System) in 2009,
and since then it has become widely adopted. SKOS is based on RDF, as is the
ontology standards RSF-S. As a result, SKOS and RDF-S statements or namespaes can be combined
in the same knowledge organization system, and taxonomies and ontologies can
thus be combined.</span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><h3 class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="font-family: inherit;"><span lang="EN-CA">Features</span></span></span></h3><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">Both taxonomies and ontologies aim to
describe a knowledge domain with collections of entities structured into groups
or types, with relationships between them. Ontologies go further in describing
the relationships in more detail. Attributes are also more extensive in
ontologies. Both support the options for notes or definitions. </span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><h4 class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">Concepts or Entities</span></span></span></h4><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">Taxonomies are comprised of concepts (sometimes
called terms), which are things. Concepts can be generic or specific and may even
include named entities (unique proper nouns). Taxonomies do not differentiate
between generic concepts and named entities, which correspond to “individuals”
in an ontology. Ontologies, on the other hand, distinguish between two types of
entities: classes and individuals. Classes can be broad or specific, but, as
the name implies, they are intended to contain something, either subclasses or
individuals. By contrast, leaf nodes (the narrowest concepts in a hierarchy) in
a taxonomy could actually be quite broad in meaning. </span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">Individuals, as defined by an ontology, tend
to be named entities (proper nouns), and they should be uniquely individual.
This may not be obvious. A brand name product is a proper noun, but technically
it is not an individual, because there are numerous specific instances of the
product owned by different people. There may be some differences of opinion on
how to define individuals.</span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><h4 class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">Relationships</span></span></span></h4><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">Taxonomies follow thesaurus standards for relationships.
Thesaurus hierarchical relationships comprise three types: generic-specific or “is
a” kind of relationship, generic-instance (where the instance is a named entity
or proper noun), and whole-part. Ontologies have only generic-specific “is a”
hierarchical relationships, which are between classes and subclasses. The
relationship between an individual and a class is not considered hierarchical
in an ontology but rather a relationships of class-member. Also, the
whole-part relationship is not considered hierarchical in ontologies (but could be created as a semantic relationship).<br /></span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">While generic-instance is a permitted
hierarchical relationship type In a taxonomy, named entity concepts (proper
nouns) are not so often narrower to a corresponding generic concept, but rather
tend to be grouped in their own separate concept scheme to serve as a separate search
facet or filter. </span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">A generic associative (“related”)
relationship may exist in taxonomies, although it is more of a feature of
thesauri. It is bidirectional and reciprocal, and it tends to be used between
concepts within the same concept scheme, which often corresponds to a class in
an ontology. Ontologies do not have a generic associative relationship. Instead,
ontologies have semantic relations which are designated by the ontology creator,
just as the classes are designated, and they are not used within classes but
across a specified pair of classes. Suggestions of what might be of related
interest to the end-user is not within the scope of an ontology’s purpose which
is more structured and based on rules. Ontologies may have other bidirectional
reciprocal relationships, such as “goes with,” “has sibling, “accompanies,”
etc. </span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><h4 class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">Equivalency and alternative labels</span></span></span></h4><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">In a taxonomy, each concept has a single
preferred label in each language for display and any number of alternative labels
and hidden labels per language to help match on searching or tagging. In the
traditional thesaurus model, “nonpreferred” terms redirect to “preferred”
terms. The alternative labels are sufficiently equivalent in the context of the
taxonomy and content to be used for a given concept, and thus might not be
exact synonyms. Alternative labels include synonyms, near synonyms, and possibly
even narrower terms not deemed needed as concepts with preferred labels.</span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA" style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;">In ontologies, t</span><span lang="EN-CA" style="line-height: 107%; mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;">he OWL element sameAs is intended for
equivalency of individuals, and equivalentClass is for the equivalency of
classes, and they mean exact equivalence. But there is no designation of one name
being preferred and the other alternative. They all are preferred. The use of
sameAs and equivalentClass are not intended for use within a single ontology,
but rather across different ontologies. So, those OWL elements are similar to the
SKOS exactMatch relationship, which is used across concept schemes or taxonomies.
They do not support search within the same data set as alternative labels do.</span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><h4 class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">Enforcement of rules</span></span></span></h4><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">SKOS is a data model for taxonomies and
thesauri, but it does not specify any rules for usage. Rather, the taxonomy
creator should attempt to follow the guidelines, not exactly rules, in the thesaurus
standards (ANSI/NISO Z39.19 and ISO 25964-1). The quality standards include disjoint
labels (a label can be used only once for a concept, preferred or alternative,
and for only one concept), single relationships (a pair concepts my have hierarchical
or associative relationships between them, but not both), and no hierarchical
cycles. The standard for ontologies, on the other hand, OWL, has many rules
built into it. This makes OWL ontologies more powerful by supporting inferencing and
reasoning. </span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><h3 class="MsoNormal" style="text-align: left;"><span style="font-size: medium;"><span style="font-family: inherit;"><span lang="EN-CA">Conclusions</span></span></span></h3><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA">Taxonomies and ontologies share some features,
but each has its own additional features. Thus, a combination of a SKOS
taxonomy with an OWL ontology combines the features of both. Furthermore, the
combination of a taxonomy with an ontology also enables a combination of uses,
namely the search and retrieval for both content and data together. Rather than
a convergence of taxonomies and ontologies, they are carefully and deliberately
combined to maximize their benefits. </span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA"> </span></span></span></p><span style="font-size: small;"><span style="font-family: inherit;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: inherit;"><span lang="EN-CA"> </span></span></span></p>
<p></p>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com8tag:blogger.com,1999:blog-9094731596169096992.post-54184135785644417332022-12-30T21:33:00.008-05:002023-01-14T11:35:46.886-05:00Taxonomy Definition<p>I usually explain that a taxonomy is a structured kind of controlled vocabulary, which is list of terms (or concepts) usually used to tag content to aid in its retrieval. The structure can be hierarchical, faceted, or a combination. Other people have defined taxonomies for a general audience in more simplistic ways as a kind of hierarchical classification system. So, while a taxonomy has two main features (naming and structure), my preferred definition has focused on the controlled vocabulary and naming aspect, whereas other definitions focus on the hierarchical classification aspect of taxonomies. However, a taxonomy and a classification system are not necessarily the same. While it is understandable that a definition is simplified for a general audience, it should not be simplified to the extent of being misleading.</p><p>I have blogged previously on the differences between <a href="http://accidental-taxonomist.blogspot.com/2013/04/taxonomies-vs-classification.html" target="_blank">taxonomies and classification systems</a>, so I won’t repeat all the differences again. The main point is that a classification system is generic and rigid and is intended to be used widely, such as the Dewey Decimal Classification for libraries, whereas a taxonomy tends to be customized for a particular use case and context and is flexible and undergoes changes.</p><p></p>Meanwhile, there are also a few well-known classification systems that are called “taxonomies,” such as the Linnaean taxonomy of organisms and Bloom’s taxonomy of educational objectives. These seem quite different from the information-retrieval type of taxonomy. The Linnaean hierarchical levels have names (Kingdom, Phylum, Class, etc.). The relationship of the hierarchical levels to each other are not all of the thesaurus standards: generic-specific, generic-instance, or whole-part. Rather, the Linnaean taxonomic relationship are generic-specific only, or more precisely that of member of class or subclass. Bloom's taxonomy has a completely different hierarchical model that does not follow thesaurus standards at all. <br /><p></p><p>How does a taxonomy of concepts for information retrieval relate to a scientific taxonomy? They are similar, and the differences are not so great that there should be considered different meanings of the word “taxonomy.” If we consider that taxonomies are systems to name and organize things hierarchically, then a taxonomy for information retrieval, comprised of terms for tagging and retrieving content (documents, images, etc.), can be considered a taxonomy <i>of a</i> controlled vocabulary, in contrast to taxonomies of things, such as organisms. This is a slightly different perspective than to consider a taxonomy as a kind of controlled vocabulary, as I previously had. The following diagram illustrates a possible way to consider how information-retrieval taxonomies related to classification systems and controlled vocabularies.</p><p></p><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgiuGwRX6SFy4OJ6J6ur4d1x-H-NFJeaFK_HugSe4a8tuh-VDEfTolYn2I3HMNgB6H2fQxYYk1I_vaGeMzJB5-RmQZTJo7jP_np_oTSO89OOl8PGcfShE1i_e53sI9hT0uW4lv7958aWmec0I3lFez7Exf8iO0b8n0CNsqKmm9ekLwiNYxgVTekzAtO/s967/Taxonomy-definition.png" style="margin-left: 1em; margin-right: 1em;"><img alt="Diagram showing that information taxonomies are at the interssection of classification systems and controlled vocabularies" border="0" data-original-height="487" data-original-width="967" height="161" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgiuGwRX6SFy4OJ6J6ur4d1x-H-NFJeaFK_HugSe4a8tuh-VDEfTolYn2I3HMNgB6H2fQxYYk1I_vaGeMzJB5-RmQZTJo7jP_np_oTSO89OOl8PGcfShE1i_e53sI9hT0uW4lv7958aWmec0I3lFez7Exf8iO0b8n0CNsqKmm9ekLwiNYxgVTekzAtO/w320-h161/Taxonomy-definition.png" title="Diagram showing that information taxonomies are at the interssection of classification systems and controlled vocabularies" width="320" /></a></div><br />Several kinds of knowledge organization systems are defined by their published standards. For thesauri, there are <a href="https://www.niso.org/publications/ansiniso-z3919-2005-r2010" target="_blank">ANSI/NISO Z39.19</a> and <a href="https://www.iso.org/standard/53657.html" target="_blank">ISO 25964</a>. For terminologies, there is <a href="https://www.iso.org/committee/48136.html" target="_blank">ISO/TC 37/SC 3</a> and other related standards. For ontologies, there is <a href="https://www.w3.org/OWL/" target="_blank">OWL (Web Ontology Language)</a> from the <a href="https://www.w3.org/" target="_blank">W3C</a>. There is no standard, however, specifically for “taxonomies” or even for “classification systems,” which is a reason why these remain difficult to define. The designations “classification system,” “classification scheme,” and “taxonomy” have been used interchangeably.<p></p><p>Wikipedia provides the definition at the entry for <a href="https://en.wikipedia.org/wiki/Taxonomy" target="_blank">Taxonomy</a>: “A taxonomy (or taxonomical classification) is a scheme of classification, especially a hierarchical classification, in which things are organized into groups or types.” But then it goes on to say, “it may refer to a categorisation of things or concepts.” Thus, an information-retrieval taxonomy is a categorization of <i>concepts</i> (also called terms in a controlled vocabulary). It is not a classification system, since the goal is not to classify things, not even the things tagged with the taxonomy concepts, but rather to organize the set of concepts that have been identified as appropriate for tagging and retrieving a set of content. <br /><br /></p><br />Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com7tag:blogger.com,1999:blog-9094731596169096992.post-76555343119895536382022-11-27T22:36:00.010-05:002022-11-30T12:45:16.501-05:00Taxonomies to Bridge Silos<p><span style="font-family: inherit;">There is increasing interest in organizations to “break down
silos” of content and data. Silos may be different software applications, distinct
web or intranet content, or merely different computer drives and folders. The
goal is to enable search and retrieval across content that is stored in
different content/document management systems and shared folders and the
analysis and comparison of data stored in different kinds of database
management systems, records management systems, and spreadsheets. This results
in better, more complete information to enable more informed decisions and knowledge
discovery, along with improved user satisfaction, while also saving time. Breaking
down or bridging such silos was a theme of my two most recent conferences.</span></p><p><span style="font-family: inherit;"></span></p> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-PEj0PQkxxqJ4LSsInnlHN-Eh1D9-h-qzKEnASLAoWWGYdyGpA0CO2rhpyvUsJ4304Q4hJPUDVcL8EzExDap15SW19AsxKm6m-pD4M9BWWfknLnZQ6qimvexbvRI9lBTbS2E-yTaePw0kvWEdDKyUKbeXFs_o6uEdIx-WvJOLcAvK8VZffI5dlA88/s4132/20221029_154844.jpg" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="3099" data-original-width="4132" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-PEj0PQkxxqJ4LSsInnlHN-Eh1D9-h-qzKEnASLAoWWGYdyGpA0CO2rhpyvUsJ4304Q4hJPUDVcL8EzExDap15SW19AsxKm6m-pD4M9BWWfknLnZQ6qimvexbvRI9lBTbS2E-yTaePw0kvWEdDKyUKbeXFs_o6uEdIx-WvJOLcAvK8VZffI5dlA88/s320/20221029_154844.jpg" width="320" /></a></div><br /><p></p><p><span style="font-family: inherit;"></span></p><h3 class="MsoNormal" style="text-align: left;"><span style="font-family: inherit;">LavaCon: Connecting Content Silos</span></h3><span style="font-family: inherit;">
</span><p class="MsoNormal" style="text-align: left;"><span style="font-family: inherit; font-size: small;">The 20<sup>th</sup> annual <a href="https://lavacon.org/" target="_blank">LavaCon</a> conference on content
strategy, held October 23-26 in New Orleans, had the theme this year of “Connecting
content silos across the Enterprise.” The conference had a number of
presentations tied to the theme, 10 of which had “silos” in their titles. Two
presentations I especially enjoyed were by leading content strategy consultants
about how to connect silos.</span></p><p style="text-align: left;"><span style="font-family: inherit; font-size: small;">
</span></p><p class="MsoNormal" style="text-align: left;"><span style="font-family: inherit; font-size: small;">Sarah O’Keefe of <a href="https://www.scriptorium.com/" target="_blank">Scriptorium</a>, in her presentation “From Silo
Busting to CaaStle Building,” with a fairy tale castle metaphor, explained that
completely unified content cannot be achieved, because CMSs are tuned to
specific content domains, corporate websites accommodate different goals of
different groups, content silos have their own delivery pipelines, and silos often
match the organizational structure. Her solution was to provide Content as a
Service (CaaS), or a “CaaStle in the cloud(s).” Silos are kept, allowing for
unique requirements, and perhaps reduced in number, but are connected were
needed.</span></p><p style="text-align: left;"><span style="font-family: inherit; font-size: small;">
</span></p><p class="MsoNormal" style="text-align: left;"><span style="font-family: inherit; font-size: small;">Val Swisher of <a href="https://contentrules.com/" target="_blank">Content Rules</a>, in her presentation “Creating
a Unified (Siloed) Content Experience: The Importance of Terminology and Taxonomy,”
explained that siloed content results in different user experiences for each
silo. But silos are not going away, because there is no single toolset,
particular content has its owners, and certain content may be considered
special. Therefore, the user experience should be improved to “ensure that all
content looks like it comes from the same company” and to “eliminate the
confusion that users experience when they consume content created by various
silos.” This is done by standardizing the content, the search, page
layout, navigation, content types, terminology, and taxonomy.</span></p><p style="text-align: left;"><span style="font-family: inherit; font-size: small;">
</span></p><p class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: inherit;"><span>At <a href="https://lavacon.org/2022-conference-program/" target="_blank">LavaCon</a>, I presented a pre-conference workshop with the
title “<span style="line-height: 107%;"><a href="https://lavacon.org/speaker/heather-hedden/" target="_blank">Using Taxonomies and Tagging to Connect Content Across the Enterprise</a>.” </span>While most of my
workshop addressed the general principles and best practice for taxonomy
creation, along with the basics of tagging, I did discuss a how centrally
managed taxonomy, external from but linked to various content management
systems and other applications or repositories of content, can bridge silos.
Taxonomy management software positioned as “middleware” such as <a href="https://www.poolparty.biz/" target="_blank">PoolParty</a>,
connects to these different content applications and repositories, and then the
taxonomy is presented to the user in a single user interface.</span></span></span></p><span style="font-family: inherit;">
</span><h3 class="MsoNormal" style="text-align: left;"><span style="font-family: inherit;">Taxonomy Boot Camp: Taxonomy Breaking Down Silos</span></h3><span style="font-family: inherit;">
</span><p class="MsoNormal"><span style="font-family: inherit;">At the annual <a href="https://www.taxonomybootcamp.com" target="_blank">Taxonomy Boot Camp conference</a>, held November 7-8
in Washington, DC, and co-located with the KM World conference, I spoke in a
two-presentation session titled “<a href="https://www.taxonomybootcamp.com/2022/program.aspx#15611" target="_blank">Taxonomy Breaking Down Silos</a>.” The idea is
that taxonomies provide the connections to break down barriers between <span class="description">different systems and teams</span>. I presented on taxonomy
linking jointly with Donna Popky, Senior Taxonomy & Information
Architecture Specialist, <span itemprop="worksFor">Harvard Business School</span>.
I explained the principles of taxonomy project linking, and Donna presented a
case study of taxonomy linking using a hub and spoke method to link separate
taxonomies managed by different business units with separate content repositories
for different purposes at Harvard Business School. So, this was a case of
creating a hub taxonomy linked to the various business unit spoke taxonomies.</span></p><span style="font-family: inherit;">
</span><p class="MsoNormal"><span style="font-family: inherit;">The other speaker in the session, Rachael Maddison, Content
Infrastructure Architect & Taxonomy Product Manager for Adobe
Digital Media Experience and Engagement, presented on taxonomy adoption across corporate
silos and <span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;">not
merely content silos. Collaboration plays a role in wider taxonomy adoption,
and as Rachael stated: “Mapping or merging</span> can’t happen until there
is stakeholder buy<span role="presentation">-</span><span role="presentation" style="transform: scaleX(0.814391);">in.</span>”</span></p><span style="font-family: inherit;">
</span><p class="MsoNormal"><span style="font-family: inherit;"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;">Over the years, my list of the benefits of taxonomies has grown. Linking
data, content, and corporate silos are additional benefits. This can be done
with a single, enterprise taxonomy or with multiple linked taxonomies. In
either case, the taxonomy needs to be managed externally from any individual
siloed application in a dedicated taxonomy management system. Taxonomies can then
break down corporate silos and connect content and data silos.</span></span></p>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-30740107387531658722022-10-18T13:32:00.002-04:002023-01-03T22:13:09.747-05:00The Accidental Taxonomist, Third Edition<p>The third edition of my book, <i>The Accidental Taxonomist</i>, will officially be published November 7, and I just received advance printed copies, so now is a good time to talk about. Details of the book are on its <a href="http://www.hedden-information.com/accidental-taxonomist/">website</a>. For those who wonder how this edition differs from the prior edition, I discuss that in the preface of the 3rd edition, which I have copied here.</p><p style="text-align: center;">****<br /></p><p>I am thrilled that taxonomies are as relevant now as they were when I
was writing my first edition in 2009 and second edition in 2015 and
even more so. Some people had previously thought that improved search
algorithms would largely replace the need for taxonomies, but users want
to be able to select search refinement terms, and the greater adoption
of search has led to more taxonomies. Some thought that AI technologies
of text analytics and auto-classification might replace human-created
taxonomies, but, on the contrary, they made taxonomies more valuable.
Some thought that ontologies would replace taxonomies, but instead
ontologies have connected and extended taxonomies, providing additional
uses for taxonomies. Innovations and trends in digital content and data
have given rise to new uses for taxonomies, including support for
recommendation, personalization, data-centric enterprise knowledge
management, voice of the customer analysis, and chatbot design.</p><div class="separator" style="clear: both; text-align: left;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLByLLVDGWxLWoVoPNafO5W7ZB8xATs2dgD2tB1dJGtFUY4NB3X3PxVSR8rZTCfiiK20hWyB3owp5akzQ3U_pQ2Yz7hBG5EH6URKqbO2A0GuzgMx9R6RpIXYm0hPKOTh0fLJeVFAJXUH_kBRC-fWRON5PlzLmeJncdPwQgxVaVGGSmzEpqw44pnjgW/s4608/TAT3-inPrint.jpg" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="4608" data-original-width="3456" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLByLLVDGWxLWoVoPNafO5W7ZB8xATs2dgD2tB1dJGtFUY4NB3X3PxVSR8rZTCfiiK20hWyB3owp5akzQ3U_pQ2Yz7hBG5EH6URKqbO2A0GuzgMx9R6RpIXYm0hPKOTh0fLJeVFAJXUH_kBRC-fWRON5PlzLmeJncdPwQgxVaVGGSmzEpqw44pnjgW/w240-h320/TAT3-inPrint.jpg" width="240" /></a></div><p></p>
<p>There are signs of interest in taxonomies in various places: social
media posts, conference presentations and workshops in a greater number
of different conferences, and a continued strong enrollment trends in my
online taxonomy course. Taxonomy consultants I know are doing well with
business. A search on “taxonomy” in Google Trends shows a continued
steady interest in the term since around 2006. Members of the Taxonomy
and Ontology Community of Practice LinkedIn group has grown from 3,330
in 2015 to 5,564 in June 2022. More people continually get involved in
taxonomy work, as our survey of taxonomists indicates relatively more
people with fewer years of experience. (See Appendix A, Question 2.) The
number of jobs for taxonomists continues to increase, as evidenced by
repeated taxonomy job searches over the years on job boards, job alert
postings, and direct queries colleagues of mine have reported receiving
from recruiters. The trend toward remote work, especially for knowledge
workers, has opened up more job possibilities for taxonomists, who are
no longer limited by their geographic location, which had previously
been an issue for this very niche specialization. We may soon see more
digital nomad taxonomists living and working all over the world.</p>
<p>Meanwhile, as I have continued to engage in taxonomist discourse,
consulted for more taxonomy clients, and attended and created new
conference presentations, I have continued to learn more and thus refine
how I understand and explain taxonomies. It is time that this book also
catches up to how I have been explaining taxonomies in my most recent
presentations and workshops. I have even revised my thinking on the
definitions and types of controlled vocabularies, so the definitions and
types section of chapter 1 has been rewritten in this edition. Also in
the first chapter, additional uses for taxonomies have been included.</p>
<p>In addition, perspectives on taxonomies have gradually changed, and I
am finally catching up. One of the main updates to this third edition
has been to move decisively from the traditional thesaurus model and
adoption of the language of the SKOS (Simple Knowledge Organization
System) with respect to taxonomies. Most significantly this means
referring to concepts and their labels and not to terms. An oft repeated
phrase is that it’s about “things, not strings.” Concepts are things,
whereas terms, as words or phrases, are merely strings (of text). This
has also involved removing the equivalence relationship section from the
chapter on relationships and adding a section on alternative labels to
the chapter Creating Concepts and Labels (which has been renamed from
Creating Terms).</p>
<p>When I updated the 2nd edition, I was working at the time for a
library database vendor, so my perspective was somewhat biased toward
that industry and use case, despite having had experience has a
consultant too. Now, with not only more consulting experience in the
interim, but from the perspective of working for a taxonomy software
vendor, I see better the varied uses and implementations of taxonomies.
As a result, I have changed number of the examples. I also made updates
to the chapter on manual tagging (formerly called human indexing) and
replaced many references to “indexing” with “tagging,” in recognition of
the more commonly used term, although they are not identical. I had
entered this field as an indexer, but I should no longer let my indexing
roots influence my perspective. I also cut out some information on
thesauri, such as details of the various thesaurus print display
formats.</p>
<p>This edition features a new chapter on ontologies. This is not merely
because ontologies may be of interest to taxonomists, but because
ontologies in business and industry are increasingly created as an
extension of existing taxonomies thus enabling taxonomies to serve more
purposes. A convergence of taxonomies and ontologies is now possible
with SKOS-based taxonomies, whereby both taxonomies and ontologies are
based on RDF and other W3C standards. I am also seeing more
taxonomist/ontologist hybrid jobs posted.</p>
<p>Technologies and vendors change, so the chapters on software and
auto-categorization needed updating. There have been evolving trends in
software, such as the ability to connect and integrate with other
systems through APIs, instead of exporting and importing taxonomies, and
including auto-tagging within the same tool. Other updates include data
from a new survey, nearly all new screenshots, and updated information
on taxonomy courses, conferences, and other resources in the final
chapter. About half of the chapter head quotes are also new.</p>
<p>In case you missed it in the preface to the second edition, the
updates from the first to the second edition (and thus also updates
between the first and the third edition) include the following: managing
taxonomies in SharePoint, the relationship between taxonomies and
metadata, reference to updated ISO standards of 25964 of 2011 and 2013,
the introduction of the SKOS standard, and improved explanations on
planning and designing taxonomies, along with results of a new
taxonomist survey and software information updates.</p>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-23747747024919695582022-09-30T13:18:00.000-04:002022-09-30T13:18:00.308-04:00Taxonomies and Semantics<p><span style="color: #161516; font-family: Arial; font-size: 15px;">How are taxonomies related to “semantics”? I considered this question, as the latest conference I participated was <a href="https://2022-eu.semantics.cc/" target="_blank">SEMANTiCS,</a></span><span style="color: #161516; font-family: Arial; font-size: 15px;"> </span><span style="color: #161516; font-family: Arial; font-size: 15px;">the European conference of semantic technologies, which took place this year in Vienna, Austria, September 13 - 15. Topics presented and discussed in this conference included ontologies, knowledge graphs, semantic models and reasoning, linked open data, machine learning, natural language processing, and other language technologies. Yet taxonomies were also discussed in a number of presentations. In contrast to a conference dedicated to taxonomies, such as Taxonomy Boot Camp, where taxonomies are the focus, at SEMANTiCS, in the context of semantic technologies, taxonomies are a component or an underlying layer in the application of semantic technologies.</span></p><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhENr57DN728EA4v7H5xV8Jkk1ox8xabKoYOXCLvC8BqbS92BWe3hlMUMlw4z8X5Wgl6RrwkMNRKOFfhXoYyTeswX1CgwbguVCbOSw49GE1Z5iNeywBlz9iXqqzzZvh7BQp5O2__9s6TcKBajfCO-pXTR9WM7kY02vf0D1kXtfLtWjKRAOw8344z4zU/s4608/20220914_090438.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="3456" data-original-width="4608" height="300" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhENr57DN728EA4v7H5xV8Jkk1ox8xabKoYOXCLvC8BqbS92BWe3hlMUMlw4z8X5Wgl6RrwkMNRKOFfhXoYyTeswX1CgwbguVCbOSw49GE1Z5iNeywBlz9iXqqzzZvh7BQp5O2__9s6TcKBajfCO-pXTR9WM7kY02vf0D1kXtfLtWjKRAOw8344z4zU/w400-h300/20220914_090438.jpg" width="400" /></a></div><span style="color: #161516; font-family: Arial; font-size: 15px;"><p><span style="color: #161516; font-family: Arial; font-size: 15px;"><br /></span></p>Semantics means “meaning.” Like the words “taxonomy” and “ontology,” there is a traditional meaning that is more academic and, in the case of semantics and ontology, also connected to philosophy, but there is also a modern meaning that deals with information science and knowledge management. For example, “semantic search,” means searching for concepts and ideas, not merely matching search strings of text. Thus, a taxonomy or thesaurus supports semantic search by comprising unambiguous concepts of “things, not strings” of text. </span><p></p>
<p style="color: #161516; font-family: Arial; font-size: 15px; font-stretch: normal; line-height: normal; margin: 0px; min-height: 17px;"><span style="font-kerning: none;"></span><br /></p>
<p style="color: #161516; font-family: Arial; font-size: 15px; font-stretch: normal; line-height: normal; margin: 0px;"><span style="font-kerning: none;">Semantics also implies Semantic Web, with technology that complies with the <a href="https://www.w3.org/standards/semanticweb/standards">Semantic Web</a> that have been developed by the World Wide Web Consortium (W3C). The Semantic Web, also known as Web 3.0, is not component of the World Wide Web nor a different web, but rather a kind of extension of the web to include not merely content and simple hyperlinks, but also all kinds of data that is semantically linked (where the links/relationships also have meaning). The Semantic Web allows more complex data, and data stored and organized in graph databases, to be machine-readable. This could be either on the public web or within an organization that follows Semantic Web standards for managing its data and content. </span></p>
<p style="color: #161516; font-family: Arial; font-size: 15px; font-stretch: normal; line-height: normal; margin: 0px; min-height: 17px;"><span style="font-kerning: none;"></span><br /></p>
<p style="color: #161516; font-family: Arial; font-size: 15px; font-stretch: normal; line-height: normal; margin: 0px;"><span style="font-kerning: none;">Taxonomies were mentioned in a number of other presentations as a given foundation to ontologies, semantic networks, or knowledge graphs. For example, taxonomies and ontologies were the basis of knowledge-based recommendation system, described by Andreas Blumauer in his presentation on that subject. In her talk “ Real World Case Studies: Five Success Factors to Implementing an Enterprise Data Fabric,” Lulit Tesfaye explained that the components of a data fabric are metadata, taxonomy, ontology, knowledge graph, connections and integrations, and front-end applications.</span></p>
<p style="color: #161516; font-family: Arial; font-size: 15px; font-stretch: normal; line-height: normal; margin: 0px; min-height: 17px;"><span style="font-kerning: none;"></span><br /></p>
<p style="color: #161516; font-family: Arial; font-size: 15px; font-stretch: normal; line-height: normal; margin: 0px;"><span style="font-kerning: none;">A session titled Taxonomies included a talk on “Taxonomy and Terminology,” compared and contrasted taxonomies and terminologies with respect to their kinds of terms and purposes, but also explained the semantics role of taxonomies. The presenter, Klaus Fleischmann, said that terminologies guide content creators, ensuring consistent, correct use of language company-wide, whereas taxonomies provide a semantic layer on top of content and metadata, often for semantic applications. Fleischmann also explained that taxonomies can be extended to ontologies or, in his words, taxonomies </span><span style="font-kerning: none; font-size: 14px; font-stretch: normal; line-height: normal;">“modeled relationships via ontologies.”Also speaking in the Taxonomies session, Nimit Mehta whose presentation was titled “The Semantic Data Stack - A user story on building a data fabric,” Mehta described taxonomies as “</span><span style="color: black; font-family: Helvetica; font-size: 14px; font-stretch: normal; line-height: normal;">A layer between your data and your business applications” and a “governance layer.”</span></p><p style="color: #161516; font-family: Arial; font-size: 15px; font-stretch: normal; line-height: normal; margin: 0px;"><span style="color: black; font-family: Helvetica; font-size: 14px; font-stretch: normal; line-height: normal;"><br /></span></p><p style="color: #161516; font-family: Arial; font-size: 15px; font-stretch: normal; line-height: normal; margin: 0px;"><span style="font-kerning: none;">Finally, I presented a taxonomy-related tutorial, although not on taxonomy creation alone, but rather titled “Knowledge Engineering of Taxonomies, Thesauri, and Ontologies,” in which I explained that taxonomies and ontologies are not so much distinct knowledge organization systems, but rather than ontologies are a semantic layer that are applied to and extend a taxonomy, giving it a greater degree of semantics. </span></p><p style="color: #161516; font-family: Arial; font-size: 15px; font-stretch: normal; line-height: normal; margin: 0px; min-height: 17px;"><span style="font-kerning: none;"></span><br /></p><p style="color: #161516; font-family: Arial; font-size: 15px; font-stretch: normal; line-height: normal; margin: 0px;"><span style="color: black; font-family: Helvetica; font-size: 14px; font-stretch: normal; line-height: normal;">
</span></p><p style="color: #161516; font-family: Arial; font-size: 15px; font-stretch: normal; line-height: normal; margin: 0px;"><span style="font-kerning: none;">I hope to participate in the next SEMANTiCS conference in September 2023 in Leipzig, Germany.</span></p>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-79787733246635710432022-08-31T21:58:00.011-04:002024-01-30T18:37:49.824-05:00SKOS-XL for Taxonomies<p style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="line-height: 107%; mso-bidi-font-weight: bold;">I recently posted about <a href="https://accidental-taxonomist.blogspot.com/2022/06/skos-taxonomies.html">SKOS (Simple Knowledge Organization System)</a>. If
you have read anything about SKOS, then you might have come across SKOS-XL (SKOS eXtension for Labels) and wondered what that is. The World Wide Web Consortium
(W3C) released its recommendations for <a href="https://www.w3.org/2009/08/skos-reference/skos.html" target="_blank">SKOS</a> and <a href="https://www.w3.org/TR/skos-reference/skos-xl.html" target="_blank">SKOS-XL</a></span><span style="line-height: 107%; mso-bidi-font-weight: bold;"><span style="mso-spacerun: yes;"> </span>at the same time in 2009 but chose
to make them separate recommendations. One way to see it is that, by separating
out SKOS-XL, SKOS is indeed truly “simple.” In the detailed <a href="https://www.w3.org/TR/skos-reference/" target="_blank">SKOS reference</a>,
SKOS-XL is an <a href="https://www.w3.org/TR/skos-reference/#xl" target="_blank">appendix</a>.</span><span style="line-height: 107%; mso-bidi-font-weight: bold;"> </span></span></span></span></p><p style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="line-height: 107%; mso-bidi-font-weight: bold;"></span></span></span></span></p><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhJO6eNltMvH2mleSaFZPWeCGsSrQ1ryDLy0tRGHOPQy1NCgx9SWrPcA8vPtVmhoEc76_zyTC9FZtipfw1q64E30h3eFw_ecf2tlpwLG5Lx3OuXGsedCqALBGFHxitEZYuUYXOlql7ohwHjAL_9lE4Cx7thxn_fs44U_JfOZBCVZ76ASz9cL5gJgT8z/s798/SKOS-XL.png" style="margin-left: auto; margin-right: auto;"><img alt="https://www.w3.org/TR/skos-reference/skos-xl.html" border="0" data-original-height="711" data-original-width="798" height="356" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhJO6eNltMvH2mleSaFZPWeCGsSrQ1ryDLy0tRGHOPQy1NCgx9SWrPcA8vPtVmhoEc76_zyTC9FZtipfw1q64E30h3eFw_ecf2tlpwLG5Lx3OuXGsedCqALBGFHxitEZYuUYXOlql7ohwHjAL_9lE4Cx7thxn_fs44U_JfOZBCVZ76ASz9cL5gJgT8z/w400-h356/SKOS-XL.png" title="https://www.w3.org/TR/skos-reference/skos-xl.html" width="400" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><a href="https://www.w3.org/TR/skos-reference/skos-xl.html">www.w3.org/TR/skos-reference/skos-xl.html</a></td></tr></tbody></table><span style="font-size: small;"><span style="font-family: arial;"><span><span style="line-height: 107%; mso-bidi-font-weight: bold;"><br /> </span></span></span></span>
<p></p><h3 class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="line-height: 107%; mso-bidi-font-weight: bold;">Extending labels to become resources</span></span></span></span></h3><p class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="line-height: 107%; mso-bidi-font-weight: bold;">“Things, not strings” is a tagline for semantic models, such as SKOS,
which emphasize concepts in taxonomies and other knowledge organization systems
and not terms or words. Of course, strings of text exist, and when associated
with concepts they are called “labels.” <span style="mso-spacerun: yes;"> </span>The distinction between a label and the
concept that the label describes may seem indistinguishable or perhaps just
philosophical. The main difference is that concepts are unique within a
taxonomy, but labels are not. A concept may have multiple labels (synonyms or
names in different languages), and the same label might apply to different
concepts (homographs).</span></span></span></span></p><p><span style="font-size: small;"><span style="font-family: arial;"><span>
</span></span></span></p><p class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="line-height: 107%; mso-bidi-font-weight: bold;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="line-height: 107%; mso-bidi-font-weight: bold;">SKOS specifies preferred labels, alternative labels, and hidden labels as options for concepts.
Hidden labels can be considered as a type of alternative label that should never
be displayed. Alternative labels may display, depending on the front-end
application. Preferred labels are what are displayed, especially in hierarchies
and facets. </span></span></span></span></span></span></span></span></p><p class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="line-height: 107%; mso-bidi-font-weight: bold;">Concepts, as things, have properties or characteristics. Labels do not. But
sometimes there are reasons to assign properties to labels, such as to indicate
the purpose or use of different labels. In this sense, you would want to turn a
string into a thing. More correctly, a thing is called a resource, as described
by the Resource Description Framework (RDF) the model upon which SKOS is based.
This is what SKOS-XL supports: converting labels to resources. It does this by
adding three more elements not found in SKOS: label, label relation, and
literal form. It is the label relation in particular that enables the extension
to establish a link between a concept and a label. Further details are in the W3C's <a href="https://www.w3.org/TR/skos-reference/skos-xl.html" target="_blank">SKOS-XL recommendation</a>,
which I am not going to repeat here.</span></span></span></span></p><h3 class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="line-height: 107%; mso-bidi-font-weight: bold;">Use for SKOS-XL <br /></span></span></span></span></h3><p class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="line-height: 107%; mso-bidi-font-weight: bold;">A typical use case for SKOS-XL to assign properties to labels is if
you want to have different labels for different user groups, such
as a medical taxonomy for shared medial content to be accessed by both medical
professionals and lay people. Medical professionals may prefer a concept
labeled Neoplasms, while lay people could call it Cancer. Different user groups
could be based in different regions. Although different ISO-code based language
labels can be used to distinguish regions in addition to language (such as
en-US and en-GB), you may not want to duplicate the vast majority of preferred
labels and merely distinguish the few that are actually different. </span></span></span></span></p><p><span style="font-size: small;"><span style="font-family: arial;"><span>
</span></span></span></p><p class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="line-height: 107%; mso-bidi-font-weight: bold;">While SKOS permits multiple alternative labels, aside from hidden labels, there
is no way to distinguish their types or purposes in SKOS. You may want to
alternative labels support search in one front-end application and not another.
You may want to designate official acronyms as distinct from other alternative
labels. You may even want to distinguish between different kinds of hidden
labels, such as those that should be hidden because they might be pejorative or
offensive, and those </span><span style="mso-bidi-font-family: Calibri; mso-bidi-font-weight: bold; mso-bidi-theme-font: minor-latin;">that you wish to
hide only from a type-ahead display because they are near duplicates of other
alternative labels and too many alternative labels would clutter up the
display. Finally, there may be
alternative labels used by only certain users or in certain regions.</span></span></span></span></p><p><span style="font-size: small;"><span style="font-family: arial;"><span>
</span></span></span></p><p class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="mso-bidi-font-family: Calibri; mso-bidi-font-weight: bold; mso-bidi-theme-font: minor-latin;">SKOS-XL lets you assign properties or
attributes to labels. Assigning the purpose or use of the label is only one
possibility, although it is the most common use of SKOS-XL. You may wish to
manage more administrative metadata about labels, such as the source or origin
of different labels. </span></span></span></span></p><h3 class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="mso-bidi-font-family: Calibri; mso-bidi-font-weight: bold; mso-bidi-theme-font: minor-latin;">Implementing SKOS-XL</span></span></span></span></h3><p class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="mso-bidi-font-family: Calibri; mso-bidi-font-weight: bold; mso-bidi-theme-font: minor-latin;">The principle of SKOS-XL is not complex, but implementation can be more challenging, and if you are building taxonomies with the SKOS-XL capability, you would want to use taxonomy management software that supports SKOS-XL, such as <a href="https://www.poolparty.biz/skos-and-skos-xl/" target="_blank">PoolParty</a>. Taxonomy management software products are quite consistent when it comes to their user interface for supporting the editing of basic SKOS taxonomies, but they are not the same for creating and editing SKOS-XL labels, which is a less common function. </span></span></span></span></p><p class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="mso-bidi-font-family: Calibri; mso-bidi-font-weight: bold; mso-bidi-theme-font: minor-latin;">Having properties, such as types, for terms
is not new, but required some more innovation in the SKOS model of things
(concepts), not strings (terms). It was common for non-SKOS taxonomy/thesaurus
management software, which treated different terms with the same meaning as
equivalence relationships, to support the customization of relationships,
including the equivalence relationship. SKOS-XL ensures that this earlier
feature is supported in the current standard, in machine-readable format.</span></span></span></span></p><p><span style="font-size: small;"><span style="font-family: arial;"><span>
</span></span></span></p><p class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span style="mso-bidi-font-family: Calibri; mso-bidi-font-weight: bold; mso-bidi-theme-font: minor-latin;">For SKOS-XL to be more widely used and maybe
even more elegantly supported requires a great sharing of use cases. I hope the
taxonomist community will share their experiences with SKOS-XL, so we can talk
about practices and recommendations and not just theory.</span></span></span></span></p><p><span style="font-size: small;"><span style="font-family: arial;"><span>
</span></span></span></p><p class="MsoNormal" style="text-align: left;"><span style="font-size: small;"><span style="font-family: arial;"><span><span lang="DE" style="mso-ansi-language: DE; mso-bidi-font-family: Calibri; mso-bidi-font-weight: bold; mso-bidi-theme-font: minor-latin;">Further information:<br /></span></span></span></span></p><ul style="text-align: left;"><li><p><span style="font-size: small;"><span style="font-family: arial;"><span><span lang="DE" style="mso-ansi-language: DE; mso-bidi-font-family: Calibri; mso-bidi-font-weight: bold; mso-bidi-theme-font: minor-latin;">
“<a href="https://www.slideshare.net/ABLVienna/taxonomy-management-based-on-skosxl" target="_blank">Taxonomy Management Based on SKOS-XL</a>” 2016 presentation slides</span></span></span></span></p></li><li><p><span style="font-size: small;"><span style="font-family: arial;"><span><span lang="DE" style="mso-ansi-language: DE; mso-bidi-font-family: Calibri; mso-bidi-font-weight: bold; mso-bidi-theme-font: minor-latin;">“From SKOS over SKOS-XL to Custom
Ontologies” 2016 webinar <a href="https://www.poolparty.biz/resources/from-skos-over-skos-xl-to-custom-ontologies/" target="_blank">video</a> and <a href="https://www.slideshare.net/semwebcompany/from-skos-over-skosxl-to-custom-ontologies" target="_blank">slides</a></span></span></span></span></p></li><li><p><span style="font-size: small;"><span style="font-family: arial;"><span><span lang="DE" style="mso-ansi-language: DE; mso-bidi-font-family: Calibri; mso-bidi-font-weight: bold; mso-bidi-theme-font: minor-latin;"> </span><span style="mso-bidi-font-family: Calibri; mso-bidi-font-weight: bold; mso-bidi-theme-font: minor-latin;">“<a href="http://www.snee.com/bobdc.blog/2011/02/what-skos-xl-adds-to-skos.html" target="_blank">What SKOS-XL adds to SKOS</a>” 2011 blog post by Bob
DuCharme</span></span><span style="mso-bidi-font-family: Calibri; mso-bidi-font-weight: bold; mso-bidi-theme-font: minor-latin;"><span> </span><br /></span></span></span></p></li></ul><p><span style="font-size: small;"><span style="font-family: arial;">
</span></span></p><p></p>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-2752593372964067852022-07-31T22:59:00.009-04:002022-08-22T11:29:28.093-04:00Taxonomy Challenges Discussed at SLA Conference<p style="text-align: left;"><span style="font-family: inherit;">When it comes to conferences dealing with the subject of taxonomy creation, implementation, and maintenance, without a doubt <a href="https://www.taxonomybootcamp.com">Taxonomy Boot Camp</a> and <a href="https://www.taxonomybootcamp.com/London/">Taxonomy Boot Camp London</a> are by far the best conferences for their content, speakers, and networking opportunities. However, there are other conferences that have sessions on taxonomies. </span></p><p style="text-align: left;"></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgA1BWpobVdLtx_f0VfJAzDNCNKsheW1MCz1-JBUyKSOOZDLaLdJ2t8RN6F_ouyCZ5ueVW5KHtvJd1c875qQX8nqadtPxv5PwE-8085sPHkI3ZMSD95MDAn_BU01nTGhx7BCWzE3V2wB9YxhyPDVUMy1UO5G6HSGYXN9jMfTrRszEMPLkZssZTpzcMr/s3571/20220801_105208.jpg" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="3571" data-original-width="3244" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgA1BWpobVdLtx_f0VfJAzDNCNKsheW1MCz1-JBUyKSOOZDLaLdJ2t8RN6F_ouyCZ5ueVW5KHtvJd1c875qQX8nqadtPxv5PwE-8085sPHkI3ZMSD95MDAn_BU01nTGhx7BCWzE3V2wB9YxhyPDVUMy1UO5G6HSGYXN9jMfTrRszEMPLkZssZTpzcMr/s320/20220801_105208.jpg" width="291" /></a></div><span style="font-family: inherit;">The <a href="https://www.sla.org/attend/" target="_blank">annual conference of the Special Libraries Association (SLA)</a> usually has multiple taxonomy-related sessions. This year, July 31 - August 2 in Charlotte, NC, the first in-person conference in three years, was no exception.</span><p></p>
<p style="font-stretch: normal; line-height: normal; margin: 0px; text-align: left;"><span style="font-family: inherit;">Thanks to the volunteer programming efforts of <a href="https://connect.sla.org/taxonomy/home">SLA’s Taxonomy Community</a> (one of over 20 specialized topic groups, formerly called “Divisions"), the annual conference is able to include multiple taxonomy sessions, some of which bring together multiple speakers, either co-presenting a single talk or coming together. Even sessions not organized by the Taxonomy Community may include taxonomy topics, such as those dealing with knowledge management, information architecture, or research that uses a taxonomy. A Taxonomy Community networking event is also regularly part of the SLA conference.</span></p>
<p style="font-stretch: normal; line-height: normal; margin: 0px; min-height: 14px; text-align: left;"><span style="font-family: inherit;"><br /></span></p>
<p style="font-stretch: normal; line-height: normal; margin: 0px; text-align: left;"><span style="font-family: inherit;">This year’s conference is hybrid, so some of the taxonomy sessions are in-person, and some are pre-recorded and available on-demand. Live-streaming was also done for keynotes and some sessions. The following are the in-person taxonomy sessions at the SLA 2022 conference:</span></p>
<p style="font-stretch: normal; line-height: normal; margin: 0px; text-align: left;"></p><p style="text-align: left;"></p><p></p><ul style="text-align: left;"><li><span style="font-family: inherit;">“The Role of DEI in Taxonomy Development, Maintenance, Search, and Retrieval,” presented by Marisa Hughes. (This presentation on a popular topic was additionally live-streamed and pre-recorded for on-demand viewing.)</span></li></ul><ul style="text-align: left;"><li><span style="font-family: inherit;">“Current Challenges and Advanced Taxonomy Topics” panel comprising Marisa Hughes, Heather Kotula, John Bertland, and myself.</span></li></ul><ul style="text-align: left;"><li><span style="font-family: inherit;">“Research Sources and Methodologies for Taxonomy Development,” jointly presented by Marisa Hughes and myself.</span></li></ul><div>The following are pre-recorded, on-demand only taxonomy sessions:</div><ul style="text-align: left;"><li><span style="font-family: inherit;">“There ain’t no Sanity Clause: Taxonomy and Data Analysis” presented by Michele Lamorte</span></li></ul><ul style="text-align: left;"><li><span style="font-family: inherit;">“Metadata Governance” presented by John Horodyski</span></li></ul><h4 style="text-align: left;"><span style="font-family: inherit;"><br /></span></h4><h4 style="text-align: left;"><span style="font-family: inherit;">Conference session on diversity, equity, and inclusion in taxonomies</span></h4><p></p><p style="font-stretch: normal; line-height: normal; margin: 0px;"><span style="font-family: inherit;">Diversity, Equity & Inclusion (DEI) is a growing area of interest in information management/sharing and content creation. Marisa Hughes, the taxonomist who edits the APA Thesaurus of Psychology Index Terms explained the challenges of revising the thesaurus terms to reflect DEI, for which she gave the following definitions:</span></p><p style="font-stretch: normal; line-height: normal; margin: 0px;"></p><ul style="text-align: left;"><li><span style="font-family: inherit;">Diversity: “The vast range of differences among individuals and groups.”</span></li><li><span style="font-family: inherit;">Equity: “The contain of being fair and impartial”</span></li><li><span style="font-family: inherit;">Inclusion: “Welcoming and respecting diverse individuals and Groups. Diversity in practice. </span></li></ul><p></p><p>She has been reviewing thousands of terms for accuracy, currency, inclusivity, avoidance of bias, stereotypes, or discrimination. Areas that this DEI review has focused on are:</p><ul><li><span style="font-family: inherit;">Racial, ethnic, and cultural identity</span></li><li><span style="font-family: inherit;">Gender diversity and sexual orientation</span></li><li><span style="font-family: inherit;">Age, disability status, and </span>socioeconomic<span style="font-family: inherit;"> class bias</span></li></ul><p></p>
<p style="font-stretch: normal; line-height: normal; margin: 0px; text-align: left;"><span style="font-family: inherit;">In the area of disability status, for example, the term should focus on the disability and not the person. Thus, “Hearing impaired” is changed to “Person with hearing loss”; and “Mentally ill” is changed to “Individual with a mental illness.”</span></p>
<p style="font-stretch: normal; line-height: normal; margin: 0px; min-height: 14px; text-align: left;"></p><table cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: right;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi4kiD_qbd8ECM3hPGqHGPDnQysOwdC_wSzsHxyNgipYWE2yTLtWvDjkwZNeSjiCkW0v03boJISRwnPpDzJXfTpojaQk5lsklu4kXBWAlTUc2GKqIgTnPJQxE5UgADwfSZk60of-Ad03xiDQf-pAennvZShPfEPKv9PmalmfqjN0_fy7IPokmnsjIEb/s3312/DEI%20presentation.jpg" style="clear: right; font-family: inherit; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img border="0" data-original-height="1874" data-original-width="3312" height="226" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi4kiD_qbd8ECM3hPGqHGPDnQysOwdC_wSzsHxyNgipYWE2yTLtWvDjkwZNeSjiCkW0v03boJISRwnPpDzJXfTpojaQk5lsklu4kXBWAlTUc2GKqIgTnPJQxE5UgADwfSZk60of-Ad03xiDQf-pAennvZShPfEPKv9PmalmfqjN0_fy7IPokmnsjIEb/w400-h226/DEI%20presentation.jpg" width="400" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><i>Marisa Hughes presenting <span style="text-align: left;">“The Role of DEI in Taxonomy</span></i><span style="text-align: left;">”</span></td></tr></tbody></table><p></p><p style="font-stretch: normal; line-height: normal; margin: 0px; min-height: 14px; text-align: left;">Additional challenges include taking the hierarchical relationships, term usage, and change management. If users can see hierarchical relationships, even if not the full hierarchy, these relationships need to be appropriate. For example, certain personal conditions and behaviors should not be narrower to the term “Disorders.” Term frequency of usage (also called “literary warrant”) is important, but the larger goal is to have respectful terms. Change management involves care that the term changes to not impact search and retrieval. Marissa oversees the large job of reindexing content with new terms, and adding change notes or history notes to changes terms. </p><p style="font-stretch: normal; line-height: normal; margin: 0px; min-height: 14px; text-align: left;"><br /></p><p></p><h4><span style="font-family: inherit;">Conference panel on current taxonomy challenges</span></h4><p style="font-stretch: normal; line-height: normal; margin: 0px; min-height: 14px;">In this session, the four panelists each gave brief opening talks, then were asked questions by the moderator, Judith Theodori, and then it was opened up for general Q&A and discussion with the audience.</p><p style="font-stretch: normal; line-height: normal; margin: 0px; min-height: 14px;"><br /></p><p style="font-stretch: normal; line-height: normal; margin: 0px; min-height: 14px;">I presented on the themes of challenges which came from 138 taxonomist survey responses to the question "What are the pain points or challenges in your taxonomy work?" The leading trends in the responses were:</p><ol style="text-align: left;"><li><span style="-webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial; font-family: inherit;">Achieving stakeholder understanding and buy-in</span></li><li><span style="-webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial; font-family: inherit;">Competing interests, expectations, and requests</span></li><li><span style="-webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial; font-family: inherit;">Organizational challenges</span></li><li><span style="-webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial; font-family: inherit;">Tools and technology inadequacies or not integrated</span></li></ol>
<p style="-webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial; font-stretch: normal; line-height: normal; margin: 0px; text-align: left;"><span style="font-kerning: none; font-variant-ligatures: no-common-ligatures;"><span style="font-family: inherit;">John Bertland, Digital Librarian and Content Specialist at the Presidio Trust spoke of the taxonomy challenges in his organization including governance at the time organizational change and funding. A specific challenge is expanding and adapting a taxonomy that was originally just for digital asset management to include the content of the intranet.</span></span></p><table cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: left;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgOzZ4zV3ngRq84DbK_DxUDnDnnkm5VBsEyqUTm4kuJ-GfdbDJSZdLoBPhFls_aAHhACaMjt7ZZgGuG5BqO-UE7wlG7MyBP7p9LUSwtdQ3RGRnryXfhjQyqKw5tq5e_EqSJ9J3Q4sZxUGFYcZkjbivLjqHk00CPMtRN7keJHRfzZeg4Zrk3AtuO5soQ/s3263/Taxonomy%20challenges.JPG" style="clear: left; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img border="0" data-original-height="1782" data-original-width="3263" height="219" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgOzZ4zV3ngRq84DbK_DxUDnDnnkm5VBsEyqUTm4kuJ-GfdbDJSZdLoBPhFls_aAHhACaMjt7ZZgGuG5BqO-UE7wlG7MyBP7p9LUSwtdQ3RGRnryXfhjQyqKw5tq5e_EqSJ9J3Q4sZxUGFYcZkjbivLjqHk00CPMtRN7keJHRfzZeg4Zrk3AtuO5soQ/w400-h219/Taxonomy%20challenges.JPG" title="Marisa Hughes, John Bertland, Heather Kotula, and Heather Hedden on the panel of taxonony challenges" width="400" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><span style="text-align: left;">“</span><i>Current Taxonomy Challenges</i><span style="text-align: left;">” </span><i>panelists Marisa Hughes, </i><i><br />John Bertland, Heather Kotula, and Heather Hedden</i></td></tr></tbody></table><p></p>
<p style="-webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial; font-stretch: normal; line-height: normal; margin: 0px; min-height: 14px; text-align: left;"><span style="-webkit-text-stroke-width: initial; font-family: inherit; font-kerning: none; font-variant-ligatures: no-common-ligatures;">Marisa Hughes, Taxonomist at the </span><span style="-webkit-text-stroke-width: initial; font-family: inherit;">American Psychological Association, related the challenge of having to quickly come up with all the COVID related taxonomy in time for the usual thesaurus update scheduled in April 2020. This involved a lot of research on literature that was still rather lacking on the subject. </span></p><p style="-webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial; font-stretch: normal; line-height: normal; margin: 0px; min-height: 14px; text-align: left;"><span style="-webkit-text-stroke-width: initial; font-family: inherit;"><br /></span></p><p style="-webkit-text-stroke-color: rgb(0, 0, 0); -webkit-text-stroke-width: initial; font-stretch: normal; line-height: normal; margin: 0px; min-height: 14px; text-align: left;"><span style="-webkit-text-stroke-width: initial; font-family: inherit;">Another challenging project was to determine the role of historical data in the vocabulary of 3500 terms for the period of 1967 to 1973, which involved removing offensive terms. It was a judgement call of whether to continue to use a potentially offensive term as a non preferred term (alternative label) or not. Heather Kotula, </span><span style="-webkit-text-stroke-color: rgb(100, 100, 100); -webkit-text-stroke-width: initial; background-color: white; font-family: inherit; font-kerning: none;">VP, Marketing and Communications of Access Innovations, Inc., the fourth panelist, also discussed the same subject of excluding pejorative terms, referred to “semantic censorship.” In the end it was concluded that often pejorative terms are actually not that much in use in the documents being tagged.<span style="font-size: 12px;"> </span></span></p>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-70880151384605188412022-06-26T21:36:00.013-04:002022-07-21T16:26:47.902-04:00SKOS Taxonomies<p>Over the 26 years that I have been involved in controlled
vocabularies, thesauri, and taxonomies, the biggest change I have seen in the
field is the adoption of SKOS (Simple Knowledge Organization System) as a schema
model and standard.
</p><p class="MsoNormal">If you are creating taxonomies exclusively within a single
system (such as the SharePoint Term Store or controlled tags or categories of a
content management system, documentation management system, DAM, etc.), then
you probably have not paid much attention to SKOS. It’s true that taxonomies
created within and used within a single system, do not have to follow an
external standard. But that is not the trend of information management and
technology anymore. Connectivity, interoperability, data sharing and reuse,
data-centric architecture, vendor-neutral formats, linked data and linked open
data, breaking down data silos, enterprise-wide knowledge, and enterprise
knowledge graphs have become the preferred trends and directions. </p>
<h3 class="MsoNormal" style="text-align: left;">Different Kinds of Standard</h3><p class="MsoNormal">With respect to standards, there exist two basic kinds: (1) standards
for design, functionality, and a consistent user experience, and (2) standards
for compatibility, interoperability, and machine-readability. For this reason,
there are two separate sets of standards for taxonomies and other knowledge
organization systems. Another way to think of it is that there are standards
for each the front end (user interface and experience) and the back end
(computer-readable code) of taxonomies, and they are somewhat independent yet
still compatible with each other. </p>
<p class="MsoNormal">For taxonomies and thesauri, more has been written about the
front-end design and best practice standards than the back-end interoperability
standards. This is for several reasons. The design and best practices standards
(ANSI/NISO Z39.19 and ISO 25964 and its predecessors ISO 2788 and ISO 5964),
have been around longer. They are lengthier and more detailed than interoperability
standards, and they apply to taxonomies and thesauri regardless of their
digital or nondigital format. So, this article will focus instead on the
back-end, interoperability standard, which is SKOS.<br /><br /></p>
<h3 class="MsoNormal" style="text-align: left;"><div class="separator" style="clear: both; text-align: right;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjXdqCaOF2ddF5r2qZdnxD1JEnFEbpbq4_KCONtP2mEEMS_9f7drwJBIynzKWe6YnPeiOIMJ9Vx2CnKvqtVYV08jpQWQ6zRFGDF2W8XwrWzZc-i3xxv6Wf6FS66jGKb5XZVUTlhtQ05MRzEjpJPxo_Cd1tUNmLGhAVVtxc1BZWsiO6rIT3oH5rpfdwj/s514/SKOS.png" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img alt="SKOS logo" border="0" data-original-height="98" data-original-width="514" height="61" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjXdqCaOF2ddF5r2qZdnxD1JEnFEbpbq4_KCONtP2mEEMS_9f7drwJBIynzKWe6YnPeiOIMJ9Vx2CnKvqtVYV08jpQWQ6zRFGDF2W8XwrWzZc-i3xxv6Wf6FS66jGKb5XZVUTlhtQ05MRzEjpJPxo_Cd1tUNmLGhAVVtxc1BZWsiO6rIT3oH5rpfdwj/w320-h61/SKOS.png" title="SKOS logo" width="320" /></a></div>SKOS Background</h3><h3 class="MsoNormal" style="text-align: left;"></h3>
<p class="MsoNormal"></p>SKOS is a recommendation for "a common data model for
sharing and linking knowledge organization systems via the Semantic Web".
These knowledge organization systems include thesauri (as defined by the
ANSI/NISO and ISO thesaurus standards), taxonomies, classification schemes,
subject heading systems, and other controlled vocabularies. SKOS is based on
<a href="https://www.w3.org/RDF/" target="_blank">RDF (Resource Description Framework)</a>, a World Wide Web Consortium (W3C)
standard for description and exchange of graph data. RDF specifies that all statements
consist of subject-predicate-object triples, and all resources have URIs (uniform
resource identifiers).<p></p>
<p class="MsoNormal">The development of SKOS aimed to<span style="mso-spacerun: yes;"> </span>build upon RDF to provide a recommended
schema for thesauri.<span style="mso-spacerun: yes;"> </span>SKOS development
was first undertaken as the Semantic Web Advanced Development for Europe
(SWAD-Europe) project before being adopted and supported by the W3C in 2004.
The W3C formally released the SKOS recommendation in 2009. </p>
<p class="MsoNormal">Meanwhile, the W3C had been working on other recommendations
for web-based ontologies, including <a href="https://www.w3.org/TR/rdf-schema/" target="_blank">RDF Schema (RDFS)</a> and <a href="https://www.w3.org/2001/sw/wiki/OWL" target="_blank">Web Ontology Language(OWL)</a>. SKOS is compatible with RDFS and OWL, and elements from the different
models can be combined. Furthermore, SKOS can even be considered as a very
generic upper ontology itself, and the W3C documentation describes SKOS in
terms of OWL and RDFS expressions. </p>
<p class="MsoNormal">The main types of elements of SKOS are <i>concepts</i>, <i>lexical
labels</i>, <i>documentation properties </i>(notes), <i>semantic relationships</i>, <i>mapping
properties</i>, and <i>concept collections</i>. (Concepts, concept schemes, and
collections are ontology classes, and the others are ontology properties.) In their
machine-readable form, the SKOS elements are concatenated with no spaces, such
as <i>preLabel</i>, <i>scopeNote</i>, and <i>exactMatc</i>h.</p>
<h3 class="MsoNormal" style="text-align: left;">SKOS Concepts, Labels, and Notes</h3>SKOS is concept-centric. Making a distinction between concepts
and labels is the biggest departure from traditional thesaurus standards and past
controlled vocabulary practice. A concept is an idea of something, and a label
is a name for that idea. Thus, a concept may have multiple labels. For the
organization of a vocabulary, especially as a hierarchy, one of the various
labels needs to be designated as the preferred displayed label. The others are
alternative labels and its sub-type, hidden label, which may be used to
designate that the label should not display to end-users. Labels for the same concept
may exist in multiple languages, but there may be only one preferred label per
language.<p></p>
<p class="MsoNormal">Notation is intended for use as an appending part of a
label, such as an alpha-numeric code, which is commonly used in classification
schemes.</p>
<p class="MsoNormal">Documentation comprises various types of notes, including <i>scope
note</i>, <i>editorial note</i>, <i>change note</i>, and <i>history note</i>. <i>Definition</i> and <i>example</i> are
additional documentation types. Scope notes are commonly used in thesauri to
clarify the usage of a concept in tagging/indexing for the specific context of
controlled vocabulary and its set of content. They serve an important role for
manual tagging. Other note types may be utilized for administration and
management of the controlled vocabulary. Definitions may be entered for more technical
controlled vocabularies or when the controlled vocabulary also serve the
function of a glossary. </p>
<h3 class="MsoNormal" style="text-align: left;">SKOS Concept Schemes and Collections</h3>
<p class="MsoNormal">What constitutes an individual "taxonomy,"
"thesaurus" or other controlled vocabulary? This may not be very clear.
SKOS introduces the formal organizing unit called a <i>concept scheme</i>, as a “collection
of concepts.” A concept scheme is a single controlled vocabulary, thesaurus, hierarchical
taxonomy, facet within a faceted taxonomy, or metadata property within a larger
metadata schema.</p>
<p class="MsoNormal">There are some advanced, lesser used features of SKOS, including
<i>in scheme</i>, which allows you to control whether a concept is in a concept scheme
regardless of whether it’s within the concept scheme’s hierarchy (which is
otherwise the default). There is also a special designation of <i>top concept</i> for
the top concepts of a concept scheme, a designation which could be utilized for
a front-end display implementation. </p>
<p class="MsoNormal"><i>Collections</i> are an additional optional way to designate a
grouping of concepts for a purpose, such as the taxonomy concepts to be used in
only specified implementations or those of subject categories for subject
matter expert review. Furthermore, concepts can be ordered within collections.</p>
<h3 class="MsoNormal" style="text-align: left;">SKOS Relations and Mapping Properties</h3>
<p class="MsoNormal">SKOS includes what are called semantic relations, although
this name could cause confusion, since they are the basic thesaurus relationships
(<i>broader</i>, <i>narrower</i>, and <i>related</i>), not customizable semantic relations characteristic
of ontologies. These thesaural-type relationships are used between concepts
within the same concept scheme. In addition, SKOS specifies <i>broader transitive</i>
and <i>narrower transitive</i>, meaning the inheritance of the relationship to additional
levels of the hierarchy. This is usually assumed to be the case by default, and
thus these specifically transitive relations are rarely implemented, but if
there are reasons <i>not</i> to inherit and extend the logical hierarchy by default,
then the transitive relations may be used. (I have not come across a use case,
though.)</p>
<p class="MsoNormal">Since SKOS specifies concept schemes, SKOS also specifies an
additional set of relation types called <i>mapping properties</i> that are to be used
between concepts in different concept schemes or different taxonomies. <span style="mso-spacerun: yes;"> </span>These comprise<i> exact match</i>, <i>close match</i>, <i>narrower
match</i>, <i>broader match</i>, and <i>related match</i>. Exact match and close match are used
to map existing taxonomies together, often so that one is used in the tagging
and the other is used in the retrieval. The other mapping relations may be used
to extend one taxonomy with another while still maintaining a distinction
between the two.</p><p class="MsoNormal">Following is a table of SKOS elements by type (class or property) with the concatenated machine-readable forms.<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhQ34VVYkOXR-jzQjqv1E3PCOHDVBsPn_Zbuv-bOOD4mERNPUxnN5ppJjD1Uc1sSXSrM77k8mKIVpWRl7lERBBBKHCr7Ep4Y7_KyKy1nI5uE-2TqkmGjMszbjQWW_d5ZrfwjxOBtLWH3xRYaVWRIPS7VerWJytaGbHpXK0CMrFBHakUKDkDAHEC7iCS/s940/Screen%20Shot%202022-06-27%20at%2011.49.13%20AM.png" style="clear: left; display: inline; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="411" data-original-width="940" height="280" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhQ34VVYkOXR-jzQjqv1E3PCOHDVBsPn_Zbuv-bOOD4mERNPUxnN5ppJjD1Uc1sSXSrM77k8mKIVpWRl7lERBBBKHCr7Ep4Y7_KyKy1nI5uE-2TqkmGjMszbjQWW_d5ZrfwjxOBtLWH3xRYaVWRIPS7VerWJytaGbHpXK0CMrFBHakUKDkDAHEC7iCS/w640-h280/Screen%20Shot%202022-06-27%20at%2011.49.13%20AM.png" width="640" /></a></p><h3 style="text-align: left;">Implementation of SKOS</h3>
<p class="MsoNormal">Most commercial and open-source taxonomy/thesaurus
management software now supports SKOS. There are also simple free tools called
SKOS editors. SKOS elements are presented in their full human readable names (such
as <i>Preferred Label</i>, instead of <i>prefLabel</i>), so it is intuitive to understand. Thus,
taxonomists don’t have to worry about SKOS, but should at least be familiar with
its principles. Familiarity with SKOS makes it easier to switch from using one software
package to another. Software may vary, however, in how well they support some
of the less common features, such as in scheme, collections, and broader/narrower
transitive. </p>
<p class="MsoNormal">Taxonomy/thesaurus management software often has the
additional administrative grouping of related concept schemes for the same
implementation into what may be called a “project” or “knowledge model.” SKOS
mapping relations tend to be used more often across concept schemes that are
managed in different projects, rather than within the same project. Within the
same project, concept schemes tend to represent facets (which have no relations
between them) or ontology classes (which have customized semantic relations
between them). </p>
<p class="MsoNormal">Since all elements of SKOS are standard machine-readable,
you can leverage any element with rules for usage, such as for how tagging
should be done and how concepts and relationships are displayed. Custom
applications of SKOS vocabularies are thus common. </p>
<p class="MsoNormal">If you want to dive into all the details of SKOS, consult
these resources from the W3C:</p>
<ul style="text-align: left;"><li><a href="https://www.w3.org/TR/skos-reference/" target="_blank">SKOS Simple Knowledge Organization System Reference</a></li><li><a href="https://www.w3.org/2009/08/skos-reference/skos.html" target="_blank">SKOS Simple Knowledge Organization System Namespace Document</a><br /></li><li><a href="https://www.w3.org/TR/2009/NOTE-skos-primer-20090818/" target="_blank">SKOS Simple Knowledge Organization System Primer</a></li><li><a href="https://www.w3.org/2004/02/skos/" target="_blank">SKOS Simple Knowledge Organization System – Project HomePage</a><span style="mso-spacerun: yes;"><br /></span></li></ul>
<p class="MsoNormal">SKOS is intended to be flexible, and it is more suggestive than
restrictive. Thus, a SKOS-based taxonomy or thesaurus could still be poorly designed,
and that’s why the other standards for best practices, ANSI/NISO Z39.19 and ISO
25964 are also important.</p>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-22909265303292474392022-05-31T16:45:00.005-04:002022-06-15T21:44:05.439-04:00A Taxonomist Community<p style="text-align: left;"><span style="font-family: inherit;"><span face="Calibri, sans-serif" style="font-size: 11pt; white-space: pre-wrap;">Taxonomists and others whose work involves taxonomies have not been a unified professional community. Taxonomy development work is interdisciplinary, spanning different specializations, and different organizational functions, including the following:</span></span></p><p style="text-align: left;"><span style="font-family: inherit;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"></span></span></p><ul style="text-align: left;"><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; white-space: pre-wrap;">Information services taxonomies and thesauri, developed by those with a background in library/information science, thesauri, and cataloging, and possibly indexing</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; white-space: pre-wrap;">Product/ecommerce taxonomies, that may be developed by those with varied backgrounds but experience in retail and product information management</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; white-space: pre-wrap;">Digital asset management taxonomies and metadata, developed by digital asset managers and others, who might have a background in image and media curation and management</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; white-space: pre-wrap;">Website taxonomies developed by information architects with a focus on the user experience</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; white-space: pre-wrap;">Enterprise taxonomies developed by those who are primarily knowledge managers but have also learned about taxonomies</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; white-space: pre-wrap;">Taxonomies for auto-categorization of large volumes of text, developed by those with expertise in natural language processing, machine learning, and other text analytics technologies</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; white-space: pre-wrap;">Taxonomies, as controlled vocabularies, to support metadata and master data management, developed by metadata architects, data managers, and possibly data scientists</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; white-space: pre-wrap;">Taxonomies in support of knowledge graphs, integrated with ontologies, developed by ontologists and other experts in semantic technologies</span></span></li></ul><p dir="ltr" style="line-height: 1.295; margin-bottom: 8pt; margin-top: 0pt;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">Thus, people who work with taxonomies, accidental taxonomists and others, associate themselves with different professions and belong to different groups or professional organizations. These include </span></span></p><ul style="text-align: left;"><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><a href="https://www.sla.org/" target="_blank">Special Libraries Association (SLA)</a> and its <a href="https://connect.sla.org/taxonomy/home" target="_blank">Taxonomies Community.</a> </span><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"> The next annual <a href="https://www.sla.org/attend/sla-2022-annual-conference-source-forward/" target="_blank">SLA conference</a> will be held July 31 – August 2 in Charlotte, NC. </span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><a href="https://www.isko.org/" target="_blank">International Society for Knowledge Organization (ISKO)</a> </span><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"> and its various country/region chapters, such as <a href="https://www.iskouk.org/" target="_blank">ISKO UK</a>. </span><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"> The <a href="https://www.communication.aau.dk/research/knowledge_groups/e-learning-lab/isko/conference-programme/" target="_blank">17th international ISKO conference</a> will be held at Aalborg University, Denmark, July 6-8, 2022. </span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><a href="http://www.aiim.org" target="_blank">AIIM (Association of Information and Image Management International)</a></span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><a href="https://www.asindexing.org/ " target="_blank">American Society for Indexing</a> </span><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">and its Taxonomies & Controlled Vocabularies Special Interest Group </span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><a href="https://www.cilip.org.uk/" target="_blank">CILIP (Chartered Institute for Library and Information Professionals)(UK)</a> and its Knowledge and Information Management Group</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><a href="http://www.asist.org" target="_blank">Association for Information Science & Technology (ASIS&T)</a></span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><a href="https://www.knowledgegraph.tech/about-kgc/" target="_blank">Knowledge Graph Conference (KGC)</a>'s associated community</span><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"> which has an ongoing Slack space for discussion that is open to all</span></span></li></ul><p dir="ltr" style="line-height: 1.295; margin-bottom: 8pt; margin-top: 0pt;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">For information architects, the Information Architecture Institute dissolved in 2019 after 17 years, and until now, information architects have temporarily been gathering on Discord servers associated with the virtual <a href="https://www.theiaconference.com" target="_blank">IAConference</a> and the <a href="https://www.worldiaday.org" target="_blank">World IA Day</a> conference, but these have been relatively inactive at other times of the year. </span></span></p><h3 style="text-align: left;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">Discussion Groups</span></span></h3><p dir="ltr" style="line-height: 1.295; margin-bottom: 8pt; margin-top: 0pt;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">Taxonomists are thus dispersed among these groups and more. It does not make sense to create a new professional membership association for taxonomists, especially at this time when traditional professional membership associations are experiencing declining membership.</span></span></p><p dir="ltr" style="line-height: 1.295; margin-bottom: 8pt; margin-top: 0pt;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">Thus, online discussion groups that do not require a paid professional association membership are a better option. The first taxonomy group, Taxonomy Community of Practice was started as a Yahoo group in 2004. It has become quite popular with over 1000 members posting questions and suggestions about taxonomies. However, Yahoo groups declined, and LinkedIn groups grew, so this group was migrated over to a LinkedIn group, later renamed <a href="https://www.linkedin.com/groups/1750/">Taxonomy and Ontology Community of Practice</a>. The problem is that this group, as most LinkedIn groups, is less of a community of practice and more an announcement forum. People are reluctant to post basic questions, as it might indicate that they are not sufficiently knowledgeable. Another former Yahoo group which migrated to Groups.io is <a href="https://groups.io/g/ControlledVocabulary">Controlled Vocabulary</a>, which is focused on activities of metadata and controlled vocabulary development and tagging of digital assets, mostly images. </span></span></p><h4 style="text-align: left;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">Communities Discussed at Conferences</span></span></h4><p dir="ltr" style="line-height: 1.295; margin-bottom: 8pt; margin-top: 0pt;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">The need for a community of practitioners, whether taxonomists, or related specialties, is something that has been raised at conferences. </span></span></p><p dir="ltr" style="line-height: 1.295; margin-bottom: 8pt; margin-top: 0pt;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">At the most recent Information Architecture Conference (IAC), in April 2022, the co-presidents for World IA Day, Grace Lau and Andrea Rosenbusch, gave a talk “</span><span face="Calibri, sans-serif" style="color: #4c4c4d; font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">(<a href="https://www.theiaconference.com/sessions/rearchitecting-a-community/" target="_blank">Re)Architecting a Community</a>” </span><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"> discussing their hopes and plans to transform World IA Day from merely a single day annual event to community. </span></span></p><p dir="ltr" style="line-height: 1.295; margin-bottom: 8pt; margin-top: 0pt;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">At the most recent Knowledge Graph Conference (KGC), Katariina Kari led a brainstorming workshop “<a href="https://www.knowledgegraph.tech/kgc-2022-workshop-building-ontologies-and-knowledge-graphs/" target="_blank">Building Ontologies and Knowledge Graphs</a>,” </span><span face="Calibri, sans-serif" style="background-color: white; font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"> </span><span face="Calibri, sans-serif" style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">as “</span><span face="Calibri, sans-serif" style="background-color: white; font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">a working group for publicly sharing best practices, stories, and the particularities of our craft of building ontologies and knowledge graphs,” seeking a “soundboard for ideas” that others could participate in. </span></span></p><p dir="ltr" style="line-height: 1.295; margin-bottom: 8pt; margin-top: 0pt;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="background-color: white; font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">The upcoming <a href="https://www.eventscribe.net/2022/SLASourceForward/index.asp" target="_blank">SLA conference</a> will have a live panel session “Communities of Practice: Where Everybody Knows Your Name” on August 2, 2022, in which I will be one of the panel speakers.</span></span></p><h3 style="text-align: left;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="background-color: white; font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">A new Taxonomist Community: Taxonomy Talk</span></span></h3><p dir="ltr" style="line-height: 1.295; margin-bottom: 8pt; margin-top: 0pt;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="background-color: white; font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">Out of conversations and research conducted by Grace Lau in leading up to her IAC talk on an information architecture community, Grace and I discussed in January the idea of an additionally dedicated taxonomist community. I then invited another taxonomist, Bob Kasenchek, to come up with ideas, including what to use for a free platform. Slack, as used by KGC, was dismissed, since the free version has limited data storage, and old messages get deleted. So, we decided to adopt Discord, as it has been used by the virtual IAC in 2021 and 2022. Taxonomy Talk was launched on April 12, and quickly gained sufficient members that they could contribute ideas and be polled for a name. On May 1 it was named Taxonomy Talk. A charter and mission are still in the works. There are several moderators, including Grace, Bob, and myself. </span></span></p><p dir="ltr" style="line-height: 1.295; margin-bottom: 8pt; margin-top: 0pt;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="background-color: white; font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">As of this writing Taxonomy Talk has just over 300 members. It has a number of dedicated subject “channels,” some of which are:</span></span></p><ul style="text-align: left;"><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span style="background-color: white; font-size: 10pt; white-space: pre-wrap;">New-to-taxonomy</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span style="background-color: white; font-size: 10pt; white-space: pre-wrap;">Looking-for-help</span></span></li><li><div class="separator" style="clear: both; text-align: center;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjz5FwETgDC_OpdYxdOIb2KXqLcWrkElV3rd3pbKY_v0QEahEwY38hSoLsbyrw6_-T1U8wy5MyxkYhJkiPTSar5f_-8PzNB0lXNUfCx1nmmZ-0BWTtNsBjBhfhvUuzCn3GF_CS3YJAnmVE1P-fglBExU9Zrs_t2b4dwZsd14VVvrErwJpDSm_eJhLFt/s2682/Screen%20Shot%202022-05-31%20at%204.04.13%20PM.png" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" data-original-height="1828" data-original-width="2682" height="218" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjz5FwETgDC_OpdYxdOIb2KXqLcWrkElV3rd3pbKY_v0QEahEwY38hSoLsbyrw6_-T1U8wy5MyxkYhJkiPTSar5f_-8PzNB0lXNUfCx1nmmZ-0BWTtNsBjBhfhvUuzCn3GF_CS3YJAnmVE1P-fglBExU9Zrs_t2b4dwZsd14VVvrErwJpDSm_eJhLFt/s320/Screen%20Shot%202022-05-31%20at%204.04.13%20PM.png" width="320" /></a></span></div><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span style="background-color: white; font-size: 10pt; white-space: pre-wrap;">Conferences-events</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span style="background-color: white; font-size: 10pt; white-space: pre-wrap;">Jobs-and-opportunities</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span style="background-color: white; font-size: 10pt; white-space: pre-wrap;">Tools-for-thought</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span style="background-color: white; font-size: 10pt; white-space: pre-wrap;">Learning-resources</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span style="background-color: white; font-size: 10pt; white-space: pre-wrap;">Reference-resources</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span style="background-color: white; font-size: 10pt; white-space: pre-wrap;">Best-practice</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span style="background-color: white; font-size: 10pt; white-space: pre-wrap;">Ontologies</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span style="background-color: white; font-size: 10pt; white-space: pre-wrap;">Standards</span></span></li><li><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span style="background-color: white; font-size: 10pt; white-space: pre-wrap;">Vocabularies</span></span></li></ul><p dir="ltr" style="line-height: 1.295; margin-bottom: 8pt; margin-top: 0pt;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="background-color: white; font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">New channels are created as requested, and we might decide to retire or merge low-use ones.</span></span></p><p dir="ltr" style="line-height: 1.295; margin-bottom: 8pt; margin-top: 0pt;"><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="background-color: white; font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">Discord supports features such as direct one-on-one chats and one-one or group video meetings. There are still features I have yet to learn. </span></span></p><span id="docs-internal-guid-f02b55ac-7fff-45d5-a120-9b0d69994a64"><span face="Calibri, sans-serif" style="background-color: white; font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">So, if you are not yet in the Taxonomy Talk Community and want to join:</span></span><p></p><div style="text-align: left;"><p><span style="font-family: inherit;"><span><span face="Calibri, sans-serif" style="background-color: white; font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><a href="https://discord.com/invite/3qyMVYCAsw" style="text-decoration: none;"><span style="color: #1155cc; font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; text-decoration-skip-ink: none; text-decoration: underline; vertical-align: baseline;">https://discord.com/invite/3qyMVYCAsw</span></a> </span><a href="https://discord.com/invite/3qyMVYCAsw" style="text-decoration: none;"><span style="color: black; font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"><br /></span></a><span style="font-size: 11pt; font-variant-east-asian: normal; font-variant-ligatures: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">(Please use your real name to promote networking. Some existing Discord users are continuing to use their Discord nicknames.)</span></span></span></p></div>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-90338301603879117022022-04-30T12:52:00.007-04:002023-04-07T21:39:10.802-04:00Polyhierarchy in Taxonomies<p style="background: white; margin: 0in;"><span style="color: #222222;">A defining characteristic
of taxonomies is that terms/concepts are arranged in broader-narrower
hierarchies, which may resemble tree structures. A limited number of top
concepts each have narrower concepts, which in turn may have narrower concepts,
etc., and the narrowest concepts at the bottom of the hierarchy are sometimes
referred to as leaf nodes, as “leaf” extends the metaphor of “tree.” The tree
model has its limits, though, because taxonomies may also have occasional cases
of “polyhierarchy,” whereby a concept may have two or more broader concepts, instead of just one. </span></p>
<p style="background: white; margin: 0in;"><span style="color: #222222;"> </span></p>
<p style="background: white; margin: 0in;"><span style="color: #222222;">People who are
new to taxonomies, however, might not consider polyhierarchies, because they
tend to think of taxonomies as classification systems. Hierarchical information
taxonomies have their origin in classification systems, such as the Linnean
taxonomy of organisms, library classification systems, and industry
classification systems. Classification systems, however, do not allow polyhierarchy
within the system. Originally, classification systems were for physical things,
such as books, which can belong in only one place, so there could be no
polyhierarchy. Standard classification systems, such as industry classification
systems, were developed by governmental, international, or nongovernmental
organizations with a primary purpose of gathering and organizing statistical
data about classes, and thus polyhierarchy is not permitted, as it would lead
to double-counting of members of a class. </span></p>
<p style="background: white; margin: 0in;"><span style="color: #222222;"> </span></p>
<p style="background: white; margin: 0in;"><span style="color: #222222;">The primary
purpose of hierarchy in a taxonomy is to provide guided browsing of topics to
end-users, who may start out looking at broad categories and then drill down to
find the narrowest concept of interest. Thus, polyhierarchy serves the same
purpose. The idea is that different people will start at different points at
the top of the hierarchy to arrive at the same concept of interest, which is
tagged to the same content set. A polyhierarchy should be implemented if the concept’s
relationship is correctly and inherently hierarchical in both of its cases. An
example of a polyhierarchy is <b>Educational software</b>, which has both <b>Software</b>
and <b>Educational products</b> as broader concepts. <b>Educational software</b>
is a kind of software, fully included within <b>Software</b>, and <b>Educational
software</b> is a kind of educational product, fully included <b>within
Educational products</b>.</span></p>
<p style="background: white; margin: 0in;"><span style="color: #222222;"> </span></p>
<p style="background: white; margin: 0in;"><i></i></p><div class="separator" style="clear: both; text-align: center;"><i><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiHLLIX90HC8mMxKPq9CgmVMzGirz_fMEaR-gasrajY5wa_1ndr11BryWPUhgwL3wO2ESC5gL0Ge4gHpKL93oWL6noczw754jyPIsxYxYY_k0ef9LZhU0eZNfHRsREZZE0twjEGH5ihvMHjYYyfeSzVZrqi5iRNGOozCkRNFVyR1rMG3qQygsWxi7tm/s540/Polyhierachy%20example.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="283" data-original-width="540" height="168" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiHLLIX90HC8mMxKPq9CgmVMzGirz_fMEaR-gasrajY5wa_1ndr11BryWPUhgwL3wO2ESC5gL0Ge4gHpKL93oWL6noczw754jyPIsxYxYY_k0ef9LZhU0eZNfHRsREZZE0twjEGH5ihvMHjYYyfeSzVZrqi5iRNGOozCkRNFVyR1rMG3qQygsWxi7tm/s320/Polyhierachy%20example.png" width="320" /></a></i></div><i><br /><span style="color: #222222;"><br /></span></i><p></p>
<p style="background: white; margin: 0in;"><span style="color: #222222;"> </span></p>
<h3 style="background: white; margin: 0in; text-align: left;"><span style="color: #222222;">Taxonomy
standards and polyhierarchy issues</span></h3>
<p style="background: white; margin: 0in;"><span style="color: #222222;"> </span></p>
<p style="background: white; margin: 0in;"><span style="color: #222222;">Taxonomy/thesaurus
standards (<a href=" http://www.niso.org/publications/ansiniso-z3919-2005-r2010" target="_blank">ANSI/NISO Z39.19</a></span><span style="color: #222222;">
and <a href=" https://www.iso.org/standard/53657.html" target="_blank">ISO 25964</a>) describe three kinds of hierarchical
relationships--generic-specific, generic-instance, and whole-part,--and polyhierarchy
may exist within any of these types. Polyhierarchy that combines different
hierarchical types, however, can be problematic, so it is best to avoid mixing
hierarchical relationship types. For example, the following polyhierarchy mixes
different types:</span></p>
<p style="background: white; margin: 0in;"><span style="color: #222222;"> </span></p>
<p style="background: white; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin: 0in 0in 0in 0.5in;"><b><span style="color: #222222;">Washington, DC</span></b></p>
<p style="background: white; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin: 0in 0in 0in 0.5in;"><span style="white-space: pre-wrap;"><span style="color: #222222;"><i>Broader:</i> <b> United States</b></span> (whole-part)</span></p>
<p style="background: white; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin: 0in 0in 0in 0.5in;"><span style="white-space: pre-wrap;"><span style="color: #222222;"><i>Broader: </i> <b>Capital cities</b></span><b> </b>(generic-instance)</span></p>
<p style="background: white; margin: 0in;"><span style="white-space: pre-wrap;"> </span></p>
<p style="background: white; margin: 0in;"><span style="white-space: pre-wrap;"><span style="color: #222222;">The reason to avoid creating a mixed type polyhierarchyis simply that the browsable hierarchy user experience can get compromised and potentially confusing. Extensive hierarchies with large numbers of narrower concept relationships would result. A hierarchical taxonomy tree should be designed with a dominant hierarchy design. An exception is a thesaurus, which is not designed so much for top-down browsing but for browsing from term to term. Mixing hierarchical types within a thesaurus is thus acceptable.</span></span></p>
<p style="background: white; margin: 0in;"><span style="color: #222222;"> </span></p>
<p style="background: white; margin: 0in;"><span style="color: #222222;">It is also
recommended to avoid creating hierarchical relationships across different facets
in a faceted taxonomy. This is because facets are designed to be mutually exclusively,
so that concepts from multiple facets can be used in combination to limit/filter/refine
a search. As such, facets are designed to be distinct aspects. There could be
an occasional exception of polyhierarchy, though, but more than 2-3 polyhierarchies
across an entire faceted taxonomy should be a cause for review.</span></p>
<p style="background: white; margin: 0in;"><span style="white-space: pre-wrap;"> </span></p>
<p style="background: white; margin: 0in;"><span style="color: black; mso-color-alt: windowtext;">With the wider adoption of the <a href="https://www.w3.org/2004/02/skos/" target="_blank">SKOS (Simple Knowledge OrganizationSystem)</a> model for taxonomies and in taxonomy management systems, taxonomies are
more commonly organized into <i>concept schemes</i>. A concept scheme can be
represented as a facet in a faceted taxonomy, but it is not limited to use as a
facet. Utilizing concept schemes, it makes sense to have separate concept
schemes with different hierarchical types, some for generic-specific (for type,
categories, topics), one or more for whole-part (geography, organizational structures),
and some containing lists of instances (named entities). In this model,
<b>Washington, DC</b>, would be narrower only to the <b>United States</b> in the whole-part
hierarchical concept scheme for geographic places. It could also be linked to
<b>Capital cities</b>, which is in a different concept scheme for place types, with a
different kind of relationship (“related” or perhaps a semantic relationship from
an ontology).</span></p>
<p style="background: white; margin: 0in;"><span style="color: black; mso-color-alt: windowtext;"> </span></p>
<p style="background: white; margin: 0in;"><span style="color: #222222;">Although
SKOS permits hierarchical relationships across different concept schemes, it is
best practice not to do this but rather to create hierarchical relationships
and polyhierarchies confined within a concept scheme, just as it is recommended
not to have polyhierarchy across facets.</span></p>
<p style="background: white; margin: 0in;"> </p>
<h3 style="background: white; margin: 0in; text-align: left;"><span style="color: black; mso-color-alt: windowtext;">Additional polyhierarchy considerations</span></h3>
<p class="MsoNormal"><span style="font-size: small;"><span style="font-family: arial;"><span style="line-height: 107%;">Polyhierarchy concerns concepts in the taxonomy, and
it is not about objects, items, or assets that get tagged with taxonomy
concepts, such as an individual publication, document, image, product record,
etc. Each of these may get tagged with multiple taxonomy concepts, and as such
may have multiple “classifications” and thus can appear as if they are in a
polyhierarchy, if a frontend application displays tagged items as if they are
leaf nodes in a taxonomy.</span></span></span></p><span style="font-size: small;"><span style="font-family: arial;">
</span></span><p class="MsoNormal"><span style="font-size: small;"><span style="font-family: arial;"><span style="line-height: 107%;">A polyhierarchy usually involves only two broader
concepts, not more. Having more than two broader concepts is extremely rare. If
you find yourself creating polyhierarchies of three or more multiple times in a
taxonomy, check to make sure you are not doing something wrong with the hierarchy
design.</span></span></span></p><span style="font-size: small;"><span style="font-family: arial;">
<span style="line-height: 107%; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin;">Some content
management systems, which have built-in taxonomy management and tagging features,
do not support polyhierarchy. The best known is SharePoint with taxonomies managed
in its Term Store feature. Taxonomy terms may be “reused” across Term Sets, but
they are not permitted within a Term Set, where it is most suitable. See my past
post,</span> <a href="https://accidental-taxonomist.blogspot.com/2016/01/polyhierarchy-in-sharepoint-term-store.html" target="_blank">Polyhierarchy in the SharePoint Term Store</a>, <span style="line-height: 107%; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin;">for more details </span></span></span>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0tag:blogger.com,1999:blog-9094731596169096992.post-67080414368574774982022-03-22T21:24:00.009-04:002023-02-01T10:05:22.914-05:00Taxonomy Quotes<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Taxonomies
are very valuable, but not always easy to define, and they are described in
various ways. They are also interdisciplinary, as taxonomies are developed by
people in different fields for slightly different, yet similar purposes. I have
heard various comments about taxonomies over the decades. </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">In the earlier years of the Taxonomy Community of Practice
discussion group, a Yahoo group, which was the precursor of the current
<a href="https://www.linkedin.com/groups/1750/" target="_blank">Taxonomy and Ontology Community of Practice</a> LinkedIn group, the group’s
moderator, Seth Earley, put out a call to the group’s members for a motto for
the group. The winning quote, which became the group’s motto, was: “Taxonomies:
That’s classified information,” by Jordan Cassel. </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p><p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjQGgsIg--9x3moQZSmg4CoXgt3yoUFF5uwYDQ37o3TGLPdje4m0Mrsue3qoIwSvLMxJFk2eNNKjSzXHuqEqv_59Lj7wUN8c1eiDDmYp-YEoG5qVTDbGKCQIJn_YVqCcYmsd61guzjEyQ_3tmqQ_MIP28vd_f9Nu62FYdQuKsHhC5u6xYz4_5v7am1W/s3025/chapter%20head%20quote.jpg" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1983" data-original-width="3025" height="263" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjQGgsIg--9x3moQZSmg4CoXgt3yoUFF5uwYDQ37o3TGLPdje4m0Mrsue3qoIwSvLMxJFk2eNNKjSzXHuqEqv_59Lj7wUN8c1eiDDmYp-YEoG5qVTDbGKCQIJn_YVqCcYmsd61guzjEyQ_3tmqQ_MIP28vd_f9Nu62FYdQuKsHhC5u6xYz4_5v7am1W/w400-h263/chapter%20head%20quote.jpg" width="400" /></a></div> <p></p><p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">There were over a dozen other good suggestions for the
motto which were posted in the group in January 2009. That turned out to be
shortly before I wrote the first edition of my book, <i>The Accidental Taxonomist,</i>
so, with permission, I took additional motto-quotes as opening headers to each
of the 12 chapters of my book. The same quotes continued in publication of my
second edition in 2016.
</p><p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">As I now am preparing a third edition (expected out in late
fall 2022), I decided to refresh the chapter head quotes. Last month I
put out a call for quotes in both the <a href="https://www.linkedin.com/groups/1750/" target="_blank">Taxonomy and Ontology Community of Practice</a>
LinkedIn group and in my own network. Some quotes were lengthier than before,
as they were no longer submissions for a motto. I received far more submissions
than I have chapters, and I have also decided to keep some of the original
quotes (including the first one). Yet many of these quotes are quite thoughtful
and/or clever, so I would like to share these new quotes here.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">In true taxonomist fashion, I have categorized these quotes
as about taxonomies, about taxonomy creation, about ontologies as compared to
taxonomies, about taxonomies, and the a few particularly witty quotes at the
end. </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<h3 class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; text-align: left;">About taxonomies</h3>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Taxonomies: organizing the disorganized.<br />
—June Tsang</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Without Taxonomies; entropy!</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Hakan Strom</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Ambiguity is the thief of Knowledge.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Robert Vane</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Good taxonomy is a love letter to the future.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Gary Carlson</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"><span class="comments-comment-item__main-content feed-shared-main-content--comment t-14 t-black t-normal"><span dir="ltr">Taxonomies - organised, effective tagging. </span></span></p><p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"><span class="comments-comment-item__main-content feed-shared-main-content--comment t-14 t-black t-normal"><span dir="ltr">—Alison Jones</span></span></p><p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"><span class="comments-comment-item__main-content feed-shared-main-content--comment t-14 t-black t-normal"><span dir="ltr"> </span></span> <br /></p><p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Taxonomy: Levels in the Playing Field</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Merridy Cox (Bradley)</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Knowledge organisation, search, and use combine to enable
us to navigate the workplace.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Bill Proudfit </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Your Taxonomy, like all metadata, is an expression of
what's important to you and to the collection.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Peter Krogh</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Taxonomies are, first of all, an act of self discovery on
how we understand the world.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Andrea Splendiani</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<h3 class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; text-align: left;">About taxonomy creation</h3>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Taxonomy: generalize or specify, that is the question.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Fabiola Aparecida Vizentim</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Taxonomy: The perfect mix of art and science.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Mollee Marcus</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Taxonomies: Normalizing to help you find, report and
aggregate across data & content</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Rita M. Benitez</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Regardless of domain, taxonomy is the science of sorting
and labelling information so it can be retrieved for future use.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Leah B.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"></p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Do your best to ignore even your most strongly held
convictions. If you want to create a user-friendly taxonomy/ontology system,
follow the data, not your heart.<br />—Rebecca B. Weiss</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Taxonomy is such a great battleground to focus consistently
on improving the user experience; it’s a first key activity to drive the user
experience.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Vellaichamy Shunmugavel</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">To ontologize or not to ontologize, that is the question
you should ask yourself in the first place.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Erick Antezana</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<h3 class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; text-align: left;">About ontologies (or ontologies compared with taxonomies)</h3>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Taxonomies tell stories, ontologies create worlds.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Fran Alexander</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Taxonomies classify; ontologies reify.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Beatrice Larentis</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Ontology: generating knowledge by connecting the dots.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Taxonomy: is like a drawer organizer for kitchen cutlery.<br />
—Brigita Perchutkaite Vollstedt</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"></p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">If a taxonomy is an elevator, an ontology is a Wonkavator!</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Caroline Coward</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">(Referencing <i>Willy Wonka and the Chocolate Factory</i>: like an
elevator but also can go sideways and in all directions.)</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Ontologies make the implications explicit.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Michele Ann Jenkins</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">A good ontology maps the way out of chaosville.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Mark Atkins </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Ontologies: organizational substrate for your data,
information, and know-how enzymes.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Heather Fox</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<h3 class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; text-align: left;">About taxonomists</h3>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Meg Morrissey</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">I wanted to figure out my place in the world, so I hired a
taxonomist.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Only when one’s data is all over the place is it discovered
that a taxonomist is necessary.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Rebecca Custis</p><p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Be the Taxonomy you want to see in the World! <br />— Elaine
Chu</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"><span class="comments-comment-itemmain-content"> </span></p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"><span class="comments-comment-itemmain-content">
I say this categorically, taxonomists are an organized bunch.</span></p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—<span class="comments-comment-itemmain-content">Jordan
Casell</span></p><p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"><span class="comments-comment-itemmain-content"> </span></p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Taxonomies: now you're where you belong.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Alan S. Michaels</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<h3 class="MsoNormal" style="text-align: left;"><br />And the especially witty ones 😉<br /><br /></h3>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"><span class="comments-comment-item__main-content feed-shared-main-content--comment t-14 t-black t-normal"><span dir="ltr"> </span></span></p><p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Ontology, Category, Property - Happy user will be! Try me,
Find me, Surprise me :)</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Dorothee Balas</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Year Make Model Engine Transmission Leather Navi Owners
Accidents Miles Color: = my used-Taxi Taxonomy.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Tony Mariella</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Taxonomy is taxidermy for data -- mounted on a framework
and stuffed for the purpose of display and study.</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Phil Taylor</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"><span class="comments-comment-item__main-content feed-shared-main-content--comment t-14 t-black t-normal"><span dir="ltr">Ontology: One graph to rule them all, one graph to find them, one graph to bring them all and in the semantic web bind them.<br /></span></span><span class="comments-comment-item__main-content feed-shared-main-content--comment t-14 t-black t-normal"><span dir="ltr">—Xeni Kechagioglou</span></span></p><p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"><span class="comments-comment-item__main-content feed-shared-main-content--comment t-14 t-black t-normal"><span dir="ltr"><br /></span></span></p><p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">I never metadata I didn't like</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Paul Belfanti</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;"> </p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">Taxonomy? Taxonoyou!</p>
<p class="MsoNormal" style="line-height: normal; margin-bottom: 0in; margin-top: 0in; mso-add-space: auto; mso-margin-bottom-alt: 8.0pt; mso-margin-top-alt: 0in;">—Ron Cascella</p>
<p class="MsoNormal"> </p>
Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com2tag:blogger.com,1999:blog-9094731596169096992.post-5209190468726357322022-02-04T22:32:00.009-05:002022-03-03T13:28:23.395-05:00Defining a Taxonomy’s Scope<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/a/AVvXsEgHBzL3LP23wTriXkExssOJvco4vXiwvikfMJC8jDjpZvUhT6i_OGm7MHub96EiRqfZ-NVfbXzjcDdjfuZOCyRbcO8xmrgrH4HnXJNkZP_kACfCi0pi90rzx2RJ5iQRRARTe3dM_6ZFt4aOB_QgdugT1Yp0lGlVAfjd6hZroud-l_9krYpbC_F2oSPV=s4608" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="3456" data-original-width="4608" height="240" src="https://blogger.googleusercontent.com/img/a/AVvXsEgHBzL3LP23wTriXkExssOJvco4vXiwvikfMJC8jDjpZvUhT6i_OGm7MHub96EiRqfZ-NVfbXzjcDdjfuZOCyRbcO8xmrgrH4HnXJNkZP_kACfCi0pi90rzx2RJ5iQRRARTe3dM_6ZFt4aOB_QgdugT1Yp0lGlVAfjd6hZroud-l_9krYpbC_F2oSPV=w320-h240" width="320" /></a></div><p style="text-align: left;">In planning a taxonomy, I have often said that it is important at the beginning to define the taxonomy’s scope, specifically the subject area scope of the taxonomy’s terms, but without going into more detail. Recently I was asked by a client how to define a taxonomy’s scope. This is a good question. The taxonomy should be suited to the subject area scope of the content that will be tagged with the taxonomy and to the scope of the user’s expectations. Terms or topics only marginal to the subject scope, however, could occur in the content, and whether they should also be included in the taxonomy is a question. Ultimately, that should depend on whether user expectations justify it, as the needs of users should also be a factor in creating a taxonomy. A taxonomy should suit both its content and its users.</p><h3 style="text-align: left;">Sources for Taxonomy Terms</h3><p>For content as a source of taxonomy terms, a combination of manual and automated approaches is recommended. By manually reviewing sample individual documents or content items, you can discern the main ideas and main topics, which should form the start and basic structure of the taxonomy and also help define its scope. Automated methods of extracting terms, through text analytics technologies, can bring in many additional terms from a much larger corpus of documents more quickly, picking up terms that a limited manual review would miss. Even though automated text analytics extracts terms based on relevancy and frequency of occurrence, such terms could be out of scope of the subject domain. That’s why it’s important to start first with a manual review of content to define the subject scope. Then, when you enrich the taxonomy with automated extraction, you can approve terms that appear to be in scope or at least closely relevant and reject others. But should you reject all that are out of scope, even if they appear with sufficient frequency and relevancy? My advice is to try to assume the role of the user. Ask yourself: Might a user want to search for content on this term in this content collection? <br /> <br />For user needs and expectations as a contributing source of taxonomy terms, obtaining this information can be very direct, such as by creating a user questionnaire (at least for your internal users) that asks what the topics of importance are, how those users would define the scope, and what “marginal” topics would be acceptable for them to include. You could also request sample challenging (not expected, basic, typical) queries that the users would make. Another good way to obtain input from the user side is to look at search query logs that list search strings that users have entered over a period of time, ranked by frequency. If a search phrase that is slightly out of scope of the subject occurs frequently, then the term should still be considered for inclusion in the taxonomy. <br /><br />In either case, the scope of the subject gets better defined as the taxonomy is created. For example, a taxonomy for recipes may initially be scoped to comprise terms for the names of dishes, ingredients, and cooking method. But then a different term shows up significant frequency, “Nutrition Facts.” If it occurs in both the content and the user research, then it likely should be included. If it shows up in the content only, but is not validated in user research, then it is more questionable. <br /></p><h3 style="text-align: left;">Taxonomy Structure</h3><p>The initial taxonomy structure itself tends to impose limits on scope. Taxonomies tend to be hierarchical with a limited number of top terms. If a candidate term appears in the content that does not seem to belong anywhere in the current taxonomic hierarchy, you might be inclined to exclude it. Factors of user needs (they might want to look up this term in this content), however, should take precedence. For example, the term “COVID-19” might be marginal but still of interest to be included many taxonomies on varied subjects, but there would exist no broader term for diseases in those taxonomies. Then adjustments need to be made, such as renaming or adding broader terms, or perhaps, more likely, the proposed term should be modified to fit the context of the taxonomy, such as becoming “COVID-19 impacts.”<br /><br />Another thing to consider is adopting more a thesaurus structure than a taxonomy structure, at least for the facet or concept scheme of the taxonomy that is for miscellaneous “topics.” One characteristic of thesauri is to not rely so heavily on extensive hierarchical trees. What this means is that you could decide that it is acceptable that not all terms have broader terms and thus it’s OK to have a very large number of top terms, with the more specific terms linked to other terms only by related-term relationships, another feature of thesauri, if not by broader/narrower-term relationships. Abandoning the full hierarchical tree structure should only be considered if this hierarchy is not displayed as a navigation to the end users. <br /></p><h3 style="text-align: left;">Documenting Policy</h3><p>In any case, you need to define policies regarding what kinds of terms can be added and what kinds should not. This will evolve out of the activity of building the taxonomy, especially from evaluating what extracted terms to approve and what search log terms to approve. Whoever is doing this task (hopefully more than one person), should document each instance of uncertainty. While many term approvals and rejections will be obvious, there will be a gray area. This should be collected and discussed together, and then a policy can emerge. </p>Heather Heddenhttp://www.blogger.com/profile/16424216206886861070noreply@blogger.com0