CAL’s Copyleft Licensing Rule

Continuing the discussion from Cryptographic Autonomy License draft v1.0-Beta:

Why conjoin both the functional characteristics of the license terms you require, compatibility, and also third-party approval, via OSI? Wouldn’t a good functionality specification be enough? If the concern is standardization, why not use some more accurate measure of it, like widespread adoption?