Identifier

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Identifiers on the back of a statue in the Louvre

An identifier is a name that identifies (that is, labels the identity of) either a unique object or a unique class of objects, where the "object" or class may be an idea, physical [countable] object (or class thereof), or physical [noncountable] substance (or class thereof). The abbreviation ID often refers to identity, identification (the process of identifying), or an identifier (that is, an instance of identification). An identifier may be a word, number, letter, symbol, or any combination of those.

The words, numbers, letters, or symbols may follow an encoding system (wherein letters, digits, words, or symbols stand for (represent) ideas or longer names) or they may simply be arbitrary. When an identifier follows an encoding system, it is often referred to as a code or ID code. Identifiers that do not follow any encoding scheme are often said to be arbitrary IDs; they are arbitrarily assigned and have no greater meaning. (Sometimes identifiers are called "codes" even when they are actually arbitrary, whether because the speaker believes that they have deeper meaning or simply because he is speaking casually and imprecisely.)

ID codes inherently carry metadata along with them. (For example, when you know that the food package in front of you has the identifier "2011-09-25T15:42Z-MFR5-P02-243-45", you not only have that data, you also have the metadata that tells you that it was packaged on September 25, 2011, at 3:42pm UTC, manufactured by Licensed Vendor Number 5, at the Peoria, IL, USA plant, in Building 2, and was the 243rd package off the line in that shift, and was inspected by Inspector Number 45.) Arbitrary identifiers carry no metadata. (For example, if your food package just says 100054678214, its ID may not tell you anything except identity—no date, manufacturer name, production sequence rank, or inspector number.)

The unique identifier (UID) is an identifier that refers to only one instance—only one particular object in the universe. A part number is an identifier, but it is not a unique identifier—for that, a serial number is needed, to identify each instance of the part design. Thus the identifier "Model T" identifies the class (model) of automobiles that Ford's Model T comprises; whereas the unique identifier "Model T Serial Number 159,862" identifies one specific member of that class—that is, one particular Model T car, owned by one specific person.

The concepts of name and identifier are denotatively equal, and the terms are thus denotatively synonymous; but they are not always connotatively synonymous, because code names and ID numbers are often connotatively distinguished from names in the sense of traditional natural language naming. For example, both "Jane Smith" and "Employee Number 8547" are identifiers for the same specific human being; but normal English-language connotation may consider "Jane Smith" a "name" and not an "identifier", whereas it considers "Employee Number 8547" an "identifier" but not a "name". This is an emic distinction rather than an etic one.

Metadata[edit]

In metadata, an identifier is a language-independent label, sign or token that uniquely identifies an object within an identification scheme.

The suffix identifier is also used as a representation term when naming a data element.

In computer science[edit]

In computer science, identifiers (IDs) are lexical tokens that name entities. Identifiers are used extensively in virtually all information processing systems. Identifying entities makes it possible to refer to them, which is essential for any kind of symbolic processing.

In computer languages[edit]

In computer languages, identifiers are tokens (also called symbols) which name language entities. Some of the kinds of entities an identifier might denote include variables, types, labels, subroutines, and packages.

Which character sequences constitute identifiers depends on the lexical grammar of the language. A common rule is alphanumeric sequences, with underscore also allowed, and with the condition that it not begin with a digit (to simplifying lexing by avoiding confusing with integer literals) – so foo, foo1, foo_bar, _foo are allowed, but 1foo is not – this is the definition used in earlier versions of C and C++, Python 2, and many other languages. Later versions of these languages, along with many other modern languages support almost all Unicode characters in an identifier. However, a common restriction is not to permit whitespace characters and language operators; this simplifies tokenization by making it free-form and context-free. For example, forbidding + in identifiers (due to its use as a binary operation) means that a+b and a + b can be tokenized the same, while if it were allowed, a+b would be an identifier, not an addition. Whitespace in identifier is particularly problematic, as if spaces are allowed in identifiers, then a clause such as if rainy day then 1 is legal, with rainy day as an identifier, but tokenizing this requires the phrasal context of being in the condition of an if clause. Some languages do allow spaces in identifiers, however, such as ALGOL 68 and some ALGOL variants – for example, the following is a valid statement: real half pi; which could be entered as .real. half pi; (keywords are represented in boldface, concretely via stropping). In ALGOL this was possible because keywords are syntactically differentiated, so there is no risk of collision or ambiguity, spaces are eliminated during the line reconstruction phase, and the source was processed via scannerless parsing, so lexing could be context-sensitive.

In most languages, some character sequences have the lexical form of an identifier but are known as keywords – for example, if is frequently a keyword for an if clause, but lexically is of the same form as ig or foo namely a sequence of letters. This overlap can be handled in various ways: these may be forbidden from being identifiers – which simplifies tokenization and parsing – in which case they are reserved words; they may both be allowed but distinguished in other ways, such as via stropping; or keyword sequences may be allowed as identifiers and which sense is determined from context, which requires a context-sensitive lexer. Non-keywords may also be reserved words (forbidden as identifiers), particularly for forward compatibility, in case a word may become a keyword in future. In a few languages, e.g., PL/1, the distinction is not clear.

