XSDs are far from perfect, but waaay more powerful than json schema.
XSLT has its problems, but completely transforming a document to a completely different structure with just a bit of text is awesome. I had to rewrite a relatively simple XSLT in Java and it was something like 10 times more lines.
XSD and XSLT files alone can replace half the JSON applications I’ve seen. I can see why it’s easier to take the barebones JSON notation and reinvent the wheel, but those tiny programs are the “Excel+VBA” of web applications.
Did you write your transform logic ground-up or use a third-party library? I’m not a Java dev, but I feel like someone has to have already solved this problem in pretty much every language anyone actually uses.
And there are some truly magic tools.
XSDs are far from perfect, but waaay more powerful than json schema.
XSLT has its problems, but completely transforming a document to a completely different structure with just a bit of text is awesome. I had to rewrite a relatively simple XSLT in Java and it was something like 10 times more lines.
XSD and XSLT files alone can replace half the JSON applications I’ve seen. I can see why it’s easier to take the barebones JSON notation and reinvent the wheel, but those tiny programs are the “Excel+VBA” of web applications.
And don’t forget about namespaces. Look at formats like HAL and ODATA that try to add HATEOAS onto JSON.
Did you write your transform logic ground-up or use a third-party library? I’m not a Java dev, but I feel like someone has to have already solved this problem in pretty much every language anyone actually uses.