What is naming convention for documents?

A File Naming Convention (FNC) is a framework for naming your files in a way that describes what they contain and how they relate to other files. Developing an FNC is done through identifying the key elements of the project, the important differences and commonalities between your files.

What is the naming conventions of a database?

For the traditional naming convention: Database names must only consist of the letters a to z (both lower and upper case allowed), the numbers 0 to 9 , and the underscore ( _ ) or dash ( – ) symbols. This also means that any non-ASCII database names are not allowed. Database names must always start with a letter.

What are naming conventions examples?

Use these alternatives instead:

  • Underscores (e.g. file_name. xxx)
  • Dashes (e.g. file-name. xxx)
  • No separation (e.g. filename. xxx)
  • Camel case, where the first letter of each section of text is capitalized (e.g. FileName. xxx)

How do you write a naming convention?


  1. Short but meaningful names.
  2. Avoid repetition and redundancy.
  3. Use capital letters to delimit words.
  4. Use two digit numbers.
  5. Write dates back to front.
  6. Surname followed by initials.
  7. Avoid common words.
  8. Order elements appropriately.

How do you do naming conventions?

File Naming Conventions

  1. Project lead’s last name or initials.
  2. File creator’s last name or initials.
  3. Project name/acronym.
  4. Date file created/generated (in YYYY-MM-DD format)
  5. Version number (with leading zeroes)

Why do we need a naming convention?

Why use naming conventions? Naming records consistently, logically and in a predictable way will distinguish similar records from one another at a glance, and by doing so will facilitate the storage and retrieval of records, which will enable users to browse file names more effectively and efficiently.

How do you create a standard naming convention?

Avoid special characters; only use alphanumeric characters. Avoid using numeric digits, except for the ending sequence number. Avoid the use of specific product or vendor names, as those can be subject to change. (There are some generally accepted exceptions: Oracle, SMS, SQL, CTX, VMW)