Construct · 3 fields · 3 citations

Where does script collide?

One name. Different field. Different construct. One map.

● jingle · one word, three constructs Nearest construct by meaningplaycompare the meanings
How to read this

Every construct on the map is compared with every other by the meaning of its definitions, and the closest one is surfaced here. The nearest construct to script is play.

Hold this as a prompt, not a verdict. Two constructs sitting close in meaning is a reason to read them side by side and decide for yourself whether they are one idea under two names. It is not proof that they are. Compare the meanings in the Collider.

script3 CONSTRUCTSCognitive scriptSCHANK · EVENT SCHEMAComputer scriptOUSTERHOUT · SCRIPT LANGWriting scriptCOULMAS · WRITING SYSTEM

Spokes are fields; dashed arcs are shared lineage. Tap a field for its definition, unit, and measures.

2026

Drag to watch the word get claimed. Each field appears at the publication date of the earliest source cited for it. Tap a year to see which.

Cognitive psychology

An event schema for a familiar routine

A stored knowledge structure for a stereotyped sequence of events in a familiar situation, such as the well known restaurant script that runs from entering to ordering to eating to paying: it lets a person fill in the expected actions and their order without being told. Schank and Abelson's 1977 Scripts, Plans, Goals, and Understanding proposed the script as a specialised kind of schema, one keyed to a routine of actions over time, and showed how it lets people understand and predict everyday episodes. The referent here is a mental structure inside a person's memory, inferred from recall and reading behaviour, not a text file of commands, a written play, or an alphabet of characters.[1]

Unit
One stored event routine, a slotted sequence for a familiar situation
Recovery means
Not applicable
Measured by
Inferred from recall and recognition errors, filled-in gaps, and reading times as people understand short stories about routine events

Computer science

A program in an interpreted scripting language

A short program written in an interpreted scripting language that automates a task or glues existing components together, such as a shell script or a Python script, rather than being compiled ahead of time into machine code. Ousterhout's 1998 Scripting: higher level programming for the 21st Century drew the contrast between scripting languages, made for gluing and quick assembly, and system programming languages built for speed and large structures. The referent is a runnable piece of software, judged by whether it executes and what it does, and it has nothing in common with a routine held in human memory, a written play, or a set of written characters.[2]

Unit
One executable text file of commands, run by an interpreter rather than compiled
Recovery means
Not applicable
Measured by
Judged by whether it runs correctly, and by lines of code, execution time, and the tasks it automates

Linguistics and writing systems

A system of characters for writing a language

A system of written characters used to record language, such as the Latin, Cyrillic, or Devanagari script: one script can serve many languages, and it is defined by its inventory of signs and the type of unit each sign stands for. Coulmas's 1999 The Blackwell Encyclopedia of Writing Systems catalogued the world's scripts and classified them as alphabets, abjads, syllabaries, and other types by how their signs map to speech. The referent is a shared inventory of graphic signs, described by its characters and their sound values, and it is not a routine in memory, a runnable program, or the written text of a single play.[3]

Unit
One inventory of written characters, shared across the languages that adopt it
Recovery means
Not applicable
Measured by
Catalogued by its inventory of signs, the type of unit each sign encodes, and the languages that use it

Next

Run it through the Collider, or take the citations with you.

See how script sits against neighbouring constructs in the Collider, or export every reference on this page in one click.

Open in ColliderExport BibTeXReport this collision

Nearby collisions

schema4 fields · 6 citationsjingle · one word, four constructsact2 fields · 2 citationsjingle · one word, two constructsalphabet2 fields · 5 citationsjingle · one word, two constructs

References

  1. Schank, R. C., & Abelson, R. P. (1977). Scripts, plans, goals, and understanding: An inquiry into human knowledge structures. Lawrence Erlbaum Associates.
  2. Ousterhout, J. K. (1998). Scripting: Higher level programming for the 21st century. Computer, 31(3), 23–30. https://doi.org/10.1109/2.660187
  3. Coulmas, F. (1999). The Blackwell encyclopedia of writing systems. Blackwell. https://doi.org/10.1002/9781118932667

Cited on this page?

Confirm your construct, or correct us.

If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.

Claim your construct