markee174: 58 licenses including all the ones you mention fit this definition, [link] have you read it yet, I've mentioned it 3 times now?
There are aditional responsibilities with some licenses, but they do not contradict the points in that definition.
The complexity of commercial and open source licensing comes from this, "If Castle were to accept code from members of the public under the terms of an open source license, Castle would not own the copyright on those contributions, they would have to ask permission to distribute them in a commercial product".
The OpenOffice project gets around that issue by asking contributors to assign copyright to Sun (who own the rest of OpenOffice) so Sun can sell their StarOffice product. As you'd expect with your work that you provided for free being used to make a company profit, it's not universally liked.