The second, and more important, reason is that AFAIK most
feed readers and aggregators wouldn't be able to render the
expanding yellowish boxes (which contain ID abstracts and
other details) anyway, because they rely on CSS and JavaScript.
Since when has anyone considered CSS and JavaScript to be
CONTENT!?!?!?
Generally, RSS and ATOM feeds are produced by software.
Software can do things like parse web pages and separate
the content from the markup and also shorten long content
items to the first 300 characters or so.
In the real world, this kind of thing is Python 101 in that
beginners who have never before used a scripting language
somehow manage to set up their own RSS and ATOM feeds.
In the real world, web site developers also do something
called "usability testing" which catches all these issues
before the site ever goes live. For example, read this:
http://www.useit.com/alertbox/20000319.html
If you would run three or four cycles of these cheap
5-user usability tests, fixing all issues before doing
the next test, then you would not have so much traffic
on the IETF complaining.
--Michael Dillon
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf