Closed croaky closed 4 years ago
Howdy, folks! Thoughts on this idea? Cheers.
Agreed, although I do think the Atom spec should have been followed here where all author items are lists. See feed https://tools.ietf.org/html/rfc4287#page-11 , and entry https://tools.ietf.org/html/rfc4287#page-11 .
Since author is already out in the wild, adding authors to each level as part of the spec would at least allow additional authors.
Cleaning up some old PRs. Okay to close this?
Thanks @croaky! Yes, multiple authors are in the version 1.1 draft, so I'll close this.
It is common for articles or podcasts to have multiple authors. Examples include The New York Times and The New Yorker:
https://github.com/brentsimmons/JSONFeed/issues/6
Currently, the JSON feed spec allows one
author
object on the top-level feed and one on each item:To provide an item with multiple authors, the author names could be concatenated and URLs and avatars removed:
Or, the author names could be concatenated and combined URLs and avatars provided:
Those use cases might work well when the author is a team:
This feels more awkward for use cases of blog posts / news articles with multiple authors, or podcasts with multiple hosts where the publisher wants to provide links for each author's individual identity, such as to a listing of that author's other works.
In those cases, this structure feels nice to me:
I can imagine a natural-looking feed reader experience of:
This change adds
authors
toitems
and attempts to make it clear to implementers how to handle the various present/missing states forauthor
andauthors
. Although all use cases can be covered by theauthors
array (single author items can be modeled as a one item array), it does not deprecateauthor
. I leave that decision to project maintainers.Also, this change does not add
authors
to the top-level feed. In my experience, even on publications with multiple authors per item, the top-level feedauthor
has appropriately been the publishing company or organization.