roachie...
This is a toughie! You're out-of-luck. SOME of us have what You want; but have accumulated this info over a life-time and guard these documents/notes "jealously". I would NEVER release this info electronically... who knows where it would end-up!
I now work for the military side of Xxxxxx Company, after a long stint working for USAF Civil Service as an ALC acft engineer. I am intimately familiar with commercial and military specs/stds ["mil"] such as AN, AS, MS, MIL, NAS, NASM, HL, etc... and Boeing specs/stds [BACxxxx, BACyyxxzz, BMSxx-yyy, etc]. In addition to my personal notes, I am privy to some corporate conversion documents [A= B= D] that are held as corporate proprietary documents. Between the (2) I have been fairly successful sliding back-and-forth between "mil" spec and corporate specs.
In many cases, corporate specs are very specific and aimed at meeting FAA/FAR requirements... wheras the "mil" specs may meet DOD requirements... but are too vague for the FAA! In-other-words, corporate specs can sometimes be used in lieu of "mil" specs... but NOT necessarily vice-versa [especially for civil acft]. HOWEVER, there is the OBVIOUS problem: Boeing stds should NOT be used on non-Boeing products [etc]; nor should Cessna specs be used on non-Cessna acft, etc. This is the "Catch-22" of using corporate specs... and why I have been using [and continue to try using] generic "mil" specs [modified as I see necessary] to address problems with my military acft.
Swertel and IRstuff have both presented good ideas... just be prepared for some frustrating encounters with "keyword" searches. Also, be prepared to compare specs VERY closely... and add Your own extra verbiage, as required. Keep good notes... and be very cautious!
Regards, Wil Taylor