[Docs] Clarify "picoschema" (and "nanoschema" ?) vs standard JSON Schema in Dotprompt documentation

[vorburger]

I'm a bit confused, because:

So https://google.github.io/dotprompt/reference/frontmatter/#output (currently) states that, quote: "Schema representing the expected output from the prompt. Must correspond to a JSON Schema object type."

But the example on https://google.github.io/dotprompt/getting-started/#example-prompt-file or https://github.com/google/dotprompt?tab=readme-ov-file#example-prompt-file uses something which does not appear to be valid JSON schema... as in, the https://json-schema.org thing? It doesn't look like e.g. https://json-schema.org/learn/getting-started-step-by-step.

I kind of gathered between the lines somewhere else on the doc that this is "picoschema"? Or "nanoschema"? But... what is that? According to almighty Google https://www.google.com/search?q=json+picoschema, that's something related to Raspberry Pi? 😆 (I know it's not, sorry I'm just having fun, on a Sunday afternoon.)

Perhaps this could be made clearer in the documentation? With links to wherever the specifications for this "yet another" new schema language are? (If there is any.) Doesn't the world have enough schema languages already? I'm collecting them, on https://docs.enola.dev/concepts/core/#schemas!

Jokes apart, do any language models dig picoschema or nanoschema? Or is the expectation that https://google.github.io/dotprompt/implementors/ "map" this? And the existing implementations listed on https://google.github.io/dotprompt/implementations/, in TS, Go and Dart all do this? Consistently?! 😺

I'm considering only supporting plain old boring standard JSON Schema in my Java implementation of dotprompt (see #301), at least initially. Entirely compliant with the (currently) documentation specification of DotPrompt! 😄

[vorburger]

Perhaps this could be made clearer in the documentation? With links to wherever the specifications for this "yet another" new schema language are? (If there is any.) Doesn't the world have enough schema languages already? I'm collecting them, on https://docs.enola.dev/concepts/core/#schemas!

I have seen https://google.github.io/dotprompt/reference/picoschema/.

At the very least, https://google.github.io/dotprompt/reference/frontmatter/ should probably link to that? (I could raise a PR, after #305.)

And https://google.github.io/dotprompt/implementors/ would then have to say that implementors are expected to write converters from Picoschema to JSON schema?

[mbleigh]

Yes, https://google.github.io/dotprompt/reference/picoschema/ is the reference for Picoschema and implementors should also be implementing a Picoschema-to-JSON-Schema converter. PRs welcome to clarify here - the documentation site was thrown together pretty hastily and is likely in need of plenty of updates.