Elements of a Hypermedia Message Document

Per issue #4, this is the first draft of this document describing the elements of a hypermedia message. It is all open for discussion, and I'd be happy to change anything. Below are some discussion items.

- [x] 1. Is the categorization of transitions helpful?
- [x] 2. Should this include the concept of curies or prefixes?
- [x] 3. Is the concept of anonymous links and actions helpful?
- [x] 4. Does it make sense to include embedded resources under transitions?
- [x] 5. How do we address more complex attributes? Ones that may include arrays of objects in JSON or nested elements in XML?

Once we come to a consensus, we can merge it into the repo. Thanks!
That *still* may not make sense, so here's an example:

Let's pretend that you could use URI templates in HTML:

```html
<form template="/payments/customers/{id}/{?year}">
  <input type="text" name="month" />
</form>
```

I don't think it's clear how this should work used. Resolve the template first with something like `?year=2014` and then add `month` to it?

Since only a couple rare media types even attempt to cover this idea, I think we can leave it out.