Categories
Intelligent Content

Key Verbs: Actions in Taxonomies

When authors tell stories, verbs provide the action. Verbs move audiences. We want to know “what happened next?” But verbs are hard to categorize in ways computers understand and can act on. Despite that challenge, verbs are important enough that we must work harder to capture their intent, so we can align content with the needs of audiences. I will propose two approaches to overcome these challenges: task-focused and situational taxonomies. These approaches involve identifying the “key verbs” in our content.

Nouns and Verbs in Writing

I recently re-read a classic book on writing by Sir Ernest Gowers entitled The Complete Plain Words. Published immediately after the Second World War, the book was one of the first to advocate the use of plain language.

Gowers attacks obtuse, abstract writing. He quotes with approval a now forgotten essayist G.M. Young:

“Excessive reliance on the noun at the expense of the verb will in the end detach the mind of the writer from the realities of here and now, from when and how, and in what mood this thing was done and insensibly induce a habit of abstraction, generalization and vagueness.”

If we look past the delicious irony — a critique of abstraction that is abstract — we learn that writing that emphasizes verbs is vivid.

Gowers refers to this snippet as an example of abstract writing:

  • “Communities where anonymity in personal relationships prevails.”

Instead, he says the wording should be:

  • “Communities where people do not know one another.”

Without doubt the second example is easier to read, and feels more relevant to us as individuals. But the meaning of the two sentences, while broadly similar, is subtly different. We can see this by diagramming the key components. The strengthening of the verb in the second example has the effect of making the subject and object more vague.

role of verb in sentence

It is easy to see the themes in the first example, which are explicitly called out. The first diagram highlights themes of anonymity and personal relationships in a way the second diagram does not. The different levels of detail in the wording will draw attention to different dimensions.

With a more familiar style of writing, the subject is often personalized or implied. The subject is about you, or people like you. This may be one reason why lawyers and government officials like to use abstract words. They aren’t telling a specific story; they are trying to make a point about a more general concept.

Abstract vs Familiar Styles

I will make a simple argument. Abstract writing focuses on nouns, which are easier for computers to understand. Conversely, content written in a familiar style is more difficult for computers to understand and act on. Obviously, people — and not computers — are the audience for our content. I am not advocating an abstract style of writing. But we should understand and manage the challenges that familiar styles of writing pose for computers. Computers do matter. Until natural language processing by computers truly matches human abilities, humans are going to need to help computers understand what we mean. Because it’s hard for computers to understand discussions about actions, it is even more important that we have metadata that describes those actions.

The table below summarizes the orientations of each style. These sweeping characterizations won’t be true in all cases. Nonetheless, these tendencies are prevalent, and longstanding.

Abstract Style Familiar Style
Emphasis
  • Nouns
  • General concepts
  • Reader is outside of the article context
  • Verbs
  • Specific advice
  • Reader is within the article context
Major uses
  • Represents a class of concepts or events
  • Good for navigation
  • Shows instance of a concept or event
  • Good for reading
Benefits
  • Promotes analytic tracking
  • Promotes automated content recommendations
  • Promotes content engagement
  • Promotes social referrals
Limitations
  • Can trigger weak writing
  • Can trigger weak metadata

These tendencies are not destiny. Steven Pinker, the MIT cognitive scientist turned prose guru, can write about abstract topics in an accessible manner — he makes an effort to do so. Likewise, it is possible to develop good metadata for narrative content. It requires the ability to sense what is missing and implied.

Challenges of a Taxonomy of Verbs

Why is metadata difficult for narrative content? Why is so much metadata tilted toward abstract content? There are three main issues:

  • Indexing relies on basic vocabulary matching
  • Taxonomies are noun-centric
  • Verbs are difficult to specify

Indexing and Vocabulary Matching

Computers rely on indexes to identify content. Metadata is a type of index that identifies and describes the content. Metadata indexes may be based the manual tagging of content (application of metadata) with descriptive terms, or be based on auto-indexing and auto-categorization.

Computers can easily identify and index nouns, often referred to as entities. Named entity recognition can identify proper nouns such as personal names. It is also comparatively easy to identify common nouns in a text when a list of nouns of interest has been identified ahead of time. This is done either through string indexing (matching the character string to the index term) or assigned indexing (matching a character string to a concept term that has been identified as equivalent.)

The manual tagging of entities is also straightforward. A person will identify the major nouns used in a text, and select the appropriate index term that corresponds to the noun. When they decide what things are most important in the article (often the things mentioned most frequently), they find tags that describe those things.

When the text has entities that are proper or common nouns, it isn’t too hard to identify which ones are important and should be indexed. Abstract content is loaded with such nouns, and computers (and people) have an easy time identifying key words that describe the content. But as we will see, when the meaning of a text is based on the heavy use of pronouns and descriptive verbs, the task of matching terms to an index vocabulary becomes more difficult. Narrative content, where verbs are especially important to the meaning, is challenging to index. Nouns are easier to decipher than verbs.

Taxonomies are Noun-centric

When we offer a one-word description, we tend to label stuff using nouns. The headings in an encyclopedia are nouns. Taxonomies similarly rely on nouns to identify what an article is about. It’s our default way of thinking about descriptions.

Because we focus on the nouns, we can easily overlook the meaning carried by the verbs when tagging our content. But verbs can carry great meaning. Consider an article entitled “How to feel more energetic.” There are no nouns in the title to match up with taxonomy terms. Depending on the actual content of the article, it might relate to exercise, or diet, or mental attitude, but those topics are secondary in purpose to the theme of the article, which is about feeling better. A taxonomy may have granular detail, and include a thesaurus of equivalent and related terms, but the most critical issue is that the explicit wording of the article can be translated into the vocabulary used in the taxonomy.

Verbs are Difficult to Specify

Verbs also can be included in descriptive vocabularies for content, but they are more challenging to use. Verbs are sometimes looser in meaning than nouns. Sometimes they are figurative.

graph of verb definition
Verbs such as to make can have many different meanings

A verb may have many meanings. These meanings are sometimes fuzzy. Actions and sentiments can be described by multiple verbs and verbal phrases. Consider the most overworked and meaningless verb used on the web today: to like. If Ralph “likes” this, what does that really mean? Compared to what else? The English language has a range of nuanced verbs (love, being fond of, being interested in, being obsessed with, etc.) to express positive sentiment, though it is hard to demarcate their exact equivalences and differences.

Many common verbs (such as work, make or do) have a multitude of meanings. When the meaning of a verbs is nebulous, it is takes more work to identify the preferred synonym used in a taxonomy. Consider this example from a text-tagging tool. The person reading the text needs to make the mental leap that the verb “moving” refers to “money transfer.” The task is not simply to match a word, but to represent a concept for an activity. We often use imprecise verb like move instead of more precise verb like transfer money. Such verbal informality makes tagging more difficult.

