Eric Herman

I would like us to consider if a paper-friendly version could be included (or even inserted) into the last couple of pages of the standard.

We have plans to automate the generation of the template [About #1201](https://github.com/publiccodenet/about/issues/1201). Once that automation is done, then we should make the template generation a part of the release process,...

See: https://github.com/publiccodenet/standard/pull/380

We can also consider the option of linking to archive.org if something is not reliably available. e.g.: http://web.archive.org/web/20201027095103if_/https://www.youtube.com/watch?v=QWt6vB-cipE&gl=US&hl=en

In light of https://blog.publiccode.net/community%20call/2022/01/11/notes-from-community-call-6-january-2022.html , let's see what a good example repository teaches us about possible wording changes to "Bundle policy and code"

I do not see that it would be valuable to "own" and rewrite the definitions of "Open source" and "Open standard" since we are specifically building on top of the...

Perhaps we should use https://open-zaak.readthedocs.io/en/stable/support/security.html as an example.

https://github.com/publiccodenet/standard/blob/develop/_config.yml#L20-L21

Indeed, that can be read as a loophole. Okay, so let's consider the real-world use-cases. An ISO standard, like the C programming language [ISO/IEC 9899:2018](https://iso-9899.info/wiki/The_Standard), does not meet the definition...

In the case of https://en.wikipedia.org/wiki/ISO_8601 this may be important for data exchange. In both of these cases, it is not in reality a problem these standards are not open. What...