1 Definition and purpose
Identifiers are labels, codes, or symbols used to refer to a specific object, record, user, resource, or concept within an information system. Their main function is to make reference reliable, so that software and people can distinguish one item from another without ambiguity. In practice, identifiers are used across databases, operating systems, programming languages, communication protocols, and administrative systems.
1.1 Core meaning
At the most basic level, an identifier is a reference that stands in for something else. The referenced item may be a physical device, a document, a database row, a software object, or a person in a user account system. An effective identifier allows the system to retrieve, compare, track, or update that item consistently.
1.2 Role in information systems
Identifiers are a foundational part of information systems because they support storage, search, linkage, and exchange. They make it possible to keep records separate, connect related data, and reduce confusion when multiple items have similar names or attributes.
1.2.1 Distinguishing objects
A system often contains many objects that are similar in content or appearance. Identifiers distinguish them from one another even when descriptive details overlap. This separation is essential in databases, file systems, and networked applications, where two records may otherwise look identical.
1.2.2 Supporting lookup and reference
Identifiers also help systems locate items quickly. A lookup table, index, or directory may use an identifier as the key for retrieving associated information. This makes processing more efficient than searching by descriptive text alone.
1.3 Identifier versus name
A name usually carries human-readable meaning, while an identifier is primarily intended for reliable reference. The two may overlap, and many names function as identifiers in everyday use. However, names can change, vary by language, or be duplicated, while identifiers are often designed to remain stable and unambiguous within a given scope.
2 Types of identifiers
Identifiers vary according to how they are assigned, what they represent, and how widely they must remain unique. Some are meaningful to humans, while others are optimized for machine processing. The most common distinctions concern whether the identifier comes from the data itself, is generated separately, or is composed of several parts.
2.1 Natural identifiers
Natural identifiers are drawn from the real-world property of the item being identified. Examples include a product code already assigned by a manufacturer or a document number that is part of an institutional process. These identifiers can be convenient because they may already exist in the source domain, but they can also be subject to change if the underlying property changes.
2.2 Surrogate identifiers
Surrogate identifiers are artificial values created solely for identification. They do not encode meaning about the item and are usually assigned by the system. Database-generated numeric keys are a common example. Surrogate identifiers are often favored because they are simple, stable, and independent of business changes.
2.3 Composite identifiers
Composite identifiers combine two or more fields to form a unique reference. A library record might use a combination of branch code and item number, for instance. Such identifiers can be useful when no single field is sufficient, though they may be more cumbersome to manage.
2.4 Persistent identifiers
Persistent identifiers are intended to remain usable over long periods, even if the item moves, changes location, or is reorganized. They are common in digital libraries, archives, and content repositories. Their value lies in continuity, since references remain meaningful even when other attributes change.
2.5 Unique identifiers
Unique identifiers are values that are guaranteed not to repeat within a defined scope. The scope may be a single database, a software application, or a larger network of systems. Uniqueness is central to preventing collisions and ensuring that each reference points to only one item.
2.5.1 Locally unique identifiers
Locally unique identifiers are unique only within a limited environment, such as one database or one organization. They are often easier to generate and manage than globally unique values. Their usefulness depends on the system being able to interpret them in the correct context.
2.5.2 Globally unique identifiers
Globally unique identifiers are designed to be unique across many systems and domains. They are often used when data moves between organizations or when items must be referenced without dependence on a single local database. Their main advantage is that they reduce the risk of duplication across boundaries.
3 Identifier design
The design of an identifier affects how it is read, validated, stored, and exchanged. Good design balances technical reliability with usability. Systems may prefer terse machine-oriented values, or they may adopt structured forms that carry additional information.
3.1 Format and syntax
Format refers to the shape of the identifier, including character set, length, and arrangement. Syntax rules determine which values are acceptable and how they should be interpreted. These choices influence both software implementation and human interaction.
3.1.1 Alphanumeric identifiers
Alphanumeric identifiers use letters, numbers, or both. They are flexible and can support compact codes that are easier to remember than long numeric strings. However, they may require case handling or normalization rules to avoid confusion.
3.1.2 Numeric identifiers
Numeric identifiers consist only of digits. They are common in databases, account systems, and sequential numbering schemes. Their simplicity makes them efficient to store and process, though they may reveal ordering or volume information when assigned sequentially.
3.1.3 Structured identifiers
Structured identifiers include internal parts that convey meaning, such as a prefix for a category or a segment for location. This structure can aid sorting and inspection, but it may also make the identifier less flexible if the meaning of the parts changes over time.
3.2 Stability and immutability
A strong identifier is usually stable, meaning it does not change frequently, and ideally immutable, meaning it never changes after assignment. Stability reduces the risk of broken links, duplicate records, and synchronization problems. When identifiers must be altered, systems often preserve aliases or mapping tables to maintain continuity.
3.3 Uniqueness constraints
Uniqueness constraints are rules that prevent two items from receiving the same identifier in the same scope. Databases enforce these rules through indexes or key constraints, while other systems use assignment services or registries. Such constraints are essential for integrity and accurate reference.
3.4 Readability and usability
Some identifiers are optimized for human recognition, while others are designed mainly for machines. Readable identifiers can be easier to communicate, type, or troubleshoot. Yet highly readable forms may be longer, more descriptive, or more vulnerable to accidental pattern changes than compact system-generated values.
4 Identifiers in computing
Computing systems rely on identifiers at many levels, from database rows to programming objects and files stored on disk. The same general concept appears in different technical contexts, but the implementation varies according to purpose and architecture.
4.1 Database identifiers
Database identifiers distinguish records and support relationships among tables. They help maintain data integrity and make it possible to locate, join, and update rows efficiently. In relational systems, identifiers are often central to schema design.
4.1.1 Primary keys
A primary key is the main identifier for a row in a database table. It must be unique and non-null within that table. Primary keys are often used by other tables as reference points and are a key part of relational structure.
4.1.2 Foreign keys
A foreign key is an identifier in one table that refers to the primary key of another. It creates a link between related records and supports referential integrity. This relationship allows databases to represent connections such as customers and orders, or users and permissions.
4.1.3 Candidate keys
Candidate keys are fields or field combinations that could uniquely identify a row. One candidate key is chosen as the primary key, while others remain available as alternate unique references. Their presence reflects the fact that a single record may be identifiable in more than one way.
4.2 Programming identifiers
Programming languages use identifiers for variables, functions, classes, modules, and other named entities. These labels help programmers write readable code and help compilers or interpreters distinguish one symbol from another.
4.2.1 Variable names
Variable names identify data values stored in memory or in a program state. Good variable names improve clarity by indicating purpose, scope, or type. They are not usually unique across an entire program, but they must be distinct within the relevant context.
4.2.2 Function names
Function names identify reusable blocks of code that perform actions or return values. They often describe behavior in a concise way and may be part of an application programming interface. Clear function naming supports maintenance and code comprehension.
4.2.3 Class and object identifiers
Classes and objects are also referenced by identifiers. Class names identify templates or blueprints, while object identifiers may distinguish individual instances at runtime. In object-oriented systems, these identifiers help organize behavior and state.
4.3 File and resource identifiers
Files, resources, and media items are commonly identified through paths, addresses, or locator schemes. These identifiers let systems open, fetch, or link to content stored locally or across networks.
4.3.1 File paths
A file path identifies the location of a file within a directory structure. It may be absolute or relative, depending on the context. Paths are widely used in operating systems and application software to locate stored content.
4.3.2 Resource locators
Resource locators are strings that indicate where a resource can be found and how it can be accessed. They may include protocol information, host details, and a path. Their purpose is practical retrieval rather than only naming.
4.3.3 URIs and URLs
Uniform Resource Identifiers and Uniform Resource Locators are standardized forms used on the internet to identify and often locate resources. A URI is a broader identifier category, while a URL is a type that includes access information. These forms underpin web links, APIs, and many online services.
5 Network and system identifiers
Networks and operating systems use identifiers to distinguish devices, users, sessions, and transactions. These identifiers allow services to route communication, maintain state, and associate actions with particular endpoints or accounts.
5.1 Device identifiers
Device identifiers distinguish hardware units or network interfaces. They are used in inventory systems, access control, networking, and maintenance. Depending on context, they may be permanent, configurable, or derived from hardware properties.
5.1.1 MAC addresses
A MAC address identifies a network interface at the data-link layer. It is commonly associated with a device’s network hardware and is used for local network communication. In many environments, it serves as a low-level technical identifier.
5.1.2 Hardware serial numbers
A hardware serial number is assigned by a manufacturer to a specific device or component. It is frequently used for support, warranty tracking, asset management, and inventory control. Unlike network addresses, serial numbers are usually meant to label the physical unit itself.
5.2 User and account identifiers
User and account identifiers distinguish individuals or entities within authentication and administration systems. They connect actions, permissions, and records to a particular account, even when display names are similar or duplicated.
5.2.1 Usernames
A username is a common identifier used for login, display, or account lookup. It may be chosen by the user or assigned by the system. Usernames are often readable and memorable, though not always stable if a service permits changes.
5.2.2 Account numbers
Account numbers are structured identifiers used in banking, customer management, subscriptions, and similar systems. They are typically intended for precise reference rather than public description. Their main function is to support reliable internal handling of accounts.
5.3 Session and transaction identifiers
Session identifiers track a user’s active interaction with a system, while transaction identifiers distinguish individual operations or events. These values are important in web applications, payment systems, logging, and troubleshooting. They help connect related actions within a limited time or workflow.
6 Identifier generation
How an identifier is generated affects its reliability, scalability, and meaning. Generation strategies range from centralized allocation to decentralized creation, and each approach has trade-offs involving coordination, speed, and collision risk.
6.1 Centralized assignment
Centralized assignment uses a single authority or service to issue identifiers. This method can simplify uniqueness control and ordering, especially in smaller or tightly managed environments. Its limitation is that the central service can become a bottleneck or a dependency.
6.2 Distributed generation
Distributed generation allows multiple systems to create identifiers independently. It improves scalability and resilience, since a single point of issuance is not required. To work well, the scheme must minimize the chance of overlap across different nodes or sites.
6.3 Random and pseudo-random identifiers
Random or pseudo-random identifiers are generated from unpredictable sequences. They are useful when uniqueness matters more than readability or ordering. Such identifiers can be difficult to guess, which may also make them useful in security-sensitive settings.
6.4 Sequential identifiers
Sequential identifiers increase in order, often by one at a time. They are easy to understand and sort, and they can reveal the order in which records were created. Their predictability makes them simple but sometimes less suitable when concealment or distributed generation is important.
7 Identifier management
Once identifiers are assigned, systems must validate, resolve, rename, and protect them. Good management ensures that references continue to work correctly as data changes over time.
7.1 Validation
Validation checks whether an identifier conforms to expected rules. This may include length limits, character restrictions, checksum tests, or format patterns. Validation helps prevent errors before values are stored or transmitted.
7.2 Resolution and mapping
Resolution means translating an identifier into the item it denotes. Mapping may be needed when one system uses a different code from another, or when an item has multiple accepted references. These mechanisms are common in directories, registries, and interoperability layers.
7.3 Renaming and aliasing
When an identifier changes or a new label is introduced, an alias can preserve access through the older reference. Aliasing reduces disruption during migration, restructuring, or rebranding. It is especially useful when external systems continue to use legacy identifiers.
7.4 Collision handling
A collision occurs when two items are assigned the same identifier in a context where uniqueness is required. Systems handle collisions by rejecting the duplicate, generating a new value, or reconciling records through mapping. Preventing collisions is usually preferable to repairing them later.
8 Security and privacy
Identifiers can reveal information about systems, users, or internal structure. For that reason, they are often treated as metadata with security implications. Their exposure may be harmless in some settings and risky in others.
8.1 Identifiers as metadata
Identifiers often function as metadata because they describe relationships without necessarily exposing the full content of the item. They can indicate ordering, classification, or ownership. Even when they seem neutral, they may still carry clues about scale, organization, or workflow.
8.2 Exposure risks
Exposed identifiers can aid unwanted tracking, enumeration, or inference. For example, predictable account numbers or sequential record IDs may make it easier to guess other valid values. Systems that publish identifiers publicly often limit what those values reveal.
8.3 Obfuscation and pseudonymization
Obfuscation and pseudonymization reduce direct exposure by replacing a sensitive identifier with a less revealing substitute. These methods can support privacy while preserving analytical or operational usefulness. They are not the same as removing all risk, since reidentification may still be possible in some contexts.
8.4 Authentication versus identification
Identification determines who or what something is, while authentication verifies that claim. A username identifies an account, but a password, token, or other credential authenticates access. Confusing the two can lead to weak system design.
9 Standards and formats
Many identifiers follow published standards so that different systems can interpret them consistently. Standardization helps interoperability, long-term preservation, and vendor-neutral exchange. Some formats are general-purpose, while others are tailored to specialized sectors.
9.1 International standards
International standards define common rules for identifier structure, registration, and use. They are especially important where data moves across borders or between independent organizations. Standard forms reduce ambiguity and improve compatibility.
9.2 Industry-specific schemes
Many industries adopt their own identifier schemes for goods, institutions, documents, or transactions. These schemes reflect domain needs and may include embedded meaning or check digits. They often coexist with broader technical standards used by software systems.
9.3 Namespace management
Namespace management organizes identifiers so that similar values can coexist without conflict. A namespace provides context that makes an identifier meaningful within a defined domain. Careful namespace design is important in distributed systems, large organizations, and internet infrastructure.
10 Examples and applications
Identifiers appear in nearly every area of computing. Their forms differ by application, but the underlying function is the same: to give systems a dependable way to refer to things.
10.1 Databases and records
In databases, identifiers link rows, enforce uniqueness, and support queries. They are used for customers, products, orders, documents, and many other records. Without identifiers, large-scale data management would be much more error-prone.
10.2 Web and internet systems
On the web, identifiers are used in domain names, URLs, API resources, cookies, and tracking systems. They help browsers and services locate content and maintain state. Many internet identifiers are designed to be both machine-readable and interoperable across platforms.
10.3 Software development
Software uses identifiers for variables, functions, modules, classes, configuration entries, and log messages. These labels support code organization, reuse, and debugging. Naming conventions are often important because they improve readability and reduce mistakes.
10.4 Enterprise and cloud environments
Large organizations and cloud platforms rely on identifiers for users, services, virtual machines, storage objects, permissions, and audit logs. Consistent identification helps coordinate many components across shared infrastructure. In such environments, identifiers are central to automation, monitoring, and administration.