24944 2014-03-05 20:49:37 +0000 Ensure references are consistent and correctly categorized 2014-11-07 01:34:33 +0000 1 1 1 Unclassified Web Cryptography Web Cryptography API Document unspecified PC All RESOLVED FIXED P2 minor --- 1 watsonm watsonm sleevi virginie.galindo oldest_to_newest 101917 0 watsonm 2014-03-05 20:49:37 +0000 References should be consistently written as [REF] in square brackets. References need to be correctly categorized as normative or informative. 101930 1 sleevi 2014-03-05 22:00:18 +0000 So, it needs to be clarified The [REF] form is for referring to the short-hand identifier of a spec that appears within the references section. However, there are still times where we want to say the full part of the specification. Something like "Refer to Section 3 of PKCS #11 [PKCS11]" Presumably 101932 2 watsonm 2014-03-05 22:02:26 +0000 (In reply to Ryan Sleevi from comment #1) > So, it needs to be clarified > > The [REF] form is for referring to the short-hand identifier of a spec that > appears within the references section. However, there are still times where > we want to say the full part of the specification. > > Something like > > "Refer to Section 3 of PKCS #11 [PKCS11]" > > Presumably I would say "Refer to Section 3 of [PKCS11]" 113072 3 virginie.galindo 2014-10-14 09:01:51 +0000 In order to progress towards exit to Last Call for the Web Crypto API, the chair suggests the following resolution for that bug. Resolution : Bug RESOLVED, editors will edit the specification to harmonize with consistent usage of specification references and/or section of specification reference. If none objects before the 20th of Oct @20:00 UTC, this resolution will be endorsed. 114630 4 watsonm 2014-11-07 01:34:33 +0000 https://dvcs.w3.org/hg/webcrypto-api/rev/586d852d2679