{ "model": { "rank": 2438, "code": "thing-q14296", "model_id": "vr.tr.top-level-domain", "name": "top-level domain", "purpose": "Enable an AI agent to recognise a top-level domain, assess its delegation and operational state, and determine which naming or administrative actions are supported and authorised.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.MED", "industry": "", "version": "", "url": "/models/thing/q14296/", "tier": 2, "score": 106, "payload": { "layer": "wikidata", "aliases": [ "pseudo-top-level domain", "generic top-level domain", "country code top-level domain", "GeoTLD", "test top-level domain", "unassigned top-level domain", "Special-use domain name", "internationalized country code top-level domain", "sponsored top-level domain" ], "aliasCount": 9, "merged": 9, "knownIn": 106, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q14296", "url": "https://www.wikidata.org/wiki/Q14296", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T09:17:50Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": null, "turns": null, "seconds": 14, "error": "Error: Internal error: {\n \"message\": \"API error (status 402 Payment Required): Grok Build usage balance exhausted\",\n \"http_status\": 402\n}", "retried": true }, "codex": { "seconds": 100.8, "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: 01a07b27-5465-7871-a371-a0d0aea8439e\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: top-level domain\nRegistry id: vr.tr.top-level-domain\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry:" } } }, "metaModel": { "id": "THING-Q14296", "registryId": "vr.tr.top-level-domain", "name": "top-level domain", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q14296/", "model": { "registry_id": "vr.tr.top-level-domain", "name": "top-level domain", "purpose": "Enable an AI agent to recognise a top-level domain, assess its delegation and operational state, and determine which naming or administrative actions are supported and authorised.", "definition": "", "scope_statement": "This model owns the identity, root-relative position, delegation, governance, registration boundaries, operational condition and lifecycle of a top-level domain under vr.tr.top-level-domain in INF / INF.MED, with the DNS root context explicitly recorded.", "in_scope": [ "Canonical TLD label, internationalised representations and root context", "Root delegation status and authoritative service relationships", "TLD manager, technical operator and applicable administrative authority", "Registration hierarchy, eligibility and namespace restrictions", "TLD-level DNS health, DNSSEC condition and application compatibility", "Delegation changes, operator transitions and retirement" ], "out_of_scope": [ "Individual descendant domain registrations, ownership and renewal histories", "Websites, email services and content hosted under descendant domains", "Registry and registrar organisations beyond their roles for this TLD", "DNS server infrastructure inventories and implementation details", "Root-zone governance beyond its decisions affecting this TLD", "Browser cookie and site-boundary rules beyond their relationship to this TLD" ], "distinguishing_features": [ "Its domain node is immediately below the DNS root in the recorded namespace; example.com is below a TLD, while com is a TLD. [RFC 9499](https://www.rfc-editor.org/rfc/rfc9499.html)", "A public suffix can contain multiple labels, such as co.uk; top-level status depends on root-relative position rather than the registration boundary. [RFC 9499](https://www.rfc-editor.org/rfc/rfc9499.html)", "A claim of current public-root delegation must be supported by root-delegation evidence, rather than the string merely appearing at the end of a name. [IANA Root Zone Database](https://www.iana.org/domains/root/db)", "The TLD is a namespace domain; its registry operator is a related organisation whose identity can change. [IANA Root Zone Management](https://www.iana.org/domains/root)", "The TLD domain includes its descendants, whereas its authoritative DNS zone stops at delegated zone boundaries. [RFC 9499](https://www.rfc-editor.org/rfc/rfc9499.html)" ], "characteristics": [ { "name": "Canonical label", "kind": "category", "unit_or_values": "Canonical DNS label; Unicode and ASCII-compatible representations where applicable", "why_it_matters": "Supports consistent identification without treating display variants as separate TLDs." }, { "name": "Root context", "kind": "relation", "unit_or_values": "Identified public, private or alternative DNS root", "why_it_matters": "Prevents identical labels in different namespaces from being conflated." }, { "name": "Administrative classification", "kind": "category", "unit_or_values": "Source-attested classification and scheme, such as country-code, generic or infrastructure; unknown", "why_it_matters": "Directs the agent to the applicable administrative and lifecycle procedures." }, { "name": "Root delegation state", "kind": "state", "unit_or_values": "Present, absent, conflicting evidence or unknown, with observation time", "why_it_matters": "Separates observed delegation from proposals, historical records and administrative intent." }, { "name": "Lifecycle stage", "kind": "state", "unit_or_values": "Proposed, approved awaiting delegation, operating, transitioning, retiring, retired or unknown, with evidence", "why_it_matters": "Determines whether provisioning or change requests are appropriate." }, { "name": "Responsible parties", "kind": "relation", "unit_or_values": "TLD manager, registry service provider and change-authorising parties, each with effective dates", "why_it_matters": "Identifies responsibility and authority without assuming one organisation performs every role." }, { "name": "Registration boundary and eligibility", "kind": "category", "unit_or_values": "Permitted registration levels, eligible applicants, reserved branches and applicable policy version", "why_it_matters": "Determines whether and where a proposed descendant name can be registered." }, { "name": "Authoritative query success", "kind": "measurement", "unit_or_values": "Percentage of successful authoritative queries, with sample size, query types, vantage points and time window", "why_it_matters": "Provides bounded evidence of TLD DNS availability." }, { "name": "DNSSEC validation condition", "kind": "state", "unit_or_values": "Secure, insecure, bogus or indeterminate, with trust anchor, queried data and observation time", "why_it_matters": "Distinguishes authenticated operation, unsigned delegation and validation failures." }, { "name": "Application acceptance", "kind": "measurement", "unit_or_values": "Acceptance rate across a named test set of applications and TLD representations, with test date", "why_it_matters": "Reveals whether technically valid names are rejected by relevant user-facing systems." } ], "affordances": [ "Identify a TLD from a domain name using an explicit root context and verified label representation.", "Verify delegation and compare published administrative records with observed DNS behaviour.", "Evaluate a proposed descendant registration against the TLD's hierarchy and eligibility rules.", "Assess TLD DNS availability, DNSSEC validation and application acceptance using bounded observations.", "Prepare and, where authorised, submit delegation, nameserver, DS-record or operator-change requests.", "Track transition or retirement conditions and identify dependent namespaces requiring follow-up." ] }, "sources": [], "structure": { "bundles": [ { "id": "tld-identity", "name": "TLD identity", "description": "Establish which root-level domain is being modelled and how its label is represented.", "rationale": "A suffix string alone cannot establish namespace identity or public delegation.", "layers": [ { "id": "root-relative-identity", "name": "Root-relative identity", "description": "Locate the domain directly beneath a specified DNS root.", "findings": [ { "id": "root-and-label", "name": "Root and label", "description": "Record the canonical label and root context needed to identify this TLD.", "questions": [ { "text": "What canonical label and DNS root jointly identify this top-level domain?", "kind": "definition", "id": "root-and-label-q01" }, { "text": "What evidence establishes its position directly beneath that root, and is it currently delegated there?", "kind": "provenance", "id": "root-and-label-q02" } ] } ] }, { "id": "label-representations", "name": "Label representations", "description": "Separate equivalent encodings from distinct labels and related variants.", "findings": [ { "id": "encoding-and-variants", "name": "Encoding and variants", "description": "Record usable label forms and the evidence for equivalence or variant relationships.", "questions": [ { "text": "Which ASCII and Unicode forms represent this same TLD label, and under which conversion rules?", "kind": "definition", "id": "encoding-and-variants-q01" }, { "text": "Which similar or variant labels are separate TLDs, reserved labels or blocked labels rather than equivalent representations?", "kind": "boundary", "id": "encoding-and-variants-q02" } ] } ] } ] }, { "id": "delegation-and-authority", "name": "Delegation and authority", "description": "Connect the root delegation to the parties and procedures responsible for this TLD.", "rationale": "An agent must establish both delegation evidence and authority before proposing administrative changes.", "layers": [ { "id": "root-delegation-evidence", "name": "Root delegation evidence", "description": "Record dated evidence of the TLD's presence and referral data in its root.", "findings": [ { "id": "published-delegation", "name": "Published delegation", "description": "Establish the observed root delegation and reconcile it with administrative records.", "questions": [ { "text": "Which dated root-zone observations establish the TLD's delegation, nameservers and any associated glue or DS records?", "kind": "provenance", "id": "published-delegation-q01" }, { "text": "Do the delegation records and the responsible registry's published information agree, and which differences remain unresolved?", "kind": "measurement", "id": "published-delegation-q02" } ] } ] }, { "id": "management-mandate", "name": "Management mandate", "description": "Identify accountable parties and the specific authority governing TLD changes.", "findings": [ { "id": "manager-and-change-rights", "name": "Manager and change rights", "description": "Distinguish the recognised TLD manager, technical provider and authorised change requesters.", "questions": [ { "text": "Who is recognised as the TLD manager, who supplies registry and DNS services, and what dated records establish those roles?", "kind": "provenance", "id": "manager-and-change-rights-q01" }, { "text": "Which TLD-specific procedure and authorisations are required to change its delegation or responsible manager?", "kind": "action", "id": "manager-and-change-rights-q02" } ] } ] } ] }, { "id": "registration-namespace", "name": "Registration namespace", "description": "Describe how this TLD partitions its descendants and permits new registrations.", "rationale": "Top-level delegation does not establish where registration is possible or who may register.", "layers": [ { "id": "registration-hierarchy", "name": "Registration hierarchy", "description": "Identify registration levels and branches administered under different rules.", "findings": [ { "id": "registrable-boundaries", "name": "Registrable boundaries", "description": "Record where applicants can obtain names and which branches have separate policies.", "questions": [ { "text": "Are registrations available directly beneath this TLD, beneath designated second-level branches, or through both arrangements?", "kind": "definition", "id": "registrable-boundaries-q01" }, { "text": "Which descendant branches have separate registration authorities, and how do those boundaries relate to relevant public-suffix rules?", "kind": "boundary", "id": "registrable-boundaries-q02" } ] } ] }, { "id": "registration-admissibility", "name": "Registration admissibility", "description": "Capture the rules that make a proposed applicant and label eligible.", "findings": [ { "id": "applicant-and-label-rules", "name": "Applicant and label rules", "description": "Establish applicable eligibility, reservation and internationalised-label constraints.", "questions": [ { "text": "Which current policies govern applicant eligibility, reserved names, supported scripts and variant treatment for the proposed registration branch?", "kind": "provenance", "id": "applicant-and-label-rules-q01" }, { "text": "Given an applicant and proposed label, which checks and registration channel are required before a registration request is admissible?", "kind": "action", "id": "applicant-and-label-rules-q02" } ] } ] } ] }, { "id": "authoritative-dns-condition", "name": "Authoritative DNS condition", "description": "Assess whether the delegated TLD is served coherently and validates as expected.", "rationale": "Published delegation alone does not establish usable or correctly authenticated DNS service.", "layers": [ { "id": "authoritative-service", "name": "Authoritative service", "description": "Measure the behaviour of the TLD's delegated authoritative service.", "findings": [ { "id": "reachability-and-consistency", "name": "Reachability and consistency", "description": "Record query results with enough context to distinguish persistent faults from bounded observations.", "questions": [ { "text": "Across which times, network vantage points, transports and address families do the delegated servers return appropriate authoritative responses?", "kind": "measurement", "id": "reachability-and-consistency-q01" }, { "text": "Do parent referrals, apex nameserver records and observed zone versions reveal persistent inconsistency or expected propagation?", "kind": "measurement", "id": "reachability-and-consistency-q02" } ] } ] }, { "id": "delegation-authentication", "name": "Delegation authentication", "description": "Assess the DNSSEC chain between the selected root and TLD zone.", "findings": [ { "id": "dnssec-chain-condition", "name": "DNSSEC chain condition", "description": "Record validation outcomes and the evidence needed for safe key or DS changes.", "questions": [ { "text": "Using which trust anchor and observation time do the parent DS records, TLD DNSKEY records and signed responses validate or fail?", "kind": "measurement", "id": "dnssec-chain-condition-q01" }, { "text": "What verified rollover stage, timing constraints and authorisations govern the next DNSKEY or parent DS change?", "kind": "action", "id": "dnssec-chain-condition-q02" } ] } ] } ] }, { "id": "resolution-and-application-boundaries", "name": "Resolution and application boundaries", "description": "Determine where names under this TLD resolve and are accepted by relevant applications.", "rationale": "A TLD may have different practical usability across resolver contexts and application implementations.", "layers": [ { "id": "resolution-context", "name": "Resolution context", "description": "Separate public-root behaviour from local overrides, filtering and conflicting namespaces.", "findings": [ { "id": "context-dependent-results", "name": "Context-dependent results", "description": "Record resolution differences without interpreting every local failure as a TLD outage.", "questions": [ { "text": "Does the same fully qualified name produce different results through the public root, private resolvers or alternative roots?", "kind": "measurement", "id": "context-dependent-results-q01" }, { "text": "Which observed differences arise from local naming, filtering or caching rather than the TLD's authoritative service?", "kind": "boundary", "id": "context-dependent-results-q02" } ] } ] }, { "id": "application-acceptance", "name": "Application acceptance", "description": "Test whether relevant software handles this TLD and its label representations correctly.", "findings": [ { "id": "tld-recognition-in-applications", "name": "TLD recognition in applications", "description": "Identify TLD-specific rejection, parsing and display problems in a defined application set.", "questions": [ { "text": "Which tested applications accept valid domain names or email addresses under this TLD, using each applicable label representation?", "kind": "measurement", "id": "tld-recognition-in-applications-q01" }, { "text": "What evidence distinguishes a TLD-recognition or encoding defect from a failure of the particular descendant service?", "kind": "boundary", "id": "tld-recognition-in-applications-q02" } ] } ] } ] }, { "id": "tld-transition-and-retirement", "name": "TLD transition and retirement", "description": "Track changes to the TLD's operational mandate, service provision and continued delegation.", "rationale": "TLD changes can affect many descendant namespaces and require explicit continuity conditions.", "layers": [ { "id": "operator-and-service-transition", "name": "Operator and service transition", "description": "Distinguish changes in managerial responsibility from changes in technical service provision.", "findings": [ { "id": "transition-readiness", "name": "Transition readiness", "description": "Record the authorised transition and evidence that namespace service can continue.", "questions": [ { "text": "Is the proposed change a transfer of TLD management, a technical-provider migration or a delegation-data update, and what establishes its effective date?", "kind": "definition", "id": "transition-readiness-q01" }, { "text": "Which continuity checks, DNSSEC coordination steps and recovery arrangements must be satisfied before this transition proceeds?", "kind": "action", "id": "transition-readiness-q02" } ] } ] }, { "id": "retirement-and-removal", "name": "Retirement and removal", "description": "Capture the grounds, stages and consequences of ending the TLD's operation.", "findings": [ { "id": "retirement-obligations", "name": "Retirement obligations", "description": "Establish the applicable retirement decision and distinguish administrative milestones from observed removal.", "questions": [ { "text": "What authoritative decision or policy establishes retirement, registration restrictions and any planned root-removal date?", "kind": "provenance", "id": "retirement-obligations-q01" }, { "text": "Which descendant namespaces and service dependencies require notification, migration or continued support before delegation can end?", "kind": "action", "id": "retirement-obligations-q02" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend this entry to include TLDs in private and alternative DNS roots, or only the public DNS root?", "Should proposed, reserved and special-use root-level labels be represented as lifecycle cases here or linked to neighbouring naming-designation models?", "Which authoritative sources and precedence rules should reconcile administrative records, live root observations and operator statements when they disagree?", "Which per-TLD rules govern internationalised variants, and which relationships imply coordinated operation rather than identity?", "What observation windows and evidence thresholds should classify TLD-wide degradation, application incompatibility and readiness for transition or retirement?" ], "statistics": { "bundles": 6, "layers": 12, "findings": 12, "questions": 24 } }, "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 top-level domain, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a top-level domain, assess its delegation and operational state, and determine which naming or administrative actions are supported and authorised.", "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: pseudo-top-level domain, generic top-level domain, country code top-level domain, GeoTLD, test top-level domain, unassigned top-level domain, Special-use domain name, internationalized country code top-level domain, sponsored top-level domain.", "9 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 106 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 top-level domain, 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": [ "pseudo-top-level domain", "generic top-level domain", "country code top-level domain", "GeoTLD", "test top-level domain", "unassigned top-level domain", "Special-use domain name", "internationalized country code top-level domain", "sponsored top-level domain" ] } ], "standing": "Described in 106 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 9 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 top-level domain from another, and a top-level domain 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 top-level domain, 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 top-level domain, 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 top-level domain 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 top-level domain, 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 top-level domain, 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 top-level domain 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 top-level domain 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 top-level domain, 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 top-level domain, 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 top-level domain 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 top-level domain from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a top-level domain, 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 top-level domain, 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 top-level domain 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 top-level domain 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 top-level domain between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a top-level domain, 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 top-level domain, 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 top-level domain 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 top-level domain, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a top-level domain 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 top-level domain, 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 top-level domain, 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 top-level domain 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 top-level domain 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 top-level domain contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a top-level domain, 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 top-level domain, 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 top-level domain 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 top-level domain and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a top-level domain, 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 top-level domain, 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 top-level domain 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 top-level domain 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 top-level domain, 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 top-level domain 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 top-level domain 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 top-level domain, 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 top-level domain, 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 top-level domain 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 top-level domain and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a top-level domain, 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 top-level domain, 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 top-level domain 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 top-level domain is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a top-level domain, 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 top-level domain, 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 top-level domain 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 } } } }