`$ref` with a relative path `$ref: ./bson_object_id` returns `References are not compatible` about gojsonschema

[sigu-399]

My understanding of the json schema specification is that referencing external file has to be done with a complete URL/URI (http://...). So by default, all your schemas "should" be served by your http server.

Now, because just like you i wanted to reference local files, I added a way to do so.
It has to be in the form: file://..., please note it has to be the full path, non relative one. for example:
"$ref": "file:///usr/something/data/json/schemas/bson_object_id.json#properties/_id"

Please note this is an "experimental" feature.

PS: Please label your issues as questions when they are not proper bugs/issues.

[phstc]

Hey @sigu-399, thanks for you reply.

I see, the specification is vague regarding to $ref. I find relative paths useful, in case we have a project with many schemas which can be deployed in different environments (test, development, staging, production etc) with different absolute paths, but always with the same relative path.

PS: Please label your issues as questions when they are not proper bugs/issues.

I'm sorry for using issues as questions. Unfortunately I can't label issues, this feature is only available for project maintainers.

---

My bson_object_id.json accepts _id as a string _id: '52b8b007cbdb04659d0009e5' or as an object _id: { '$oid': '52b8b007cbdb04659d0009e5' }, as type accepts a string or an array. The "problem" is in case of object, because I would like to define a specific object which only accepts/requires $oid as a property/member. So I created an array of types as follows:

/data/json/schemas/bson_object_id.json

{
  "type": "object",
  "properties": {
    "_id": {
      "type": [ { "type": "string" },
                { "type": "object",
                  "additionalProperties" : false,
                  "properties": {
                    "$oid": {
                      "type": "string"
                    }
                  },
                  "required": [ "$oid" ]
                }
              ]
    }
  }
}

When I try to validate I get type must be of type string/array of strings. Do you have a suggestion how to define this kind of complex types?

PS: I know that the JSON schema still draft and it is vague. So, the implementations of JSON schema can diverge. In this case I'm trying to reuse (and measure how difficult it could be to adapt schemas, create Pull Requests etc) my schemas definitions which work with json-schema-ruby.

[sigu-399]

This is in my opinion a strange way to write a schema given your needs.

I based my work on this http://json-schema.org/latest/json-schema-validation.html#anchor79 for the type keyword.
You could also use the OneOf keyword.