{ "model": { "rank": 5138, "code": "thing-q118455746", "model_id": "vr.tr.authority-control", "name": "authority control", "purpose": "Enable an agent to recognise, assess and maintain authority control that consistently identifies entities and manages the names and access points used to describe and retrieve them.", "family": "Thing Registry", "category": "Activities and processes", "status": "research-draft", "kind": "thing", "plane": "ACT", "domain": "ACT.ACT", "industry": "", "version": "", "url": "/models/thing/q118455746/", "tier": 2, "score": 69, "payload": { "layer": "wikidata", "aliases": [], "aliasCount": 0, "merged": 0, "knownIn": 69, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q118455746", "url": "https://www.wikidata.org/wiki/Q118455746", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:44:48Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 23.9, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\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: 01a08820-883d-7280-8924-78630cd5d60d\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: authority control\nSense to describe: (none recorded)\nDomain code: ACT.ACT\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 10", "usd": 0, "recall": true }, "codex": { "seconds": 60.3, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\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: 01a08820-8839-7693-b7a3-dd13d77ce575\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: authority control\nRegistry id: vr.tr.authority-control\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded into this entr" } } }, "metaModel": { "id": "THING-Q118455746", "registryId": "vr.tr.authority-control", "name": "authority control", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q118455746/", "model": { "registry_id": "vr.tr.authority-control", "name": "authority control", "purpose": "Enable an agent to recognise, assess and maintain authority control that consistently identifies entities and manages the names and access points used to describe and retrieve them.", "definition": "Authority control is the library and information-management practice of maintaining records that identify and distinguish entities and connect their preferred and variant names or titles so that descriptions and searches refer consistently to the intended entities.", "scope_statement": "This model owns authority control in the bibliographic and cultural heritage sense: the governed activity of distinguishing entities, managing authorised and variant access points, and maintaining their application across descriptive records; it does not cover political authority or access permissions.", "in_scope": [ "The authority policy and community within which an access point is authorised", "Identification and differentiation of persons, organisations, works, places and other entities covered by that policy", "Authorised, variant and multilingual names or access points linked to identified entities", "Evidence, uncertainty and review supporting identity and naming decisions", "Application, reconciliation and maintenance of authority links in descriptive records" ], "out_of_scope": [ "Authentication, permissions and cybersecurity access control", "Political legitimacy, institutional power and chains of command", "Complete bibliographic description and resource cataloguing", "General ontology construction and subject classification beyond their authority-control interfaces", "Comprehensive biographies or histories of the entities identified" ], "distinguishing_features": [ "A spelling-normalisation operation becomes authority control only when it supports a governed decision about an entity or controlled access point.", "Matching name strings alone does not establish identity: the process must accommodate different entities with identical names.", "Different names can lead to the same entity without requiring their original forms to be discarded.", "An authorised access point is preferred within a stated authority context, rather than asserted to be the universally correct name.", "An authority-control decision can affect links and retrieval across multiple descriptive records, rather than merely editing one displayed label." ], "characteristics": [ { "name": "Authority context", "kind": "relation", "unit_or_values": "Responsible agency, authority file, applicable policy and policy version", "why_it_matters": "Establishes where and under whose rules an access point or identity decision applies." }, { "name": "Controlled entity category", "kind": "category", "unit_or_values": "Person, organisation, work, expression, place, subject concept or locally defined category", "why_it_matters": "Determines which distinguishing evidence and access-point rules are relevant." }, { "name": "Identity resolution state", "kind": "state", "unit_or_values": "Unresolved, provisionally identified, established under policy, disputed or pending split", "why_it_matters": "Separates evidence-based identification from an unreviewed candidate match." }, { "name": "Access-point role", "kind": "category", "unit_or_values": "Authorised, variant, parallel authorised, historical or deprecated, qualified by authority context", "why_it_matters": "Controls how a name supports display, navigation and retrieval." }, { "name": "Name context", "kind": "relation", "unit_or_values": "Language, script, transliteration scheme, usage community and period of use", "why_it_matters": "Prevents context-specific names from being treated as interchangeable in every setting." }, { "name": "External identity mapping", "kind": "relation", "unit_or_values": "Target identifier, asserted relationship, supporting evidence and review state", "why_it_matters": "Distinguishes confirmed identity links from approximate or unresolved cross-file matches." }, { "name": "Authority-link coverage", "kind": "measurement", "unit_or_values": "Percentage of eligible descriptive access points linked to an applicable authority record, with denominator and date stated", "why_it_matters": "Shows how much of a defined catalogue actually benefits from authority control." }, { "name": "Maintenance state", "kind": "state", "unit_or_values": "Current, awaiting review, superseded, merged, split or withdrawn", "why_it_matters": "Determines whether an authority record can still be applied and what dependent records need attention." } ], "affordances": [ "Propose an authority record or access point with supporting evidence and explicit uncertainty.", "Distinguish namesakes and flag suspected conflation of separate entities.", "Connect variant and multilingual names to an identified entity under an applicable policy.", "Reconcile descriptive access points against authority files and route uncertain matches for review.", "Propose merges, splits or renamings while preserving decision history and affected links.", "Audit retrieval, linking coverage and propagation of approved authority changes." ] }, "sources": [], "structure": { "bundles": [ { "id": "authority-policy-and-scope", "name": "Authority policy and scope", "description": "The meaning, jurisdiction and operating rules of the authority-control activity.", "rationale": "An agent cannot judge whether a heading is authorised without knowing the community and rules that authorise it.", "layers": [ { "id": "control-approach", "name": "Control approach", "description": "How the implementation understands authority control and what it treats as a controlled instance.", "findings": [ { "id": "heading-and-identity-emphasis", "name": "Heading and identity emphasis", "description": "Record whether the approach prioritises consistent headings, persistent entity identity or both, and who endorses that approach.", "questions": [ { "text": "Does the responsible community define authority control primarily through authorised headings, entity identification or a combination?", "kind": "definition", "id": "heading-and-identity-emphasis-q01" }, { "text": "What distinguishes a controlled access point from an ordinary label or an unreviewed identifier link in this implementation?", "kind": "boundary", "id": "heading-and-identity-emphasis-q02" } ] } ] }, { "id": "policy-jurisdiction", "name": "Policy jurisdiction", "description": "The agency, catalogue, entity categories and rules to which authority decisions apply.", "findings": [ { "id": "applicable-authority-rules", "name": "Applicable authority rules", "description": "Identify the governing policy, its version and the limits of local discretion.", "questions": [ { "text": "Which agency and policy version govern construction and approval of these access points?", "kind": "provenance", "id": "applicable-authority-rules-q01" }, { "text": "When local practice conflicts with an external authority file, which decision may the agent apply and which requires review?", "kind": "action", "id": "applicable-authority-rules-q02" } ] } ] } ] }, { "id": "entity-identification-and-separation", "name": "Entity identification and separation", "description": "Evidence and decisions that establish what an authority record identifies.", "rationale": "Consistent names are insufficient if records conflate namesakes or separate references to the same entity.", "layers": [ { "id": "identity-evidence", "name": "Identity evidence", "description": "The sources and distinguishing attributes used to support identification.", "findings": [ { "id": "supported-entity-identification", "name": "Supported entity identification", "description": "Record the evidence connecting an observed name or resource attribution to a particular entity.", "questions": [ { "text": "Which consulted sources connect this name to this entity, and what does each source actually establish?", "kind": "provenance", "id": "supported-entity-identification-q01" }, { "text": "Which distinguishing attributes, such as dates, affiliations or associated works, support or contradict the proposed identification?", "kind": "measurement", "id": "supported-entity-identification-q02" } ] } ] }, { "id": "identity-boundaries", "name": "Identity boundaries", "description": "Treatment of namesakes, pseudonyms, organisational changes and other cases where identity boundaries need a policy decision.", "findings": [ { "id": "separate-or-shared-identities", "name": "Separate or shared identities", "description": "Make explicit whether related names represent one controlled identity, multiple linked identities or an unresolved case.", "questions": [ { "text": "Under the applicable policy, does this pseudonym or organisational name change require a variant name, a separate authority record or a successor relationship?", "kind": "boundary", "id": "separate-or-shared-identities-q01" }, { "text": "What additional evidence is required before the agent may merge suspected duplicates or split a conflated authority record?", "kind": "action", "id": "separate-or-shared-identities-q02" } ] } ] } ] }, { "id": "names-and-access-points", "name": "Names and access points", "description": "Selection, construction and contextual interpretation of controlled names.", "rationale": "Authority control must connect diverse naming practices to reliable access without confusing preference with universal correctness.", "layers": [ { "id": "authorised-access-point-selection", "name": "Authorised access point selection", "description": "The rules and evidence behind preferred forms and distinguishing additions.", "findings": [ { "id": "contextual-name-preference", "name": "Contextual name preference", "description": "Record why a particular form is authorised and how qualifiers distinguish it from competing access points.", "questions": [ { "text": "Which rule and evidence justify this authorised form and any dates, titles or other distinguishing additions?", "kind": "provenance", "id": "contextual-name-preference-q01" }, { "text": "Is this form authorised globally within the file, only for a particular language or catalogue, or alongside parallel authorised forms?", "kind": "boundary", "id": "contextual-name-preference-q02" } ] } ] }, { "id": "variant-and-multilingual-access", "name": "Variant and multilingual access", "description": "Alternative names, scripts and historical forms that support discovery.", "findings": [ { "id": "qualified-name-relationships", "name": "Qualified name relationships", "description": "Record how alternative forms relate to an entity and where their use is appropriate.", "questions": [ { "text": "Which variants are attested names, transliterations, abbreviations or historical forms, and what language, script or period qualifies each?", "kind": "provenance", "id": "qualified-name-relationships-q01" }, { "text": "Which forms should support search expansion, public display or historical interpretation under the relevant policy?", "kind": "action", "id": "qualified-name-relationships-q02" } ] } ] } ] }, { "id": "catalogue-application-and-reconciliation", "name": "Catalogue application and reconciliation", "description": "How authority decisions are applied to descriptive records and aligned across authority files.", "rationale": "A maintained authority file provides limited control unless its identities and access points are correctly connected to catalogue use.", "layers": [ { "id": "descriptive-record-linking", "name": "Descriptive record linking", "description": "Association of a resource's recorded access point with the intended authority identity.", "findings": [ { "id": "context-sensitive-link-assignment", "name": "Context-sensitive link assignment", "description": "Assess candidate links using resource context and retain unresolved assignments where evidence is insufficient.", "questions": [ { "text": "What evidence from this resource distinguishes the intended entity from other authorities with the same or similar name?", "kind": "provenance", "id": "context-sensitive-link-assignment-q01" }, { "text": "Which assignments may be accepted automatically, and which must remain unresolved or receive human review?", "kind": "action", "id": "context-sensitive-link-assignment-q02" } ] } ] }, { "id": "cross-file-alignment", "name": "Cross-file alignment", "description": "Mappings between independently governed authority records and identifiers.", "findings": [ { "id": "mapping-semantics-and-evidence", "name": "Mapping semantics and evidence", "description": "Distinguish asserted identity from relatedness or approximate correspondence across files with different identity policies.", "questions": [ { "text": "Does the external mapping assert the same entity, a related identity or only a candidate correspondence?", "kind": "definition", "id": "mapping-semantics-and-evidence-q01" }, { "text": "Do the two files treat pseudonyms, organisational succession or work boundaries differently enough to prevent an identity-equivalence link?", "kind": "boundary", "id": "mapping-semantics-and-evidence-q02" } ] } ] } ] }, { "id": "authority-maintenance-and-evaluation", "name": "Authority maintenance and evaluation", "description": "Review, correction and assessment of authority control over time.", "rationale": "Identity and naming decisions change, and their effects must be traceable across dependent records and retrieval behaviour.", "layers": [ { "id": "change-and-propagation", "name": "Change and propagation", "description": "Controlled handling of revised headings, merged identities, splits and retired records.", "findings": [ { "id": "traceable-authority-revision", "name": "Traceable authority revision", "description": "Record the grounds, approval and downstream consequences of an authority change.", "questions": [ { "text": "What evidence and authorised decision justify the revision, and how can the previous state be reconstructed?", "kind": "provenance", "id": "traceable-authority-revision-q01" }, { "text": "Which dependent links can be redirected safely, and which require reassessment because a split or changed identity boundary makes automatic reassignment ambiguous?", "kind": "action", "id": "traceable-authority-revision-q02" } ] } ] }, { "id": "control-quality-and-retrieval", "name": "Control quality and retrieval", "description": "Evaluation of identity correctness, authority-link coverage and discovery through alternative names.", "findings": [ { "id": "measured-authority-effectiveness", "name": "Measured authority effectiveness", "description": "Assess whether authority control brings relevant records together while keeping different entities apart.", "questions": [ { "text": "Within a defined catalogue sample, what proportion of eligible access points is correctly linked, incorrectly linked or unresolved?", "kind": "measurement", "id": "measured-authority-effectiveness-q01" }, { "text": "Do searches using attested variants retrieve the intended entity's resources without including resources belonging to namesakes?", "kind": "measurement", "id": "measured-authority-effectiveness-q02" } ] } ] } ] }, { "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-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "The name is interpreted in its library and information-science sense; no recorded sense was supplied.", "The boundary between name authority control and subject or vocabulary control varies across professional communities.", "Standards and identifier schemes are recalled without source consultation; current editions and maintenance arrangements should be checked." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of authority control this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Personal-name authority control", "Corporate-body authority control", "Geographic-name authority control", "Work and expression title authority control", "Subject authority control", "Genre/form authority control" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of authority control this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "Library of Congress Control Number (LCCN)", "value_or_pattern": "Alphabetic prefix with year and serial-number components for name authority records", "note": "Identifies an authority record; it is not exclusively a scheme for identifying people." }, { "scheme": "Virtual International Authority File (VIAF)", "value_or_pattern": "Numeric identifier", "note": "Identifies a cluster linking authority records contributed by participating institutions." }, { "scheme": "International Standard Name Identifier (ISNI)", "value_or_pattern": "16 characters: 15 digits followed by a digit or X", "note": "Identifies public identities of parties involved in creative activities." }, { "scheme": "ORCID iD", "value_or_pattern": "16 characters in four groups, with a final check character that can be X", "note": "Identifies individuals engaged in research and related activities; can support reconciliation with library authority records." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of authority control this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "RDA: Resource Description and Access, maintained under the RDA Steering Committee, provides guidance for describing entities and recording names, titles and relationships.", "MARC 21 Format for Authority Data, maintained by the Library of Congress with Library and Archives Canada, specifies machine-readable authority-record structures.", "IFLA Library Reference Model, issued by the International Federation of Library Associations and Institutions, provides a conceptual model for bibliographic entities and their appellations.", "ISO 27729, issued by the International Organization for Standardization, specifies the International Standard Name Identifier." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of authority control this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Bringing together works by the same person despite spelling changes, pseudonyms or different scripts.", "Separating different people or organizations that share a name.", "Connecting preferred subject terms with synonyms and related concepts for catalogue searching.", "Reconciling catalogue records across institutions and languages.", "Maintaining continuity when organizations change names or relationships between entities are clarified." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of authority control this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Conflating distinct entities that share names.", "Splitting one entity across duplicate authority records and fragmenting retrieval.", "Treating a preferred name in one catalogue or language as universally authoritative.", "Propagating incorrect dates, relationships or identity matches through shared records.", "Exposing sensitive identity information or retaining outdated and discriminatory terminology." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of authority control this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "National libraries and cataloguing communities can choose different preferred names, scripts and transliteration conventions.", "Subject authority vocabularies reflect different languages, cultural perspectives and institutional policies.", "Implementation varies with local cataloguing rules, cooperative programmes and adoption of international standards." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of authority control this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "Access control", "difference": "Access control determines permissions; authority control establishes consistent references to entities in information resources." }, { "name": "Entity resolution", "difference": "Entity resolution determines whether records refer to the same entity; authority control additionally maintains curated names, identifiers and relationships for continuing use." }, { "name": "Controlled vocabulary", "difference": "A controlled vocabulary supplies managed terms; authority control maintains the records and reference relationships that govern their consistent application." }, { "name": "Bibliographic description", "difference": "Bibliographic description records characteristics of resources; authority control manages consistent identification of entities associated with those resources." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of authority control this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend the bibliographic and cultural heritage sense of authority control, and does it include subject authority control as well as names and titles?", "Which reference sources and practitioner communities should anchor the distinction between heading-based authority control and entity-based identity management?", "Which policies should govern pseudonyms, organisational succession and work or expression boundaries when participating authority files disagree?", "How should self-identification, historical evidence and community naming preferences be weighed when selecting public access points?", "What evidence thresholds, review responsibilities and evaluation samples are appropriate for automated reconciliation in the intended deployment?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "abstract concept", "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 authority control, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise, assess and maintain authority control that consistently identifies entities and manages the names and access points used to describe and retrieve them.", "characteristics": { "substance": "activity", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Described in 69 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 authority control, and on what evidence are they told apart?" ], "whatItIsMadeOf": "something that happens over time", "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": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Nothing to see. What is recognised is an instance of it, and which instances count is exactly what is argued about." ], "relatedModels": [], "standing": "Described in 69 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one authority control from another, and a authority control 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 authority control, 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 authority control, 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 authority control 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 authority control, 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 authority control, 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 authority control 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 authority control 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 authority control, 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 authority control, 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 authority control 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 authority control from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a authority control, 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 authority control, 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 authority control 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 authority control 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 authority control between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a authority control, 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 authority control, 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 authority control 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 authority control, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a authority control 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 authority control, 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 authority control, 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 authority control is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "process-and-outcome", "name": "Process, inputs and outcome", "description": "How a authority control proceeds, what it needs and what it leaves behind.", "rationale": "An activity is known by its steps and its results, and both have to be recordable while it is still running.", "layers": [ { "id": "steps-and-sequence", "name": "Steps and sequence", "description": "The steps of a authority control, their order and what may run in parallel.", "findings": [ { "id": "steps-and-preconditions", "name": "Steps, preconditions and completion", "description": "What has to be true before each step of a authority control and what marks it done.", "questions": [ { "id": "steps-and-preconditions-q01", "text": "What identifies and describes a step of a authority control, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "steps-and-preconditions-q02", "text": "Who or what asserted this about a step of a authority control, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "steps-and-preconditions-q03", "text": "What may an agent decide or do once a step of a authority control is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "inputs-and-results", "name": "Inputs, resources and results", "description": "What a authority control consumes and what it produces.", "findings": [ { "id": "inputs-and-outputs", "name": "Inputs, outputs and side effects", "description": "The resources a authority control takes and the results it leaves, wanted or not.", "questions": [ { "id": "inputs-and-outputs-q01", "text": "What identifies and describes the inputs and results of a authority control, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "inputs-and-outputs-q02", "text": "Who or what asserted this about the inputs and results of a authority control, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "inputs-and-outputs-q03", "text": "What may an agent decide or do once the inputs and results of a authority control is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "definitions-in-contest", "name": "Definitions and who holds them", "description": "What authority control is taken to mean, and by whom.", "rationale": "When a field disagrees about a concept, the disagreement is the content. A model that picks one definition silently destroys the information.", "layers": [ { "id": "competing-definitions", "name": "Competing definitions", "description": "The main readings and the traditions behind them.", "findings": [ { "id": "definition-map", "name": "Definitions and their holders", "description": "Each definition with the school or body that holds it.", "questions": [ { "id": "definition-map-q01", "text": "Which definitions of authority control are in use, and which tradition or body holds each?", "kind": "definition" }, { "id": "definition-map-q02", "text": "What turns on the difference between them in practice?", "kind": "boundary" } ] } ] }, { "id": "operationalisation", "name": "Operationalisation", "description": "How it is measured or applied when it has to be.", "findings": [ { "id": "operational-record", "name": "Measures and proxies", "description": "Instruments and indicators used to stand in for it.", "questions": [ { "id": "operational-record-q01", "text": "How is authority control operationalised or measured in practice, and by what instrument?", "kind": "measurement" }, { "id": "operational-record-q02", "text": "What does that operationalisation leave out, and when does that matter?", "kind": "boundary" } ] } ] } ] }, { "id": "instances-and-use", "name": "Instances, use and consequence", "description": "What counts as an instance of authority control and what follows from calling something that.", "rationale": "Applying a concept is an act with consequences, so a model must say what the label licenses and what it does not.", "layers": [ { "id": "instances", "name": "What counts as an instance", "description": "Clear cases, borderline cases and non-cases.", "findings": [ { "id": "instance-tests", "name": "Tests for an instance", "description": "What would settle whether something falls under it.", "questions": [ { "id": "instance-tests-q01", "text": "What would settle whether something is an instance of authority control?", "kind": "boundary" }, { "id": "instance-tests-q02", "text": "Which borderline cases are argued about, and on what grounds?", "kind": "definition" } ] } ] }, { "id": "consequence", "name": "Consequence of application", "description": "Rights, duties or decisions that follow from the label.", "findings": [ { "id": "consequence-record", "name": "What the label licenses", "description": "What an agent may do once something is classified this way.", "questions": [ { "id": "consequence-record-q01", "text": "What follows practically once something is treated as authority control?", "kind": "action" }, { "id": "consequence-record-q02", "text": "What must an agent not infer from the label alone?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a authority control 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 authority control and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a authority control, 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 authority control, 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 authority control 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 authority control is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a authority control, 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 authority control, 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 authority control 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 } } } }