manton
Listing of (un)official extensions
As JSON Feed offers JSON feed extensions, how about having a listing of JSON Feed Extensions as part of the official JSON feed website?
In RSS there are some extensions which are rather helpful:
Currently I found some semi-official extension for JSON Feed… but more may be out there:
- _Cast
- Micro.blog
- Possible idea for extension: Feed update frequency
- Possible idea for extension: Links to identical feeds in other formats
- Possible idea for extension: Event Calendar Items
- Possible idea for extension: GeoJSON
In this manner we could make JSON Feed as modular as RSS, while keeping the main specification lean and clean.
I've been hammering out an extension for encapsulating metadata about different post types and have implemented it on my site:
- https://cleverdevil.io/content/all/?_t=jsonfeed
For some particular post types:
- https://cleverdevil.io/content/rsvp/?_t=jsonfeed
- https://cleverdevil.io/content/locations/?_t=jsonfeed
- https://cleverdevil.io/content/photos/?_t=jsonfeed
- https://cleverdevil.io/content/statusupdates/?_t=jsonfeed
- https://cleverdevil.io/content/posts/?_t=jsonfeed
- https://cleverdevil.io/content/bookmarkedpages/?_t=jsonfeed
Open to feedback, and definitely would like to include my proposal in this list of unofficial extensions in the hope of getting adoption!
this seems related to https://github.com/brentsimmons/JSONFeed/issues/88 and i agree that having a registry of some sorts might be helpful. not sure that the current way extensibility is handled is particularly helpful, because it makes the distinction between blessed and private a hard one. one data point to keep in mind learned from a lot of painful experience with this kind of design: https://tools.ietf.org/html/rfc6648
here's is my little extension that will never gain acceptance in this modern world of SEO and data-mining, but hey contributin's contributin'
https://github.com/planeguy/jsonfeed._ephemeral_items
I created an _itunes extension that adds fields missing from JSON feed needed for iTunes RSS feeds. Also for the conversion from JSONFeed to RSS, it will map standard JSONFeed fields to the extension fields making most of them optional, the idea being that most of the redundant _itunes extension fields derivable values, with the option to override.
See https://github.com/bcomnes/jsonfeed-to-rss
Looks similar to the _cast extension.
I find the challenge with doing extensions for existing formats comes down to what can be found already present in JSONFeed (and can be used during a conversion process) and what is a necessary addition. It looks like the _cast extension did a good job of supplementing fields missing from JSONFeed that make sense in any non-vendor specific podcast feed.
EDIT: When supporting extensions from RSS, there is a logic that needs to be derived similar to https://jsonfeed.org/mappingrssandatom.
