Changing property key names in output format

[gregsdennis]

This PR is the start of changes to the output format as discussed here.

It covers changing property names:

• keywordLocation -> evaluationPath
• absoluteSchemaLocation -> schemaLocation
• errors/annotations -> nested

(In making these edits, I began to see why so many people were asking for examples with annotations. I expected that to be a trivial exercise given the error examples, but I get it now.)

[handrews]

Looks good to me! I'm glad to hear you're thinking about annotation examples :-)

[karenetheridge]

Like the previous discussion on required->present, I'm opposed to changing the names of things without a really good reason. What makes these names better than the existing ones? "nested" in particular I find to be really vague.

[karenetheridge]

I noticed you didn't update the schema that validates the output formats. It probably needs a bit of work anyway even before changing the spec.

[gregsdennis]

We have reasons for changing these. They're in the discussion. If we need to change them to something else, then please continue the discussion there. Nothing else has changed there on this topic, so I decided to move forward.

[gregsdennis]

I noticed you didn't update the schema that validates the output formats.

I think I may leave this one for the end. I'll update the examples as I go, though.

[gregsdennis]

Going ahead with merging this. If we want to change nested to something else later, that's easy to do.