SDT Schema

I originally used JsonSchema for the Sila stablecoin.
And it still looks decent, popularity-wise.

but... chatGBT to the rescue again. It gave me a one paragraph description of several alternatives. Here's a summary:

Avro
Use case: Data serialization and schema-based validation.
Key feature: Supports schema evolution, compact binary format, widely used in big data environments.

Protocol Buffers (Protobuf)
Use case: Data serialization with efficient performance.
Key feature: Language-neutral and platform-neutral schema, better performance than JSON in terms of size.

YAML Schema (Kwalify)
Use case: YAML document validation.
Key feature: Similar to JSON Schema but for YAML, supports complex constraints.

Schematron
Use case: XML validation, adaptable for JSON.
Key feature: Rule-based validation (using XSLT), very flexible for custom rules.

OpenAPI Specification (Swagger)
Use case: API definition, validation, and documentation.
Key feature: Describes RESTful API schema, automates client/server code generation.

JSON Logic
Use case: Logic-based validation for JSON data.
Key feature: Allows rule-based processing, applying complex business logic to JSON.

JOI
Use case: Data validation in JavaScript/Node.js apps.
Key feature: Chainable, flexible validation rules, excellent for dynamic data validation.

Zod
Use case: Type-safe validation in TypeScript/JavaScript.
Key feature: Type-safe, minimalistic, integrates well with TypeScript for developer-friendly validation.

Superstruct
Use case: Type-safe validation for JavaScript/TypeScript.
Key feature: Lightweight, flexible, and integrates well with modern TypeScript.

Pydantic
Use case: Data validation in Python.
Key feature: Type annotations-based, automatic JSON parsing and serialization.

GraphQL Schema
Use case: Schema definition for GraphQL APIs.
Key feature: Strong typing for queries, mutations, and responses in GraphQL.

Cerberus
Use case: Lightweight schema validation in Python.
Key feature: Flexible, extensible validation with support for complex constraints.

TJS (Tiny JSON Schema)
Use case: Lightweight JSON schema validation in JavaScript.
Key feature: Minimalistic, fast, perfect for small projects.

JSONPath
Use case: Querying and validating JSON data.
Key feature: Extracts data from JSON documents using path expressions, useful for dynamic validation.

Most of these are niche tools. GraphQL schema is tempting because it would be a better fit for a future security schema, polymorphic REST signatures. But ultimately, OpenAPI is probably the best fit to support 3rd party support, standard integration, etc, as it's actually a superset of JsonSchema.

ChatGBT: Therefore, OpenAPI can be viewed as a superset of JSON Schema in the context of describing APIs, where JSON Schema is used within OpenAPI for data validation.

ChatGBT: OpenAPI and Swagger: Swagger is a set of tools that work with OpenAPI specifications to help design, document, and generate code for APIs.

ChatGBT: OpenAPI and AWS: AWS services like API Gateway, Lambda, and Amplify support OpenAPI for defining and deploying RESTful APIs in the cloud.

ChatGBT: Thus, OpenAPI integrates well with both Swagger (for tools and documentation) and AWS (for deployment and management).

ChatGBT: OpenAPI itself doesn't directly generate Python dictionaries, but you can use tools like OpenAPI Generator or Swagger Codegen to generate Python code (including models), which can be easily converted to dictionaries.

OpenAPI for our schema definitions, validation and possibly REST signatures.

ChatGBT: "Summary of Best Python Versions for OpenAPI Development:
Best Versions: Python 3.8 or Python 3.9 for stability, long-term support, and compatibility with OpenAPI tools."