4 ms·
> It's less difficult (though still far from easy) to handle name squatting on organization/corporate names as qualifiers for packages than to try and prevent
by swsieber 5y ago
> It's less difficult (though still far from easy) to handle name squatting on organization/corporate names as qualifiers for packages than to try and prevent name squatting on package names.
So we're back to fighting who owns "com.oracle"?
It seems like no matter the approach taken to validating namespace ownership there's some drawback.
- thaumasiotes 5y agoNo. There is no fighting over who owns com.oracle. There's nothing stopping you from releasing software in the com.oracle namespace, but when you do, either you are Oracle or you are falsely claiming to be Oracle. Avoiding accidental collisions just isn't the same problem as validating a potentially fraudulent claim of identity. Namespacing solves the first problem; it's not intended to address the second, and doesn't.