Elements of a Hypermedia Message Document

[smizell]

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.

• 1. Is the categorization of transitions helpful?
• 2. Should this include the concept of curies or prefixes?
• 3. Is the concept of anonymous links and actions helpful?
• 4. Does it make sense to include embedded resources under transitions?
• 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!

[smizell]

@fosrias @kylef @zdne @kylef All comments and questions addressed offline. Good to merge!

[fosrias]

@smizell Should this be Hypermedia Messages?

[zdne]

Agree with @fosrias, lets talk about Hypermedia message (based on examination of hypermedia formats – media types)

[zdne]

In addition I would explicitly state that this document is describing elements of Hypermedia Messages in HTTP APIs, not in general.

[fosrias]

Is this actually protocol dependent?

[smizell]

I believe I've included HTTP stuff, but we should make it protocol independent. I don't think it would take much effort. Most of the HTTP stuff centers around the HTTP methods.

[smizell]

Regarding the title, I thought @fosrias was interested in changing from referring to this as message, which is what I originally had:

smizell@91950c0

I'm really fine either way, and I think both are applicable.

[fosrias]

@smizell Sorry for the confusion. Wanted to keep messages. So, your original commit was good.

[fosrias]

@smizell Finished commenting on your comments.

[smizell]

@fosrias @zdne @kylef Ok, finally, I got around to this. Maybe it's good to merge now?

[zdne]

👍