Tagging a verb with a taxonomy term.  Screenshot via Brat.
Tagging a verb with a taxonomy term. Screenshot via Brat.

With the semantic web, predicates play the role of verbs defining the relationship between subjects and objects. The predicates can have many variants to express related concepts. If we say, “Jane Blogs was formerly married to Joe Blogs,” we don’t know what other verbal phrase would be equivalent. Did Jane Blogs divorce Joe Blogs? Did Joe Blogs die? Another piece of information may be needed to infer the full meaning. Verbal phrases can carry a degree of ambiguity, and this makes using a standard vocabulary for verbs harder to do.

Samuel Goto, a software engineer at Google, has said: “Verbs … they are kind of weird.”

Computers can’t understand verbs easily. Verb concepts are challenging for humans to describe with standardized vocabulary. Tagging verbs requires thought.

Why Verb Metadata Matters

If verbs are a pain to tag, why bother? So we can satisfy both the needs of our audiences and the needs of the computers that must be able to offer our audiences precisely what they want. As an organization, we need to make sure all this is happening effectively. We need to harmonize three buckets of needs: audience, IT, and brand.

Audience needs: Most audiences expect content written in familiar style, and want content with strong, active verbs. Those verbs often carry a big share of the meaning of what you are communicating. Audiences also want precise content, rather than hoping to stumble on something they like by accident. This requires good metadata.

IT needs: Computers have trouble understanding the meaning of verbs. Computers need a good taxonomy to support navigation through the content, and deliver good recommendations.

Brand needs: Brands need to be able to manage and analyze content according to the activities discussed in the content, not just the static nouns mentioned in it. If they don’t have a plan in place to identify key verbs in their content, and tag their meaning, they run the risk of having a hollow taxonomy that doesn’t deliver the results needed.

A solution to these competing needs is to have our metadata represent the actions mentioned in the content. I’m calling this approach finding your key verbs.[1]

Approaches to a Metadata of Actions

Two approaches are available to represent verb concepts. The first is to make verbs part of your taxonomy. The second is to translate verbs in your content into nouns in your taxonomy.

Task-focused Taxonomies

The first approach is to develop a list of verbs that express the actions discussed in your content. Starting with the general topics about which you produce content, you can do an analysis and see what specific activities the content discusses. We’ll call these activities “tasks.”

Think about the main tasks for the people we want to reach. How do they talk about these tasks? People don’t label themselves as a new-home buyer: they are looking for a new home. They may never actually buy, but they are looking. Verbs help us focus on what the story is. There may be sub tasks that our reader would do, and would want to read about. Not only are they looking for a new home, they are evaluating kitchens and getting recommendations on renovations. This task focus is important to help us manage content components, and track their value to audience segments. We can do this using a task-focused taxonomy.

I am aware of two general-purpose taxonomies that incorporate verbs. The tasks these taxonomies address may differ from your needs, but they may provide a starting point for building your own.

The new “actions” vocabulary available in schema.org is the better known of the two. Schema.org has identified around 100 actions “to describe what can be done with resources.” The purpose is to be able not only to find content items according to the action discussed, but to enable actions to be taken with the content. As a simple example, you might find an event, and click a button to confirm your attendance. Behind the scenes, that action will be managed by the vocabulary.

The schema actions are diverse. Some describe high-level activities such as to travel, while others refer to very granular activities, such as to follow somebody on a social network. Some task are real world tasks, and others strictly digital ones. I presume real-world actions are included to support activity-reporting from the Internet of Things (IoT) devices that monitor real-world phenomena such as exercise.

screenshot of schema.org actions terms
Schema.org actions taxonomy (partial)

Framenet, a semantic tagging vocabulary used by linguists, is a another general vocabulary that provides coverage of verbs. If a sentence uses the verb “freeze” (in the sense of “to stop”), it is tagged with the concept of “activity_pause.” It is easiest to see how Framenet verb vocabulary works using an example from David Caswell’s project, Structured Stories. Verbs that encapsulate events form the core of each story element. [2]

screenshot structured stories
Screenshot from the Structured Stories project, which uses Framenet.

Applications of Task Taxonomies

While both these vocabularies describe actions at the sentence or statement level, they can be applied to an entire article or section of content as well.

A task focus offers several benefits. Brands can track and manage content about activities independently of who specifically is featured doing the activity, or where/what the object or outcome of the activity is. So if brands produce content discussing options to travel, they might want to examine the performance of travel as a theme, rather than the variants of who travels or where they travel.

Task taxonomies also enable task-focused navigation, which lets people to start with an activity, then narrow down aspects of it. A sequence might start: What do you want to do? Then ask: Where would you like to do that? The sequence can work in reverse as well: people can discover something of interest (a destination) and then want to explore what to do there (a task).

Situational taxonomies

A second option uses nouns to indicate the notable events or situations discussed. Using nouns as proxies for actions unfortunately doesn’t capture a sense of dynamic movement. But if you can’t support a faceted taxonomy that can mix nouns and verbs, it may be the most practical option. When you have a list of descriptors that express actions discussed in your content, you are more likely to tag these qualities than if your taxonomy is entirely thing-centric. I’ll call a taxonomy that represents occasions using noun phrases a situational taxonomy. The terms in a situational taxonomy describe situations and events that may involve one or more activities.

If you have ever done business process modeling, you are familiar with the idea of describing things as passing through a routine lifecycle. We reify activities by giving them statuses: a project activity is under development, in review, launched, and so on. Many dimensions of our work and life involve routines with stages or statuses. When we produce content about these dimensions, we should tag the situation discussed.

One way to develop a situational taxonomy is by creating a blueprint of a detailed user journey that includes an end-to-end analysis of the various stages that real-world users go through, including the “unhappy path” where they encounter a situation they don’t want. Andrew Hinton has made a compelling case in his book Understanding Context that the situations that people find themselves in drive the needs they have. Many user journey maps don’t name the circumstances, they jump immediately into the actions people might do. Try to avoid doing that. Name each distinct situation: both the ones actively chosen by them as well as those foisted on them. Then map these terms to your content.

Situational taxonomies are suited to content about third parties (news for example) or when emphasizing the outcomes of a process rather than the factors that shape it. Processes that are complex or involve chance (financial gyrations or a health misfortune, for example) are suited to situational taxonomies. A situational taxonomy term describes “what happened?” at a high level. Thinking about events as a process or sequence can help to identify terms to describe the action discussed in the content.

