Ian Ward

Great to see huge progress on this by @TkTech https://github.com/ckan/ckan/pull/3485

There is some overlap with work I'm doing on scheming: UI snippets for viewing/selecting taxonomies values, validators for schema and a method to store and share taxonomies and their translated...

@davidread will do when the vocabulary/choice parts are a little more complete. For now there are the [form and display snippets](https://github.com/open-data/ckanext-scheming#form_snippet) and use of the [IValidators](http://docs.ckan.org/en/latest/extensions/plugin-interfaces.html#ckan.plugins.interfaces.IValidators) for registering new validators...

I'm planning to publish the taxonomies as a part of the scheming schemas I will be using. There's no interface for updating because the schemas are considered to be site...

data.gov uses groups for some taxonomies. The plus is groups can have extra fields to support multilingual representations and SKOS information. Some negatives are the group permission model would allow...

Thank you for this Eric. We've arrived at our current imperfect state of dependency management after struggling with some of the ideas you present above. Semantic versioning is a nice...

:+1: really looking forward to this too

Maybe we can step back for a moment. What's the actual problem you've got that makes you want to change the ini file to another format?

That's interesting! I'm on the other side of the "more understandable" argument. I really like the ini format *because* it's so limited. I also hate editing JSON in a text...

Let's do this for ipython notebooks too