On Tue, Feb 17, 2009 at 5:50 PM, Bob Wyman <[email protected]> wrote: ...
> Unfortunately, there is no way to encode an entry that shows both the > entry's source as well as the reason why it has been included in an > aggregate feed. Doing this would require an ability to "add data" to an > entry after it is originally published. But, Atom provides no mechanisms for > adding data to entries once they are published -- except for the business > about inserting atom.source if not present. There was recently some interesting discussion on just this issue on the activity streams mailng list. It came up in the context of "bookmarking" or "favorite-ing" or "rating" someone elses activity (activities are represented by atom entries). The idea being that you include that entry but, essentially, add some metadata saying why you are including it. And that act is itself and activity, also represented by an atom entry. It's actually an interesting issue that won't go away anytime soon. It'd be nice to have some best practices established ( a pattern language for Atom anyone?) . --peter keane During the process of defining > the atom format, we discussed at length a number of alternatives that would > have permitted adding more "history" to entries but we couldn't get any > agreement on what to do. The discussions typically included ideas for > describing the "provenance" of an entry... > > Are you sure you *really* want to include a listing of the queried feeds? > What would you do if you had millions of feeds to query? > > bob wyman > > >
