4 ms·
I think they're preempting a problem that doesn't exist. There's many APIs that don't own the .com of the same name, but it never causes much of a problem... a
by damian2000 12y ago
I think they're preempting a problem that doesn't exist. There's many APIs that don't own the .com of the same name, but it never causes much of a problem...
angular.com
cocoa.com
node.com
flask.com
bootstrap.com
backbone.com
etc.
- Blahah 12y agoThe domains you've listed are all common words, so claiming exclusive use of them would not be reasonable. HealthKit is not a common word, so it seems more reasonable for an entity to expect exclusive use of it as a trademark.
- curiouscats 12y agoI don't think you can expect to slap two common words together and prevent anyone from using those words in any way everywhere. If you make up some new word Exxon etc. then maybe. For slapping two common words together there have to be sensible limits on everyone else being prohibited. If you own things like onetwo.com great that may well be a reason for someone else to be dissuaded from naming a consumer product that because they want an easy to remember domain. Thinking all uses of HealthKit are bad seems more to me like Facebook thinking anyone using "book" prefaced by something else is doing wrong - which I think is silly. I would be amazed if there are not many previous uses of health kit - just removing the space hardly seems an amazing transformation to me.