I liked your survey ;) It would be great if you could disclose (in a few days or so) how many visitors took part in it compared to how many people your site visited!
I find your concept a little bit messy though (while your website design is really clean, I love it!).
I think it's because you described so many ideas without a lot of technical explanations. Your scenarios are helpful, but they are also quite superficial - I don't see exactly how your solution might be of help there. I also had difficulties extrapolating how your solution might work technically from you example document.
I think you need a very robust and clear implementation for it to be really useful!
Btw, I spent some significant time on a typed data description language meant to be an alternative to JSON, also with extensive schema support. I had a vision very similar to yours, but I failed to implement it. It just turned out to be too hard to do it so that its usage is always frictionless.
Just a couple of days ago, however, I started to port some of my ideas to a very slim JSON-Schema alternative. As a key difference to your idea, I don't want to include turing complete validators into the schema but rather use globally unique type names so that these validators can be implemented somewhere else in arbitrary programming languages. It also allows for automatic UI generation.
If you want to stay in touch and exchange ideas, you can reach out to me on twitter (hediet_dev)!
I find your concept a little bit messy though (while your website design is really clean, I love it!). I think it's because you described so many ideas without a lot of technical explanations. Your scenarios are helpful, but they are also quite superficial - I don't see exactly how your solution might be of help there. I also had difficulties extrapolating how your solution might work technically from you example document.
I think you need a very robust and clear implementation for it to be really useful!
Btw, I spent some significant time on a typed data description language meant to be an alternative to JSON, also with extensive schema support. I had a vision very similar to yours, but I failed to implement it. It just turned out to be too hard to do it so that its usage is always frictionless.
Just a couple of days ago, however, I started to port some of my ideas to a very slim JSON-Schema alternative. As a key difference to your idea, I don't want to include turing complete validators into the schema but rather use globally unique type names so that these validators can be implemented somewhere else in arbitrary programming languages. It also allows for automatic UI generation.
If you want to stay in touch and exchange ideas, you can reach out to me on twitter (hediet_dev)!