[curious_man]

Data is central. More specifically: the information schema. This is useful for different cases, for example for data integration and database management (other than the coercion example in the post).

However this makes me think about "types-driven development" and static typing a-la Scala or Haskell. I'm more inclined toward the dynamic typing camp, but I'm still debating with myself about this.

In the first post about Schema and in the recently released talk about it static typing was cited but my key takeaway was: schema is about data-shape validation and documentation, similar to static typing but much more lightweight and a-la carte. So good so far. Now with the 0.2.0 version schemas (an information model encoding) can be leveraged to do coercions, code generation, etc. Schema encodings start to resemble abstract data types and a kind-of optional and a-la carte "static" typing. Maybe the main difference is that while static types are central and a way of thinking, here schemas are a tool that can be used in different ways.

Just my crude ruminations, soon I'll come around studying Haskell. What do you think?

edit: fixed a typo and added some minor things.