Quality standard enhancements

[vhirtham]

Just want to gather some ideas to enhance the workflow when dealing with quality standards

1. Provide a function to list all available quality standards
Self-explaining, I guess...

2. Provide quality standard diff function
I think it would be nice to provide some functionality to compare different versions of the same standard. A real simple version would just compare the manifests and list the schema mapping differences. A more advanced version could also compare the schemas using compare_nested or a similar function to list the schema diffs. Theoretically, we could use the advanced version to also compare the differences between two individual quality standards. I think such a tool would be really beneficial for the end-user so that he doesn't have to figure out the differences by comparing schemas manually.

3. Wrap important static functions by free functions
Might be unnecessary, but I think for the user it is more convenient to just write enable_quality_standard(...) instead of Config.enable_quality_standard(...). Also helps to keep user code shorter ;)

4. add_quality_standard should accept path like objects
This way, the user can skip the creation of the quality standard object and just provide the path to it. add_quality_standard will create the object internally

[marscher]

Just my fifty cents:

1. Agreed
2. A diff tool for nested structures seems like good idea, we could use it all over the place. However it could be come tricky to implement for arbitrary types.
3. That's the way to go for a user frontend
4. Agreed, since easier to use.

[CagtayFabry]

regarding 2. Provide quality standard diff function

can we create some kind of diff output using git as a simple hack?