draft JSON data schema, etc.

All right, per Issue #13 here's the JSON Schema and a sample transcription in JSON (Dell's 2010 EEO-1). **However**: I don't think the schema, validation tool(s), and raw JSON belong in this repository, so I don't actually think you should merge this ;)

*Instead* my proposal is maybe you could open a separate repo (odd-data?), publish it to [npm](https://www.npmjs.org/) and/or [bower](http://bower.io/) and/or [pip](https://pypi.python.org/pypi/pip) and then this repo/site can install the npm package in order to get the JSON files for linking to download, but anyone else who just wants *all* the data at once can get it all (along with the toolkit - i.e., schema, validation, etc.) just by doing an `npm install` or similar. I came across this somewhere else recently - releasing data by publishing it as a package, but I can't remember where :/ I thought it was a cool idea though, and I think it makes sense, separation-of-concerns-wise.

I'll be able to take care of the PR on this repository to add the dependency, links to JSON (just Dell at the moment), etc. I've never (myself) published to npm or bower or pip before, but I'm quite familiar with the first two and pretty sure I can figure it out.

Thoughts?
I add a quick `version` property, but I'm not sure JSON Schema supports a versioning system natively (yet). I'll do some research on this.