> However, if enabling automatic processing (such as letting people write > scripts to pull the feed and print all of the entries as a kind of > personal newspaper, or whatever) is a consideration,
Yes, that's the main goal. > As for atom:content, what do you *currently* have in there? In general, > content published in feeds should avoid any sort of chrome anyway – > since the content gets rendered in a big variety of display contexts, it > will be more widely useful the more purely semantical and > non-presentational it is. So depending on circumstances the answer to > your question may really be to simply stick the printer-friendly content > in atom:content and not worry about including special link. Yes, this is what we're thinking is the best approach, beucase it jives with what appears to be the original intent of atom:content Thank you all for your help. Yours, John
