In a previous posting I reported a lack of success when enquiring of the USB Implementors' Forum if a Vendor ID had been reserved for documentation.
To recap my motivation, a Vendor ID -- or at least a range of Product IDs -- is desirable to:
Avoid defamation, such as using a real VID:PID to illustrate a "workaround", which carries the implication that the product is less-than-perfect. Furthermore, failing to check if a VID:PID has actually been used is "reckless defamation".
Avoid consumer law, such as using a real VID:PID to illustrate a a configuration for a video camera, when in fact the product is a mouse.
Avoid improper operation, as may occur if a user cuts-and-pastes an illustrative example and that effects a real device.
Avoid trademark infringment.
Allocation of 256 Product IDs, thanks to OpenMoko
OpenMoko has been generous enough to reserve a range of Product IDs for use by documentation:
0x1d50:0x5200 through to 0x1d50:0x52ff
Note carefully that other Product IDs within Vendor ID 0x1d50 are allocated to actual physical USB devices. Only the Product IDs 0x1d50:0x5200 through to 0x1d50:0x52ff are reserved for use by documentation.
My deep thanks to OpenMoko and Harald Welte.
The application form submitted to OpenMoko read:
a name and short description of your usb device project
Documentation concerning the configuration of USB buses and devices.
For example, documentation showing configuration techniques for Linux's udev rules.
The meaning of "documentation" shall not extend to actual configuration of a actual device. It is constrained to showing methods for configuration. If an VID:PID for an actual device is required then these can be obtained from elsewhere.
OpenMoko will not assign these "Documentation PIDs" to any actual device, now or forever.
Operating systems may refuse to accept devices with these "documentation VID:PIDs". Operating systems may refuse to accept configuration which uses these "documentation VID:PIDs".
the license under which you are releasing the hardware and/or software/firmware of the device
The documentation may use any license. Restricting use to only free documentation is problematic: the definition of "free" for documents is controversial; and it would be better if the PID:VIDs were well known and widely used by all authors of technical documentation.
a link to the project website and/or source code repository, if any
Nil, one can be created if this is felt to be necessary (eg, to publicise the allocation).
if you need multiple Product IDs, please indicate + explain this at the first message, rather than applying for a second ID later