This link has been bookmarked by 1 people and liked by 1 people. It was first bookmarked on 01 Nov 2009, by Graham Perrin.
-
01 Nov 09
-
aggregated Content distribution
-
the client model for processing a single vs.
aggregated distribution might be quite a bit different -
nervous about the whole notion of PuSH co-opting <source> for
its own purposes -
provenance
-
when you copy an entry from any feed document
other than that feed document whose metadata is in the entry's atom:source -
no way to indicate from which feed document you copied the entry
unless you insert some extension element -
it *is* important to know not only the source feed
but *also* where you found the entry -
Atom spec
didn't envision this use case -
atom:source is almost, but not quite,
what's needed -
confusion is understandable
-
something like a psh:provenance element
-
like atom:source
-
most recent context
-
not aggregate at the PubSubHubbub level
until you've proved that -
(a) you have to
-
(b) multipart/related
won't cut it -
the PSHB use case *was* frequently discussed in the Atom WG
-
pretty much what FeedMesh
was intended to provide -
to show provenence, you need to add an extension element
-
war stories about
multipart/related and batching -
skeptical
about ease of subscriber implementation -
This thread is a great example of peer review
-
Add Sticky NoteI'll file an issue in
the bug tracker
-
Public Stiky Notes
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.