{ "model": { "rank": 4801, "code": "thing-q133153", "model_id": "vr.tr.iso-3166-2", "name": "ISO 3166-2", "purpose": "Enable an agent to recognise ISO 3166-2, assess the authority and currency of its subdivision-code information, and use that information without confusing code assignments with geographic or legal facts.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.MED", "industry": "", "version": "", "url": "/models/thing/q133153/", "tier": 2, "score": 72, "payload": { "layer": "wikidata", "aliases": [ "ISO 3166-2:BG" ], "aliasCount": 1, "merged": 1, "knownIn": 72, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q133153", "url": "https://www.wikidata.org/wiki/Q133153", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:01:45Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 19.7, "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: 01a087f9-04e4-7001-a704-5a80942c1551\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: ISO 3166-2\nSense to describe: (none recorded)\nDomain code: INF.MED\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 1001 regi", "usd": 0, "recall": true }, "codex": { "seconds": 66.5, "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: 01a087f9-04d5-7dc0-b6e8-30be8c615f9a\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: ISO 3166-2\nRegistry id: vr.tr.iso-3166-2\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCo" } } }, "metaModel": { "id": "THING-Q133153", "registryId": "vr.tr.iso-3166-2", "name": "ISO 3166-2", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q133153/", "model": { "registry_id": "vr.tr.iso-3166-2", "name": "ISO 3166-2", "purpose": "Enable an agent to recognise ISO 3166-2, assess the authority and currency of its subdivision-code information, and use that information without confusing code assignments with geographic or legal facts.", "definition": "ISO 3166-2 is the part of the International Organization for Standardization's ISO 3166 standard that assigns codes to principal subdivisions of countries and other territories represented in ISO 3166-1.", "scope_statement": "This model covers ISO 3166-2 as a standard and maintained country-subdivision coding system for registry entry vr.tr.iso-3166-2 in INF / INF.MED, including its editions, assignments, representations and conditions of use.", "in_scope": [ "Identity of ISO 3166-2 within the ISO 3166 family", "Structure and interpretation of subdivision code elements", "Country-specific subdivision names, categories and recorded relationships", "Authority, editions, data snapshots and assignment changes", "Validation, mapping and permitted reuse of subdivision-code information" ], "out_of_scope": [ "Independent modelling of ISO 3166-1 country codes or ISO 3166-3 formerly used country names", "Subdivision geometry, coordinates and boundary surveying", "Legal authority, sovereignty and territorial-dispute adjudication", "Complete national administrative classifications beyond ISO's recorded coverage", "Postal routing, address validation and geocoding systems", "Individual PDF files, database exports or printed copies as standalone artifacts" ], "distinguishing_features": [ "The designation identifies Part 2 of ISO 3166, concerning country subdivision codes, rather than country codes alone. [ISO standard record](https://www.iso.org/standard/72483.html)", "A subdivision code combines an ISO 3166-1 two-letter code, a separator and up to three alphanumeric characters; a bare country code or unqualified subdivision suffix does not identify the same kind of assignment. [ISO glossary](https://www.iso.org/glossary-for-iso-3166.html)", "A candidate string must be checked against an authoritative assignment at a relevant date; matching the code pattern alone cannot establish that ISO assigned it.", "The standard, a dated edition, a maintained assignment and a downloaded representation are distinguishable records with different identity and currency questions.", "A code assignment identifies a subdivision within this coding system; it does not itself supply a boundary polygon or establish legal jurisdiction." ], "characteristics": [ { "name": "Standard identity", "kind": "category", "unit_or_values": "ISO 3166-2; country subdivision coding standard", "why_it_matters": "Distinguishes the registered thing from neighbouring parts of ISO 3166 and from particular code elements." }, { "name": "Normative edition", "kind": "relation", "unit_or_values": "Identified ISO edition and its authoritative publication record", "why_it_matters": "Makes the rules being applied explicit without treating an edition date as the date of every assignment." }, { "name": "Assignment snapshot", "kind": "state", "unit_or_values": "Source, retrieval date and supplied update or release identifier", "why_it_matters": "Supports reproducible lookups and distinguishes current evidence from an older cached list." }, { "name": "Country-code dependency", "kind": "relation", "unit_or_values": "Referenced ISO 3166-1 alpha-2 assignment", "why_it_matters": "Establishes the namespace in which the subdivision suffix is interpreted." }, { "name": "Code element", "kind": "category", "unit_or_values": "Full country-prefixed subdivision code preserved as text", "why_it_matters": "Prevents suffix collisions and loss of significant characters through numeric conversion." }, { "name": "Subdivision designation", "kind": "relation", "unit_or_values": "Source-recorded subdivision names, language annotations, category and parent relationship where supplied", "why_it_matters": "Connects the identifier to its documented referent without assuming globally uniform administrative levels." }, { "name": "Assignment assessment", "kind": "state", "unit_or_values": "Agent assessment: confirmed at date, historical, unconfirmed or conflicting evidence", "why_it_matters": "Keeps uncertainty visible without presenting these assessment labels as ISO's own status vocabulary." }, { "name": "Reuse permission", "kind": "state", "unit_or_values": "Verified permissions and restrictions for the particular document, dataset or service", "why_it_matters": "Determines whether the agent may cache, transform, redistribute or embed the acquired material." } ], "affordances": [ "Resolve a supplied code against an identified authoritative snapshot", "Validate code structure and assignment separately", "Retrieve the recorded subdivision designation and country context", "Compare snapshots and flag changes requiring downstream review", "Propose evidence-backed mappings to national or application-specific identifiers", "Determine whether a particular representation may be reused for the intended operation" ] }, "sources": [], "structure": { "bundles": [ { "id": "standard-and-representation", "name": "Standard and representation", "description": "Identify the ISO 3166-2 standard separately from its editions and data carriers.", "rationale": "An agent must know whether it is interpreting a normative rule, consulting maintained assignments or reading a derivative copy.", "layers": [ { "id": "place-in-iso-3166", "name": "Place in ISO 3166", "description": "Establish the scope contributed by Part 2 and its dependency on country identifiers.", "findings": [ { "id": "subdivision-coding-scope", "name": "Subdivision coding scope", "description": "Record the part designation and the subdivision-coding scope supported by the identified edition.", "questions": [ { "text": "What does the applicable edition specify as ISO 3166-2's subdivision coverage?", "kind": "definition", "id": "subdivision-coding-scope-q01" }, { "text": "Which country-identification rules belong to ISO 3166-1 rather than this model?", "kind": "boundary", "id": "subdivision-coding-scope-q02" } ] } ] }, { "id": "edition-and-data-carrier", "name": "Edition and data carrier", "description": "Separate the standard's edition from the assignment data and their particular delivery formats.", "findings": [ { "id": "identified-consulted-resource", "name": "Identified consulted resource", "description": "Identify whether the evidence is an edition, an online record, an export or a derivative dataset, with its own date and provenance.", "questions": [ { "text": "Which edition and which assignment snapshot does the consulted resource represent?", "kind": "provenance", "id": "identified-consulted-resource-q01" }, { "text": "Is this resource authoritative for the proposed lookup, or must its claims be checked against ISO?", "kind": "action", "id": "identified-consulted-resource-q02" } ] } ] } ] }, { "id": "code-elements-and-validation", "name": "Code elements and validation", "description": "Interpret full code elements and distinguish structural validity from a confirmed assignment.", "rationale": "A plausible string can still be unassigned, historical or misinterpreted outside its country context.", "layers": [ { "id": "country-qualified-syntax", "name": "Country-qualified syntax", "description": "Preserve the country prefix, separator and subdivision suffix as a single textual identifier.", "findings": [ { "id": "lossless-code-parsing", "name": "Lossless code parsing", "description": "Determine the applicable character and length rules and retain the original input alongside any normalised candidate.", "questions": [ { "text": "Does the complete input satisfy the applicable edition's code-element syntax?", "kind": "measurement", "id": "lossless-code-parsing-q01" }, { "text": "Would normalisation remove significant characters, or treat an isolated suffix as globally unique?", "kind": "boundary", "id": "lossless-code-parsing-q02" } ] } ] }, { "id": "assignment-resolution", "name": "Assignment resolution", "description": "Resolve a structurally acceptable code against a specified assignment source and date.", "findings": [ { "id": "evidenced-code-membership", "name": "Evidenced code membership", "description": "Report whether the consulted evidence confirms the assignment, without treating lookup failure in a partial dataset as proof of nonexistence.", "questions": [ { "text": "Which authoritative record confirms this full code and its subdivision at the requested date?", "kind": "provenance", "id": "evidenced-code-membership-q01" }, { "text": "Should the agent accept, reject or defer the input when evidence is incomplete or contradictory?", "kind": "action", "id": "evidenced-code-membership-q02" } ] } ] } ] }, { "id": "subdivision-semantics", "name": "Subdivision semantics", "description": "Connect code assignments to documented names, subdivision categories and country-specific organisation.", "rationale": "Name matching and administrative comparisons require more than a code string and must respect differences between countries.", "layers": [ { "id": "names-and-language", "name": "Names and language", "description": "Distinguish recorded subdivision names from translations, aliases and application display labels.", "findings": [ { "id": "source-qualified-designations", "name": "Source-qualified designations", "description": "Preserve source-provided spelling and language annotations while recording separately any locally introduced labels.", "questions": [ { "text": "Which names and language annotations are actually supplied by the authoritative record?", "kind": "provenance", "id": "source-qualified-designations-q01" }, { "text": "What evidence distinguishes an alternate name for one assignment from a similarly named different subdivision?", "kind": "boundary", "id": "source-qualified-designations-q02" } ] } ] }, { "id": "categories-and-hierarchy", "name": "Categories and hierarchy", "description": "Interpret country-specific subdivision categories and parent relationships only where documented.", "findings": [ { "id": "documented-administrative-context", "name": "Documented administrative context", "description": "Record the category and any parent relationship without assuming every country uses the same depth or that suffixes encode hierarchy.", "questions": [ { "text": "What subdivision category and parent relationship, if any, does the country entry explicitly record?", "kind": "definition", "id": "documented-administrative-context-q01" }, { "text": "Which geographic units or administrative levels fall outside this country's recorded ISO coverage?", "kind": "boundary", "id": "documented-administrative-context-q02" } ] } ] } ] }, { "id": "maintenance-and-time", "name": "Maintenance and time", "description": "Track the authority and temporal interpretation of assignment information.", "rationale": "A fixed edition citation does not by itself establish whether a local code list is current or suitable for historical records.", "layers": [ { "id": "authoritative-maintenance", "name": "Authoritative maintenance", "description": "Identify ISO maintenance evidence and distinguish it from third-party update claims.", "findings": [ { "id": "maintenance-evidence", "name": "Maintenance evidence", "description": "ISO identifies its Maintenance Agency as responsible for country and subdivision assignments and points to the Online Browsing Platform for access. [ISO country codes](https://www.iso.org/iso-3166-country-codes.html)", "questions": [ { "text": "Which ISO record supports the particular addition, deletion or other change being asserted?", "kind": "provenance", "id": "maintenance-evidence-q01" }, { "text": "When was the local snapshot retrieved, and what evidence establishes its update coverage?", "kind": "measurement", "id": "maintenance-evidence-q02" } ] } ] }, { "id": "historical-interpretation", "name": "Historical interpretation", "description": "Keep changes to codes, names and administrative entities distinguishable.", "findings": [ { "id": "change-aware-record-handling", "name": "Change-aware record handling", "description": "Represent documented changes without assuming a rename, code replacement and territorial reorganisation have identical consequences.", "questions": [ { "text": "Does the evidence describe a name change, code change, category change or change to the represented subdivision?", "kind": "definition", "id": "change-aware-record-handling-q01" }, { "text": "Can a historical record be migrated unambiguously, or should its original code and date be retained pending review?", "kind": "action", "id": "change-aware-record-handling-q02" } ] } ] } ] }, { "id": "interoperation-and-reuse", "name": "Interoperation and reuse", "description": "Control mappings to other systems and establish permissions for the material used.", "rationale": "Operational use requires both a justified identifier mapping and evidence that the chosen document or dataset can be used as intended.", "layers": [ { "id": "external-code-mappings", "name": "External code mappings", "description": "Evaluate crosswalks to national codes, postal systems, statistical regions and geographic datasets.", "findings": [ { "id": "qualified-crosswalk", "name": "Qualified crosswalk", "description": "Record mapping evidence, date and cardinality, with unresolved differences in coverage or territorial meaning.", "questions": [ { "text": "Does the external identifier denote the same subdivision at the same date, or only an overlapping or similarly named area?", "kind": "boundary", "id": "qualified-crosswalk-q01" }, { "text": "Is the proposed mapping one-to-one, one-to-many, many-to-one or unresolved?", "kind": "measurement", "id": "qualified-crosswalk-q02" } ] } ] }, { "id": "resource-use-conditions", "name": "Resource use conditions", "description": "Assess the specific terms governing normative text, online access, exports and derivative datasets.", "findings": [ { "id": "permitted-material-use", "name": "Permitted material use", "description": "Attach permission evidence to the particular resource and intended operation; accessibility alone does not establish redistribution rights.", "questions": [ { "text": "Which terms apply to the exact document, export or service the agent acquired?", "kind": "provenance", "id": "permitted-material-use-q01" }, { "text": "Do those terms permit the intended caching, transformation, embedding or redistribution?", "kind": "action", "id": "permitted-material-use-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": [ "This description is recalled knowledge; no sources were consulted.", "Verify the applicable edition and current ISO 3166 Maintenance Agency updates before using individual assignments operationally.", "Check country-specific coverage and historical code changes rather than assuming all administrative units are included." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of ISO 3166-2 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": "ISO standard designation", "value_or_pattern": "ISO 3166-2", "note": "Identifies the standard part; a dated edition additionally includes a publication year." }, { "scheme": "ISO 3166-2 subdivision code", "value_or_pattern": "AA-X to AA-XXX", "note": "An ISO 3166-1 alpha-2 code, a hyphen, and one to three alphanumeric characters identifying a subdivision; for example, US-CA identifies California." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of ISO 3166-2 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": [ "ISO 3166-2, issued by ISO, specifies codes for country subdivisions.", "ISO 3166-1, issued by ISO, supplies the country and territory codes used as prefixes." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of ISO 3166-2 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": [ "Identifying administrative subdivisions in databases and data exchanges.", "Normalizing state, province, or region fields in address records.", "Joining geographic, statistical, and business datasets by subdivision.", "Supporting subdivision selection in software interfaces." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of ISO 3166-2 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": [ "Outdated code lists can misrepresent subdivisions after administrative changes.", "Removing the country prefix destroys the full identifier and can create collisions.", "Assuming every country uses the same subdivision types or administrative levels produces incorrect comparisons.", "Treating a subdivision code as a postal code or a boundary geometry confuses distinct kinds of information.", "Assuming codes are permanent can corrupt historical records when assignments change." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of ISO 3166-2 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": [ "Covered subdivision categories vary by country and can include states, provinces, regions, departments, and other administrative units.", "Subdivision suffixes can be alphabetic, numeric, or alphanumeric.", "Coverage and administrative hierarchy vary between country entries; the standard does not impose a uniform worldwide administrative structure." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of ISO 3166-2 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": "ISO 3166-1", "difference": "Identifies countries and certain territories rather than their principal subdivisions." }, { "name": "ISO 3166-3", "difference": "Codes formerly used country names rather than current country subdivisions." }, { "name": "Postal code", "difference": "Supports postal routing or delivery geography rather than identifying subdivisions under ISO 3166-2." }, { "name": "Administrative boundary dataset", "difference": "Represents geographic boundaries; ISO 3166-2 supplies identifiers and associated subdivision information, not boundary geometry." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of ISO 3166-2 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which normative edition and dated assignment source should govern the intended Vercy deployment?", "What country-specific coverage exceptions and hierarchy conventions must be verified before implementing subdivision selection?", "What authoritative historical records are available to establish change dates and successor relationships without guessing?", "Which exact acquisition and reuse terms apply to the ISO resources or third-party datasets selected for integration?", "How should Vercy resolve conflicting crosswalks when national administrative records, geographic datasets and ISO assignments reflect different dates?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "questions": 27 } }, "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 ISO 3166-2, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise ISO 3166-2, assess the authority and currency of its subdivision-code information, and use that information without confusing code assignments with geographic or legal facts.", "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: ISO 3166-2:BG.", "1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 72 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 ISO 3166-2, 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": [ "ISO 3166-2:BG" ] } ], "standing": "Described in 72 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 ISO 3166-2 from another, and a ISO 3166-2 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 ISO 3166-2, 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 ISO 3166-2, 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 ISO 3166-2 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 ISO 3166-2, 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 ISO 3166-2, 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 ISO 3166-2 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 ISO 3166-2 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 ISO 3166-2, 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 ISO 3166-2, 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 ISO 3166-2 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 ISO 3166-2 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a ISO 3166-2, 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 ISO 3166-2, 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 ISO 3166-2 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 ISO 3166-2 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 ISO 3166-2 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a ISO 3166-2, 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 ISO 3166-2, 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 ISO 3166-2 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 ISO 3166-2, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a ISO 3166-2 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 ISO 3166-2, 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 ISO 3166-2, 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 ISO 3166-2 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 ISO 3166-2 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 ISO 3166-2 contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a ISO 3166-2, 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 ISO 3166-2, 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 ISO 3166-2 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 ISO 3166-2 and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a ISO 3166-2, 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 ISO 3166-2, 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 ISO 3166-2 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 ISO 3166-2 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 ISO 3166-2, 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 ISO 3166-2 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 ISO 3166-2 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 ISO 3166-2, 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 ISO 3166-2, 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 ISO 3166-2 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 ISO 3166-2 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a ISO 3166-2, 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 ISO 3166-2, 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 ISO 3166-2 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 ISO 3166-2 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a ISO 3166-2, 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 ISO 3166-2, 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 ISO 3166-2 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 } } } }