Type Alias IDeepSeekSchema

Type schema info of the DeepSeek.

IDeepSeekSchema is a type schema info of the DeepSeek function calling.

IDeepSeekSchema seems fully supporting the JSON schema definition of the OpenAPI v3.1 specification; OpenApiV3_1.IJsonSchema. By the way, as the OpenApiV3_1.IJsonSchema has too much ambiguous and duplicated expressions, IDeepSeekSchema is designed to be clear and simple for the DeepSeek function calling, by utilizing ILlmSchemaV3_1 which has been transformed from the OpenApi.IJsonSchema for the convenience and clarity.

Therefore, IDeepSeekSchema does not follow the entire specification of the OpenAPI v3.1. It has own specific restrictions and definitions. Here is the list of how ILlmSchemaV3_1 is different with the OpenAPI v3.1 JSON schema.

• Decompose mixed type: OpenApiV3_1.IJsonSchema.IMixed
• Resolve nullable property: OpenApiV3_1.IJsonSchema.__ISignificant.nullable
• Tuple type is banned: OpenApiV3_1.IJsonSchema.ITuple.prefixItems
• Constant type is banned: OpenApiV3_1.IJsonSchema.IConstant
• Merge OpenApiV3_1.IJsonSchema.IAnyOf to IDeepSeekSchema.IOneOf
• Merge OpenApiV3_1.IJsonSchema.IAllOf to IDeepSeekSchema.IObject
• Merge OpenApiV3_1.IJsonSchema.IRecursiveReference to IDeepSeekSchema.IReference
• Do not support OpenApiV3_1.IJsonSchema.ITuple type

If compare with the OpenApi.IJsonSchema, the emended JSON schema specification,

• IDeepSeekSchema.IParameters.$defs instead of the OpenApi.IJsonSchema.schemas
• Do not support OpenApi.IJsonSchema.ITuple type
• IDeepSeekSchema.properties and IDeepSeekSchema.required are always defined

For reference, if you've composed the IDeepSeekSchema type with the IDeepSeekSchema.IConfig.reference false option (default is false), only the recursive named types would be archived into the IDeepSeekSchema.IParameters.$defs, and the others would be escaped from the IDeepSeekSchema.IReference type.