I disagree that the name for something like this is a trivial decision. Especially when considering the name for a framework which will need to be discoverable on Google to gain popularity. And even more especially when you choose to name the framework for working with a technological concept in one specific programming language the same thing (albeit different casing) as that technological concept itself.

How is that not a really important decision that should be considered practically? If I want to query Google for REST vs. Rest, or even converse with people about it, you don't think that will quickly become (needlessly) confusing assuming the framework becomes popular? And if you aren't expecting the framework to become popular, does that make it OK to choose such a lazy name?

But, hey, at least you got to namedrop the term "bikeshedding" along with your highly specious argument.