Re: [pkcs11] RE: Space or no space in standard name?

[Greg Scott <greg.scott@cryptsoft.com>]

Valerie, Sander,

Going back to the initial email thread in the PKCS #11 archive the references all have a space.

Earliest document I have has a space (image below).

However I would make a suggestion that if we were to mandate the space then it should be a non-breaking-space as it makes no sense to have the â#11â wrap to another Lin in any usage.

My $0.02

Greg

â

Greg Scott | CEO

Cryptsoft Pty Ltd

E: greg.scott@cryptsoft.com

M(AU): +61 406 255 166

M(US): +1 650 931 6039

On 4 June 2019 at 6:17:28 am, Fenwick, Valerie (valerie.fenwick@intel.com) wrote:

Looking at several historic versions of this and other PKCS standardsâ it seems âwith spaceâ is what it should be.

Â

I believe this is a very minor change, we should be able to do this fairly easily, as it is non impactful to the meaning.

Valerie

Â

From: pkcs11@lists.oasis-open.org <pkcs11@lists.oasis-open.org> On Behalf Of Temme, Sander
Sent: Monday, June 3, 2019 11:23 AM
To: pkcs11@lists.oasis-open.org
Subject: [pkcs11] Space or no space in standard name?

Â

Team,

Â

Our tech writer asked whether to use âPKCS #11â (with space) or âPKCS#11â (without space).Â

Â

In the v2.40 standard http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/pkcs11-base-v2.40.doc I see the space being used in the title, but in the introduction on page 6 we see four occurrences of âPKCS#11â without the space. The variant with the space is used 24 times in this document.Â

Â

In WD10 of the v3.0 base spec, Iâm seeing an additional occurrence of âPKCS#11â w/o space on page 35, and the ones in the Introduction are still there. This document also has 24 occurrences with the space.Â

Â

It seems to me that the variant with the space: âPKCS #11â is the one we intend to use. Is that correct? Worth a (minor) edit to the v3.0 documents?

Â

Thanks,

Â

Sander

Â

---

Â

SanderÂTemme
Senior Product Line Manager

Tel: +1 954 888 6283
Mob: +1 415 359 4260

nCipher Security

United States

www.ncipher.com

Â