liveBook · Manning

Pluralization

As explained in API Design Patterns

Pluralization is the grammatical process of forming a word that denotes more than one instance of a noun.

Pluralization forms a noun that denotes more than one instance. API naming usually keeps resource names singular—Book, Publisher, and Author—but RESTful URLs commonly use plural collection names such as /books/1234. section 3.3.2

Regular and irregular collections

Book becomes Books by adding “s,” but Foot requires the irregular collection name feet. Person creates a choice between persons and people, so the collection convention must remain clear and unambiguous. section 3.3.2

Apply these naming rules:

  • Keep API resource names singular when they represent one resource. section 3.3.2
  • Choose collection names deliberately when ordinary pluralization produces an irregular or ambiguous result. section 3.3.2

How API Design Patterns covers it

How deep it goes
Defines the naming tension and demonstrates regular, irregular, and ambiguous plurals without prescribing a universal irregular-plural rule.
Examples
Uses Book/Books, Foot/feet, and Person/persons-or-people to expose regular, irregular, and ambiguous collection names.
What it assumes
Assumes familiarity with API resources and RESTful URLs while clarifying how singular and plural names interact.
What you can do after
Apply API naming conventions by separating singular resource names from deliberate plural collection names.
How it connects
Connects pluralization with API resources, collections, resource naming, and RESTful URLs.

This explainer was generated by Manning's knowledge graph from the text of API Design Patterns. The section links point to the parts of the book it draws on.