OPML for use-case development Update 
It's like writing any prose document -- why would you want to use anything but an outliner :-). Seriously though, I think it was a useful approach. Like any outline, it tended to expose the structure of what you are outlining. The only pitfall was I found myself writing pseudo code in the outline. This is undesireable because a use-case is supposed to concentrate on describing the behavior and not the implementation of the system.
AJAX based OPML editor?
I've been thinking about what it would take to implement a simple, browser based OPML editor using AJAX technology. Let me know what you think.
