User Hypermedia format

/* pardon the cross-posting */

I just published a first working draft of a new hypermedia format I am
(humbly) calling "Uber Hypermedia"[1]. I'm maintaining it in github[2]
where you can post issues, clone/PR, etc. if you like.

It is designed to be *very* minimal. It has only three elements, 11
attributes, and seven reserved strings.

Here is some text from the opening:
<snip>
The Uber message format is a minimal read/write hypermedia type designed to
support simple state transfers and ad-hoc hypermedia-based transitions.
This document describes both the XML and JSON variants of the format and
provides guidelines for supporting Uber messages over the HTTP protocol.

The Uber message model has a number of design goals:
- Keep the message structure as lean as possible.
- Support all the H-Factors [HFactor] in hypermedia controls.
- Be compatible with multiple protocols (e.g. HTTP, CoAP, etc.)
- Maintain fidelity for more than one base message format (XML, JSON, etc.)
</snip>

I'm looking for any/all feedback here or in the repo space.  Thanks in
advance.


[1] https://rawgithub.com/mamund/media-types/master/uber-hypermedia.html
[2] https://github.com/mamund/media-types
 <https://github.com/mamund/media-types>

mamund <https://github.com/mamund/media-types>
+1.859.757.1449
skype: mca.amundsen
<https://github.com/mamund/media-types>http://amundsen.com/blog/
http://twitter.com/mamund
https://github.com/mamund
http://linkedin.com/in/mamund