GlossaryFragment

Part of the WebMEM® Protocol
Fragment Class: GlossaryFragment
Location: /protocol/fragments/glossaryfragment/
Status: Current Draft
Last Updated: 2026-08-24

Overview

A GlossaryFragment is a WebMEM fragment class for publishing a structured glossary or collection of defined terms within a specified semantic context.

Each GlossaryFragment establishes the glossary itself, the domain or namespace within which its terminology applies, and the defined terms that belong to that glossary.

Unlike a DefinedTermFragment, which represents the canonical meaning of an individual term, a GlossaryFragment represents the organized semantic collection to which defined terms belong.

This allows publishers to expose domain-specific vocabularies explicitly and to connect terminology used throughout an SDT to a consistent semantic context.

Semantic Purpose

The semantic purpose of a GlossaryFragment is to state:

Within this defined semantic context, these are the terms that belong to this glossary or vocabulary and the relationships necessary to interpret that terminology consistently.

A GlossaryFragment may establish:

the identity of the glossary;
the name and description of the glossary;
the domain, namespace, vocabulary, or semantic scope within which it applies;
the defined terms belonging to the glossary;
relationships among those terms;
relationships to other glossaries or vocabularies;
the publisher or authority responsible for the glossary;
and provenance supporting the glossary and its terminology.

The GlossaryFragment provides a shared semantic context that other WebMEM knowledge objects may reference when their interpretation depends on domain-specific terminology.

GlossaryFragment Within an SDT

A GlossaryFragment exists as one modular knowledge object within a Semantic Data Template (SDT).

The relationship is:

Web Resource → SDT → GlossaryFragment → Defined Terms

An SDT may contain one GlossaryFragment or multiple GlossaryFragments when the resource uses terminology from different domains, authorities, namespaces, or vocabularies.

A GlossaryFragment may identify the terms belonging to its semantic collection directly or reference individual DefinedTermFragment objects that publish the canonical definitions of those terms.

This allows the glossary and its individual terms to remain independently identifiable while participating in the same semantic structure.

GlossaryFragment Requirements

A conforming GlossaryFragment should establish enough information to identify the glossary, understand its semantic scope, and determine which terms belong to it.

Element	Purpose
Fragment Class	Identifies the knowledge object as a `GlossaryFragment`.
Fragment ID	Provides a stable identifier for the GlossaryFragment within the published knowledge structure.
Glossary ID	Provides a stable identity for the glossary or vocabulary represented by the fragment.
Glossary Name	Provides the human-readable name of the glossary.
Semantic Scope	Identifies the domain, namespace, vocabulary, organization, or other context within which the glossary applies.
Terms	Identifies the defined terms belonging to the glossary.
Provenance	Identifies or references the source, publisher, authority, and lineage supporting the glossary.

Descriptions, term relationships, related vocabularies, version information, and other semantic metadata may be included when appropriate.

Glossary Identity

A glossary should have a stable identity that is distinct from the identity of the GlossaryFragment publishing it.

For example:

Fragment ID: identifies a particular GlossaryFragment within an SDT.
Glossary ID: identifies the semantic collection represented by that fragment.

A glossary identity might take a form such as:

glossary:webmem-core

Individual defined terms may then use stable term identifiers within or associated with that glossary.

This allows the glossary and its terms to remain identifiable across multiple resources and SDTs without depending on a particular publication instance.

Semantic Scope

The semantic scope of a GlossaryFragment establishes the context within which its terminology is intended to be interpreted.

That scope may represent:

a technical protocol;
an industry;
a regulatory domain;
a public program;
an organization;
a dataset vocabulary;
a legal or policy vocabulary;
or another defined semantic domain.

Explicit semantic scope is particularly useful when the same word may carry different meanings in different domains.

For example, a term such as resolution may have a specific meaning within the WebMEM Protocol that differs from its meaning in another technical or general-language context.

Glossary Terms

A GlossaryFragment identifies the terms belonging to a glossary or vocabulary.

