iglu

As far as I know, Snowplow is one of the largest active users of JSON Schema, and we maintain one of the larger repositories of JSON Schemas on the internet, https://github.com/snowplow/iglu-central After something of a hiatus, we are re-starting active work on our schema registry technology (https://github.com/snowplow/iglu). We'd love to be involved in new design work on the JSON Schema spec. How do we get the old (or new!) band back together?

Great question - we invented a system for this at Snowplow, called SchemaVer: http://snowplowanalytics.com/blog/2014/05/13/introducing-sch... SemVer doesn't work for data - for one thing, there is no concept of a "bug" in your data (so patches are meaningless). We have hundreds of companies actively using SchemaVer via the Snowplow (https://github.com/snowplow/snowplow/) and Iglu (https://github.com/snowplow/iglu/) projects.

Great read, thanks for sharing! If readers are interested in open source schema registries, check out: * https://github.com/confluentinc/schema-registry * https://github.com/snowplow/iglu Disclosure, I work on Iglu.

The guys at Snowplow Analytics are really into applying schemas to event streams, and will write or bang on about it at any opportunity: http://snowplowanalytics.com/blog/2014/07/11/on-the-benefits... http://snowplowanalytics.com/blog/2014/05/15/introducing-sel... https://github.com/snowplow/iglu I think there's a lot to be said for knowing for sure what shape your data is.

It looks like Teleport is trying to do too many things. Input validation systems are great - there's an excellent one for Python already, called Schematics (https://github.com/schematics/schematics). Declarative schema systems are also great - JSON Schema (http://json-schema.org/) is the industry standard for JSON. The clever thing about JSON Schema is that it is itself written using JSON - so it's completely language independent. A JSON Schema is a document which you can a) version and b) upload to a schema repository like Iglu (https://github.com/snowplow/iglu). I don't see any equivalent non-language-tied schema approach in Teleport. Thirdly, tooling to help document APIs is also a great aim - the go-to project here is Swagger (https://helloreverb.com/developers/swagger). These are all huge problems _in themselves_, and the above solut

I'm just finishing off the first release of Iglu, a schema repository initially for JSON Schemas, https://github.com/snowplow/iglu/wiki It's the first new product since we started work on Snowplow two and a half years ago. The idea is that you register your JSON Schemas in an Iglu repo and then software like Snowplow can go fetch the Schemas to check that incoming JSONs pass validation. There's also "Iglu Central" which is like Rubygems.org or Maven Central, but for schemas instead of code.