The way from OPML, through RSS to atom
I seems have more than one objective. I’m not really sure that OPML is what I’m now looking for. The new thing for me is obvious RSS Syndication as found in bloglines.com. The point that triggered me was above all its UI and its ability to show unread posts.
The OPML thing is bound to the account tree, which for me is more or less a thing of the past. As of Summa Summarium GXXI we have decided to have accounts without trees, but have various report trees.
So some of my questions were maybe in vain. What I really want is the syndication functionality, and then some possible link to OPML for the report trees. So Jeremy Bowers’s suggestion to use a link to the OPML part and have the main thing in RSS 2.0 seems pretty sane.
- has as a minimum title, description and link. Both have also categories. The question is whether use each channel as a ledger or an account. And use one directory (OPML) as a ledger.
The benefit of having channels as accounts are that roles could be could be assigned to accounts. In a GL for instance, it is possible to imagine a salesperson could see payments, but have no access to payroll accounts.
I have to think on storage, browsing, entering data, analyzing and confirmation.
My idea is to use:
- OMG GL entry as format
- database or XML file for the ledger
- produce RSS feeds for all new transactions
How to test ideas:
- recreate XML to RSS 2.0 format
- read XML in bloglines.com
- make test with channel = ledger and channel = account
- understand the difference between atom and RSS and OPML
- create RSS feeds from XML with XSLT
- add data to a large XML file