RSS feedSeen on the atom-syntax mailing list:
[..] Thus, you can’t say things like “Give me only the entries that have been updated since time XXXX'”. Should HTTP be extended to address better the needs of Atom? Should RFC-3229 be extended to define an ATOM specific mechanism for retrieving Atom Fragments?
Well, you could indeed, for most CMSes, create a URI that would launch a query that would retrieve a bunch of entries, or an RSS/Atom feed for them, or whatever. There might be scope for standardizing the query encoding. – Tim Bray
At the risk of sounding like a broken record, and I promise this will be my final post to include the words control, publishing and pipeline, please mark 18th May 2004 down in your diary as the day Atom started to get it.
Amongst discussions of pull vs. pull, firewalls, open ports, and other technical issues, ultimately what is important is that I am able to get access to the content that I want. At it’s most simple level, this is a pull, and in order to get all the content I want, I’m going to need filtering/querying, directories and content relationships. Do RSS or Atom currently do any of this?
See my previous posts for details on pulled feeds as information filters, big media changing to content based business models, insight into why personal control of content is inevitable, and why RSS is simply a distraction from the real game.
And on that note, I’ll leave you in peace. 🙂
(Originally posted to Synop weblog)