Hacker News Reader

The Article only mentioned it's string restrictions, but I'm still interested in how they formalize and implement their schemas. It's granted that xsd is pretty messy, but exposing a schema like this - or with alternative definition languages - goes a long way in helping client adaption seeing as there are a trillion autopwn validation and binding tools available.

View on HN

Exactly. I like how you threw binding in there too; I use schema languages (such as XSD) for binding at least as much as for validation. Maybe it's because I program in a statically typed language, but I really apprecicate the value of schema's and related tools - even while acknowledging the schema languages themselves can be messy and imperfect.

I sort of like schema validation, but it makes it a pain to add things to your objects later if clients of your API are depending on that (they will break when you add something).

Reply on news.ycombinator.com