in what tool did the problem surface? what was the set up?
I'm using ex_json_schema, which is a JSON schema validator for Elixir.
First the validator accepts a schema that is provided locally (e.g. I run
File.read!('definitions/schema/Organization.schema.json') |> Poison.decode! 1). The validator was requesting http://hl7.org/fhir/json-schema/Organization (since that is what is in the
"id" field for the schema) and failing because that resource isn't actually there (http code 404).
To fix this issue, I removed the
"id" field and appended the local server to the front of the
$ref and was able to resolve the schema.
My assumption is that the aforementioned Elixir JSON schema validator has a bug, since the
$refs should theoretically work.
we've already had discussions about these things, and changed some of them
I don't think any changes would be necessary. You've given me everything I need to be able to modify the schemata
id to fix the issue. What I plan to do is make the
$refs relative again and then replace the
id with the correct server address to request each schema.
 This reads the file into memory and then parses the JSON into a data structure that Elixir can process.