For implementations of programming languages that are using a compiler, identifiers are often only compile time entities. That is, at runtime the compiled program contains references to memory addresses and offsets rather than the textual identifier tokens (these memory addresses, or offsets, having been assigned by the compiler to each identifier).

In languages that support reflection, such as interactive evaluation of source code (using an interpreter or an incremental compiler), identifiers are also runtime entities, sometimes even as first-class objects that can be freely manipulated and evaluated. In Lisp, these are called symbols.

Compilers and interpreters do not usually assign any semantic meaning to an identifier based on the actual character sequence used. However, there are exceptions.

For example:

  • In Perl a variable is indicated using a prefix called a sigil, which specifies aspects of how the variable is interpreted in expressions.
  • In Ruby a variable is automatically considered immutable if its identifier starts with a capital letter.
  • In Fortran, the first letter in a variable's name indicates whether by default it is created as an integer or floating point variable.
  • In Go, the capitalization of the first letter of a variable's name determines its visibility (public for uppercase, private for lowercase).

In some language such as Go, identifiers uniqueness is based on their spelling and their visibility.[1]

In HTML an identifier is one of the possible attributes of an HTML element. It is unique within the document.

Ambiguity[edit]

IDs versus UIDs[edit]

Many resources may carry multiple identifiers. Typical examples are:

  • One person with multiple names, nicknames, and forms of address (titles, salutations)
    • For example: One specific person may be identified by all of the following identifiers: Jane Smith; Jane Elizabeth Meredith Smith; Jane E. M. Smith; Jane E. Smith; Janie Smith; Janie; Little Janie (as opposed to her mother or sister or cousin, Big Janie); Aunt Jane; Auntie Janie; Mom; Grandmom; Nana; Kelly's mother; Billy's grandmother; Ms. Smith; Dr. Smith; Jane E. Smith, PhD; and Fuzzy (her jocular nickname at work).
  • One document with multiple versions[2]
  • One substance with multiple names (for example, CAS index names versus IUPAC names;[3][4] INN generic drug names versus USAN generic drug names versus brand names)

The inverse is also possible, where multiple resources are represented with the same identifier (discussed below).

Implicit context and namespace conflicts[edit]

Many codes and nomenclatural systems originate within a small namespace. Over the years, some of them bleed into larger namespaces (as people interact in ways they formerly hadn't, e.g., cross-border trade, scientific collaboration, military alliance, and general cultural interconnection or assimilation). When such dissemination happens, the limitations of the original naming convention, which had formerly been latent and moot, become painfully apparent, often necessitating retronymy, synonymity, translation/transcoding, and so on. Such limitations generally accompany the shift away from the original context to the broader one. Typically the system shows implicit context (context was formerly assumed, and narrow), lack of capacity (e.g., low number of possible IDs, reflecting the outmoded narrow context), lack of extensibility (no features defined and reserved against future needs), and lack of specificity and disambiguating capability (related to the context shift, where longstanding uniqueness encounters novel nonuniqueness). Within computer science, this problem is called naming collision. The story of the origination and expansion of the CODEN system provides a good case example in a recent-decades, technical-nomenclature context. The capitalization variations seen with specific designators reveals an instance of this problem occurring in natural languages, where the proper noun/common noun distinction (and its complications) must be dealt with. A universe in which every object had a UID would not need any namespaces, which is to say that it would constitute one gigantic namespace; but human minds could never keep track of, or semantically interrelate, so many UIDs.

Identifiers in various disciplines[edit]

A small sample of various identifiers

Identifier Scope
atomic number, corresponding one-to-one with element name international (via ISV)
Australian Business Number Australian
CAGE code U.S. and NATO
CAS registry number originated in U.S.; today international (via ISV)
CODEN originated in U.S.; today international
Digital object identifier (DOI, doi) Handle System Namespace, international scope
DIN standard number originated in Germany; today international
E number originated in E.U.; may be seen internationally
EC number
Employer Identification Number (EIN) U.S.
Global Trade Item Number international
Group identifier many scopes, e.g., specific computer systems
International Chemical Identifier international
International Standard Book Number (ISBN) ISBN is part of the EAN Namespace; international scope
International Standard Serial Number (ISSN) international
ISO standard number, e.g., ISO 8601 international
Library of Congress Control Number U.S., with some international bibliographic usefulness
Personal identification number many scopes, e.g., banks, governments
Personal identification number (Denmark) Denmark
Product batch number
Serial Item and Contribution Identifier U.S., with some international bibliographic usefulness
Serial number many scopes, e.g., company-specific, government-specific
Service batch number
Social Security Number U.S.
Tax File Number Australian

See also[edit]

Notes[edit]

  1. ^ "The Go Programming Language Specification - The Go Programming Language". Golang.org. 2013-05-08. Retrieved 2013-06-05. 
  2. ^ University of Glasgow. "Procedure for Applying Identifiers to Documents". Retrieved 28 April 2009. 
  3. ^ Advanced Chemistry Development. "IUPAC vs. CAS Index". Retrieved 28 April 2009. [dead link]
  4. ^ University of Pennsylvania. "Information on Chemical Nomenclature". Retrieved 28 April 2009.