How to reduce feed size? (aka SSFF)

Atom <atom-syntax@imc.org>

(alternate formats: Notation3, PNG graph, OPML, SVG graph, RDF, QuestMap)

How to reduce feed size?    q1

[Reduce] <feed> format [...] to a list of URIs pointing to <entry>    (orig) i1

+1 +1 +0.5 +1    a11

only bandwidth increase is the HTTP headers in subsequent GETs of the individual entries.    (orig) a3

[entry content is only ever retrieved once each change]    (orig) a4

Removal of an entry can be implicitly handled by a 410 Gone    (orig) a5

number of places that an <entry> document is available is reduced to one    (orig) a6

This is something different than RSS-all-over-again.    (orig) a7

[should have 'some' minimal metadata]    (orig) i2

feedreaders must always look in two places to look for all of the information    (orig) a15

metadata contained in the entry construct [is] advisory (the real metadata is in the entry).    (orig) a16

+1 +1 +1 +1    a12

SOAP bindings [...] have to reauthenticate for every entry    (orig) a2

How would that be different than re-authenticating with HTTP?    (orig) a8

[feeds (entries) can have full content again]    (orig) a10

Support both inline and content by reference    (orig) i4

+1    a13

use feed flag to indicate content-by-reference    (orig) i5

use different top-level element to indicate content-by-reference    (orig) i6

only sends down the last n items newer than the If-Modified-Since date sent by the client    (orig) i3

violates the HTTP spec    (orig) a9

requires a 'live' server    (orig) a14