The technical word for making nouns out of verbs is “nominalization.” For example, the verb “decide” becomes the noun “decision.” Not all nominalizations are equal: some are very clunky or empty of meaning. Decision is a better word than determination, for example. Try to keep situational terms from becoming too abstract.

Situational taxonomies are less granular than task-based ones. They provide an umbrella term that can represent several related actions. They can enhance tracking, navigation and recommendations, but not as precisely as task-based terms. Task taxonomies express more, suggesting not only what happens, but also how it happens.

Key Verbs Mark the Purpose of the Content

Identifying key verbs can be challenging work. Not all headlines will contain verbs. But ideally the opening paragraph should reveal verbs that frame the purpose of the article. Content strategists know that too much content is created without a well-defined purpose. Taxonomy terms focused on actions indicate what happens in the content, and suggest why that matters. Headlines, and taxonomy terms that rely entirely on nouns, don’t offer that.

We will look at some text from an animal shelter. I have intentionally removed the headline so we can focus on the content, to find the core concepts discussed. A simple part-of-speech app will allow us to isolate different kinds of words. First we will focus on the verbs in the text, which includes the terms “match”, “spot”, “suit”, “ask”, and “arrange”. The verb focus seems to be “matching.” Matching could be a good candidate term in a task taxonomy.

part of search view of verbs in narrative

Now we’ll look at nouns. In additional to common nouns such as dogs and families, we see some nouns that suggest a process. Specifically, several nouns include the word “adoption.” Adoption would be a candidate term in a situational taxonomy. Note the shift in focus: adoption suggests a broader discussion about the process, whereas matching suggests a more specific goal.

part of search view of nouns in narrative

When you look at content through the lens of verbs, questions arise. What verbs capture what the content is describing? Why is the content here? What is the reader or viewer supposed to do with this information? Could they tell someone else what is said here?

If you are having trouble finding key verbs, that could indicate problems with the content. Your content may not describe an activity. There is plenty of content that is “background content,” where readers are not expected to take any action after reading the content. If your goal for producing the content is simply to offer information for reference purposes, then it is unlikely you will find key verbs, because the content will probably be very noun-centric. The other possibility is that the writing is not organized clearly, and so key actions discussed are not readily seen. Both possibilities suggest a strategy check-up might be useful.

Avoid a Hollow Taxonomy

Even when tagging well-written content, capturing what activity is represented will require some effort. This can’t be automated, and the people doing the tagging need to pay close attention to what is implied in the content. They are identifying concepts, not simply matching words.

Tagging is easier to do when one already has vocabulary to describe the activities mentioned in your content. That requires auditing, discovery and planning. If your taxonomy only addresses things and not actions, it may be hollow. It can have gaps.

Most content is created to deliver an outcome. Metadata shouldn’t only describe the things that are mentioned. It should describe the actions that the content discusses, which will be explicitly or implicitly related to the actions you would like your customers to take. You want to articulate within metadata the intent of the content, and thus be in a position to use the content more effectively as a result. Key verbs let you capture the essence of your content.

By identifying key verbs, brands can use active terminology in their metadata to deliver content that is aligned with the intent of audiences.

diagram of key verb roles
How key verb metadata can support content outcomes

The Future Web of Verbs

Web search is moving “from the noun to the verb,” according to Prabhakar Raghavan, Google’s Vice President of Engineering.

We are at the start of a movement toward a web of verbs, the fusing of content and actions. Taxonomy is moving away from its bookish origins as the practice of describing documents. Its future will increasingly be focused on supporting user actions, not just finding content. But before we can reach that stage, we need to understand the relationship between the content and actions of interest to the user.

Taxonomies need to reflect the intent of the user. We can understand that intent better when we can track content according to the actions it discusses. We can serve that intent better when we can offer options (recommendations or choices) centered on the actions of greatest interest to the user.

The first area that verb taxonomies will be implemented will likely be transactional ones, such as making reservations using Schema actions. But the applications are much broader than these “bottom of the funnel” interventions. Brands should start to think about using action-oriented taxonomy terms through their content offerings. This is an uncharted area, linking our metadata to our desired content outcomes.

— Michael Andrews


  1. Key verbs build on the pre-semantic idea of key words, but are specific to activities, and represent concepts (semantic meaning) instead of literal word strings.  ↩
  2. You can watch a great video of the process on YouTube.  ↩
Categories
Intelligent Content

Ontology for the Perplexed

Sooner or later people who deal with content hear about an odd word called ontology.  It is often discussed as a forbidding topic: the representation of all knowledge, and the source of endless grief for those who dare to wrestle with it.  I’ve seen online debates of people trying to define what it is, often by comparing it to other forms of content organization.  These definitions are sometimes theoretical, sometimes impossibly mechanical, and routinely confusing.

Ontology is often shrouded in mystery.  But it is an important topic with practical uses.  Ontologies are used to organize content on various topics, though the details of specific implementations can be complex.  In an effort to distill some of the essence of what ontology is about, I read a recent book by an analytic philosopher named Nikk Effingham entitled An Introduction to Ontology (Polity Press, 2013).  I learned that ontology is a controversial field, full of debates and disagreements about terminology.  While the details of the philosophy were less practical than I might have hoped, I did find the range of topics debated useful to understanding many foundational issues content strategy professionals must take into consideration.

To get a sense of the importance of ontology, consider the emerging field of the Internet of Things.  Already, we have a multitude of things that are connected together, each sending out signals indicating what each thing is sensing. The devices and the systems they interact with, are constantly sensing, monitoring, and interpreting.  These signals may address social, physical, biological, or cognitive phenomenon.  What do all these signals mean?  Deciphering and translating their meaning is partly the role of ontology.

There are plenty of complex definitions of ontology, but I will offer a more direct one.  Ontology is simply identifying and describing what exists that might be significant.  We can refer to what exists generically as a thing.  We need to define what is the thing is, especially since we commonly define things in terms of other things.

When I looked at some of the philosophy that inspired this way of thinking, I found several themes that resonated with me that seemed of practical value.  I will summarize these below in several propositions.  They are my insights, rather than a summary of the field, which as I noted, it far from consensus.

Before we try to construct an elaborate network of inter-related definitions, the formal mechanics of ontology, it is important to identify dimensions that can impact how we define things.

image via synsemia
image via synsemia

Use Properties To Help You Establish How Similar Things Are

We can identify various properties associated with a thing.  The more properties a thing shares with another thing, the more likely the two things are related, all things equal.  Related things will be seen as complementary or competitive with each other.

