D.3 Naming conventions

33.1283GPPProtocol and procedures for Lawful Interception (LI)Release 18SecurityStage 3TS

Table D.3-1: Naming conventions

D.3.1	To meet ASN.1 syntax rules, the first character of each ASN.1 field name are lower-cased.
D.3.2	To meet ASN.1 syntax rules, the first character of an ASN.1 type name are upper-cased.
D.3.3	To meet ASN.1 syntax rules, the first character of a field or a type name is not a number.
D.3.4	Only the character ranges A-Z, a-z and 0-9 are used in names.
D.3.5	Names are CamelCased, where the first character of each word is upper-cased (except for the first character of the name – see rule D.3.1).
D.3.6	Any acronyms in a name should be entirely upper-cased (except for the first character of the name – see rule D.3.1).

ExampleBadStructure ::= SEQUENCE

{

FirstField [1] FirstFieldType, — D.3.1 First letter of field is upper case

secondField [2] secondFieldType, — D.3.2 First letter of type is lower case

3rdField [3] 3rdFieldType, — D.3.3 Names starts with digit

fourth-field [4] Fourth_Field_Type, — D.3.4 Names include hyphen and underscore

fifthfield [5] Fifthfieldtype, — D.3.5 Names are not camelCased

msisdn [6] MSISDN, — D.3.6 Acronyms in field name not wholly upper-cased

mSISDN [7] Msisdn — D.3.6 Acronyms in type name not wholly upper-cased

}

Figure 1 – Naming convention counter-examples