I love that you are noodling in the open, and getting feedback / impressions early -- that's the recipe for doing something new, better! Now, unfiltered first

I love that you are noodling in the open, and getting feedback / impressions early -- that's the recipe for doing something new, better! Now, unfiltered first thoughts... Have you used SOAP RPC and is it clear why the industry (outside of banking and financial services that depend on correctness!) largely shifted to JSONic REST? At first exposure to this, the delimiters feel like line noise, as if SOAP and a lineprinter got together and said, "How could this offer less utility while being more opaque?" There's a cognitive tax on something being unlike other things, which is why so many substitutions end up adopting handlebars/mustache type syntax, or so many things look like INI/TOML/YAML/etc. Have you looked at JSON5, XML + XSLT, JSONNET and the like? What about JSON Schema and similar? ( https://json-schema.org/understanding-json-schema/reference/comments https://json-schema.org/understanding-json-schema/reference/... ) Not saying any of those are be-all end-all, they are not. But it would be super helpful to have a "Why not X" page on your README that shows you've considered SOTA across the landscape, and why that doesn't work for you. See, for example: https://hitchdev.com/hitchstory/why-not/ https://hitchdev.com/hitchstory/why-not/