Re: If not JSON, what then ?

| 1) Using the first character of the field-value as a signal that the encoding is in use is interesting. I was 
| thinking of indicating it with a suffix on the header field name (e.g., Date-J). Either is viable, but I 
| don't think it's a good idea to reuse existing header field names and rely on that signal to differentiate 
| the value type; that seems like it would cause a lot of interop problems to me. Defining a new header field 
| (whether it's Date-J or Date2 or whatever) seems much safer to me.
| 2) Regardless of #1, using < as your indicator character is going to collide with the existing syntax of the 
| Link header.

Or perhaps use ':' as indicator? Causes double '::' on HTTP/1


Is this viable ?

/ Kari Hurtta

Received on Wednesday, 3 August 2016 06:38:01 UTC