Mitar

Its uses are the same as what other URI Fragment Identifiers are meant to support. Queries is one. But also highlighting/anchoring in the browser and things like that. This issue...

I do no think this is a problem in this case. Because this embedding happens on the client in my view. So client fetches `http://example.com/foo`, but embeds just `field1` and...

No, I think the JSON example I had is also obsolete with your [example here](https://github.com/braid-work/braid-spec/issues/21#issuecomment-778738386). So we can ignore it. So this issue is really just about being able to...

I think this (from the RFC 7111) is more relevant to "same reasons": > The fragment identifier consists of additional reference information to be interpreted by the client after the...

To move discussion back to the multiple JSON pointers in the URI fragment, I would suggest we: * document that fragment should be encoded like query string * multiple URI...

You could define a new method and then one could use almost standard `X-Method-Override` header to pass it until Braid becomes so popular that everyone implements it.

I appreciate your comments @toomim, but I also share that `$link` would be better. It is pretty common in JSON schema and other places to have things like `$ref`, `$id`....

I got it from there. :-)

I mean, the issue is about making comparison of those in the spec. Otherwise I think we are abound to get and keep getting questions of the form "but why...

What is nice with `Patch-Lengths: 90, 78` is that it can also be defined that one can do: ``` Patch-Lengths: 90 Patch-Lengths: 78 ``` For same effect. Which can then...