Schemas are currently defined in a very specific json format. That's fine for most uses, but to make it more accessible to end users and especially for something like an obsidian plug-in, we could support the specification of a schema in the form of either yaml or markdown with enough structure to specify entities and what's required, and in particular rules that can sit alongside content. This allows a plug-in user to specify their schema and their rules for their content in a more approachable way that could get converted into a json schema and validated and then used as usual. I have in mind some idea that this can be an sctx plug-in point where the markdown plugin for example can provide a schema. The details of that need to be worked out though. Indeed, it may be simpler if it's not a pluggable thing and a schema can be provided at some layer in the api/sdk to then be available downstream.
Schemas are currently defined in a very specific json format. That's fine for most uses, but to make it more accessible to end users and especially for something like an obsidian plug-in, we could support the specification of a schema in the form of either yaml or markdown with enough structure to specify entities and what's required, and in particular rules that can sit alongside content. This allows a plug-in user to specify their schema and their rules for their content in a more approachable way that could get converted into a json schema and validated and then used as usual. I have in mind some idea that this can be an sctx plug-in point where the markdown plugin for example can provide a schema. The details of that need to be worked out though. Indeed, it may be simpler if it's not a pluggable thing and a schema can be provided at some layer in the api/sdk to then be available downstream.