Why JSON API Specification suggest use of hyphen/minus to separate words in member names?
<p>According to recommendation on <a href="http://jsonapi.org/recommendations/" rel="noreferrer">JSON API</a> specification site, we should use all lower case member names in JSON separated by hyphens:</p>

<blockquote>
  <p>The allowed and recommended characters for an URL safe naming of
  members are defined in the format spec. To also standardize member
  names, the following (more restrictive) rules are recommended:</p>
  
  <p>Member names SHOULD start and end with the characters "a-z" (U+0061 to
  U+007A) Member names SHOULD contain only the characters "a-z" (U+0061
  to U+007A), "0-9" (U+0030 to U+0039), and the hyphen minus (U+002D
  HYPHEN-MINUS, "-") as separator between multiple words.</p>
</blockquote>

<p>So basically, we should be using JSON like this:</p>

<pre><code>{
    "first-name": "Jason",
    "last-name": "Tough"
}
</code></pre>

<p>Would not it make it <a href="https://stackoverflow.com/questions/13869627/unable-to-access-json-property-with-dash">cumbersome</a> to access those properties in JavaScript? Or any other programming language for that matter, especially if we want to generate classes from JSON Schema? </p>

<p>What is the motivation behind this recommendation?</p>