The properties should be meaningful and hold significance.  Trivial properties (for example, something true in all cases) won’t convey much useful information.  The property that is most unique about a thing is often interesting, although it is also possible the property is not significant.  A test of significance is looking at the potential explanatory value of a property.  Might the property influence the behavior of the thing, or perhaps other things that interact with it?   Suppose we divide things into those that have metallic finish colors, and those with matte finish colors.  Is that difference significant, or inconsequential?  The significance of properties will depend on the context.  Rarely does one property alone entirely sway outcomes, so the covariation of properties are most interesting.

Differentiate Whether Things are Equivalent, or the Same

Sometimes a single thing is described in different ways.  Sometimes different things are described in the same way.

We know a single individual can have different monikers.  Mark Twain was the same person as Samuel Clemens, but unless we are aware that this author used a pen name, we might believe the names referred to different people.

A more challenging issue is when we want to see things that are broadly similar as being a single item.  We can match up things that agree on numerous properties and will say they are the same kind of thing.  When every property is identical, we can be tempted to assume the two things themselves are identical.  But we can be tricked into seeing things as identical when they are merely equivalent, due to the limitations of our descriptions.  Suppose all Model Z computers share the same properties we have identified — they have the same specs.  There is a bug in the computer, and the engineering team develops a fix.  The customer service team announces that Model Z’s problems are now fixed.  But a group of people using the Model Z continues to experience problems.  It turns out their computers are not exactly identical to other users: perhaps they have loaded software from Adobe or Oracle, which is outside of the specs the manufacturer tracks, which created the conflict.

Any time there are two or more instances of a thing, there will be some variation.  Sometimes that variation is so minor we can comfortably say the instances are effectively identical.  It is useful to know how much variation might be possible before assuming all instances of a thing will behave the same way.  And it is very important not to treat clusters of things (including people) that seem broadly similar as being identical.  There’s much value knowing how things might be equivalent to one another, but one should also be aware of potential differences.

Distinguish Categorical and Qualified Descriptions

Many descriptions are factual, and not subject to interpretation or subsequent change.  Your car will generally have the same engine size over its lifespan.  We say your car is a V-6: it is part of the identity of the car.  For many tangible things, as long as the thing exists, its properties will remain the same, even when it reaches the landfill.

Some descriptions are qualified by time or place.  When we see a map on a sign saying “you are here” we know that  “here” is relative to our current location and changes as we move around.  If we were to view this sign through a webcam remotely, the message would be incongruous.  As mobile technology allows us to shift location and time zones and communicate asynchronously, descriptions of where and when become more challenging.

Time and place can have more subtle effects on identity.  I once worked with a telecommunications firm that had a “family” package.  The marketing staff liked how friendly the word family sounded.  But when defining family, the definition subtly shifted to becoming members of your household.  Then the question arose of who qualifies as a member of a household.  Would children in university count?  If so, would it be only when they are living at home, or when they are away at university?  It may have seemed like an arcane issue to debate that distracted from other tasks, but the issue had significant impacts on sales, recurring revenues, and cost of service.

Ontologists refer to qualified descriptions as indices.  With the rise of big data, we are finding more indices pretending to be solid things.  I shop online, and am told that based on my “profile” I presented with various recommended products.  If I regularly shop for a wide variety of products, my profile is always changing, but never seems to match me, because now I’m seeking something different.

Know Whether a Concept is Abstract or Transitional

We often use intangible concepts to describe things — it helps us make sense of the qualities of a thing.  The meaning of many concepts we use to describe things are stable and familiar, so much so we think of them as real things, rather than as concepts.  When we say something is a meter long, the meaning of a meter is won’t fluctuate — the definition of a meter has been fixed for a couple of centuries.  Such concepts are abstract: independent of time or location.   But some concepts are less fixed, and more subject to time and place.  We might describe a work of art as contemporary, because it was created less than 20 years ago.  But in another five years, it might be more appropriate to call the same unchanged item of art as being modern, especially if the artist were to die.

Cultural values are especially susceptible to changes in meaning over time — just look at how old advertisements describe products in ways we find offensive or clueless today.  A simple example would be the shifting meaning of the term “healthy.”  Occasionally cultural changes can happen even faster than products change, such as gender role changes: for example, eyeliner for men being dubbed guyliner. Even many technology descriptions are conceptual, and transitional.  The label smartphone is just a concept that has no stable identity.  What we consider to be a smartphone has changed over time, and there is no guarantee we will continue using this term in the future.

Concepts are useful.  Just be aware that because they are often not precisely defined, their meaning is more likely to drift over time.

Watch Out for Frankenobjects

People in the marketing world are sometimes prone to package together unrelated items.  Consider Amazon Prime.  What is it, exactly?  Is it a club membership?  A prepaid shipping fee?  A streaming video service?  A music service?  What will it be next year?

Philosophers studying ontology call things that are glued together from parts that are not conceptually related or normally connected as “gerrymandered objects.”  Like gerrymandering in politics, the motivation is to trap something in an incomprehensible identity that changes form over time.  If you have to present a gerrymandered object to audiences, be prepared to do a lot of explaining what it is, how it works, and why it matters.

Understand What a Grouping has in Common

There are two types of groupings: collections and sets.

Collections are groupings of things that have common properties.  They are things that seem to belong together.  We see a collection of clothing for spring that are colored yellow.  The types of clothes are different, but they are all yellow, and all for spring, so they seem like a meaningful collection.  The creation of collections relies on rules based on the properties of things included in the collection.

Sets are things that are placed together on the basis of a choice that may be extrinsic to the properties of the items.  A good example is an online shopping cart. I may have a roll of cellophane tape, a pair of socks, and a bottle of allergy medicine in my cart.  It is a set of things that are unrelated, except for the fact I placed them there at a specific time with the intent to purchase them.  Sets are often created or changed as a consequence of an event.  There may not be any rules about what can be included in a set.

Sets may include related things, but do not have to.  Sets require interpretation to know what they contain, since we may not know the details or themes of their contents except through inspection.  We can combine sets, or look for unique items among several sets.  Whereas common properties define collections, with sets, you might check common or unique properties after making changes to the set.

Both collections and sets are useful, but they serve different purposes.

Understand the Changes of State that are Possible for a Thing

It can be difficult to say when something changes from one state to another.  This is especially true if we can’t identify a specific event responsible for causing the change.  I don’t know when my hair turned from brown to grey.  In fact, when listening to other people’s opinions on this topic, there seems to be minor disagreement.  Not only is change sometimes hard to pin down, it can be subjective as well.  When will my hair stop being grey?  When I shave my head, or dye my hair orange.

