Re:The lack of namespaces on crates.io is a feature
by kibwen on Friday September 11, 2020 @01:27PM
(#24445119)
Can I get a link to the quoted document? The quote raises more questions than it answers. Who determines that someone applying for a qualified name is the owner of that trademark (presumably this is a full-time employee; who pays their salary?), and what is the process? Trademarks are not a universal namespace--even within a single legal jurisdiction you can have the same name legally owned by different people due to different contexts--so who decides who wins?
Re:The lack of namespaces on crates.io is a feature
by didibus on Friday September 11, 2020 @04:45PM
(#24447158)
The quote is from: https://insideclojure.org/2020/07/28/clj-exec/ under section "Deprecated unqualified lib names".
That said, ya this is best intentions unfortunately. I'm guessing if you own a real trademark, you could actually sue people using your trademark as their group-id.
Otherwise in general they recommend using a registered web domain name. Someone else could take over your domain name as theirs, but I think the registry owner, like maven-central, if you contacted them and could show you own that domain, they might be able to take actions against the impersonator. Same for a github user.
Actually, thinking about this, I feel it be great if the repository owner like maven-central required a form of proof of ownership of the domain or the github id. That could add a lot of trust to the whole process.
Re:The lack of namespaces on crates.io is a feature
by Symbiote on Friday September 11, 2020 @08:45PM
(#24448868)
> maven-central required a form of proof of ownership of the domain
They do. There's even a manual review procedure.
Re:The lack of namespaces on crates.io is a feature
by didibus on Saturday September 12, 2020 @01:22AM
(#24450045)
Oh really? Wow that's awesome I had no idea maven central did that.
Re:The lack of namespaces on crates.io is a feature
by gw on Friday September 11, 2020 @01:40PM
(#24445252)
The quote was a guideline, not a requirement. Cognitect (who makes the clojure CLI tool) doesn't even control clojars, the main clojure maven repo, so they wouldn't be able to enforce that even if they wanted to.
The new tools.deps in Clojure actually is moving to disallow collapsed names for similar reason and will force iglu/iglu.
Here's a rationale from them:
> The groupId exists to disambiguate library names so our ecosystem is not just a race to grab unqualified names. The naming convention in Maven for groupId is to follow Java’s package naming rules and start with a reversed domain name or a trademark, something you control. Maven itself does not enforce this but the Maven Central repository does all new projects.
> In cases where you have a lib with no domain name or trademark, you can use a third party source of identity (like github) in combination with an id you control on that site, so your lib id would be github-yourname/yourlib. Using a dashed name is preferred over a dotted name as that could imply a library owned by github.