In software design/standards there's long been the philosophy of "Mechanism, Not Policy". Which means get the plumbing etc working, don't try to (overly) second guess what people might do with it. And, in particular, whether it's useful or valuable based on one's generally very limited, spur of the moment, off the top of one's head imagination. Of course nothing is quite that black & white and policy creeps in due to potential harm, limited resources, adding unjustified complexity ("creeping featurism" aka "feeping creaturism"), etc But it's not a bad guiding philosophy. Put another way an objection of "why would anyone ever need that?" is generally suspicious -- trying to inject policy unnecessarily where mere mechanism, just make it work, would suffice. -- -Barry Shein Software Tool & Die | bzs@TheWorld.com | http://www.TheWorld.com Purveyors to the Trade | Voice: +1 617-STD-WRLD | 800-THE-WRLD The World: Since 1989 | A Public Information Utility | *oo*