From c2f9c36a2be4de419a95dfcbb4c95f02132f9e96 Mon Sep 17 00:00:00 2001 From: handrews Date: Sat, 19 Nov 2016 23:39:49 -0800 Subject: [PATCH] "uritemplate" and "jsonpointer" formats Addresses issue #109 by adding "uritemplate" and "jsonpointer", as defined by their RFCs, both of which already play roles within JSON (Hyper-)Schema. We use "uritemplate" in hyper-schema, but until the preprocessing step is removed we technically can't put the format in the meta-hyperschema. This is being addressed elsewhere. While we do not need "jsonpointer" for our meta-schema, it is used for schema+json URI fragments, and in other JSON-based media types such as JSON Patch. --- jsonschema-validation.xml | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml index b476264d..c92b96ab 100644 --- a/jsonschema-validation.xml +++ b/jsonschema-validation.xml @@ -7,6 +7,8 @@ + + ]> @@ -817,6 +819,25 @@ +
+ + This attribute applies to string instances. + + + A string instance is valid against this attribute if it is a valid URI Template + (of any level), according to . + +
+ +
+ + This attribute applies to string instances. + + + A string instance is valid against this attribute if it is a valid JSON Pointer, + according to + +
@@ -861,6 +882,8 @@ &RFC2673; &RFC3339; &RFC3986; + &RFC6570; + &RFC6901; &RFC7159; &RFC5322;