Shared Glossary of Technology Services Terms Used Across Network Member Sites

The technology services sector operates through a dense vocabulary of technical, regulatory, and architectural terms that carry precise meanings across disciplines. This glossary establishes consistent definitions for terms used across the 7 member sites of this network, covering artificial intelligence, cloud computing, data science, database systems, distributed systems, operating systems, and software engineering. Alignment on terminology is foundational to cross-domain research, procurement decisions, and professional qualification assessments. For a structural overview of how these domains relate to one another, the Network Glossary provides the canonical term hierarchy used across all member properties.

Definition and scope

A shared glossary in a technology services network is a controlled vocabulary — a defined set of terms, each with a bounded meaning, that governs how concepts are described, compared, and classified across member sites. The scope of this glossary spans 7 distinct technical domains, each maintained as an independent reference authority but cross-linked through common definitional standards.

The IEEE Standards Association and the National Institute of Standards and Technology (NIST) are the two primary public sources from which foundational technology definitions are drawn. Where IEEE or NIST definitions exist for a term, those definitions take precedence over colloquial or vendor-specific usages. NIST's Computer Security Resource Center (NIST CSRC) maintains the authoritative Glossary of Key Information Security Terms (NIST IR 7298), which covers over 1,300 terms relevant to computing infrastructure, data handling, and systems architecture.

The 7 member domains covered by this glossary correspond to 3 internal verticals — infrastructure and systems (covered in the Infrastructure and Systems Vertical), data and intelligence (covered in the Data and Intelligence Vertical), and software development (covered in the Software Development Vertical). Terms that span multiple verticals are cross-classified, with each relevant member site linking back to the canonical definition held here.

How it works

The shared glossary operates as a hub-and-spoke definitional model. The hub — this site, Computer Science Authority — holds the master definition for each cross-domain term. Each spoke (member site) adopts that definition, may extend it with domain-specific elaboration, and links back to the hub entry for the foundational meaning.

The process for a term moving through the glossary follows 4 discrete phases:

1. Identification — A term is flagged as cross-domain when it appears in 2 or more member sites with material differences in definition or usage.
2. Source anchoring — A canonical definition is sourced from a named public body (IEEE, NIST, ISO/IEC, ACM, or an equivalent standards organization). If no public definition exists, a working definition is constructed and marked as network-internal pending external standardization.
3. Cross-domain mapping — The term is mapped to each member domain where it applies, noting any domain-specific constraints or expansions on meaning.
4. Publication and linking — The master entry is published here; each member site updates its usage to reference the master entry, maintaining terminological consistency across the network.

The how the domains relate page provides the structural diagram showing which member sites share definitional territory for the highest-frequency cross-domain terms, including terms such as latency, throughput, concurrency, containerization, pipeline, schema, and inference.

Common scenarios

Cross-domain term collision is the most frequent problem this glossary resolves. The term pipeline, for example, carries distinct meanings in Software Engineering Authority — a site covering the full software development lifecycle, build automation, CI/CD toolchains, and engineering process standards — versus in Data Science Authority, which addresses statistical modeling, machine learning workflows, and analytical pipeline architecture. Without a shared glossary entry, the same word describes incompatible architectural constructs.

Infrastructure terminology divergence is a second high-frequency scenario. Cloud Computing Authority — which covers cloud service models (IaaS, PaaS, SaaS), deployment architectures, and provider-agnostic cloud operations standards — and Distributed System Authority — which addresses consensus algorithms, fault tolerance, replication, and distributed coordination protocols — both use terms such as node, cluster, and replica, but with scope differences that this glossary resolves by specifying which definition applies in which deployment context.

Operating system and database layer overlap produces a third class of ambiguity. Operating Systems Authority covers kernel architecture, process scheduling, memory management, and system-level resource allocation — and uses terms like process, thread, and lock in a kernel context. Database Systems Authority — which covers relational and non-relational database design, query optimization, indexing, and transaction management — uses lock and transaction in a storage-engine context. The glossary entry for each such term specifies the layer boundary that separates the two usages.

AI and data science boundary terms form a fourth category. Artificial Intelligence Systems Authority covers machine learning model architectures, training methodologies, inference systems, and AI governance frameworks. Terms like model, feature, inference, and training appear in both AI and data science contexts; the glossary holds a master definition that distinguishes layer-specific from cross-layer usage.

Decision boundaries

The glossary applies a 3-tier classification to manage definitional authority:

The boundary between Tier A and Tier B is determined by whether the public definition is domain-specific or general-purpose. A NIST definition written for cybersecurity contexts is classified as Tier B when applied in a general computing context — the external definition is retained verbatim, and the elaboration is additive, not substitutive.

Terms that are purely domain-internal — applying only within a single member site's subject area — are not included in this shared glossary. Those terms are maintained by the respective member site. The membership criteria page specifies the threshold at which a domain-internal term qualifies as cross-domain and enters the shared glossary workflow.

The network editorial standards that govern term accuracy, citation requirements, and revision protocols are published separately and apply to all member sites equally. For broader orientation to the network's coverage structure, the site index lists all member domains and their subject boundaries. Researchers assessing coverage gaps across the 7 member domains should consult the network coverage map.

References

• NIST IR 7298 — Glossary of Key Information Security Terms
• NIST Computer Security Resource Center (CSRC)
• IEEE Standards Association
• ISO/IEC JTC 1 — Information Technology Standards
• ACM Computing Classification System
• NIST SP 800-82 Rev. 3 — Guide to OT Security