Before OpenSearch, adding a site's search to a browser or toolbar meant special handling: find the form, infer the query parameter, and hope the page did not change. Amazon's A9 team reduced the problem to a description file.

The OpenSearch 1.1 draft defines a description document, query element, URL template syntax and response metadata. The core trick is the URL template: a client substitutes search terms into the published template instead of reverse-engineering the site.

MDN documents the format as a way for browsers to add website search engines. That is why the standard worked: the site owner published intent once, and every browser or search client could discover the same interface.

Describe search as a URL template

XML autodiscovery let sites advertise search capability from ordinary pages.

The URL template covered both simple search and richer search suggestions.

Clients could ignore unknown extensions, so the format could grow without breaking old browsers.

The standard made search integration a publishing task, not a browser partnership.

A standard spreads when it makes the smallest useful contract explicit: name the endpoint, name the parameter, and let every client do the rest.

OpenSearch became the common description format for browser search plugins and site-search discovery. Its visible footprint is small, but the pattern endured: publish a machine-readable contract beside the web page so clients stop guessing.

FOLLOW THE EVIDENCE

The sources

  1. OpenSearch 1.1 Draft 6 raw.githubusercontent.com
  2. OpenSearch description format developer.mozilla.org