>to documentation of a proprietary programming language.
We're probably just quibbling over terminology. The people I know use whitepapers to mean more business-oriented, less vendor-specific thought leadership pieces. And use other terms for technical deep dives--which can indeed be longer.
While some of these are written by analyst firms, quite a few are not. They're work-for-hire, often by techies or journalists who know the area in great depth, and who can ask the in-house experts the right questions and turn those answers into something genuinely useful. (Well, when they're good. Mine are good. :-) )