Is there a standard way to declare that your Atom/RSS feed contains full articles and not just partials/summaries? I’ve noticed that the https://webfeeds.org/rss/1.0 namespace defines a webfeeds:partial element but I have never seen it used (I searched all the code forges and search engines. Not one example).

This is unrelated to feed pagination and archive feeds; I’m talking about having a way to say that each entry contains the full-text of each article.

#Atom #RSS

@Seirdy ooh. Do you have a good reference for "this is what a modern RSS feed looks like"? I'm using Perl's XML::RSS module and generating files that I'm pretty sure are crap for my blog, but.... haven't touched that code for 20 years and should definitely do better.

@danlyke A modern RSS feed is called an Atom feed. 

I try to make mine showcase “everything Atom has to offer” (except pagination and WebSub) over at https://seirdy.one/atom.xml, which validates with the W3C Feed Validator and xmllint.

@danlyke If you still wish to use RSS, I recommend consulting the RSS Best Practices Profile by @rssboard. Feel free to borrow some of the namespaces I use in my Atom feed, too. Even though I use Atom, I still found it to be a useful reference.
RSS Best Practices Profile

A set of recommendations for RSS feed publishers and developers offered by the RSS Advisory Board.

@Seirdy thanks. I think I'm happy to switch to Atom, the politics of that are long in the past. I just need to think a little bit about XML generation and use yours as a template....

@danlyke I recommend the W3C’s feed validator (hosted on their site and also available on GitHub as a maintained fork of an old project), xmllint (part of libxml), and a couple feed readers to test (Liferea and NewsBlur should be good for testing media handling). You can ignore any of the namespaces I import. You can especially ignore the OStatus, poco, and ActivityStreams namespaces in my feed; I mainly included those out of sentimental nostalgia for the classic OStatus-based pre-ActivityPub Fediverse.

Some of my posts are replies to other posts, which is why I use the threading extension. The “webfeeds” namespace is basically Open Graph metadata for feeds. “slash” comes from classic Slashdot, and annotates the number of comments (webmentions) a post has; barely any readers display that information.

The only extension that’s actually useful today in Atom feeds is the Media extension. It gives you a nice way to include featured images for entries, or to delegate a media enclosure. The latter is common for podcasts, but podcasting never made the jump to Atom; it’s still mostly RSS-only.

@danlyke If your feed gets too massive (say, over 500kb compressed), you may also wish to look into paginated/archive Atom feeds.
@Seirdy awesome! It'll be good to get a look at what's currently being done, because over the years I've thought that a reader that understands IndieWeb and things like the threading extension could replace most of what we use "social media" services for, just not enough tuits to do anything with that thought.

@Seirdy @rssboard @danlyke

Thanks for pointing to this post. I'm currently researching how to best define the source or sources for the item and to me it seems as dc:creator is the best one.

I may have a need to define more than one source - like:
One source is a distributor
Another source is the publisher