From 4943726574c3e5430f47b0f9daba63809474a827 Mon Sep 17 00:00:00 2001 From: Karuna Tata Date: Thu, 25 Apr 2024 16:58:24 +0530 Subject: [PATCH 1/7] validation result and JSON pointer --- pages/learn/glossary.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/pages/learn/glossary.md b/pages/learn/glossary.md index 2c92e4b57..fed142d4f 100644 --- a/pages/learn/glossary.md +++ b/pages/learn/glossary.md @@ -55,6 +55,10 @@ The essence of JSON Hyper-Schema lies in its ability to define links and actions In other words, JSON Hyper-Schema extends JSON Schema by introducing features for creating hypermedia controls. This facilitates the creation of interactive APIs and ensures compatibility with existing JSON HTTP APIs, maintaining a seamless integration. It adds a layer of interactivity to JSON documents, making it easier to interact with remote JSON resources. +### JSON pointer + +JSON Pointer is a format for data exchange between systems, defining a string for accessing and modifying values within a JSON document. By using JSON Pointer, we can precisely reference and retrieve specific values within a JSON document. The [subschema](#subschema) is typically identified via a JSON Pointer, or equivalent syntax, allowing for targeted validation and manipulation of data within the JSON document. + ### keyword A property appearing within a [schema](#schema) object. @@ -137,6 +141,10 @@ The following are considered tools: Applications which use JSON Schema internally without exposing that functionality in some way, for example, validating configuration files or web requests, are not considered tooling. +### validation result + +The validation result in the context of JSON Schema refers to the outcome of applying the entire JSON Schema to the entire instance document. This application should yield a boolean assertion, indicating whether the instance document conforms to the rules and constraints specified in the schema. The validation result signifies whether the instance document passes or fails validation against the [schema](#schema). + ### vocabulary A tightly related collection of [keywords](#keyword), grouped to facilitate re-use. From 101f77dda14c2f15c81642e9f6980e36803d9afa Mon Sep 17 00:00:00 2001 From: Karuna Tata Date: Thu, 25 Apr 2024 17:09:25 +0530 Subject: [PATCH 2/7] add related article --- pages/learn/glossary.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/pages/learn/glossary.md b/pages/learn/glossary.md index fed142d4f..72e3ad567 100644 --- a/pages/learn/glossary.md +++ b/pages/learn/glossary.md @@ -145,6 +145,10 @@ Applications which use JSON Schema internally without exposing that functionalit The validation result in the context of JSON Schema refers to the outcome of applying the entire JSON Schema to the entire instance document. This application should yield a boolean assertion, indicating whether the instance document conforms to the rules and constraints specified in the schema. The validation result signifies whether the instance document passes or fails validation against the [schema](#schema). +### See also + +[Get started with JSON schema](../blog/posts/get-started-with-json-schema-in-node-js.md) + ### vocabulary A tightly related collection of [keywords](#keyword), grouped to facilitate re-use. From d7cb92361e28366f3568595382a5aff923ecb4db Mon Sep 17 00:00:00 2001 From: Karuna Tata Date: Thu, 25 Apr 2024 17:10:05 +0530 Subject: [PATCH 3/7] fix --- pages/learn/glossary.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/learn/glossary.md b/pages/learn/glossary.md index 72e3ad567..3fa29c03d 100644 --- a/pages/learn/glossary.md +++ b/pages/learn/glossary.md @@ -145,7 +145,7 @@ Applications which use JSON Schema internally without exposing that functionalit The validation result in the context of JSON Schema refers to the outcome of applying the entire JSON Schema to the entire instance document. This application should yield a boolean assertion, indicating whether the instance document conforms to the rules and constraints specified in the schema. The validation result signifies whether the instance document passes or fails validation against the [schema](#schema). -### See also +#### See also [Get started with JSON schema](../blog/posts/get-started-with-json-schema-in-node-js.md) From 9096111ce14767dda4ea79acca494d33509f7082 Mon Sep 17 00:00:00 2001 From: Karuna Tata Date: Mon, 29 Apr 2024 12:07:48 +0530 Subject: [PATCH 4/7] fix JSON pointer definition --- pages/learn/glossary.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/learn/glossary.md b/pages/learn/glossary.md index 3fa29c03d..16f2a7aa4 100644 --- a/pages/learn/glossary.md +++ b/pages/learn/glossary.md @@ -57,7 +57,7 @@ In other words, JSON Hyper-Schema extends JSON Schema by introducing features fo ### JSON pointer -JSON Pointer is a format for data exchange between systems, defining a string for accessing and modifying values within a JSON document. By using JSON Pointer, we can precisely reference and retrieve specific values within a JSON document. The [subschema](#subschema) is typically identified via a JSON Pointer, or equivalent syntax, allowing for targeted validation and manipulation of data within the JSON document. +[JSON Pointer](https://datatracker.ietf.org/doc/html/rfc6901) is a format for data exchange between systems, defining a string for identifying locations within a JSON document. It provides a means to precisely reference specific parts of the document for retrieval or manipulation. By using JSON Pointer, we can effectively access and modify values within a JSON document. The [subschema](#subschema) is typically identified via a JSON Pointer, or equivalent syntax, allowing for targeted validation and manipulation of data within the JSON document. ### keyword From 61bdea766f785ac13fa13e6c6b71b59c6950f7d6 Mon Sep 17 00:00:00 2001 From: Karuna Tata Date: Mon, 29 Apr 2024 15:21:23 +0530 Subject: [PATCH 5/7] Update glossary.md --- pages/learn/glossary.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/learn/glossary.md b/pages/learn/glossary.md index 16f2a7aa4..a8b3e72f9 100644 --- a/pages/learn/glossary.md +++ b/pages/learn/glossary.md @@ -57,7 +57,7 @@ In other words, JSON Hyper-Schema extends JSON Schema by introducing features fo ### JSON pointer -[JSON Pointer](https://datatracker.ietf.org/doc/html/rfc6901) is a format for data exchange between systems, defining a string for identifying locations within a JSON document. It provides a means to precisely reference specific parts of the document for retrieval or manipulation. By using JSON Pointer, we can effectively access and modify values within a JSON document. The [subschema](#subschema) is typically identified via a JSON Pointer, or equivalent syntax, allowing for targeted validation and manipulation of data within the JSON document. +[JSON Pointer](https://datatracker.ietf.org/doc/html/rfc6901) is a format for data exchange between systems, defining a string for identifying locations within a JSON document. It provides a means to precisely reference specific parts of the JSON document for retrieval or manipulation. The [subschema](#subschema) is typically identified via a JSON Pointer, or equivalent syntax, allowing for targeted validation of data within the JSON document. ### keyword From 4f3aabab8698ee9a6247f663e72cab9d8ecc03bd Mon Sep 17 00:00:00 2001 From: Karuna Tata Date: Tue, 30 Apr 2024 14:16:25 +0530 Subject: [PATCH 6/7] Update glossary.md --- pages/learn/glossary.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/learn/glossary.md b/pages/learn/glossary.md index a8b3e72f9..ed4375983 100644 --- a/pages/learn/glossary.md +++ b/pages/learn/glossary.md @@ -57,7 +57,7 @@ In other words, JSON Hyper-Schema extends JSON Schema by introducing features fo ### JSON pointer -[JSON Pointer](https://datatracker.ietf.org/doc/html/rfc6901) is a format for data exchange between systems, defining a string for identifying locations within a JSON document. It provides a means to precisely reference specific parts of the JSON document for retrieval or manipulation. The [subschema](#subschema) is typically identified via a JSON Pointer, or equivalent syntax, allowing for targeted validation of data within the JSON document. +[JSON Pointer](https://datatracker.ietf.org/doc/html/rfc6901) is a string syntax for identifying a value at a specified location within a JSON document. It serves to precisely reference specific parts of the document for retrieval or manipulation. A subschema is often identified using a JSON Pointer, specifying its location within the containing resource. ### keyword @@ -147,7 +147,7 @@ The validation result in the context of JSON Schema refers to the outcome of app #### See also -[Get started with JSON schema](../blog/posts/get-started-with-json-schema-in-node-js.md) +[Get started with JSON schema](../blog/posts/get-started-with-json-schema-in-node-js.md#creating-a-schema-and-validating-data) ### vocabulary From 41aa43bb5c1eb0e22b25813614ce6b1bd11fdf9b Mon Sep 17 00:00:00 2001 From: Karuna Tata Date: Tue, 30 Apr 2024 14:25:54 +0530 Subject: [PATCH 7/7] Update glossary.md --- pages/learn/glossary.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/pages/learn/glossary.md b/pages/learn/glossary.md index ed4375983..50e584ed7 100644 --- a/pages/learn/glossary.md +++ b/pages/learn/glossary.md @@ -143,11 +143,7 @@ Applications which use JSON Schema internally without exposing that functionalit ### validation result -The validation result in the context of JSON Schema refers to the outcome of applying the entire JSON Schema to the entire instance document. This application should yield a boolean assertion, indicating whether the instance document conforms to the rules and constraints specified in the schema. The validation result signifies whether the instance document passes or fails validation against the [schema](#schema). - -#### See also - -[Get started with JSON schema](../blog/posts/get-started-with-json-schema-in-node-js.md#creating-a-schema-and-validating-data) +The [validation result](../blog/posts/get-started-with-json-schema-in-node-js.md#creating-a-schema-and-validating-data) in the context of JSON Schema refers to the outcome of applying the entire JSON Schema to the entire instance document. This outcome can encompass more than just a boolean assertion and may include various output formats, such as error messages, error codes, or detailed validation reports. It signifies whether the instance document adheres to the rules and constraints specified in the schema. The validation result signifies whether the instance document passes or fails validation against the [schema](#schema). ### vocabulary