Add database_specific to affected[].ranges[]. (#37)

* Add database_specific to `affected[].ranges[]`.

This is intended only for metadata that enables databases to losslessly
convert OSV entries back into their original representation.

Part of #35.

* Update docs/schema.md

Co-authored-by: Chris Bloom <[email protected]>

Co-authored-by: Chris Bloom <[email protected]>

docs/schema.md

@@ -83,7 +83,8 @@ A JSON Schema for validation is also available
 				"fixed": string,
 				"last_affected": string,
 				"limit": string
-			} ]
+			} ],
+			"database_specific": { see description }
 		} ],
 		"versions": [ string ],
 		"ecosystem_specific": { see description },
@@ -490,6 +491,17 @@ describing a single range.  The range object defines the fields `type`,
 
 This field is required if `affected[].ranges[].type` is `GIT`.
 
+### affected[].ranges[].database_specific field
+
+The `ranges` object's `database_specific` field is a JSON object holding
+additional information about the range from which the record was obtained. The
+meaning of the values within the object is entirely defined by the database and
+beyond the scope of this document.
+
+Databases should only use this field to store additional context that may be useful in converting from the OSV
+format back into the original database representation. Values in this field
+have no effect on the [evaluation algorithm](#evaluation).
+
 ### affected[].ecosystem_specific field
 
 The `affected` object's `ecosystem_specific` field is a JSON object holding

validation/schema.json

@@ -157,6 +157,9 @@
                     ]
                   },
                   "minItems": 1
+                },
+                "database_specific": {
+                  "type": "object"
                 }
               },
               "allOf": [