{"canonical_url":"https://engineer.company/glossary/rss/","content_markdown":"# RSS\n\n## What it is\n\nRSS is an XML format for publishing a feed: one `channel` element that describes\na site and holds a list of `item` elements, each a post with a link, a date and\nsome text, at an address that feed readers fetch on a schedule. Its\nspecification spells the name out as Really Simple Syndication, many people say\n“RSS feed” for a feed in any format, and RSS 1.0, “RDF Site Summary”, is a\nseparate format built on RDF rather than an earlier version of the one in use\ntoday.\n\nThe format began at Netscape, which published RSS 0.90 in March 1999 and 0.91\nthat July. UserLand published its own 0.91 in June 2000, then 0.92 and, in\nAugust 2002, RSS 2.0. The Berkman Klein Center at Harvard Law School published\n2.0.1, written by Dave Winer, in July 2003, and the RSS Advisory Board has kept\nthe text since, under a Creative Commons licence. Its roadmap says the format\nis, for all practical purposes, frozen at 2.0.1. The board has published\nrevisions of the document since, the current one in March 2009, but new needs\nare met by extensions in their own XML namespaces rather than by new versions of\nRSS.\n\nA document is small. Its root is an `rss` element whose `version` attribute must\nbe `2.0`, holding a single `channel`. The channel needs a `title`, a `link` and\na `description`. Every element of an item is optional, as long as the item has\nat least a title or a description. Everything else, from `pubDate` and `guid` to\nthe channel’s `image` and `ttl`, is there when a publisher wants it:\n\n```xml\n\u003c?xml version=\"1.0\" encoding=\"UTF-8\"?\u003e\n\u003crss version=\"2.0\"\u003e\n  \u003cchannel\u003e\n    \u003ctitle\u003eExample Notes\u003c/title\u003e\n    \u003clink\u003ehttps://example.com/\u003c/link\u003e\n    \u003cdescription\u003eShort notes on running servers.\u003c/description\u003e\n    \u003citem\u003e\n      \u003ctitle\u003eMoving the database\u003c/title\u003e\n      \u003clink\u003ehttps://example.com/notes/db-move/\u003c/link\u003e\n      \u003cguid isPermaLink=\"true\"\u003ehttps://example.com/notes/db-move/\u003c/guid\u003e\n      \u003cpubDate\u003eSat, 17 Oct 2026 09:00:00 GMT\u003c/pubDate\u003e\n      \u003cdescription\u003eWhy the move took one evening.\u003c/description\u003e\n    \u003c/item\u003e\n  \u003c/channel\u003e\n\u003c/rss\u003e\n```\n\n## Why it matters\n\nRSS is loose, and the looseness is what a publisher has to understand. An item’s\n`description` may hold plain text or HTML escaped into the element, and nothing\nin the file says which, so the reader decides. The `guid` is optional, so\nwithout one a reader works out by itself whether an item is new. Dates follow\nRFC 822, an email standard from 1982, as strings such as\n`Sat, 17 Oct 2026 09:00:00 GMT` with English day and month names, and the\nspecification still allows a two-digit year. And the format has no way to\ndeclare a base URL, so a relative link inside an item has nothing reliable to be\nresolved against.\n\nThe board’s answer is the RSS Best Practices Profile, published in October 2007:\nrecommendations for documents that work across the wide range of software that\nreads them. It asks for a `guid` on every item and for absolute URLs in links\nand descriptions. It reports that the only date forms every aggregator it tested\nhandled were in Universal Time, ending in `GMT`, `+0000` or `-0000`. It also\ndocuments an `atom:link` with `rel=\"self\"` that names the feed’s own address. A\nfeed written to the profile leaves its readers far less to guess.\n\nTwo extensions carry most of what a modern feed adds. `atom:link` borrows that\nelement from Atom. `content:encoded`, from a module first written for RSS 1.0,\nholds an item’s full HTML. The profile describes using both together, the full\ntext in `content:encoded` and a shorter summary in `description`, and found\nthat, when an item carried both, six of the eight aggregators it tested\ndisplayed `content:encoded` and ignored the summary. The `enclosure` element\nattaches a media file to an item with three required attributes, its `url`, its\n`length` in bytes and its MIME `type`.\n\nFrozen is also a strength. A format that has not changed since 2003 is a fixed\ntarget, and a feed written to it today is read by software written against the\nsame text years ago. Atom closes most of the gaps above by specification, so the\ncase for publishing RSS as well is about readers rather than rigour: some take\nonly RSS, and an RSS address handed out years ago is still being polled.\n\n## What it looks like in practice\n\nThis site publishes RSS 2.0 at `/index.xml`, next to an Atom feed and a JSON\nFeed. The [credits page explains why there are two XML feeds](/credits/): all\nthree carry the full text, and there are two XML feeds rather than one because\nsome readers take only one of the two and neither is reliably the one. The same\npage links the RSS feed to the\n[W3C Feed Validator](https://validator.w3.org/feed/), beside the Atom feed, so\nthat anyone can run the check without taking the site’s word for anything.\n\nThe [page about reading the site from a terminal](/cli/) treats the feeds as\ndata. It says the portfolio is syndicated in three formats, each carrying the\nfull text of every item rather than a teaser, and fetches the RSS one with\nnothing more than `curl`:\n\n```sh\ncurl -s https://engineer.company/index.xml\n```\n\n## Where it goes wrong\n\n**The channel’s picture is missing, and the validator objects.** A reader shows\nno image beside the feed’s name, and the W3C service warns about the image\nformat. RSS’s `image` element is the strictest picture element of the three feed\nformats: GIF, JPEG or PNG only, at most 144 pixels wide and 400 high. A social\nshare card in WebP is the wrong file for it. This site’s RSS template points\n`image` at its 144-pixel PNG icon instead, and the comment beside it records\nthat the WebP card had drawn an `ImageUrlFormat` warning, caught by validating\nagain after the change.\n\n**Items sort in the wrong order, and nothing reports it.** A reader lists new\nitems below old ones, or shows them with the wrong date. RSS dates are strings,\nso an ISO 8601 date, a misspelt layout or a day name in another language still\nmakes well-formed XML, and only the reader’s date parser notices. In Hugo, a\ntemplate’s `Format` method on a date writes English names, while the\n`time.Format` function localises them; a Danish `pubDate` is not an RFC 822\ndate. This site formats each `pubDate` with the method, from a layout kept in\none partial template together with Atom’s, and the comment there says a typo in\neither is not a build failure but a feed that parses and sorts wrongly in\nsomebody else’s reader.\n\n**Icons in a post draw nothing, and the validator lists errors.** The full text\nin `content:encoded` leaves its page, so anything that depends on the page goes\nmissing. An SVG icon that points into a sprite defined elsewhere on the page\ndraws nothing in a reader, and the W3C service flags the `svg` itself. This\nsite’s feeds get their headings without the brand’s cog divider for that reason;\nthe comment on that template records that the validator had reported twelve\n`Non-html tag: svg` messages and six complaints about a `role` attribute.\n\n**Links inside a post go nowhere.** A subscriber follows a link in an item and\nlands on a missing page, or on nothing at all. A root-relative link such as\n`/notes/` works on the web page because the browser knows the page’s address,\nbut an RSS document cannot declare a base URL. The profile says a description\nshould not contain relative URLs and that an aggregator may try to resolve one\nagainst the channel’s `link`; a reader that does not try leaves the link broken.\nWrite every link in a feed’s HTML as an absolute URL.\n\n**Two categories with the same word look like one.** An item tagged in two\nvocabularies shows a term twice, or a reader merges two terms that mean\ndifferent things. RSS’s `category` element takes an optional `domain` attribute\nthat names the vocabulary a term comes from. This site’s RSS template writes it\non every category, because, as its comment says, without the domain the two\nvocabularies’ overlapping terms would read as duplicates.\n\n## Further reading\n\n- [RSS 2.0 Specification](https://www.rssboard.org/rss-specification) — the RSS\n  Advisory Board’s text of the format, element by element, with the roadmap that\n  declares it frozen.\n- [RSS Best Practices Profile](https://www.rssboard.org/rss-profile) — the\n  board’s recommendations, with what it found when it tested real aggregators.\n- [RSS History](https://www.rssboard.org/rss-history) — every version from\n  Netscape’s 0.90 to the current text, with dates and publishers.\n- [RDF Site Summary (RSS) 1.0](https://web.resource.org/rss/1.0/spec) — the\n  separate RDF-based format that shares the name.\n- [RFC 822](https://www.rfc-editor.org/rfc/rfc822) — the 1982 email standard\n  whose date and time syntax RSS still uses.\n\n\u003chttps://engineer.company/glossary/rss/\u003e\n","date_modified":"2026-10-18T22:40:12Z","description":"What an RSS 2.0 file holds, why a frozen and loosely specified format still earns a place beside Atom, and the details that trip readers up.","formats":{"gemtext":"https://engineer.company/glossary/rss/index.gmi","gopher":"https://engineer.company/glossary/rss/gophermap","html":"https://engineer.company/glossary/rss/","json":"https://engineer.company/glossary/rss/index.json","markdown":"https://engineer.company/glossary/rss/index.md","pdf":"https://engineer.company/glossary/rss/index.pdf"},"kind":"page","language":"en","title":"What is RSS?","url":"https://engineer.company/glossary/rss/","version":1}