FeedSummary.com Summary prompts

JSON syndication

JSON Feed Summary

Use JSON Feed as a clean developer-facing input while preserving content choices, timestamps, authors, attachments, and source provenance.

JSON Feed 1.1content_htmlcontent_textauthorsattachments

Developer-friendly feed

JSON Feed maps cleanly to application records

Its fields are familiar, but downstream quality still depends on identity, content coverage, and source behavior.

Direct parsing

Items, authors, tags, attachments, and dates arrive as JSON values and arrays.

Text + HTML

Preserve both content representations and choose the richer safe value explicitly.

Required item IDs

Use the source ID with canonical URLs and hashes to track moves and revisions.

Example record

A safe item mapping

Do not let convenient syntax hide missing or inconsistent publisher data.

normalized-item.json
{
  "source_format": "json_feed",
  "source_item_id": "post-448",
  "canonical_url": "https://…",
  "published_at": "2026-10-14T09:00:00Z",
  "content_selected": "content_html",
  "authors": ["…"],
  "attachments": []
}

Source selection

When multiple feed formats exist

Test the actual payloads instead of applying a global preference.

Evaluate completeness

Compare full text, dates, authors, tags, attachments, and update behavior across the publisher’s RSS, Atom, and JSON variants.

The newest format is not automatically the best maintained.

Preserve compatibility

Support the source’s most reliable feed and keep parser behavior format-neutral downstream.

Record the advertised media type, response media type, and detected format when they differ.

Feed Signals

Format comparison

A full comparison of JSON Feed, RSS, and Atom for summary pipelines.