Mike Kelly

Has anyone sketched out what this might look like?

I think the only reasonable way of achieving broader adoption is to ship APIs where clients will code against them without even knowing what hypermedia is. This means we need...

@kevinswiber > We care more about the media types, because that's what we do. Most people just want to get the job done. I'm in the latter camp for sure....

Yes that sounds like a really good idea. fwiw, when I spiked the haltalk demo - this is what the link relation documentation ended up looking like: http://haltalk.herokuapp.com/rels/signup

> I'd like to show @zdne some respect and not pollute this thread with nerd battle great, me too! It's not a personal affront, I'm just offering advice that I...

> Which media types help support the features I'm looking to implement? More features in the media type does not translate to more features of a service. Compromising on media...

Defending complexity by offering more "features" is a well proven sales technique, though - I'll grant you that.

Yes, I'd be very interested in that. Also in structuring the code base in a way that makes it easier to work with the various packaging systems. Unfortunately, I don't...

To link two resources together, you can POST/PUT hal+json to a given resource. Hal specifies the processing rules for the representation, that's all - it is down to your application...

For me, what you are describing is outside of what the media type specification should include. HAL is meant to be simple, which it will not be if it starts...