We assume hair color will change over time, even though it is generally not a significant property of people.  But we often underestimate the changes in the more significant properties of other things.  This poses two issues. One is that the description fails to update itself when the thing has changed. Another is that we are unprepared for unexpected change, and don’t even have vocabulary ready to describe it.  We need to account for edge cases, and intermediate properties that could be significant.

Closing Thoughts

Creating an ontology is challenging work. They typically require a team of people working over the course of years to develop them.  No one is going to create a new ontology for the Internet of Things in a few weeks time.

But ontological thinking is easier to do, and more immediately applicable.  Ontology reminds us that we often bring a point of view that colors how we perceive and categorize things.  Our view may be influenced by a specific time, place or situation in which we are located.  When we are aware of these factors, we can develop a person-independent description of things.

— Michael Andrews

Categories
Intelligent Content

Is Rich Narrative Possible From Structured Content?

Two of the biggest themes in content these days are structured content, and storytelling.  A number of people are suggesting the two approaches complement each other.  For example, Robert Rose, a well-known promoter of content marketing, commented in a LinkedIn discussion: “It’s not just about tags, taxonomies and 1’s and the 0’s… And it’s not just about the storytelling, personas and buyer’s journey… It’s where those things — and most importantly people —  meet that move the business forward.”  The proposed combination of structured content with narrative has sparked both anticipation and uncertainties.  Will it be transformational and game-changing, or a hornet’s nest of anguish?

Storytelling and factually oriented technical communication can potentially learn from each other.   The structured content approaches associated with technical documentation enable content to scale up for use by many different people in different channels.  The storytelling approaches embraced by the best content marketing and journalism, when backed by robust analytics, can enable content to be genuinely wanted by people, rather than just be minimally adequate.

Even if we have a solid rationale for trying to get the two concepts to work together, that doesn’t guarantee the effort will be successful or easy.  How editorial structure (the framework behind storytelling) and content structure (the framework behind intelligent content) work together is still unclear.  The two approaches are different in their origin and purpose, and anyone curious about how they might complement each other needs to understand their differences.

So far, there are few concrete examples of semantic content use in narratives.  Many different kinds of issues are involved: technical, emotional, and pragmatic.  It is hard to separate what’s visionary potential from what’s wishful thinking.

The potential of semantic content is linked to a number of foundational questions. These include:

  • What is the relationship between editorial structure, and the structure of content as understood by computers?
  • How far can stories be structured?  To what extent does structured content support narrative?
  • How does structure support or hinder communication — the ability of people to understand on their own terms?
  • Is structure the same as modular reuse?
  • Can the modular content techniques developed for technical support documentation be readily applied to narrative-driven marketing collateral?

Besides presenting an intriguing goal, the topic holds larger significance.  The proposition that semantic content and storytelling can be combined challenges the discipline of content strategy to examine its assumptions, and consider possibilities for innovation.

The Many Dimensions (and Guises) of Intelligent Content

Intelligent content is a term used to describe approaches for making content more intelligent to both audiences and the computers serving them.  It is an umbrella term covering a range of different related concepts: structured content, modular content, atomic content and reusable content.  Because there is significant overlap in these concepts, there can be a tendency to treat them as equivalent.  On occasion we use these terms interchangeably, which in some contexts is appropriate.  At the same time, there can be differences in meaning and nuance among these terms we should be aware of.  As best I can tell, there is no consensus in the content strategy community defining these terms, and as a result, they are sometimes used in somewhat different ways.  To me, the terms can suggest slightly different things:

  • Semantically structured content — how the structure of an article or episode affects its meaning, expressed through machine-readable metadata such as page section descriptions.  For some people HTML5 offers semantic structure, for others, only XML is sufficient.
  • Modular content — chunks of content that can be assembled in different ways
  • Atomic content — the smallest meaningful unit of content
  • Reusable content — content that can be used multiple times in different contexts without any modification.

Consider how these terms can be used differently.  Semantically structured content does not automatically imply modularity, where the content can be reassembled in a different way.  You might use the semantic structure purely for SEO purposes, for example.  Modular chunks of content are not necessarily the smallest meaningful units, which means that the chunks may not be completely repurpose-able.  Modular content that is composed of a collection of atomic elements is not necessarily reusable content that permits the module can be used in diverse contexts.

How one thinks about these terms shapes one’s expectations for what capabilities they represent.  Some of these concepts are too new or too fluid to have a well-established meaning.  There is too much play in how they might be implemented to settle on their exact meaning and scope.  Locking down precise definitions would be counterproductive.

Structure in Linear and Nonlinear Content

The content community has expressed a range of views about the extent to which structure is compatible with narrative content.  It’s a thought provoking discussion because it touches on many core issues we grabble with.

One argument is that narrative content is different in character, and that narrative content cannot be reused.  Deane Barker has written: “To effectively manage content down to the paragraph or sentence level and re-use them in extended narratives, you would have to make sure each one was completely self-contained and match the style, tone, and tense of everything before or after. This is not easy.”  In response to this comment, Rahel Anne Bailie stated: “narrative isn’t one of the genres meant for any kinds of re-use.”

Another concern is that pre-defined structure inhibits narrative flow.  Rick Yagodich writes in his book Author Experience that “the idea of narrative and structured content may appear to be at odds with each other. Structure puts up walls and determines boxes we need to fill-in, whereas narrative is a good story, a flow that adapts to the needs of the message being conveyed.”

On the other side, some journalists are exploring how to incorporate structure into journalistic content. Adrian Holovaty, a journalist-programmer, wrote an influential post on this topic in 2006.  In it, he argued: Newspapers need to stop the story-centric worldview.  Repurposing and aggregating information is a different story, and it requires the information to be stored atomically — and in machine-readable format.  A lot of the information that newspaper organizations collect is relentlessly structured.”  He maintained: “But stories have structure — otherwise they are a torrent of associations that aren’t logically tied together.”

There have been several journalistic initiatives to put into practice Holovaty’s ideas of making the story flow out of a structure.  The best known is Circa, which is based on the atomization of content.  Each paragraph is a distinct unit of content.  Circa differs from a lot of other storytelling through how it structures stories.  The story is emergent, and based around time, so that it builds up over time as atoms are published.

The Continuum of Structure

I question the idea that there is a clean dichotomy between narrative content, and factual (descriptive or explanatory) content.  It is true that some content, narrative especially, is predominately linear, while other content, for example an e-commerce catalog, is non-linear.   But narrative does have structure, and factual content often implies stories.

Rather than seeing two genres, story and fact, one can identify many dimensions of structure across various genres.  The below diagram shows how genres have common structures, and even different genres can have parallel structures.

table of content structures for different content types and genres
Common structures for different content genres

