jadeallenx · January 4, 2018 21:21 · Jan 4, 2018 · Jan 4, 2018
diff --git a/refs.md b/refs.md
@@ -16,7 +16,8 @@ I tried to make things as simple as possible. I had a file with the "base" schem
          "type": "number"
       }
    }
-}```
+}
+```
 
 And then I had another file which took a collection of these items. It looked like this:
 
@@ -32,7 +33,8 @@ And then I had another file which took a collection of these items. It looked li
           "items": { "$ref": "record" }
         }
    }
-}```
+}
+```
 
 The intention here is clear - I want to reuse the schema for record as the elements in an array.  For example, this is a valid input against the schema:
 
@@ -48,7 +50,8 @@ The intention here is clear - I want to reuse the schema for record as the eleme
        "bar": 19.2
      }  
   ]
-}```
+}
+```
 
 But how to communicate this to jesse?  Well, it turns out that jesse canonicalizes your references - it insists on prefixing your ids with a URL - either "http://" or "file://".  So to make this work in jesse, I needed to prefix both my ids with "file://" and then always reuse "file://record" anytime I wanted to use it elsewhere.
 

diff --git a/refs.md b/refs.md
@@ -0,0 +1,57 @@
+If you use the [jesse][1] application for JSON schema validation, you will no doubt be mystified by the byzantine way that references are handled in the application. I spent well over 30 hours trying to figure it out, since it is totally undocumented what the format should be.
+
+I tried to make things as simple as possible. I had a file with the "base" schema for an item.  I called it `record.json` It looked something like this:
+
+```json
+{
+   "id": "record",
+   "description": "Base schema for a valid record",
+   "type": "object",
+
+   "properties": {
+      "foo": { 
+         "type": "string"
+      },
+      "bar": {
+         "type": "number"
+      }
+   }
+}```
+
+And then I had another file which took a collection of these items. It looked like this:
+
+```json
+{
+   "id": "records-bulk",
+   "description": "A collection of records",
+   "type": "object",
+
+   "properties": {
+       "records": {
+          "type": "array",
+          "items": { "$ref": "record" }
+        }
+   }
+}```
+
+The intention here is clear - I want to reuse the schema for record as the elements in an array.  For example, this is a valid input against the schema:
+
+```json
+{
+  "records": [
+     { 
+       "foo": "hoge",
+       "bar": 42
+     },
+     { 
+       "foo": "qux",
+       "bar": 19.2
+     }  
+  ]
+}```
+
+But how to communicate this to jesse?  Well, it turns out that jesse canonicalizes your references - it insists on prefixing your ids with a URL - either "http://" or "file://".  So to make this work in jesse, I needed to prefix both my ids with "file://" and then always reuse "file://record" anytime I wanted to use it elsewhere.
+
+Apparently it is not possible to have "naked" references for reasons I can't possibly fathom. I might open a PR about this because it almost beggars imagination.
+
+[1]: https://github.com/for-GET/jesse
No results found