Repository navigation
Conversation
It is common for articles or podcasts to have multiple authors. Examples include The New York Times and The New Yorker: #6 Currently, the JSON feed spec allows one `author` object on the top-level feed and one on each item: ```json author: { name: "Alice", url: "https://example.org/alice", avatar: "https://example.org/alice.png", } ``` To provide an item with multiple authors, the author names could be concatenated and URLs and avatars removed: ```json author: { name: "Alice and Bob", } Or, the author names could be concatenated and combined URLs and avatars provided: ```json author: { name: "Alice and Bob", url: "https://example.org/alice-and-bob", avatar: "https://example.org/alice-and-bob.png", } ``` Those use cases might work well when the author is a team: ```json author: { name: "Engineering Team", url: "https://example.org/team/engineering", avatar: "https://example.org/team/engineering.png", } ``` 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: ```json authors: [ { name: "Alice", url: "https://example.org/alice", }, { name: "Bob", url: "https://example.org/bob", } ] ``` I can imagine a natural-looking feed reader experience of: ``` Article Title by Alice and Bob May 6, 2018 ``` This change adds `authors` to `items` and attempts to make it clear to implementers how to handle the various present/missing states for `author` and `authors`. Although all use cases can be covered by the `authors` array (single author items can be modeled as a one item array), it does not deprecate `author`. 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 feed `author` has appropriately been the publishing company or organization.
Author
|
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. |
Author
|
Cleaning up some old PRs. Okay to close this? |
Owner
|
Thanks @croaky! Yes, multiple authors are in the version 1.1 draft, so I'll close this. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It is common for articles or podcasts to have multiple authors.
Examples include The New York Times and The New Yorker:
#6
Currently, the JSON feed spec allows one
authorobjecton 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
authorstoitemsand attempts to make it clearto implementers how to handle the various present/missing states
for
authorandauthors. Although all use cases can be covered by theauthorsarray (single author items can be modeled as a one item array),it does not deprecate
author. I leave that decision to project maintainers.Also, this change does not add
authorsto the top-level feed.In my experience, even on publications with multiple authors per item,
the top-level feed
authorhas appropriately been the publishingcompany or organization.