CACrown ArchivesThe cinema collection
Menu
Research dossier · Science & Nature

Fully qualified name

unambiguous name for an entity in a computing language containing an identifier and all enclosing namespaces

Specimen drawers, botanical folios and brass scientific instruments under study light
Science and natureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionJul 5, 2026
Entity authorityQ5508349
Source-derived summary

In computer programming, a fully qualified name is an unambiguous name that specifies which object, function, or variable a call refers to without regard to the context of the call. In a hierarchical structure, a name is fully qualified when it "is complete in the sense that it includes (a) all names in the hierarchic sequence above the given element and (b) the name of the given element itself."

Programming

Fully qualified names explicitly refer to namespaces that would otherwise be implicit because of the scope of the call. While always done to eliminate ambiguity, this can mean different things dependent on context.

Commonly encountered applications of the notion have been given their own names, such as the fully qualified domain name and the fully qualified file name.

Examples

To distinguish a fully qualified name from a regular name, C++, Tcl, Perl and Ruby use two colons (::), and Java uses dots (.), as does Visual Basic .NET. and C#. In Java, ActionScript, and other object-oriented languages the use of the dot is known as "dot syntax". Other examples include:

As an example of a relational database, in Microsoft SQL Server the fully qualified object name is the one that specifies all four parts: server_name.[database_name].[schema_name].object_name.

In Perl, a fully qualified scalar ($scalar) that is in the package package2 would be referred to as $package2::scalar

In Ruby, the fully qualified class name is the name of such class with all its parent modules, as Vehicles::Cars::Factory would be the fully qualified name of Factory class within Cars module within Vehicles module.

In Rust, the fully qualified type name is the name of such type with all its parent modules, as crate::components::transform::Transform would be the fully qualified name of Transform class within the transform module within the components module of the crate. This can be determined by calling the core::any::type_name function.

Editorial summary

“Fully qualified name” enters the record as unambiguous name for an entity in a computing language containing an identifier and all enclosing namespaces. Crown Archives preserves that source wording while asking what Fully, qualified and name can confirm, complicate or overturn.

Editorial reviewA sound reference starting point where classification, measurement and the date of the underlying evidence remain visible. The current 308-word lead offers orientation but no explicit four-digit date, so chronology should not be assumed. The selected authority fields contribute no independent date. Its strongest next move is a source search built around Fully, qualified and name.
Editorial analysis

Why this record matters

“Fully qualified name” is worth following because a concise public description often conceals a longer documentary argument. Here, Fully, qualified and name provides the most credible route into that argument.

Evidence profile

Stable identifiers, scientific names and standards terminology offer the best bridge between this overview and specialist evidence. The source revision retrieved here is dated Jul 5, 2026. The linked authority identifier is Q5508349.

Critical limits

Current terminology should not be projected backward without checking the classification used when the underlying evidence was created. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.

Best used for
  • Current terminology
  • Classification context
  • Finding cited technical literature
Verify next

Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.

Three-step research path

  1. Establish the record: confirm the title “Fully qualified name”, its source revision and the description used here.
  2. Expand the search: follow Fully qualified name primary sources, Fully qualified name archive and Fully research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Fully qualified name”?
  2. Which observation, specimen, dataset or publication supports the account?
  3. Has classification or technical consensus changed since the cited source?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from Fully qualified name” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.