@WP-API/amigos #reviewmerge

@joehoyle @rachelbaker Can I get your review and thoughts? This needs to go in sooner rather than later so we can work from it.

@danielbachhuber @joehoyle @rmccue I am still not sold on the idea of fixed schemas, but willing to acquiesce to a majority opinion. I see the rigidness as a drawback, and am concerned we wouldn't be solving a real problem. Just my opinion.

Looking through this PR brought the following questions to mind:

1. How do we handle expressing the additional fields returned in non-default contexts?
2. Are there only three User object schema properties defined because that schema is incomplete?

I am still not sold on the idea of fixed schemas, but willing to acquiesce to a majority opinion.

I was under the assumption that we had all agreed on fixed schemas?

Are there only three User object schema properties defined because that schema is incomplete?

Oh, I didn't finish. I can finish User and Comment schemas before merging if you'd like

I'm going to finish up schemas for all Resources, and then this will be ready for a final reviewmerge