this sounds very interesting. is there a guideline how: * rss readers in general handle additional meta dat * which metadata is allowed/specified in rss readers * how items which get removed from the fieed are handled i.e. you look at a query with "my open items" and somebody else closes one of the tickets
many thanks, -solo. On 4/22/07, Robert Chin <[EMAIL PROTECTED]> wrote: > > Hello, > > I'm the author of an RSS reader that runs on OS X, and is designed > specifically for use with Trac. As such, I would like to propose a > Trac RSS module + namespace specification, so that we can provide > additional useful data in the timeline rss feed. > > 1. userid element > A tag that shows the userid of the user. The userid and the e-mail > address are often very different. At least on our system, the userid > is the same as the svn commit userid, which makes a specific user id > field a lot more useful. > 2. changeset element > A changeset element is optional, but usually contains file elements > 3. file element > A file element must be contained within a changeset element, and a > changeset element can contain multiple file elements. Each of these > file elements must contain one path element, one description element > and optionally a link element > 4. path element > A path element must be contained within a file element. It contains > the path that trac reports on the Changeset html page. > 5. description element > The description element that is a child of the file element contains > the path along with the number of diffs -- something like, "branches/ > 0.10-stable/trac/versioncontrol/cache.py (2 diffs)" > 6. link element > The link element contains a link back to the file with the specific > revision number of the file element (so, the trac file page for a > specific revision of the file). > > This would allow for a lot more useful information to be displayed in > the rss feed, for readers that are built to support this additional > metadata. Anyway, I am asking for comments on this proposed > specification, since I would like to implement the necessary changes > in Trac to provide this additional information. > > Thanks, > > Robert Chin > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
