OPML the new CSV file?
So far, as a developer, I haven’t seen anything in OPML that I can’t do with a flat text file. OPML defines a few VERY generic tags, but all of the examples that Dave provides at the spec site include very problem domain specific attributes and tags in the generic
Everything in the spec from “expansionState” to “WindowRight” should be removed. Expansion state could be moved to become an attribute of the outline element. It looks to me that everytime you add a new node, you have to change the numbering in the Expansion state. The WindowRight, bottom, etc.. is just bizzare to have in a data file. Why does the data care about how it is presented? Shouldn’t it just carry the information to me and let me decide how I want to view it? Lets say I want to scroll an OPMl list across the ticker at GMA in Times Square, how does WindowRight, etc… help me there?
I don’t know if I’d call the OPML format “crappy” anymore than I’d call CSV or a tab-delimited file “crappy”. It’s just too generic to really be of any use and I’m afraid too much of Daves ego is tied up in it to allow much change. I could be wrong there.



Pingback: Lazycoder » 2005 » October » 01