In a message dated 3/23/2010 10:41:17 AM Pacific Daylight Time, br...@brianleach.co.uk writes:
> 1/ It's not the term MultiValue I have a problem with - that we should > continue to support since it already has a meaning and a presence, and one > worth building on. For one thing, MVDBMS is a nice abbreviation! > > It's the terminology used within that, that is the problem: for example, I > want to put some web pages out giving an introduction to the query > language. > What do I call it? If I use the word 'RetrieVe' that alienates every other > variant: if I mention all of them, it just gets silly. Even writing purely > for U2, the fact that there are two names - RetrieVe and UniQuery -from > the > same manufacturer for two variants that to all intents and purposes do the > same thing, is confusing for anyone from outside. That's the level where > we > need some consensus. >> Call it what it is "MultiValue Query Language" MVQL "Each vendor has branded the MultiValue Query Language, but the core components have not changed...." or whatever. W.J. _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
