Put CVR last in XSD

[JDziurlaj]

The CVR schema has its elements ordered alphabetically (with some exceptions). This means that all CVRs appear before any of the reusable data (e.g. Election, GpUnit, etc.). This precludes the effective use of streaming (or would require multiple passes). I propose we move CVR to the last element of CastVoteRecordReport.

[raylutz]

When people use prettyprint or other such utilities to print the JSON it defaults to sorting the keys. You can override that and keep them in a specific order.

Some NoSQL format, such as DynamoDB on AWS use a non-encapsulated JSON format. Each record is complete json and does not have any comma at the end, and does not need to be encapsulated. I also recommend for ease of use that some white space be added into the format in the form of newlines between records.

[JDziurlaj]

We'll need to put in a preference somewhere in the body of the specification for JSON, since you cannot specify key order in JSON schema.

[raylutz]

We'll need to put in a preference somewhere in the body of the specification for JSON, since you cannot specify key order in JSON schema.

@JDziurlaj -- When is key order important?