Each term should have a stable identity when practical.

A glossary entry may identify:

the term ID;
the human-readable term name;
a reference to the corresponding DefinedTermFragment;
relationships to other terms;
and other information necessary to place the term within the glossary.

The GlossaryFragment does not need to duplicate the complete canonical definition of every term when those definitions are represented by separate DefinedTermFragments.

Example GlossaryFragment

The following example represents a WebMEM core glossary using the current WebMEM HTML serialization.

<template
  data-webmem-fragment
  data-fragment-class="GlossaryFragment"
  data-fragment-id="glossary-webmem-core">

  <section
    data-entity-type="Glossary"
    data-entity-id="glossary:webmem-core"
    data-semantic-scope="webmem"
    data-provenance-ref="#provenance-webmem-protocol">

    <h3 data-role="glossary-name">
      WebMEM Core Vocabulary
    </h3>

    <p data-role="description">
      Defined terms used by the WebMEM Protocol to describe
      publisher-side machine knowledge and resolution.
    </p>

    <ul data-role="terms">

      <li
        data-term-id="webmem:sdt">
        <a
          data-role="defined-term-ref"
          href="#defined-term-sdt">
          Semantic Data Template
        </a>
      </li>

      <li
        data-term-id="webmem:fragment">
        <a
          data-role="defined-term-ref"
          href="#defined-term-fragment">
          WebMEM Fragment
        </a>
      </li>

      <li
        data-term-id="webmem:machine_fact_object">
        <a
          data-role="defined-term-ref"
          href="#defined-term-machine-fact-object">
          Machine Fact Object
        </a>
      </li>

      <li
        data-term-id="webmem:resolution">
        <a
          data-role="defined-term-ref"
          href="#defined-term-resolution">
          Machine Resolution
        </a>
      </li>

    </ul>

  </section>

</template>

The fragment establishes that:

the knowledge object is a GlossaryFragment;
the glossary has a stable identity;
the glossary belongs to the WebMEM semantic scope;
the glossary has a human-readable name and description;
the terms belonging to the glossary are explicitly identified;
the terms can reference their individual DefinedTermFragments;
and provenance supporting the glossary can be resolved through the referenced provenance object.

GlossaryFragment and DefinedTermFragment

GlossaryFragment and DefinedTermFragment serve complementary but distinct semantic purposes.

DefinedTermFragment	GlossaryFragment
Represents an individual defined term.	Represents a structured glossary or vocabulary containing multiple terms.
Establishes the identity and canonical meaning of one term.	Establishes the identity, scope, and membership of a semantic collection.
Answers: What does this term mean?	Answers: What terms belong to this glossary or semantic context?
May identify relationships to related terms.	May organize and relate multiple defined terms.

A GlossaryFragment may therefore reference multiple DefinedTermFragments without duplicating their complete definitions.

Term Relationships

A GlossaryFragment may express relationships among the terms it contains.

Examples may include:

broader and narrower concepts;
related terms;
preferred and alternate terminology;
historical terminology;
prerequisite concepts;
equivalent terms when equivalence is explicitly established;
or other relationships defined by the publisher.

Relationships should use stable term identities where available.

The existence of a relationship should not imply equivalence unless equivalence is explicitly represented.

Cross-Fragment Semantic Alignment

A GlossaryFragment can provide shared terminology for other WebMEM fragment classes within an SDT.

For example:

a DataFragment may use a defined term to establish the meaning of a factual field;
an EligibilityFragment may reference defined terms used in qualification criteria;
a PolicyFragment may reference terms whose meaning is established by regulation or policy;
a ProcedureFragment may reference terms used in procedural steps;
an ExplainerFragment may reference terms required to understand its subject;
and an FAQFragment may reference terminology appearing in a question or answer.

The glossary provides the shared semantic context. The individual fragments retain their own distinct semantic purposes.

Multiple Glossaries

An SDT may contain or reference multiple GlossaryFragments when its knowledge spans more than one semantic domain.