What is common to many genres is a need

  • to set the context of a discussion
  • to establish the relevance to the reader
  • to give the reader points of comparison to other things she knows about already, or might want to learn more about
  • to satisfy a goal we assume the reader has
  • to provide a satisfying experience, so the reader will want more content from our source in the future

Why Editorial Structure Matters to Narrators

Editorial structure — how writers and editors arrange content to provide meaning to readers — is a topic that predates intelligent content by hundreds of years.   Analog content with a strong editorial structure provides enormous intelligence for readers, even if computers can’t understand its nuances.

Semantically structured content is not the same as editorial structure. Consider a help guide. The below screen shot presents the help guide for one of the most popular XML tools intended for creating structured content.  The content is minutely structured in XML.  It can be read online, within the application itself, and as a PDF.  It would seem a prime example of the benefits of structured content.  But the content itself is barely usable.  The content is fragmented.  One cannot get a sense of the relationship among the information: there seems to be an endless list of links, some of which go to other lists of links.   When the output of structured content is so unwelcoming for audiences, many writers are understandably hesitant to embrace structured content.

Screenshot of the help facility of an XML tool, generated using structured content.
Screenshot of the help facility of an XML tool, generated using structured content. It is difficult to understand the relationship of the various content presented.

The reality is that many writers and editors feel stymied by attempts to impose structure on them.  Jeff Eaton, a content developer who has worked with leading publishers, notes: “this doesn’t mean that editors and writers are content with rigid, predictable designs for the material they publish.  This challenging requirement — providing editors and writers with more control over the presentation of their content — is where many well-intentioned content models break down.”

Editors and writers concerned with presentation want more than what is offered by a CSS style sheet.  It is fundamental to their ability to communicate meaning to audiences — the deep meaning that storytelling content aims to deliver.  Dismissing these concerns as unimportant or someone else’s problem won’t advance adoption and development of structured content.  We need to appreciate and accommodate the vital function editorial structure plays.

Structure is More than Lexical

By some measures, editorial structure has become less robust with the rise of structured content.  This trend was not inevitable.  It reflects the absence of a central coordinating mechanism directing how audiences receive their content.  The separation of content from presentation and from behavior often means that none of these things is centrally coordinated.  The editor has gone missing in the action.  A core weakness stems from treating structure as entirely lexical, and assuming metadata describing words and characters are the only factor enabling structure.

Rob Waller, an information designer and fellow at London’s Royal College of Art, laments how poor the narrative experience is for a digital product compared to a printed one.   “The reader of the paper version can slip easily between related stories because cohesion within the set is provided graphically: their physical location, the typographic hierarchy, and visual genre distinctions all provide cohesion cues that in the Web version are absent or are entirely lexical.”  He notes: “whatever their actual content, we tend to assume that things that are physically close on the page are related in some way (the proximity principle), and that things that look similar are members of the same category (the similarity principle).”

Waller praises what he calls “a golden age of layout, the 1970s and 1980s. Publishers such as Time-Life, Reader’s Digest, Dorling Kindersley, and others developed a new genre that, inspired by magazine design, used the double-page spread as a unit of meaning.  The diagrammatic quality of these books – typically on hobbies, sports, history, or travel – brought layout to the fore. They were developed by multidisciplinary teams in much the same way as films are produced. Unlike the traditional book, in which the author’s voice is primary, in these books, the writer fills in spaces to order, and provides functional text such as descriptions and captions on request from editors, illustrators, photographers, and designers.”

To get a sense of how editorial structure supports narrative richness, let’s look at a couple of examples from Dorling Kindersley (DK) guides I own.  The first, from a guide to the Italian region of Umbria, presents a map of a park with associated commentary to let the reader choose their physical (or vicarious) adventure: a visit to Roman ruins, a medieval village, a summit or a cave.  The page spread shows a wide range of content: introductory explanation, the map itself, symbols on the map indicating various types of places, pictures of some of the places with a pointer to where they are, description of places with a pointer to where they are, and a sidebar of related information about wildlife in the park.  What makes the narrative rich is that it seamlessly integrates all kinds of different information types into one narrative, the story of a park.

Guidebook example
This guidebook spread integrates many information types into a cohesive presentation. Readers can choose their personal interests: perhaps paragliding, or visiting paleolithic ruins.

For a very different example of editorial structure, we will look at a DK guide to the opera.  Opera is an archetypal form of storytelling, so it’s interesting to see how a narrative that’s long, complex, and multifaceted can be condensed into its essence in an engaging way.  The discussion of the opera Tosca has a wealth of structured content, but unlike much XML generated content, the structure doesn’t assault the reader.  There are information boxes with key facts about the opera performance (duration, dates of composition and first performance, librettist and sources), and the principle roles.  But the interesting structure comes from the presentation of the story itself.  Operas are structured stories, and within each act are highlights, especially the major songs.  The songs are indicated at the exact point in the story they are sung with an indication of their type (aria, duet, or ensemble), and the key line from the song in a call out.  There are also images and sidebars relating to notables performances of the opera.  Again in this example, the editorial structure leads to a planned and integrated presentation of content.

Oper guide example -- structured content
Structured content supports the telling of an operatic story.

Reuse Isn’t Monolithic

What is different about the examples from the guidebooks is that the content structure seems primarily aimed at supporting audience needs, rather than reducing the burden to the publisher.  As someone who has used DK guides for many years, I am aware they use structure to reuse content across different products, and to revise their guides.  But the structure doesn’t appear to the enduser to be an efficiency measure.  Rather, it seems natural, because the elements are so well integrated.

Reuse is not the only benefit of structure.  Focusing on reuse obsessively can result in overly complicated and unworkable solutions.  We need to evaluate reuse from an editorial perspective, not just a publishing productivity one.

Content elements often have cross-dependencies.  Cross-dependencies are a good thing, even though they create challenges.  Elements offer value in relation to what they are presented with — the meaning can be based on the cross-dependency.  The integration of different elements in a thoughtful manner yields larger meaning.

We like to think we can rearrange pieces of content to create different content.  But the pieces have cross-dependencies, and need to arranged in a precise way.  This puzzle, which I bought at a Munich Christmas market, looks simple, but is in fact be tricky.
We like to think we can easily rearrange pieces of content to create different content. But the pieces have cross-dependencies, and need to arranged in a precise way. This puzzle, which I bought at a Munich Christmas market, looks simple, but is in fact tricky.

The discussion of reuse can often be monolithic, looking to reuse everything, instead of selectively reusing items in the context of content that is not intended to be reusable.  When viewed from an editorial perspective, the chief benefits of reuse are to ensure accuracy when precision is essential, and to enable the combination of items in truly novel ways that bring value to audiences, rather than simply provide a minor variation.

