Mike Amundsen

as far as i can tell, this will be a breaking change, right? i've resisted "strong-typing" the message to reduce rejected responses (e.g. the receiver was expecting a boolean and...

there is nothing built into the spec right now to handle this, i think. however, if you'd like to build up a working extension that would be backward compatible, that'd...

Since this extension has _two_ properties which have a relationship between them, we should also make explicity how to handle msgs that have one or both properties *missing* and/or one...

can you expand on this a bit? possibly write up a short example that includes the HTTP request/response that you want to support?

OK, i think i am getting it. the current spec lays out "link" interactions for `text/csv` and `application/json`. you are suggesting we need to add support for _more_ media types...

OK. color me a skeptic but that might be due to my not "getting it" quite yet. here's what i suggest. show us a working version of what you'd like...

thanks. looking forward to it. ping me directly if you need anything at all.

if i recall correclty, the current state of affairs has to do w/ the original definition of `value` as a string and `selectedValues` as an array. we wanted to support...

well, the actual design of each representation is up in the air, really. IOW, there is no "rule" about where links should appear. The example in the book definitely does...

@robertovelasco looks pretty good. FWIW, i implemented this pattern for Cj recently (not yet published) and used almost identical elements (didn't use "embedded" property, but that's a minor thing). _suggest_...