What a Clip RSS item contains

A dependable item has a stable GUID, human-readable title, canonical page, publication date, summary, primary media enclosure, duration, thumbnail, language, and source reference. Advanced fields can add in and out points, transcript excerpts, caption assets, alternate aspect ratios, review status, and rights scope.

The design remains compatible with ordinary RSS by placing essential identity and media in standard elements. Namespaced extensions can carry richer clip metadata for editing systems, agents, social publishers, and archives. Consumers that ignore extensions still receive a useful feed item.

Three delivery patterns

A rendered-asset feed publishes a finished media file. A segment-reference feed points to a longer source plus edit boundaries. A hybrid feed provides both. Public distribution usually benefits from a rendered primary asset, while source timecodes preserve provenance and make future correction or reformatting possible.

Choose one primary asset and label alternates by role, dimensions, language, and creative version. A vertical social render and a landscape web master can belong to the same editorial clip without becoming unrelated feed entries.

From candidate to approved item

A clip should move through explicit states: detected, selected, edited, reviewed, approved, published, restricted, or withdrawn. Automated systems can propose moments and metadata, but publication should occur only after the required editorial and rights checks.

The feed becomes the handoff between the editing environment and downstream destinations. It can drive a website card, newsletter block, social export, archive, or internal agent while preserving one source of truth.

Minimal schema checklist

Require a stable clip ID, title, description, link, publication date, enclosure URL, byte length, MIME type, duration, thumbnail, source ID, source in and out points, transcript excerpt, language, rights state, and publication status. Document units and revision rules.

Validate the XML and the transport. Fetch every asset, inspect response headers, compare file size, test seeking, and confirm that a metadata correction updates an existing item instead of creating a duplicate.

Example item structure

<item>
  <title>Key moment from the source program</title>
  <link>https://cliprss.com/clips/example/</link>
  <guid isPermaLink="false">cliprss:clip:cr-0241</guid>
  <pubDate>Tue, 20 Oct 2026 17:00:00 GMT</pubDate>
  <description>A reviewed summary of the selected moment.</description>
  <enclosure url="https://cliprss.com/media/cr-0241.mp4"
             length="18420322" type="video/mp4" />
  <media:thumbnail url="https://cliprss.com/media/cr-0241.png" />
  <clip:sourceId>program-2026-10-20</clip:sourceId>
  <clip:inPointMs>724000</clip:inPointMs>
  <clip:outPointMs>768000</clip:outPointMs>
  <clip:status>approved</clip:status>
</item>