For example, a healthcare resource might use:

a Medicare terminology glossary;
a pharmaceutical terminology glossary;
a geographic vocabulary;
and publisher-defined WebMEM terminology.

Terms should remain associated with the appropriate glossary or semantic scope so that similarly named terms from different vocabularies are not treated as equivalent without an explicit relationship.

GlossaryFragment and Identity

A glossary and the terms within it are identifiable semantic objects.

Stable identities allow:

the glossary to be referenced by multiple fragments or SDTs;
individual terms to be referenced without repeating their definitions;
relationships to be expressed across glossaries;
and machines to distinguish between terms with similar labels but different semantic meanings.

Glossary identity, term identity, and fragment identity should remain distinct where those distinctions are necessary to preserve the knowledge model.

Read the Identity specification →

GlossaryFragment and Relationships

A GlossaryFragment may participate in relationships with other WebMEM knowledge objects.

For example, a GlossaryFragment may relate to:

DefinedTermFragments belonging to the glossary;
another GlossaryFragment representing a related vocabulary;
DataFragments using terminology from the glossary;
PolicyFragments using authoritative domain terminology;
EligibilityFragments using defined qualification terms;
ProcedureFragments using defined procedural terminology;
ExplainerFragments providing deeper explanation of glossary concepts;
or other WebMEM fragments whose interpretation depends on the glossary.

Explicit relationships allow terminology to remain connected to the knowledge objects that use it without requiring definitions to be duplicated throughout the SDT.

Read the Relationships specification →

GlossaryFragment and Resolution

A GlossaryFragment can participate in machine resolution by connecting a semantic domain or vocabulary to the individual terms and definitions belonging to it.

A resolution path may take the form:

Glossary → GlossaryFragment → Term ID → DefinedTermFragment → Canonical Definition

or:

Machine Fact Object → Term ID → GlossaryFragment → DefinedTermFragment → Definition

or:

Domain → GlossaryFragment → Related Terms → Related Knowledge Objects

This allows machines to move from terminology encountered within publisher knowledge toward explicit publisher-defined semantic meaning.

The GlossaryFragment publishes the semantic collection. It does not require a consuming system to adopt the glossary or treat its terminology as universally authoritative outside the declared scope.

Read the WebMEM Resolution Model →

Provenance

A GlossaryFragment should preserve the provenance and authority associated with the glossary it publishes.

Provenance may identify:

the person, organization, standards body, agency, or other authority responsible for the glossary;
the source vocabulary, publication, standard, regulation, or documentation from which terminology originates;
the canonical source location;
publication or revision dates;
retrieval or access dates;
version information;
license or reuse terms;
semantic or jurisdictional scope;
editorial or usage guidelines;
and other lineage information necessary to establish the origin and intended scope of the glossary.

When individual terms originate from different authorities or sources, the provenance model should preserve those distinctions rather than implying that every term has the same evidentiary origin.

Read the Provenance specification →

Conformance

A conforming GlossaryFragment must:

identify itself as a GlossaryFragment;
have an identifiable fragment scope;
provide a stable identity for the glossary or vocabulary;
provide a human-readable name or equivalent identifying label;
identify the semantic scope within which the glossary applies when that scope is necessary for interpretation;
identify one or more terms belonging to the glossary;
provide stable term identities when practical;
identify or reference provenance supporting the glossary;
preserve relationships to individual term definitions when those definitions are represented separately;
and conform to the applicable WebMEM serialization requirements.

Term relationships, related vocabularies, descriptions, and other semantic metadata are optional unless required by an applicable domain or conformance profile.

Relationship to WebMEM 1.x

The GlossaryFragment class originated in the WebMEM 1.x Semantic Data Template specification and remains a defined fragment class in the current WebMEM Protocol.

Earlier specifications described GlossaryFragment primarily as a machine-ingestible defined-term structure and associated it with retrieval hints, memory anchoring, glossary conditioning, trust scoring, semantic digests, and federated glossary behavior.