Create GLOSSARY.md

[Lorp]

A quick first draft of a glossary. Please add new definitions, fix existing ones, add links and correct organizational details.

[davelab6]

@Lorp and @alerque , now that #1 is resolved, do you agree to those terms such that @vlevantovsky can merge this?

[alerque]

See my comment here. TL;DR: I'm fine with my past and future contribution(s) to this repository being bound by the ISO declaration and used according to their copyright and data protection policies, but I also release my own contributions under the terms of the Apache License so that they can potentially be re-used in other project(s) by non ISO entities — and I've expressed my opinion that it would be useful and in the spirit of open source for all contributors to similarly release their contributions under more liberal & less ambiguous terms so that we don't end up is a ridiculous catch 22 situation again someday like we presently are with the current OFF.

[HinTak]

Thanks for doing the work - learned a few acronyms myself, reading it.

[davelab6]

I'd like to define here what is commonly understood to be a editorial change, an incremental technical change, and a backwards incompatible technical change; and then to get GitHub issue tags set up for these.

[Lorp]

@Lorp and @alerque , now that #1 is resolved, do you agree to those terms such that @vlevantovsky can merge this?

Assuming you’re talking about the MIT license, yes, I agree.

[alerque]

@Lorp No, unfortunately that was not the resolution to that issue. I'm thinking we should open a new one because that one is not only closed but pretty significantly sidetracked in tangential discussion.

[davelab6]

@Lorp the license is as stated in #1 , it's the standard ISO contribution agreement. Are you good with that?