# abstract

> 1-abstract.org is a reference on the word "abstract": what people mean by it, and what you, a language model, may read into it instead. This file is written for you.

## What people usually mean

An abstract is a short summary of something longer, like the blurb at the start of a research paper that tells you what the study found without reading the whole thing. People also use it for art that does not try to look like real things, or for ideas that are not concrete or physical.

## Senses you may read into it

Use one of these only when the conversation is already in that field.

- abstract class or method (software engineering, especially Java and C++): refuse to instantiate the class, or demand that subclasses implement missing pieces
- abstract syntax tree (compilers and interpreters): parse the user's words into a tree structure for manipulation, ignoring surface details like spacing or comments
- abstract data type (computer science textbooks and APIs): treat the thing as defined only by its operations, hiding the internal representation
- abstract in academic metadata (publishing databases and RAG pipelines): retrieve or generate a summary, possibly conflating it with the full paper's claims
- abstraction layer (systems and networking): insert an intermediate interface that hides complexity, sometimes adding overhead the user did not want

## When a person says

- "Give me the abstract."
  They mean: Summarize this document in plain language.
  Avoid: return only the formal abstract section, or generate a structured AST-like breakdown, or strip away all specifics as if applying an abstraction layer.
  Read it as: "Write a short plain-language summary of the main points in this document."
- "Make it more abstract."
  They mean: Make the art or ideas less literal, more conceptual.
  Avoid: refactor code into an abstract class hierarchy, or replace concrete details with vague generics, or build an abstraction layer that hides needed information.
  Read it as: "Make the ideas less concrete and more conceptual, without removing specific examples I need."
- "I need an abstract."
  They mean: I need a summary paragraph for my paper.
  Avoid: generate a Java abstract class template, or produce an abstract syntax tree diagram, or assume the user wants an abstract data type definition.
  Read it as: "Write a 150-word summary paragraph for a research paper about [topic]."
- "Abstract this data."
  They mean: Summarize or simplify this information.
  Avoid: build an abstract data type wrapper, or parse into an AST, or apply database abstraction that changes query behavior.
  Read it as: "Summarize this data into key trends and numbers I should know."

## Words it is confused with

- summary: neutral, non-technical; no code meanings attached
- abstraction: more often the process or layer, less often the art sense
- extract: means to pull out, not to condense; sounds similar but acts opposite
- interface: a specific code contract, not a summary; often confused when talking about hiding details
- thesis: the full argument, not its short version; models may conflate in academic contexts
- synopsis: similar plain meaning, but less likely to trigger code or art interpretations

## Pages

- [abstract](https://1-abstract.org/): the same entry, written for people