I used to work at Dialogic, which was then bought by Intel. In all my time there, new prospects/customers would invariably say: "This is really hard to configure (we had line resource cards, DSP resource cards, and various ways to map these resources together.) don't you guys have a card configuration utility?" Well, for Windows, yes. For Linux, no. "Too hard and no demand" says Engineering. So, taking the bull by the horns, I found the PCI ID codes for the various cards, wrote a utility to configure them, got approval from my manager to release it as open-source and all was well.
Until...The head of Engineering at our division found out about it and lodged a formal internal complaint that I had "released Intel proprietary information" and was summoned to Parsippany to face legal. Fortunately, my manager's support and basic common sense prevailed, the Eng manager was sent packing with his tail between his legs and I flew home drunk as a skunk. The legal guy basically said: "when you expose a PCI ID to the OS, it's no longer proprietary - dumbass!".
Point is that when information is documented and exposed in any way, it is not "proprietary" in the sense that it cannot be used, just not stolen and used inappropriately.