Attempt to better clarify differences between JSON Schema and other projects

Author: Relequestual

docs/openjsf/application.md

@@ -70,18 +70,21 @@ Use cases such as code generation, form generation, database generation (and val
 
 - How does it differ from other projects?
 
-Some consider JSON Schema to be an Data Definition Language, others are only familiar with it through the use of OpenAPI or AsyncAPI.
+JSON Schema is a domain-specific declarative language for validating and annotating JSON data.
 
-It cannot be compared to OpenAPI, as they are different. OpenAPI 3.1 now defers the schema definitions to JSON Schema[1]. Nor can it be compared to JSON-LD, which is designed for linked data. Nor can it be compared to schema.org which provides data semantics.
+It cannot be compared to OpenAPI. OpenAPI 3.1 now defers the schema definitions to the most recent release of JSON Schema[1]. Nor can it be compared to JSON-LD, which is designed for linked data. Nor can it be compared to schema.org which provides data semantics.
 
 A possible comparison is to JSON Type Definition (RFC 8927), which is designed for code generation.
 By way of comparison, JSON Schema has an extensive test suite, many more implementations and languages supported, and has vastly more use in the ecosystem.
 
-Procol Buffers and Avro do not just specify a structure, but define the "over the wire" format and serialisation method. JSON Schema does not do that.
+Protocol Buffers and Avro do not just specify a structure, but define the "over the wire" format and serialisation method. JSON Schema is designed for validation of JSON data rather than data definitions, enabling the definition of more complex validation constraints than would otherwise be possible.
 
 In comparison to Joi, a popular and well used Javascript validation library, JSON Schema offers a language agnostic and portable validation mechanism.
 
-Beyond validation, at its core, JSON Schema enables the definition of contracts in terms of a JSON data structure, something of critical importance to REST like APIs.
+Many times we see comparisons made from one solution to JSON Schema. Often, they miss several key understandings.
+In summary, JSON Schema is language agnostic, declarative constraints based, interoperable, validation and annotation for JSON.
+
+Beyond validation and annotation, we are actively supporting special interest groups to define new vocabularies and dialects to add additional semantics and mechanisms to JSON Schema in order to support other use cases, such as UI generation, code generation, and databases.
 
 ## Desired Initial Project Phase