v6 hyper-schema: baseUri about json-schema-spec HOT 4 CLOSED

Having thought about this proposal for a while, I find it more confusing than it's worth. There's the child-propagation concern, and the complications mentioned there. It also is saving just a few keystrokes per URI at the cost of substantial readability. Having to mentally assemble the URI across several fields (which may be many lines apart) is much harder to work with than just seeing the URI template at the point where you need it.

I'm solidly (although not vehemently) against this proposal.

from json-schema-spec.

Did this get put in the latest draft as base without actually finishing the discussion or resolving the issue?

from json-schema-spec.

Uh... yeah, yeah it did. I must have missed this issue.

The functionality was already in JSON Hyper-schema as a special case for links where rel="self", which is somewhat unprecedented, since links shouldn't be changing the document's behavior just by existing. I can't really take the behavior out (it's used by JSON Schema itself), so it was just spun into a keyword.

We'll see if it works out or not.

from json-schema-spec.

LOL that's a good reason to have added it!

FWIW I'm not as opposed to it as I was in the earlier comment. There's a bit of weirdness (to me) with all of these resolution scope-changing keywords, but I think some early bad experiences with id has led me to be too harsh on the concept.

from json-schema-spec.