Difference between Macrostructure and Microstructure

All structure is not the same, even when it is semantically marked up.  Some structures describe many things at once; other structures describe very specific items of information.  Discussing structure as a single abstract concept can cause us to overlook important differences.

Macrostructure is high-level structure that is common to a content type.  It provides the descriptive elements of what is being discussed.  Suppose the content deals with bird identification.  Most bird field guides have similar sections: name, identifying physical characteristics, behaviors such as feeding and nesting, habitat, voice calls, and range.

Microstructure is concerned with details and facts.  They are often the variables within a content type, and may be marked up using a standardized schema.  They identify people, places, things and quantities.

We know in many areas of life that a thing is often more than the sum of its parts — described by a scientist who pioneered the theory of the constructive emergence of hierarchies as “more is different.”  We need to understand what’s different about complex content structures.

What Bird-watching Can Teach Us About Content Structure

Birds are things in the real world that are classified with exactness.  Long before librarians thought to use taxonomies to classify content, naturalists developed the concept of taxonomies to classify birds and other living things.  One might think that birds are a topic were one can “roll-up” specific facts about a type of bird to develop larger chunks of content about them.  The challenge is that the facts about birds don’t necessarily define what they are.  They simply are indicators.  A recent book on learning (Make it Stick) notes: “To identify a bird’s family, you consider a wide range of traits like size, plumage, behavior, location, beak shape, iris color, and so on. A problem in bird identification is that members of a family share many traits in common but not all.”  It adds: “Because rules for classification can only rely on these characteristic traits rather than on defining traits (ones that hold for every member), bird classification is a matter of learning concepts and making judgments, not simply memorizing features.”

The story of a bird is more than the facts about it: it involves communicating a concept.  The difference between concepts and facts is the difference between macrostructure and microstructure.  Stories are made from both macrostructure and microstructure.

Functions of Editorial Structure

Does the content look as if it was constructed by a database?  Much structured content is not very good hiding its piecemeal origins.  And unfortunately editorial structure can’t be faked by asking your CSS expert to create a style sheet that magically makes disparate pieces of content seem like they belong together.   Editorial structure is a more comprehensive concept than font sizes and cell padding.

Where the tagging of microstructure has been motivated by search, and content reuse, the role of macrostructure is different.  Macrostructure supports how people interact with content, a major focus of editorial structure.  Editorial structure performs a curatorial role: showcasing topics (what things have in common, showing examples) and themes (comparing aspects).

Macrostructure supports way-finding.  Consider the reader’s journey.  They come from other content to this content.  What do they do next? Get more details?  Look for related content? Take action on the content? Good content has a take-away.  Editorial structure supports that.  It defines the purpose of the assembled content, while microstructure has no inherent purpose – it can be used in various situations.

The danger to narrative content is that the emphasis on smaller units of content can result in a poor narrative experience.  The issue isn’t so much whether atomic content is compatible with narrative, but how rich a narrative experience one can develop building from atomic content.

Finding the Relationships Among the Pieces

As we have become more analytical about our content, and seek to bring more transparency to the tacit judgments of editors, we can become overwhelmed by the enormity of detail we face.  Suddenly things that make sense on an intuitive level seem bewildering when exposed in minutia.

While the mechanics of intelligent content are important, it is equally important to understand how these can serve audience needs and create impact.  To do this, we need to appreciate how audiences experience content through patterns and storytelling devices.

Authors and editors use various techniques to guide the reader.  They emphasize different aspects of content.  The below chart summarizes how the choices that authors and editors make (the center two columns) can address audience needs.

chart showing intelligent content and editorial structure relationships
Editorial structure is what ties together intelligent content to audience experiences

On the left side are tactics from the toolkit of intelligent content.  The task is to choose appropriate tactics to support the goals of authors and editors.  Moving from left to right, each column has building blocks that support items to the right.   The building books culminate in experiences for audiences.  Conversely, starting with the needs of audiences, we can design experiences for them by building structure into content as we move toward columns on the left.

Structure is Semantic, but also Visual and Behavioral

Meaning is bigger than how something is described. It consists of implicit dimensions: perceptions and behavioral experience over time.

Perceptions are often visual, though they could be auditory, or haptic.  Visual design addresses issues like gestalt, continuation, and picture— word interactions that influence our interpretation of content.  We know from eye tracking that layout has a significant  impact on how content is perceived and understood.  It is not simply a cosmetic thing.  The term stylesheet, while a powerful concept, can falsely suggest that visual design is no more than paint-by-numbers coloration of a canvas.

Behavioral structure is a combination of interaction design (setting up how users can explore available content) and algorithmic design (the computer deciding what order and sequence of content to present).

Visuals and experiences in time are themselves information. They shape how people feel about something as much as words do.  A photo accompanying an article can dramatically shape how a reader feels about the subject. The pacing of interaction can shape how exciting or precious something seems.

We can’t allow the notion of “presentation independent” content to devolve into “experience free” content. We need to be able to describe the feelings we want our content to convey, wherever it appears.

Semantic Markup Needs Human Judgment

There is sometimes a tendency to treat semantic markup as some sort of objective reality that people uncover for the benefit of computers. This view ignores the subjective character of much semantic markup, which is essential to conveying meaning.  If semantic markup doesn’t apply judgments of humans, it is probably superficial and will be limited in what it can accomplish.

Going back to our discussion of birds.  A species doesn’t just represent a series of tagged data; it represents a concept, an idea.  There was a judgment made on how to classify the bird. Higher level structure involves judgments, which though subjective, are shared by wide numbers of people.

Like editorial structure, semantics aren’t purely lexical. People infer semantics through context and presentation.  They perceive semantic elements as having boundaries, identities, and hierarchies.  Boundaries express the aboutness of the section, which can vary in explicitness and in uniformity.  Identities may be implied, rather than explicitly named. Hierarchies must be understood to matter.

Semantic markup is not simply what is explicitly described: it is meant to capture what people interpret when they see see (or hear) the content.  The folks who understand this best are those working in the digital humanities using an XML schema called TEI.  The Text Encoding Initiative (TEI) defines markup as “any means of making explicit an interpretation of a text… it is a process of making explicit what is conjectural or implicit, a process of directing the user as to how the content of the text should be (or has been) interpreted.”  TEI uses XML to structure content to convey the meaning represented by the layout and other presentational dimensions of content. “The physical appearance of one particular printed or manuscript source may be of importance: paradoxically, one may wish to use descriptive markup to describe presentational features such as typeface, line breaks, use of whitespace and so forth.”

