Schema Specification and Reference Implementation

[veritas2023]

Schema Registry provides support for schema evolution so that the data can be evolved over time and still work with older or newer producers and consumers and vice versa. Most serialization models, especially the ones that aim for portability across different platforms and languages, rely on a schema that describes how the data is serialized in the binary payload. In order to serialize the data and then to interpret it, both the sending and receiving sides must have access to a schema that describes the binary format. In certain cases, the schema can be inferred from the payload type on serialization or from the target type on deserialization.

However, many applications benefit from having access to an explicit schema that describes the binary data format. A schema registry could let you store schema information in a textual format (typically JSON) and makes that information accessible to various applications that need it to receive and send data in binary format.

We believe that data exchange formats are the basis for facilitating system interoperability. Although there are some popular implementations in the industry like the spring cloud schema registry styles, they do not communicate with each other, resulting in fragmented ecological communities. OpenSchema, as an industry collaborative effort to address such problems.

In this summer code campaign, we will open up the following questions, and we hope you could finish the following task:

1. Reference Implementation SchemaGrid, could bridge nowadays exist implementation.
2. OpenMessaging SDK support to get the schema from the SchemaGrid.