$ref relative paths - is this standardized? Doesn't work in interactive mode

[Gabriel Underwood]

It seems like support for relative paths  doesn't work or at least is not standardized.

The example in the widely cited https://spacetelescope.github.io/understanding-json-schema/structuring.html 

says  {"$ref":"definitions.json#/address"} will reference "definitions.json" file in the same directory as the current schema.

jsonschema in interactive mode gives an error

jsonschema.exceptions.RefResolutionError: unknown url type: 'definitions.json'

The only thing that I have been able to get to work is explicit "file:" URIs with fully-qualified file paths, not relative paths. 

Is there a way to support relative resources in schema documents that can be validated by jsonschma and that is likely to be portable across other implementations?    

[rlyacht]

Same question here.  I want to have a schema with many files that define individual objects. The only way I can make it work is to put them at http://some.thing.here/blah.json and then have

{"$ref":"http://some.thing.here/blah.json#/definitions/something"}

Like OP, I would like to be validate with this:

{"$ref": "./blah.json/definitions/something"}

Is that only kosher in draft5, or should it work?