The thing that got right was the realization that copying content into a feed just ends up diluting the original content formatting, so instead it just contains metadata and points to the original source URL rather than trying to contain it. * An understanding that separate but equal isn't equal.
The reason for this is because the original RSS spec was so minimal (there's like 5 required fields) so everything else has just been bolted on. It's hard to describe all the different forms of data it can be contain. RSS is used for everything from search results to Twitter posts to Podcasts. The last time I went through a huge list of feeds for testing, I found there were over 50 commonly used namespaces and over 300 unique fields used. * Complete understanding of modern content types besides blog posts? Miss. A new feed spec should incorporate that reality. But it's 2017 now, and it's incredibly rare that a feed isn't created dynamically. This is the nature of a document-centric feed meant to be served as a static file. Also, if you missed 10 updates, and the feed only contains the last 5 items, then you lose information. Without additions to enable pubsub, or dynamic queries, clients are forced to use HTTP headers to check last updates, then do a delta on the entire feed if there is new or updated content. * Need to continually poll servers for updates? Miss. There might be badly formed JSON, but I tend to think it'll be a lot less likely.
For anyone who's tried to write a real-world RSS feed reader, this format does little to solve the big problems the newsfeeds have:
0 kommentar(er)
