Data Referencing - Invalid JSON
The JSON conversion does not support control characters like line breaks.
Especially the "Instructions for proper use" usually have a longer text that must be cleaned to a "one-liner".
Just a short question:
did you invent the structure of the JSON yourself or did you lean towards an established standard? I don't think it's a good idea to create your own standard there, so if you find something suitable, I would go for something established.
The JSON Table Schema standard of the Open Knowledge looks similar: http://specs.frictionlessdata.io/json-table-schema/
Another point: When making up example email addresses, try to use @example.com as, as that is what the domain is there for according to RFC 2606.