You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I work on Media Feeds which is a different standard for JSON based feeds although we are solely focused on the video use case. One point of feedback was our incompatibility with JSON feeds and looking at your spec it looks like even with extensions we cannot support complex image types: WICG/media-feeds#29
As the JSON feeds community I wanted to invite you to give comment (if you would like).
The text was updated successfully, but these errors were encountered:
Thanks for reaching out @beccahughes. I don't think another feed format is needed. Although the focus with Media Feeds is a little different, building off of JSON Feed (or RSS for that matter) seems preferable. Especially for media, RSS is used everywhere for podcasts already.
We didn't propose a new feed format lightly because of the risk of fragmentation if there are too many different formats, but now that JSON Feed and other feed formats are here and widely adopted, I think there is a very high bar to meet to introduce another format.
As for adding more complex image types, JSON Feed extensions could help with this. If an extension is adopted by multiple providers, it would be a good candidate to roll into an updated version of the spec. You could say that the _media field naming is a little clunky, but I'd argue that it's actually much cleaner than some of the Media Feeds required fields like @context and @type.
Hi there,
I work on Media Feeds which is a different standard for JSON based feeds although we are solely focused on the video use case. One point of feedback was our incompatibility with JSON feeds and looking at your spec it looks like even with extensions we cannot support complex image types: WICG/media-feeds#29
As the JSON feeds community I wanted to invite you to give comment (if you would like).
The text was updated successfully, but these errors were encountered: