TWAIN is a standard for acquiring from image scanners: an image capture API for Microsoft Windows and Apple Macintosh operating systems. The word TWAIN is not officially an acronym, however, it is widely known as an acronym for "Technology (or Toolkit or Thing) Without An (or Any) Intelligent (or Important or Interesting) Name".
The disadvantage of TWAIN is that it does not separate the user-interface from the driver of a device. This makes it difficult to provide transparent network access. Whenever an application loads a TWAIN driver it is completely unattachable from the supplied manufacturer's GUI. To be precise, it is not a fault of TWAIN specification but of such device drivers, because they are not fully compliant with TWAIN.
Kevin Bier, chairman-emeritus of the TWAIN Working Group and the original author/editor of TWAIN 1.0 (with the aid of several others from seven companies), confirms authoritatively that TWAIN, while not officially an acronym, was conceived as referring to a "toolkit without an important name."
This non-acronym was inspired by Bier's contemporaneous reading of a collection of letters by Mark Twain. Bier reports that he finished reading one such letter at nearly midnight one evening, then checked voicemail one last time only to receive notice of yet another set of potential names for the as-yet-nameless technology. In aggravation, he made up the name on the spot and left it as a heated suggestion in a voicemail reply. The name search succeeded and, following consultation with the Mark Twain (S. L. Clemens) estate to assure the legality of the use, the name was officially launched on February 29th, 1992 (which Bier saw as "a fitting date for release of our endeavor").
Bier observes that some believe the binding of the UI into the TWAIN "driver" (actually a piece of application code and not a driver at all) is a failing. He responds that it was an explicit design goal of the group to lay responsiblity for presenting the functionality of the device in the hands of the device manufacturer.
"It was our premise that no one else could know all the features of the device or how best to present that functionality to the user," Bier says. "Regardless of one's opinion about the relative goodness of that premise, it was an essential foundation of the success of the spec as measured both by adoption and adoptability."
TWAIN | TWAIN | TWAIN | TWAIN | TWAIN | TWAIN | TWAIN | TWAIN | TWAIN | TWAIN