The question is why is it 'nuts' for puck.js to have to pay up in order to use the intellectual property/patents that the Bluetooth SIG own?
One has to be clear about this "intellectual property" thing (A contradiction in terms if I ever saw one).
There are patents. There are trademarks. There are copyrights. There are non-disclosure agreements. These are all very different things and subject to different laws.
It's nuts for Puck.js to have to pay up for patents. Perhaps it uses patented technology in the Bluetooth module. But the dues on that will already have been paid by Nordic Semiconductor, the makers of the radio. Heck, even the LEDs on the board are subject to patents. That is a problem for the LED manufacturer not Puck.js.
I don't see how copyright is an issue here.
That leaves, trademark.
Well, I don't see how Puck.js is passing itself of as a maker of Bluetooth radios. So no problem there.
It appears from the original links at the top of this thread that for Bluetooth(R) that the model is NOT that the chipset manufacturer pays for use of the patent but that ANY user of Bluetooth technology is required to do so.
Here is the stock answer from the Bluetooth SIG
The company that will be branding the product will want to complete the listing process:
Every company that builds or brands or represents ANY Bluetooth product(s) as their own must complete the Bluetooth Qualification and Declaration Process. Which pieces of the process depends upon how you are using the Bluetooth portion of your product. Let's break it down.
You need to Qualify AND Declare if you are:
• Using an unqualified Bluetooth portion (chip, module, stack or design)
• Buying a Bluetooth qualified design and modifying it for your product
• Using a design that was qualified as a "component" product type
• Have the rights or license to use another company's brand and want to sell those products with changes to the already qualified Bluetooth portion (chip, module, stack or design)
You do not need to qualify but still need to Declare if you are using:
• An unmodified Bluetooth qualified design (a chip, module, stack or design you are leaving as-is)
• A factory or supplier that already qualified the Bluetooth portion (chip, module, stack or design) of your product
• An already qualified design for a product you are developing
Is my Bluetooth enabled product Already Properly Qualified?
Step One: If your product has already been qualified, the manufacturer/supplier should have the QDID (Qualified Design ID) readily available.
Step Two: Once you have your QDID, you need to find your product type by using our "Listing Search Tool." In the "Search" box, type in the QDID and hit "Search." Look under "Product Type(s)" column. If your design/product includes one of the combinations below and you have not made ANY changes, you do not need to complete qualification because your product has already been qualified. You will, however, need to complete the "Declaration Process" and buy a Declaration ID.
• End Product only
• (End Product QDID + Profile Subsystem QDID) – multiple profiles may be added
• (Controller Subsystem QDID + Host Subsystem QDID)
• (Controller Subsystem QDID + Host Subsystem QDID + Profile Subsystem QDID) – multiple profiles may be added
Step Three: If you have a different combination of product types or a "Component" you will then need to complete a new "Qualification." Since the Qualification process involves testing and other technical elements, and you aren't sure you can do it on your own, you may want to hire a BQE (Bluetooth Qualification Expert) or BQTF (Bluetooth Qualification Testing Facility).
More information regarding the Declaration and Qualification process can be found in our "Start Guide."
Anyway hopefully an answer about the Raspberry PI 3 position will be forthcoming from them.