pkcs11 — archive

[Dennis Hamilton]

Check the OASIS rules for specification consistency and conflicts between document text and external files (schemas, programming-language codes for some purpose, etc.). An OASIS PKCS#11 specification needs to align with that. With regard to in-text inclusion of code snippets, it is important to identify their standing and also deal with any conflicts between any "normative" snippets and normative statements in the text. - Dennis PS: I am not a believer, generally, that code is the specification. However, if that is intended there is a new task: It is necessary to normatively rely on the programming language chosen and deal with profiling of the language elements used where its specification is silent or dependent on agreements beyond that specification. PPS: The objective for a specification that is intended to support interoperable implementations is that such a specification-conformant, interoperable implementation can be achieved without having to consult an implementation. There are the usual caveats about what skills and level of art are required for accomplishing that with the specification.