TEI uses metadata to describe appearance. We can similarly use metadata to express preferred presentation.

Karen McGrane has wisely counseled that “we can’t rely on visual cues” to convey semantic information. She says this because our content by necessity must be ready to be multi-channel and multi-media, and we can’t presume to know how it will appear, exactly.  But that doesn’t mean we should not use visual cues, if they are available to use. Presentation independence doesn’t mean presentation is not relevant.

Unfortunately most metadata today is exclusively literal. When used to describe legacy content, it tends to strip out meaning that is implied in the context in which it sits. When used to describe new content, it denies authors the ability to indicate the preferred context in which it might appear. We need to find ways to enhance metadata with contextual cues, so that it can convey more meaning.

While we may not be able to predict all the forms in which our content may appear, we need to think about content holistically, not just atomically.  Semantic markup should not only define boundaries, but suggest possible linkages to other semantic elements.

Making Structured Content More Narrative-Friendly

I am cautiously optimistic that semantic structure can support the development and delivery of narrative content — stories in various forms that audiences will enjoy and act on. The technical challenges are solvable. If we are to believe the view that rich narrative is the best way to gain audience attention at a time when content is too plentiful and too generic,  then monetary incentive to move in this direction is present.  But we won’t get there relying on existing approaches.  I don’t see the DITA toolkit favored by technical writers as supporting narrative content.

To enable structure to support narrative, we need to stretch our abilities in three key areas:

  • Broadening our concept of narrative
  • Broadening our concept of metadata structure
  • Broadening our toolset

Broadening our concept of narrative

For all the interest and excitement surrounding storytelling, people often hold a surprisingly narrow view of what a story is.  For many people, a story is a plot-driven, hero-centric tale. They equate stories with the template used by Hollywood blockbusters, the hero’s journey pattern so often recycled by the advertising industry.  But stories can take many forms, and be experienced in many ways.

Stories are any content that offers a vicarious experience. The key ingredient is that people experience something: they are involved with the content.  It could be interacting with a map or a timeline, composing a plan with images, or immersing oneself in a podcast. None of these things is necessarily a story, but each of them could be. The test is asking someone what he or she did today. If they mention your content, it left a memorable impression. If they remark on some aspect that meant something to them, it indicates they experienced something using your content.

Scope is another story dimension. We tend to think about content as narrative, or non-narrative.  But it is possible to have story elements embedded in non-narrative content. One can imagine mini-stories consisting of swappable, targeted anecdotes or case studies included in a longer body of content. It’s harder to produce an experience with a short piece of content, but if appropriately targeted to be personally relevant to the audience, it could improve how audiences relate to the content.

Broadening Our Concept Of Metadata

In addition to adding element metadata, we need to expand the use of metadata describing the attributes of the elements.  If structured content is to really going to engage audiences, instead of being just more dross they have to cope with, the structure needs to reflect what is engaging about it. The success of semantically enriched content narratives will be judged and measured by the concrete impact they achieve.

Metadata needs to capture the big ideas behind the content: to indicate how we want audiences to interpret a section of content. Rather than simply indicating an “overview section,” the metadata needs to indicate what’s different about this overview section compared to others. As mentioned earlier, metadata for more complex, higher level content objects could capture more subjective, conceptual qualities, describing the fuzzier aspects of “aboutness”. Just because a quality is fuzzy (non tangible and more difficult to describe) doesn’t mean the concept isn’t real or is unimportant. When describing subjective qualities, the standard to use is intersubjective agreement: when multiple people describe a quality in similar ways (even if the exact term each uses differs). This metadata will provide valuable clues about appropriate usage of the content in different situations. I offered one idea for such an application in my CS Forum talk last year on content attractors, but there are many other applications possible.

In addition to capturing aboutness, attribute metadata should also provide clues about the compatibility of the content chunk with other chunks. Imagine you had a press release about an unfortunate event at your organization — a fire perhaps.   You note that CEO expressed his concern for the well being of people evacuated from your facility. And the press release is accompanied by a photo of the CEO — who is smiling.  Photos can have a tone, but photo metadata often doesn’t capture that. Compatibility metadata relates to any editorial aspects that indicate what items tend to work well together, or should be avoided using together. Perhaps some pull-quotes of testimonials should not be used in certain contexts: attribute metadata could indicate that.

How values are described is another aspect of metadata that can be enhanced to improve storytelling capabilities.  We tend to treat the value as a literal word that will be used everywhere. Multilingual content shows us that it is not the word describing the value that’s important, it’s what the value represents. We may call the first month of the year January, but it can be called many other things, depending on the language.  This same idea of separating values from the expression of values can be applied elsewhere.  A place can be represented by a name, geographic coordinates, or a dot on a map.  We might label an entity type on a screen using a word, an icon, or a color.  Enabling expressive fluency, where the same semantically described idea can be expressed multiple ways in different contexts, will be important to developing rich narratives using intelligent content.

Broadening Our Toolkit

Stories have structure, but that structure sometimes needs to be more flexible than used for strictly factual content to accommodate a range of expression.  Content management tools need to provide more editorial control over structure.  Cookie cutter templates make all content look the same, and dull the experience.  You can see this on Medium, where the US President’s State of the Union address looks similar to a posting by your neighbor’s college age kid.   The recent example of the Washington Post’s PageBuilder points to a possible model for giving editors more control over the structure of the content.

Narrative authors will use semantic content differently than technical communicators do. The tools need to reflect these differences.  Stories won’t be generated directly by databases. Rather, authors will use semantic content to identify appropriate content to use in different contexts. The process will change from enforced content reuse to elective reuse.  Semantic content will empower the author to find what’s available and appropriate, and create an option to include it where it can work. The goal should be to use intelligent content to empower an editor, rather than to replace an editor, to use databases to reflect curatorial decisions, rather than making those choices.

Finally, little progress will be realized until the tools for structured content become easier and more pleasant to use. That is a very big challenge given that some dimensions of content will be need to be defined in even more detail than they are today, and today’s semantic content tools are completely unacceptable to creative writers who write narrative. Again, this a solvable issue; it just hasn’t been anyone’s priority. While everyone agrees in principle that the UX of content management is ghastly, I see few people cite poor UX as a major barrier to the adoption of semantically structured content. Those who advocate using structured content for narrative, but who have largely mastered these tools already, may be unaware of, or underestimate, this chasm.

Closing Thoughts

Whether or not storytelling incorporates semantic content, and whether or not any such changes happen in the near future, the topic prompts the content strategy community to think deeply about how we approach our craft, and how it can be extended.  There is great potential, and many challenges to be solved.

— Michael Andrews