digital object identifier
Enable an AI agent to recognise a digital object identifier, establish what it identifies, assess its registration and resolution evidence, and select justified lookup or maintenance actions.
Bundle → Layer → Finding → Questions Filled
7 bundles · 13 layers · 20 findings · 41 questions
DOI name recognition Establish the identifier represented by an observed string.
Name extraction
Separate the candidate DOI from its presentation context.
Candidate boundaries
Record the original text, proposed prefix and suffix, and any unresolved boundary ambiguity.
- Which characters belong to the DOI name rather than a label, URL wrapper or surrounding citation? boundary
- Could apparent trailing punctuation or an encoded character be part of the suffix? definition
Name equivalence
Assess whether differing presentations identify the same DOI name.
Comparison transformations
Record reversible extraction steps and the applicable comparison rule without treating guessed repairs as confirmed identifiers.
- Which decoding and case-comparison rules apply to these exact representations? definition
- If the input is a shortDOI alias, what full DOI does the alias service establish? provenance
- Can the agent establish equivalence without dropping potentially meaningful characters? action
Registration and responsibility Establish registration evidence and the parties responsible for this DOI.
Assignment evidence
Distinguish an observed candidate from an evidenced registration.
Registration confirmation
Record the queried authority, environment, result and observation time.
- Which authoritative response confirms assignment of this exact DOI? provenance
- Does a negative result concern this service or environment only, or establish something broader? boundary
Maintenance responsibility
Identify the registration agency, registrant and current record maintainer separately.
Responsible service
Record evidenced responsibility and the route for registration questions or corrections.
- Which evidence identifies the current agency and record maintainer? provenance
- What service or contact accepts corrections for this DOI? action
- Does the evidence distinguish an original registrant from the current maintainer? boundary
Referent binding Establish exactly what the DOI identifies and how that identity relates to other identifiers.
Declared identity
Assess the entity and granularity declared for the DOI.
Referent boundary
Record enough referent description to distinguish the intended entity from neighbouring versions and parts.
- What entity does the registration metadata declare this DOI to identify? definition
- Does it identify a concept, a specific version, a manifestation, a component or a collection? boundary
- What evidence connects the object in the agent's task to that declared entity? provenance
Related identifiers
Distinguish equivalent referents from related but separately identified entities.
Identifier relationship evidence
Record claimed equivalence, version, part and other relationships with their asserted direction and source.
- Are these DOI names asserted to identify the same entity, or entities related by version, part or another relationship? boundary
- Who asserted the relationship, and what evidence supports it? provenance
- Should the agent retain distinct identities, select a task-appropriate DOI or flag a suspected duplicate assignment? action
DOI metadata evidence Evaluate the provenance and sufficiency of descriptions obtained for the DOI.
Metadata origin
Identify where each descriptive assertion came from.
Retrieval context
Record the service, response format, retrieval time and whether a record is authoritative, mirrored or transformed.
- Was this description obtained from the registration agency, a resolver representation, a landing page or an aggregator? provenance
- Which schema or transformation determines how its fields should be interpreted? definition
Metadata sufficiency
Assess whether available descriptions support the intended identification decision.
Identity agreement
Record missing or conflicting identity-bearing assertions without silently combining incompatible records.
- Which assertions distinguish the referent sufficiently for this task? boundary
- Which titles, creators, dates, types or version assertions disagree across the retrieved evidence? measurement
- Can the agent proceed with qualified evidence, or must it obtain clarification from the maintainer? action
Resolution and destination Assess DOI resolution separately from the usefulness and identity of its destination.
Resolver observation
Capture the context and result of a specific lookup.
Resolution result
Record the resolver, request time, requested representation, response and redirect chain where applicable.
- Which resolver and request parameters produced this result? provenance
- Did the request produce a response, an identifier-not-found result, a service failure or a network failure? measurement
- Does the task require ordinary navigation or a metadata representation supported by this service? action
Destination assessment
Inspect what the resolution result actually provides.
Destination fit
Assess referent correspondence, access barriers and status notices independently of redirect success.
- Does the destination identify the declared referent, provide a status notice, or lead somewhere unrelated? boundary
- Is the result a landing page, content, metadata, an access challenge or an error? measurement
- Should the agent follow an evidenced alternate route, retry later or report a destination problem? action
Persistence and maintenance Support continuing identification as locations, descriptions and responsible parties change.
Change classification
Determine what an observed or proposed change means for this DOI's binding.
Binding continuity
Separate record correction and relocation from changes that require an agency-specific identity decision.
- Does the proposed change preserve the declared referent or identify a distinguishable entity? boundary
- Which agency or community policy governs whether this change requires another DOI? provenance
- Is an apparent withdrawal or replacement a statement about the referent, the destination or the registration record? definition
Authorised intervention
Determine permitted maintenance and verify its effect.
Record change authority
Record the actor's authority, intended metadata or destination change, and evidence needed to confirm completion.
- What authorisation permits this actor to change this DOI's specific records? provenance
- Which supported operation corrects the problem while preserving the intended referent binding? action
- Which subsequent agency response and resolution check would establish that the requested change took effect? measurement
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Kinds and varieties
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these kinds and varieties hold for the sense of digital object identifier this model covers, and on what evidence? provenance
Identifiers and schemes
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these identifiers and schemes hold for the sense of digital object identifier this model covers, and on what evidence? provenance
Standards and regulation
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these standards and regulation hold for the sense of digital object identifier this model covers, and on what evidence? provenance
Real-world use
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these real-world use hold for the sense of digital object identifier this model covers, and on what evidence? provenance
Typical measurements
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these typical measurements hold for the sense of digital object identifier this model covers, and on what evidence? provenance
Failure modes and hazards
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these failure modes and hazards hold for the sense of digital object identifier this model covers, and on what evidence? provenance
Regional variation
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these regional variation hold for the sense of digital object identifier this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of digital object identifier this model covers, and on what evidence? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Information and virtual systems
- Entry kind
- thing
- Plane
- INF
- Domain
- INF.MED
- Other names and narrower kinds
- Entertainment Identifier Registry
What it is Filled
A Digital Object Identifier (DOI) is a persistent, resolvable identifier assigned to a digital or physical object under the DOI system, consisting of a unique character string that is registered in a central directory and bound to current location and metadata so that the object can be located even when its URL changes.
In scope
- DOI name recognition, representation and equivalence
- Registration evidence and responsible registration agency
- Referent identity, granularity and identifier relationships
- Descriptive metadata provenance and agreement
- Resolution behaviour and destination correspondence
- Persistence obligations and authorised record maintenance
Out of scope
- The content, quality and lifecycle of the identified work, dataset, physical object or other referent
- Full bibliographic descriptions and citation-style rendering
- Hosting infrastructure and preservation repositories
- Copyright ownership, licensing decisions and access entitlements
- The internal operation of the Handle System or a registration agency
Why it exists Filled
Enable an AI agent to recognise a digital object identifier, establish what it identifies, assess its registration and resolution evidence, and select justified lookup or maintenance actions.
Distinguishing features Filled
- A candidate DOI name has a prefix beginning with the directory indicator 10 and a slash-separated suffix; matching syntax alone does not establish registration. [DOI Handbook: Numbering](https://www-old.doi.org/doi_handbook/2_Numbering.html)
- A DOI name and a URL presenting that name must be distinguished from the destination URL returned by resolution. [DOI Handbook: Resolution](https://www-old.doi.org/doi_handbook/3_Resolution.html)
- A DOI names a declared referent rather than identifying content through a computed hash; referent meaning must be established from metadata, not decoded from the suffix. [DOI Handbook: Numbering](https://www-old.doi.org/doi_handbook/2_Numbering.html)
- A DOI can identify a physical entity or an abstraction as well as digital material, so being a downloadable file is not a recognition requirement. [DOI Handbook: Numbering](https://www-old.doi.org/doi_handbook/2_Numbering.html)
- Two different DOI names may identify the same referent; identifier equivalence and referent equivalence therefore require separate tests. [DOI Handbook: Numbering](https://www-old.doi.org/doi_handbook/2_Numbering.html)
What robots and AI may and may not do Filled
Must not
- Invent DOIs or cite ones that do not exist.
- Register or alter DOIs or their metadata without the registrant's authority.
- Use a DOI to point readers to pirated copies.
- Present a DOI as proof that a work is peer reviewed or reliable.
Only with a human decision
- Redirecting or retracting a DOI.
May
- Resolve and cite DOIs and report the metadata registered for them.
- Check that a cited DOI resolves to the work it is claimed to identify.
Moral aspects Filled
- Fabricated citations, including fake DOIs, undermine trust in research.
Who is affected
- Researchers and authors
- Readers
- Publishers
Owners Filled
Steward
The registrant that assigned it through a registration agency; the DOI foundation governs the system.
Master systems
- DOI registration agency databases
Links to other meta-models Filled
parent
- Q15087423 - registry parent class
- Q1781028 - registry parent class
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.digital-object-identifier
- Wikidata: Q25670 (https://www.wikidata.org/wiki/Q25670)
Direct properties not applicable Not applicable
- Observed representation: bare DOI name | labelled DOI | DOI proxy URL | shortDOI alias | ambiguous text
- Recognition assessment: unassessed | syntactically plausible | malformed | extraction ambiguous
- Registration evidence: unverified | confirmed by identified authority | absent from queried service | conflicting evidence
- Responsible parties: DOI to registration agency, registrant and current maintainer, with evidence and observation time
- Referent granularity: work or concept | version or edition | manifestation | component | collection | other declared scope | unresolved
- Metadata agreement: unchecked | consistent for task | incomplete | conflicting
- Resolution observation: unobserved | response obtained | identifier-not-found response | resolver failure | network failure | ambiguous result
- Destination correspondence: unchecked | matching referent | matching status notice | ambiguous | mismatching | unreachable
- Observation age: seconds since the recorded registration, metadata or resolution check
- Maintenance authority: unknown | lookup only | authorised for specified record changes | authority disputed
Plane INF: no invented physical properties.
Recognition optional Filled
- A string beginning with 10. followed by a prefix, a slash and a suffix.
- Often shown as a link through the doi.org resolver.
Capabilities and actions required Filled
- Extract and compare DOI names while retaining the original representation and transformation evidence.
- Discover the registration agency and retrieve available registration or descriptive metadata.
- Resolve a DOI and inspect its destinations or supported negotiated representations.
- Match the declared referent and granularity to a citation, object or task requirement.
- Investigate conflicting metadata, suspected duplicate assignments or broken destinations.
- Prepare or perform authorised metadata and destination corrections through the responsible service.
Hazards and failure modes required Filled
- Broken resolution when metadata are not updated.
- Fabricated or mistyped DOIs in citations.
Standards and interfaces required Filled
- ISO 26324, Information and documentation - Digital object identifier system, International Organization for Standardization.
Context of use required Filled
- Digital object identifiers occur in scholarly references, research repositories, publication metadata and data catalogues.
- They support persistent citation and linking by associating an identified object with maintained metadata and resolution information.
- Agents use them to retrieve records, reconcile references and distinguish identified versions or related objects.
Sources Filled
- ISO 26324:2022 Information and documentation - Digital object identifier system - Formal definition of the DOI system as an ISO standard; identifier syntax and resolution.
- DOI Handbook - Operational definition, resolution, metadata, and registration agency practice.
- DOI display guidelines and DOI facts - How DOIs are assigned and displayed for scholarly publications.
- DataCite DOI registration and metadata - Dataset, software, and research-output DOI practice distinct from journal articles.
- Wikidata item Q25670: digital object identifier - identity and sense of the item
- Wikipedia: Digital object identifier - general description of the item
Open questions
- Which current DOI syntax and equivalence rules cover non-ASCII characters, legacy names and ambiguous percent-encoding, and what validation procedure should this model require?
- Which registration agencies and environments must be supported, and how should their different registration states and negative responses map to the proposed evidence states?
- Which agency or community policies distinguish metadata corrections from referent changes requiring a separate DOI, especially for evolving datasets and software?
- What evidence should resolve suspected duplicate assignments or conflicting referent descriptions when authoritative services disagree?
- Which maintenance, transfer and unavailable-content policies apply across the supported agencies, and how long may observations remain usable for each intended task?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q25670/spec.json