short vs long term goals

The web access has gotten to be a nice wiki. Future intentions are grand and glorious, but I'm thinking that it would benifit tremendously from a bit of cleanup, even at the risk of sub-optimizing from the perspective of those long term goals.

Case in point: pages & data sets?

Why have both? OK, yes, there are likely some long-term reasons. But for right now, a dataset does everything a page does, and more. So lets drop the pages for now. Datasets can be used as pages, so why not use datasets for everything? (The Data dataset being a minor exception here, as it is not the same kind of dataset as all the rest.)

So the crpage and crds commands become just cr, for now. And while I'm at it, chtnm should just be chnm.

So the short term goal is to make Web into a nice wiki, and nothing more than a nice wiki (with a built-in time machine, structural context, qualified references, et all). OK, it should be a really super wiki. But its a really short term goal, and mostly to do with documentation. (I.E. I'm likely not going to add extended formatting for now.)

Then I need to focus for a while on .dmp files. If the CompStrm Web is to be a great wiki, then we gotta get out of Alpha! And more than .dmp files in the narrow sense, I want to fix things so sharing works well. (Gosh, it would be nice to browse someone's wiki and download a .dmp file of a selected dataset. ;-)

After that, the focus will probably shift to making it more than a wiki. Like private, internal and external dataset members, explicit context (includes), perspectives, type-specific displays and other commands, ledgers, etc.