title: How to handle default values of sub-objects within a JSON schema validation?
body: <p>How should a JSON schema validator handle the case where a sub-object of an object has a default value but the parent object hasn't?</p>
  
  <p>Imagine the following schema </p>
  
  <pre><code>{
      "type": "object",
      "properties": {
          "element": {
             "type": "object",
             "properties": {
                 "number" : { "type": "integer", "default": 15 }
             }
          }
      }
  }
  </code></pre>
  
  <p>Validated against the following JSON: <code>{}</code> it is resulting in <code>{}</code>.</p>
  
  <p>But shouldn't it result in </p>
  
  <pre><code>{
      "element": {
          "number": 15
      }
  }
  </code></pre>
  
  <p>.</p>
  
  <p>How do we have to interpret the <code>default</code>-keyword? I read the corresponding lines in the standard, but they haven't helped me further.</p>