{ "model": { "rank": 2276, "code": "thing-q25670", "model_id": "vr.tr.digital-object-identifier", "name": "digital object identifier", "purpose": "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.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.MED", "industry": "", "version": "", "url": "/models/thing/q25670/", "tier": 2, "score": 110, "payload": { "layer": "wikidata", "aliases": [ "Entertainment Identifier Registry" ], "aliasCount": 1, "merged": 1, "knownIn": 110, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q25670", "url": "https://www.wikidata.org/wiki/Q25670", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T11:16:02Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.00349316, "turns": 1, "seconds": 46, "error": null }, "codex": { "seconds": 88.7, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a07b93-bc1c-7922-a899-e331bd2b41d4\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: digital object identifier\nRegistry id: vr.tr.digital-object-identifier\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folde" } } }, "metaModel": { "id": "THING-Q25670", "registryId": "vr.tr.digital-object-identifier", "name": "digital object identifier", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q25670/", "model": { "registry_id": "vr.tr.digital-object-identifier", "name": "digital object identifier", "purpose": "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.", "definition": "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.", "scope_statement": "This model owns the DOI identifier represented by vr.tr.digital-object-identifier, including its representations, assignment, referent binding, metadata evidence, resolution observations and maintenance authority; it does not own the identified object.", "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" ], "distinguishing_features": [ "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)" ], "characteristics": [ { "name": "Observed representation", "kind": "category", "unit_or_values": "bare DOI name | labelled DOI | DOI proxy URL | shortDOI alias | ambiguous text", "why_it_matters": "Determines the extraction and expansion needed before identifier comparison." }, { "name": "Recognition assessment", "kind": "state", "unit_or_values": "unassessed | syntactically plausible | malformed | extraction ambiguous", "why_it_matters": "Prevents a recognisable string from being treated as a verified registration." }, { "name": "Registration evidence", "kind": "state", "unit_or_values": "unverified | confirmed by identified authority | absent from queried service | conflicting evidence", "why_it_matters": "Keeps service-specific negative results distinct from universal nonexistence." }, { "name": "Responsible parties", "kind": "relation", "unit_or_values": "DOI to registration agency, registrant and current maintainer, with evidence and observation time", "why_it_matters": "Identifies where authoritative information and correction routes can be sought." }, { "name": "Referent granularity", "kind": "category", "unit_or_values": "work or concept | version or edition | manifestation | component | collection | other declared scope | unresolved", "why_it_matters": "Determines whether the DOI identifies the exact entity required by the task." }, { "name": "Metadata agreement", "kind": "state", "unit_or_values": "unchecked | consistent for task | incomplete | conflicting", "why_it_matters": "Controls whether metadata can support identification or needs reconciliation." }, { "name": "Resolution observation", "kind": "state", "unit_or_values": "unobserved | response obtained | identifier-not-found response | resolver failure | network failure | ambiguous result", "why_it_matters": "Separates observed lookup behaviour from registration and referent state." }, { "name": "Destination correspondence", "kind": "state", "unit_or_values": "unchecked | matching referent | matching status notice | ambiguous | mismatching | unreachable", "why_it_matters": "A completed redirect is insufficient evidence that the destination serves the intended referent." }, { "name": "Observation age", "kind": "measurement", "unit_or_values": "seconds since the recorded registration, metadata or resolution check", "why_it_matters": "Supports task-specific decisions about whether evidence needs refreshing." }, { "name": "Maintenance authority", "kind": "state", "unit_or_values": "unknown | lookup only | authorised for specified record changes | authority disputed", "why_it_matters": "Distinguishes the ability to inspect a DOI from permission to change its records." } ], "affordances": [ "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." ] }, "sources": [ { "id": "iso-26324", "title": "ISO 26324:2022 Information and documentation - Digital object identifier system", "url": "https://www.iso.org/standard/83123.html", "what_it_supports": "Formal definition of the DOI system as an ISO standard; identifier syntax and resolution.", "url_status": "blocked" }, { "id": "doi-handbook", "title": "DOI Handbook", "url": "https://www.doi.org/the-identifier/resources/handbook/", "what_it_supports": "Operational definition, resolution, metadata, and registration agency practice.", "url_status": "live" }, { "id": "crossref", "title": "DOI display guidelines and DOI facts", "url": "https://www.crossref.org/documentation/member-setup/constructing-your-dois/", "what_it_supports": "How DOIs are assigned and displayed for scholarly publications.", "url_status": "live" }, { "id": "datacite", "title": "DataCite DOI registration and metadata", "url": "https://datacite.org/dois/", "what_it_supports": "Dataset, software, and research-output DOI practice distinct from journal articles.", "url_status": "blocked" } ], "structure": { "bundles": [ { "id": "doi-name-recognition", "name": "DOI name recognition", "description": "Establish the identifier represented by an observed string.", "rationale": "Copying, URL encoding and citation punctuation can make identifier recognition uncertain before any lookup occurs.", "layers": [ { "id": "name-extraction", "name": "Name extraction", "description": "Separate the candidate DOI from its presentation context.", "findings": [ { "id": "candidate-boundaries", "name": "Candidate boundaries", "description": "Record the original text, proposed prefix and suffix, and any unresolved boundary ambiguity.", "questions": [ { "text": "Which characters belong to the DOI name rather than a label, URL wrapper or surrounding citation?", "kind": "boundary", "id": "candidate-boundaries-q01" }, { "text": "Could apparent trailing punctuation or an encoded character be part of the suffix?", "kind": "definition", "id": "candidate-boundaries-q02" } ] } ] }, { "id": "name-equivalence", "name": "Name equivalence", "description": "Assess whether differing presentations identify the same DOI name.", "findings": [ { "id": "comparison-transformations", "name": "Comparison transformations", "description": "Record reversible extraction steps and the applicable comparison rule without treating guessed repairs as confirmed identifiers.", "questions": [ { "text": "Which decoding and case-comparison rules apply to these exact representations?", "kind": "definition", "id": "comparison-transformations-q01" }, { "text": "If the input is a shortDOI alias, what full DOI does the alias service establish?", "kind": "provenance", "id": "comparison-transformations-q02" }, { "text": "Can the agent establish equivalence without dropping potentially meaningful characters?", "kind": "action", "id": "comparison-transformations-q03" } ] } ] } ] }, { "id": "registration-and-responsibility", "name": "Registration and responsibility", "description": "Establish registration evidence and the parties responsible for this DOI.", "rationale": "A plausible DOI string does not establish assignment, and maintenance actions need a specific responsible service.", "layers": [ { "id": "assignment-evidence", "name": "Assignment evidence", "description": "Distinguish an observed candidate from an evidenced registration.", "findings": [ { "id": "registration-confirmation", "name": "Registration confirmation", "description": "Record the queried authority, environment, result and observation time.", "questions": [ { "text": "Which authoritative response confirms assignment of this exact DOI?", "kind": "provenance", "id": "registration-confirmation-q01" }, { "text": "Does a negative result concern this service or environment only, or establish something broader?", "kind": "boundary", "id": "registration-confirmation-q02" } ] } ] }, { "id": "maintenance-responsibility", "name": "Maintenance responsibility", "description": "Identify the registration agency, registrant and current record maintainer separately.", "findings": [ { "id": "responsible-service", "name": "Responsible service", "description": "Record evidenced responsibility and the route for registration questions or corrections.", "questions": [ { "text": "Which evidence identifies the current agency and record maintainer?", "kind": "provenance", "id": "responsible-service-q01" }, { "text": "What service or contact accepts corrections for this DOI?", "kind": "action", "id": "responsible-service-q02" }, { "text": "Does the evidence distinguish an original registrant from the current maintainer?", "kind": "boundary", "id": "responsible-service-q03" } ] } ] } ] }, { "id": "referent-binding", "name": "Referent binding", "description": "Establish exactly what the DOI identifies and how that identity relates to other identifiers.", "rationale": "An agent can retrieve a valid DOI yet use it for the wrong version, component or conceptual level.", "layers": [ { "id": "declared-identity", "name": "Declared identity", "description": "Assess the entity and granularity declared for the DOI.", "findings": [ { "id": "referent-boundary", "name": "Referent boundary", "description": "Record enough referent description to distinguish the intended entity from neighbouring versions and parts.", "questions": [ { "text": "What entity does the registration metadata declare this DOI to identify?", "kind": "definition", "id": "referent-boundary-q01" }, { "text": "Does it identify a concept, a specific version, a manifestation, a component or a collection?", "kind": "boundary", "id": "referent-boundary-q02" }, { "text": "What evidence connects the object in the agent's task to that declared entity?", "kind": "provenance", "id": "referent-boundary-q03" } ] } ] }, { "id": "related-identifiers", "name": "Related identifiers", "description": "Distinguish equivalent referents from related but separately identified entities.", "findings": [ { "id": "identifier-relationship-evidence", "name": "Identifier relationship evidence", "description": "Record claimed equivalence, version, part and other relationships with their asserted direction and source.", "questions": [ { "text": "Are these DOI names asserted to identify the same entity, or entities related by version, part or another relationship?", "kind": "boundary", "id": "identifier-relationship-evidence-q01" }, { "text": "Who asserted the relationship, and what evidence supports it?", "kind": "provenance", "id": "identifier-relationship-evidence-q02" }, { "text": "Should the agent retain distinct identities, select a task-appropriate DOI or flag a suspected duplicate assignment?", "kind": "action", "id": "identifier-relationship-evidence-q03" } ] } ] } ] }, { "id": "doi-metadata-evidence", "name": "DOI metadata evidence", "description": "Evaluate the provenance and sufficiency of descriptions obtained for the DOI.", "rationale": "Metadata retrieval supports identification only when its source, interpretation and conflicts are visible.", "layers": [ { "id": "metadata-origin", "name": "Metadata origin", "description": "Identify where each descriptive assertion came from.", "findings": [ { "id": "retrieval-context", "name": "Retrieval context", "description": "Record the service, response format, retrieval time and whether a record is authoritative, mirrored or transformed.", "questions": [ { "text": "Was this description obtained from the registration agency, a resolver representation, a landing page or an aggregator?", "kind": "provenance", "id": "retrieval-context-q01" }, { "text": "Which schema or transformation determines how its fields should be interpreted?", "kind": "definition", "id": "retrieval-context-q02" } ] } ] }, { "id": "metadata-sufficiency", "name": "Metadata sufficiency", "description": "Assess whether available descriptions support the intended identification decision.", "findings": [ { "id": "identity-agreement", "name": "Identity agreement", "description": "Record missing or conflicting identity-bearing assertions without silently combining incompatible records.", "questions": [ { "text": "Which assertions distinguish the referent sufficiently for this task?", "kind": "boundary", "id": "identity-agreement-q01" }, { "text": "Which titles, creators, dates, types or version assertions disagree across the retrieved evidence?", "kind": "measurement", "id": "identity-agreement-q02" }, { "text": "Can the agent proceed with qualified evidence, or must it obtain clarification from the maintainer?", "kind": "action", "id": "identity-agreement-q03" } ] } ] } ] }, { "id": "resolution-and-destination", "name": "Resolution and destination", "description": "Assess DOI resolution separately from the usefulness and identity of its destination.", "rationale": "Resolution can return associated information rather than the object itself. [DOI Handbook: Resolution](https://www-old.doi.org/doi_handbook/3_Resolution.html)", "layers": [ { "id": "resolver-observation", "name": "Resolver observation", "description": "Capture the context and result of a specific lookup.", "findings": [ { "id": "resolution-result", "name": "Resolution result", "description": "Record the resolver, request time, requested representation, response and redirect chain where applicable.", "questions": [ { "text": "Which resolver and request parameters produced this result?", "kind": "provenance", "id": "resolution-result-q01" }, { "text": "Did the request produce a response, an identifier-not-found result, a service failure or a network failure?", "kind": "measurement", "id": "resolution-result-q02" }, { "text": "Does the task require ordinary navigation or a metadata representation supported by this service?", "kind": "action", "id": "resolution-result-q03" } ] } ] }, { "id": "destination-assessment", "name": "Destination assessment", "description": "Inspect what the resolution result actually provides.", "findings": [ { "id": "destination-fit", "name": "Destination fit", "description": "Assess referent correspondence, access barriers and status notices independently of redirect success.", "questions": [ { "text": "Does the destination identify the declared referent, provide a status notice, or lead somewhere unrelated?", "kind": "boundary", "id": "destination-fit-q01" }, { "text": "Is the result a landing page, content, metadata, an access challenge or an error?", "kind": "measurement", "id": "destination-fit-q02" }, { "text": "Should the agent follow an evidenced alternate route, retry later or report a destination problem?", "kind": "action", "id": "destination-fit-q03" } ] } ] } ] }, { "id": "persistence-and-maintenance", "name": "Persistence and maintenance", "description": "Support continuing identification as locations, descriptions and responsible parties change.", "rationale": "The DOI name persists through changes in ownership or management, while maintenance responsibility may move. [DOI Handbook: Numbering](https://www-old.doi.org/doi_handbook/2_Numbering.html)", "layers": [ { "id": "change-classification", "name": "Change classification", "description": "Determine what an observed or proposed change means for this DOI's binding.", "findings": [ { "id": "binding-continuity", "name": "Binding continuity", "description": "Separate record correction and relocation from changes that require an agency-specific identity decision.", "questions": [ { "text": "Does the proposed change preserve the declared referent or identify a distinguishable entity?", "kind": "boundary", "id": "binding-continuity-q01" }, { "text": "Which agency or community policy governs whether this change requires another DOI?", "kind": "provenance", "id": "binding-continuity-q02" }, { "text": "Is an apparent withdrawal or replacement a statement about the referent, the destination or the registration record?", "kind": "definition", "id": "binding-continuity-q03" } ] } ] }, { "id": "authorised-intervention", "name": "Authorised intervention", "description": "Determine permitted maintenance and verify its effect.", "findings": [ { "id": "record-change-authority", "name": "Record change authority", "description": "Record the actor's authority, intended metadata or destination change, and evidence needed to confirm completion.", "questions": [ { "text": "What authorisation permits this actor to change this DOI's specific records?", "kind": "provenance", "id": "record-change-authority-q01" }, { "text": "Which supported operation corrects the problem while preserving the intended referent binding?", "kind": "action", "id": "record-change-authority-q02" }, { "text": "Which subsequent agency response and resolution check would establish that the requested change took effect?", "kind": "measurement", "id": "record-change-authority-q03" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "journal-article DOI", "dataset DOI", "software DOI", "book/chapter DOI", "conference-proceedings DOI", "preprint DOI", "grant/funder DOI", "physical-object / sample DOI" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of digital object identifier this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "scheme": "Wikidata", "value_or_pattern": "Q25670", "note": "Wikidata item for Digital Object Identifier" }, { "scheme": "ISO", "value_or_pattern": "ISO 26324", "note": "International standard for the DOI system" }, { "scheme": "DOI syntax", "value_or_pattern": "10./", "note": "Handle-based DOI string; prefix 10.NNNN (or longer) assigned to a registrant, suffix assigned by that registrant" }, { "scheme": "URI form", "value_or_pattern": "https://doi.org/10./", "note": "Preferred display and resolution URL via the DOI proxy" } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of digital object identifier this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "ISO 26324:2022 Information and documentation - Digital object identifier system (ISO)", "ANSI/NISO Z39.84 Syntax for the Digital Object Identifier (NISO, historically; syntax now aligned with ISO 26324)", "Handle System / RFC 3650-3652 as the resolution substrate (CNRI / IETF informational RFCs)", "DOI Foundation policies and Registration Agency agreements (International DOI Foundation)", "Crossref and DataCite membership terms governing assignment, metadata deposit, and persistence commitments" ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of digital object identifier this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Cited in scholarly articles, datasets, and software as a stable link that resolves to the current landing page", "Deposited with Crossref by journal publishers so references can be matched and cited", "Minted by DataCite repositories (Zenodo, Figshare, institutional repos) for datasets and software releases", "Used as a Handle (doi:10.xxxx/yyyy) and as an HTTPS URL (https://doi.org/10.xxxx/yyyy) in metadata, PDFs, and library catalogues", "Embedded in funder and grant records (e.g. Crossref Grant IDs) and in physical sample identifiers (IGSN, now under DataCite)" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of digital object identifier this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "quantity": "DOI string length", "typical_range": "typically 15-80 characters for the 10.prefix/suffix form; suffix length is registrant-defined", "unit": "characters" }, { "quantity": "Resolution latency via doi.org proxy", "typical_range": "typically sub-second to a few seconds under normal load", "unit": "seconds" }, { "quantity": "Assigned DOIs in the system", "typical_range": "on the order of 10^8 globally (hundreds of millions), growing continuously", "unit": "count" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of digital object identifier this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Broken persistence: DOI still resolves but landing page is gone, paywalled without notice, or replaced by unrelated content", "Duplicate assignment of the same object under different DOIs, or one DOI reused for a different object", "Prefix/suffix collision or malformed syntax that will not resolve", "Metadata drift: deposited bibliographic metadata no longer matches the object", "Tombstone or 'DOI not found' when a registration agency or member disappears without transferring records", "Confusion of versioned objects (article version of record vs preprint vs dataset version) leading to wrong citation", "Linkrot of the displayed URL if publishers print a publisher URL instead of the doi.org form" ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of digital object identifier this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Registration agencies are global but market-split: Crossref dominates scholarly journals (especially North America/Europe); CNKI, JST, and others operate regional DOI services in China and Japan", "Display conventions differ: some publishers still print 'doi:' URI form; Crossref now requires https://doi.org/ display", "Legal deposit and open-access mandates in the EU and UK increasingly require DOIs on publications and datasets; practice is less uniform in regions without those mandates", "Some national libraries and repositories mint handles or URNs instead of, or in addition to, DOIs" ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of digital object identifier this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "name": "Handle (CNRI Handle System)", "difference": "A DOI is a Handle with the DOI namespace prefix 10.; every DOI is a Handle, but most Handles are not DOIs and are not governed by the IDF/ISO 26324 social contract" }, { "name": "URL / HTTP URI", "difference": "A URL locates a current network address; a DOI names the object and is resolved through a registry that can update the location" }, { "name": "ISBN / ISSN", "difference": "ISBN and ISSN identify the product or serial title as a bibliographic identifier; a DOI identifies a specific digital (or registered) object instance and is resolvable; a book may have both" }, { "name": "PMID / PMCID", "difference": "PubMed and PMC identifiers are database accession numbers inside NCBI; they are not ISO 26324 DOIs, though a paper often has both a PMID and a Crossref DOI" }, { "name": "ARK (Archival Resource Key)", "difference": "ARKs are persistent identifiers with a different resolver (N2T/EZID) and no central ISO registration-agency model; persistence depends on the assigning institution" }, { "name": "PURL", "difference": "Persistent URLs redirect via a PURL server the owner controls; they lack the DOI prefix registry, metadata kernel, and multi-RA governance" }, { "name": "UUID / OID", "difference": "UUIDs and ISO OIDs uniquely name an entity but do not by themselves provide a global public resolution and metadata service" } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "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?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "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?" ], "statistics": { "bundles": 7, "layers": 13, "findings": 20, "questions": 41 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "work, medium or creative form", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a digital object identifier, record what state it is in, and decide what may be done with it.", "whatItIs": "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.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted", "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Entertainment Identifier Registry.", "1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 110 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a digital object identifier, and on what evidence are they told apart?" ], "whatItIsMadeOf": "content that has to be carried by something else", "physicalCharacter": [ "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "read it and act on what it says", "observe it, measure it, record its state" ], "howItIsRecognised": [ "What is seen is a copy or a performance, not the work. Recognising the work means recognising the content through whatever is carrying it." ], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "Entertainment Identifier Registry" ] } ], "standing": "Described in 110 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 1 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one digital object identifier from another, and a digital object identifier from things that resemble it.", "rationale": "Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.", "layers": [ { "id": "naming-and-identifiers", "name": "Names and identifiers", "description": "The names this thing goes by and the identifiers that survive translation and time.", "findings": [ { "id": "preferred-name-and-aliases", "name": "Preferred name, aliases and local names", "description": "Which name to use, which names mean the same thing, and which merely sound similar.", "questions": [ { "id": "preferred-name-and-aliases-q01", "text": "What identifies and describes the name of a digital object identifier, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "preferred-name-and-aliases-q02", "text": "Who or what asserted this about the name of a digital object identifier, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "preferred-name-and-aliases-q03", "text": "What may an agent decide or do once the name of a digital object identifier is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "stable-identifiers", "name": "Stable identifiers and external keys", "description": "Identifiers that keep pointing at this kind of thing across systems and languages.", "questions": [ { "id": "stable-identifiers-q01", "text": "What identifies and describes an identifier for a digital object identifier, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stable-identifiers-q02", "text": "Who or what asserted this about an identifier for a digital object identifier, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stable-identifiers-q03", "text": "What may an agent decide or do once an identifier for a digital object identifier is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "classification-and-granularity", "name": "Classification and granularity", "description": "Where a digital object identifier sits among kinds, and how finely a task needs to cut it.", "findings": [ { "id": "kind-and-parents", "name": "Kind, parents and neighbouring kinds", "description": "The classes this thing belongs to and the ones it is next to.", "questions": [ { "id": "kind-and-parents-q01", "text": "What identifies and describes the kind of a digital object identifier, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "kind-and-parents-q02", "text": "Who or what asserted this about the kind of a digital object identifier, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "kind-and-parents-q03", "text": "What may an agent decide or do once the kind of a digital object identifier is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "distinguishing-features", "name": "Distinguishing features", "description": "What separates a digital object identifier from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a digital object identifier, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "distinguishing-features-q02", "text": "Who or what asserted this about what distinguishes a digital object identifier, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "distinguishing-features-q03", "text": "What may an agent decide or do once what distinguishes a digital object identifier is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "state-and-lifecycle", "name": "State and lifecycle", "description": "The states a digital object identifier passes through and the events that move it between them.", "rationale": "Most decisions about a thing depend on what state it is in now, which is a claim with a time on it, not a property.", "layers": [ { "id": "lifecycle-stages", "name": "Lifecycle stages", "description": "From coming into existence to ceasing to be one of these.", "findings": [ { "id": "stages-and-transitions", "name": "Stages and transitions", "description": "The stages worth naming and what moves a digital object identifier between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a digital object identifier, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stages-and-transitions-q02", "text": "Who or what asserted this about the lifecycle of a digital object identifier, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stages-and-transitions-q03", "text": "What may an agent decide or do once the lifecycle of a digital object identifier is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "observations-and-status", "name": "Observations and current status", "description": "What is observed about a digital object identifier, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a digital object identifier is recorded so that it can be superseded rather than overwritten.", "questions": [ { "id": "observation-record-q01", "text": "What identifies and describes an observation of a digital object identifier, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "observation-record-q02", "text": "Who or what asserted this about an observation of a digital object identifier, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "observation-record-q03", "text": "What may an agent decide or do once an observation of a digital object identifier is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "content-and-access", "name": "Content, encoding and access", "description": "What a digital object identifier says, how it is encoded and who may read it.", "rationale": "An informational thing carries content that can be copied, versioned and withheld, none of which its physical carrier explains.", "layers": [ { "id": "content-and-encoding", "name": "Content and encoding", "description": "The content itself, its format and its language.", "findings": [ { "id": "content-and-format", "name": "Content, format and language", "description": "What a digital object identifier contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a digital object identifier, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "content-and-format-q02", "text": "Who or what asserted this about the content of a digital object identifier, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "content-and-format-q03", "text": "What may an agent decide or do once the content of a digital object identifier is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "access-and-rights", "name": "Access, rights and retention", "description": "Who may read, copy or change it, and for how long it is kept.", "findings": [ { "id": "access-rules", "name": "Access rules and retention", "description": "The permissions attached to a digital object identifier and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a digital object identifier, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "access-rules-q02", "text": "Who or what asserted this about access to a digital object identifier, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "access-rules-q03", "text": "What may an agent decide or do once access to a digital object identifier is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "work-and-manifestation", "name": "Work, version and copy", "description": "Which level of digital object identifier a statement is about.", "rationale": "The work, the edition, the file and the copy in hand are four things; rights and content attach to different ones.", "layers": [ { "id": "levels", "name": "Levels of the thing", "description": "Work, expression, manifestation and item, in plain terms.", "findings": [ { "id": "level-rules", "name": "What belongs at each level", "description": "Which facts hold for the work and which only for one copy.", "questions": [ { "id": "level-rules-q01", "text": "For digital object identifier, which facts belong to the work itself, which to a version, and which to a single copy?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifier exists at each level, and which one is being cited?", "kind": "definition" } ] } ] }, { "id": "versions", "name": "Versions, editions and variants", "description": "How versions differ and which is canonical to whom.", "findings": [ { "id": "version-record", "name": "Versions and canonicity", "description": "Differences that matter and who calls one authoritative.", "questions": [ { "id": "version-record-q01", "text": "Which versions or editions of digital object identifier exist, and how do they differ substantively?", "kind": "definition" }, { "id": "version-record-q02", "text": "Who treats which version as authoritative, and for what purpose?", "kind": "provenance" } ] } ] } ] }, { "id": "authorship-and-rights", "name": "Authorship, rights and permitted use", "description": "Who made digital object identifier and what may be done with it.", "rationale": "Rights are jurisdictional, time-limited and attached to a level, and an agent that ignores that will copy what it may not.", "layers": [ { "id": "authorship", "name": "Authorship and contribution", "description": "Who contributed what, and in what capacity.", "findings": [ { "id": "contribution-record", "name": "Contributors and roles", "description": "The people and bodies behind it, with their roles.", "questions": [ { "id": "contribution-record-q01", "text": "Who authored or contributed to digital object identifier, in what roles, and how is that attested?", "kind": "provenance" }, { "id": "contribution-record-q02", "text": "Where authorship is disputed or anonymous, what is recorded instead?", "kind": "boundary" } ] } ] }, { "id": "rights", "name": "Rights and permissions", "description": "Which rights subsist, where, until when, and what they permit.", "findings": [ { "id": "rights-record", "name": "Rights, term and permitted acts", "description": "The regime in force and what it allows.", "questions": [ { "id": "rights-record-q01", "text": "What rights subsist in digital object identifier, in which jurisdictions, and until when?", "kind": "definition" }, { "id": "rights-record-q02", "text": "Which acts are permitted without further permission, and which must an agent refuse?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a digital object identifier came from and when it held.", "rationale": "A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.", "layers": [ { "id": "source-and-authority", "name": "Source and authority", "description": "Who said it, on what evidence, and how strongly.", "findings": [ { "id": "claim-provenance", "name": "Claim provenance and confidence", "description": "The authority behind each claim about a digital object identifier and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a digital object identifier, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "claim-provenance-q02", "text": "Who or what asserted this about a claim about a digital object identifier, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "claim-provenance-q03", "text": "What may an agent decide or do once a claim about a digital object identifier is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "time-and-versions", "name": "Time, versions and supersession", "description": "When a claim was true, when it was learnt, and what replaced it.", "findings": [ { "id": "validity-and-supersession", "name": "Validity period and supersession", "description": "How an old claim about a digital object identifier is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a digital object identifier, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "validity-and-supersession-q02", "text": "Who or what asserted this about the validity of a claim about a digital object identifier, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "validity-and-supersession-q03", "text": "What may an agent decide or do once the validity of a claim about a digital object identifier is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 12, "findings": 14, "questions": 38 } } } }