-
Example: https://mila.quebec/en/publications/
It would be nice to reuse the same code as in the Mila website. Not sure if that's 'easily' possible via RTD
-
OGC documents have been confirmed to have both a "Terms and definitions" clause and a "Glossary" that is an annex.
The "Terms and definitions" clause will follow ISO practice, which allows:
* "T…
-
User AdrianR points out that resolution.rst does not actually include any information about how to include dQ information for slit-smeared data in a data file. We do, however, provide some information…
smk78 updated
2 years ago
-
Only CryptoSuites that fully define both public and private key representations should be accepted as potential normative deliverables.
For suites built on JWK or PGP this is not an issue.
For s…
-
When I include this line in metanorma references
`* [[[BS202000,BS 202000:2020]]], _Standardization management system_`
this error will appear
```
[relaton] BS 202000 does not have a recogni…
-
Given that minisign aims to be a modern crypto tool for the future, resiliance to future advances in quantum computing should be considered.
This could be implemented by offering an option to use h…
-
Thanks for creating the JSON Schema variant of the vulnerability extension. This prompted me to take a run at describing some real world data using the format. Here's the full example https://gist.git…
-
@selfissued wrote:
> We should be removing public key formats from the spec - not adding them. We should get down to one key format to increase interoperability of implementations - preferably JWK.
…
-
Should also we move the ASN.1 schema from Appendix B of
{{?I-D.raza-ace-cbor-certificates}} here and let it have it by reference?
The compression methods defined in {{?I-D.ietf-tls-certificate-com…
-
Given that age aims to be the encryption tool for the future, it should include (asymmetric) crypto that will survive the expected arrival of quantum computers.
openssh already has this implemented…