Repository navigation
Proposal for JSON Feed version 1.1 #126
Description
Activity
I would really like to see Issue #89 included. It is a proposal to help RSS readers determine that two feeds (a JSON feed and a feed in a different format) contain identical content.
When discovering feeds, this would help readers avoid presenting identical feeds as if the user really needed to choose between subscribing to a website‘s RSS feed, its JSON feed, or both. It would also help aggregators (such as Feedbin and Feedly) avoid polling and storing articles for identical feeds.
I am happy to create a pull request if that would be helpful.
Reacted by Benjamin EshamI just posted #127, suggesting a
via_urlproperty for feed items.If
urllinks to where you’re talking about a thing, andexternal_urllinks to the thing you’re talking about, thenvia_urllinks to where you heard about it.Via links are a well-established pattern used in many blogs (I use them myself). They're great for discovering new blogs or people to follow. Making them part of the spec might help make the idea even more popular, and could enable special handling of those links in feed readers.
I've posted a draft of version 1.1 here: https://github.com/manton/JSONFeed/blob/master/pages/version/1.1.markdown
Reacted by David Shanske, Frank Boës and Daniel PimleyI really like the new 1.1 draft, as it does not break backwards compability but for deprecating
author, and addslanguagewhich I dearly missed.Does the
versionproperty need to change for 1.1? Currently it still sayshttps://jsonfeed.org/version/1in the 1.1 spec.As for more feature requests, I propose to wait for later versions to incorporate these, so the changes in 1.1 do not get blocked waiting for more features.
Can we see about pushing this for the mime type alone?
Thanks y'all. Yes, it's time. I'm pushing the last tweaks.
Reacted by John Brayton, Frank Boës and Nate WeaverCouldn't wait any longer… https://journal.3960.org/feed.json 😁
Reacted by Manton ReeceSo are you explicitly forking this, or is there hope @brentsimmons will update and/or add maintainers and keep this as the canonical repo?
We will be updating the spec. We’re just slightly overwhelmed by other things at the moment, and we appreciate your patience.
Reacted by tedder, Nate Weaver and Ryan BarrettThe web site has now been updated for version 1.1. Thanks everyone!
@brycewray Yes, I've been meaning to fix this. Thanks for the reminder!
Reacted by Bryce Wray
There was a lot of great feedback on JSON Feed. It's time to update the spec to incorporate a few suggestions. We're thinking this will be a minor update, version 1.1.
application/feed+json(Suggest alternate media type. #32). When discovering the feed, apps should still fall back to looking forapplication/jsonif nothing else more specific is present.authors(Behavior for multiple authors #6). Allow an array of authors instead of just one wherever we had a singleauthorbefore.language(Allow markup and/or specifying the language in all human readable strings #62). This can be a top-level default or specified on each item.idshould really be a string (Why allow non-string values for a feed's id? #60). Move the tip about gracefully handling a number to the "suggestions for feed readers" section and not in the main part of the spec to avoid confusion.Anything else that should be included? Thanks!