{ "model": { "rank": 5665, "code": "thing-q25754", "model_id": "vr.tr.bibcode", "name": "bibcode", "purpose": "Enable an AI agent to recognise a bibcode, establish which bibliographic record it identifies, assess the reliability of that identification, and choose justified lookup, linking or correction actions.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.MED", "industry": "", "version": "", "url": "/models/thing/q25754/", "tier": 2, "score": 65, "payload": { "layer": "wikidata", "aliases": [ "ADS bibcode" ], "aliasCount": 1, "merged": 1, "knownIn": 65, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q25754", "url": "https://www.wikidata.org/wiki/Q25754", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T08:57:13Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": null, "turns": null, "seconds": 15.8, "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": 87.6, "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: 01a07b14-a936-7dc3-a38f-3346b128ae5b\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: bibcode\nRegistry id: vr.tr.bibcode\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Vercy m" } } }, "metaModel": { "id": "THING-Q25754", "registryId": "vr.tr.bibcode", "name": "bibcode", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q25754/", "model": { "registry_id": "vr.tr.bibcode", "name": "bibcode", "purpose": "Enable an AI agent to recognise a bibcode, establish which bibliographic record it identifies, assess the reliability of that identification, and choose justified lookup, linking or correction actions.", "definition": "", "scope_statement": "This model owns the bibcode as an identifier registered under vr.tr.bibcode: its exact representation, interpretation, assignment evidence, resolution state and relationships to other identifiers; it does not own the identified publication.", "in_scope": [ "Exact bibcode text and its extraction from citations, URLs or bibliographic records", "Interpretation of positional components under an evidenced bibcode convention", "Evidence that a bibliographic service recognises and assigns the code", "Agreement between the resolved record and the intended citation", "Service-reported canonical, alternative or superseding identifier relationships", "Permissible lookup, preservation, linking and correction actions" ], "out_of_scope": [ "The publication's scientific claims, methods and evidential quality", "Complete bibliographic descriptions and citation-style rendering", "Author identity and researcher identifier management", "Journal identity, editorial policy and publication schedules", "DOI registration and arXiv identifier lifecycle", "Full-text hosting, access rights and licensing" ], "distinguishing_features": [ "A conventional bibcode has 19 characters arranged as YYYYJJJJJVVVVMPPPPA, with periods used for padding; appearance alone does not establish assignment. See [ADS bibcode documentation](https://ui.adsabs.harvard.edu/help/actions/bibcode).", "Its conventional positions encode publication year, publication abbreviation, volume or publication type, qualifier, page-related information and first-author surname initial. See [ADS format guidance](httpswww.adsabs.harvard.edu/abs_doc/help_pages/data.html).", "A candidate should be tested as a bibcode identifier in a bibliographic service; a locally chosen BibTeX citation key does not become a bibcode merely by resembling one.", "A DOI, arXiv identifier or ADS page URL may lead to related material, but each must remain distinguishable from the exact bibcode token." ], "characteristics": [ { "name": "Exact identifier text", "kind": "category", "unit_or_values": "Literal character sequence, preserving case, punctuation and padding", "why_it_matters": "Prevents extraction or normalisation from silently changing the identifier." }, { "name": "Token length", "kind": "measurement", "unit_or_values": "Characters; conventional bibcode length is 19", "why_it_matters": "Detects truncation, attached punctuation and incomplete search patterns without claiming that length proves validity." }, { "name": "Representation assessment", "kind": "state", "unit_or_values": "Unexamined | conventional form | documented exception | malformed | uncertain", "why_it_matters": "Separates ordinary parsing from exceptions requiring additional evidence." }, { "name": "Component interpretation", "kind": "category", "unit_or_values": "Year, publication abbreviation, volume-or-type, qualifier, locator and author initial; each interpreted, uninterpreted or disputed", "why_it_matters": "Supports citation comparison while making incomplete decoding visible." }, { "name": "Assignment evidence", "kind": "state", "unit_or_values": "Constructed candidate | externally asserted | service-confirmed | disputed", "why_it_matters": "Distinguishes a plausible generated string from a recognised identifier." }, { "name": "Resolution observation", "kind": "state", "unit_or_values": "Unchecked | matched | no match | redirected | ambiguous response | service failure; qualified by service and observation time", "why_it_matters": "Prevents a temporary lookup failure from being treated as proof of an invalid bibcode." }, { "name": "Identified bibliographic record", "kind": "relation", "unit_or_values": "Service-qualified record reference with retrieval evidence", "why_it_matters": "Anchors interpretation to the actual record returned." }, { "name": "Citation agreement", "kind": "state", "unit_or_values": "Uncompared | consistent | partially consistent | conflicting | insufficient metadata", "why_it_matters": "A resolving bibcode can still identify the wrong item for the user's citation." }, { "name": "Identifier relationship", "kind": "relation", "unit_or_values": "Canonical code | alternative code | reported replacement | DOI mapping | arXiv mapping | related-item link; each with evidence", "why_it_matters": "Supports linking without collapsing distinct publication versions or related records." } ], "affordances": [ "Extract a candidate bibcode while retaining its original citation or URL context.", "Parse its positions using a documented convention and flag unsupported interpretations.", "Query a bibliographic service for the exact identifier and record the outcome.", "Compare returned metadata with the intended citation before attaching the identifier.", "Follow evidenced identifier relationships while preserving the supplied code.", "Propose a correction or replacement for review when lookup and citation evidence justify it." ] }, "sources": [], "structure": { "bundles": [ { "id": "token-recognition", "name": "Token recognition", "description": "Establish what exact string is being offered as a bibcode and whether it is complete.", "rationale": "Bibcode padding and positional structure make apparently harmless text cleanup capable of changing identification.", "layers": [ { "id": "capture-context", "name": "Capture context", "description": "Separate the identifier token from its surrounding representation.", "findings": [ { "id": "literal-token", "name": "Literal token", "description": "Record the supplied characters and how they were extracted.", "questions": [ { "text": "What exact bibcode text was supplied, and did it come from a record field, citation, URL or user entry?", "kind": "provenance", "id": "literal-token-q01" }, { "text": "Which surrounding characters or URL encodings were removed or decoded, and can the original representation be recovered?", "kind": "action", "id": "literal-token-q02" } ] } ] }, { "id": "form-assessment", "name": "Form assessment", "description": "Distinguish complete conventional codes from malformed tokens and lookup patterns.", "findings": [ { "id": "complete-code-or-pattern", "name": "Complete code or pattern", "description": "Assess token length and positional plausibility without equating syntax with registration.", "questions": [ { "text": "How many characters remain after extraction, and do they fit the documented positional layout?", "kind": "measurement", "id": "complete-code-or-pattern-q01" }, { "text": "Is this a complete identifier, a partial bibcode search expression or a claimed exception requiring separate documentation?", "kind": "boundary", "id": "complete-code-or-pattern-q02" } ] } ] } ] }, { "id": "bibliographic-decoding", "name": "Bibliographic decoding", "description": "Interpret the bibliographic clues embedded in the token without treating them as a complete citation.", "rationale": "Bibcode components assist recognition but require conventions that depend on publication type and locator usage.", "layers": [ { "id": "publication-coordinates", "name": "Publication coordinates", "description": "Interpret year, publication abbreviation and volume-or-type positions.", "findings": [ { "id": "container-and-year", "name": "Container and year", "description": "Associate positional clues with a supported publication context.", "questions": [ { "text": "Which year and publication abbreviation does the code express, and what authority identifies that abbreviation?", "kind": "definition", "id": "container-and-year-q01" }, { "text": "Does the volume-position content represent a serial volume, a publication-type marker or an interpretation that remains unresolved?", "kind": "boundary", "id": "container-and-year-q02" } ] } ] }, { "id": "locator-and-initial", "name": "Locator and initial", "description": "Interpret qualifier, locator and author-initial positions conservatively.", "findings": [ { "id": "special-position-semantics", "name": "Special-position semantics", "description": "Identify when locator-related characters or author initials need publication-specific interpretation.", "questions": [ { "text": "What documented rule explains the qualifier and locator characters for this publication, including any non-page usage?", "kind": "definition", "id": "special-position-semantics-q01" }, { "text": "Does the final initial agree with the record's first author under the applicable convention, and what uncertainty prevents a reliable comparison?", "kind": "boundary", "id": "special-position-semantics-q02" } ] } ] } ] }, { "id": "assignment-and-resolution", "name": "Assignment and resolution", "description": "Establish recognition by a named bibliographic service and distinguish lookup outcomes.", "rationale": "A bibcode generated from citation details can look correct without being assigned to the intended record.", "layers": [ { "id": "assignment-provenance", "name": "Assignment provenance", "description": "Identify the evidence behind the claim that the string is an assigned bibcode.", "findings": [ { "id": "recognition-evidence", "name": "Recognition evidence", "description": "Separate service-returned identifiers from copied assertions and locally constructed candidates.", "questions": [ { "text": "Was this bibcode returned by a bibliographic service, copied from a secondary citation or constructed from metadata?", "kind": "provenance", "id": "recognition-evidence-q01" }, { "text": "What retrieved record or response establishes that the service recognises this exact code?", "kind": "provenance", "id": "recognition-evidence-q02" } ] } ] }, { "id": "lookup-state", "name": "Lookup state", "description": "Record what happened when the exact bibcode was queried.", "findings": [ { "id": "observed-resolution", "name": "Observed resolution", "description": "Preserve service identity, observation time and returned identifier alongside the lookup outcome.", "questions": [ { "text": "Which service was queried, when, and did it return a matching record, another code, no match or an operational error?", "kind": "measurement", "id": "observed-resolution-q01" }, { "text": "Does the observed result justify using the code, retrying the lookup or investigating an identifier mismatch?", "kind": "action", "id": "observed-resolution-q02" } ] } ] } ] }, { "id": "referent-and-equivalence", "name": "Referent and equivalence", "description": "Determine whether the bibcode identifies the intended bibliographic item and which identifier relationships are supported.", "rationale": "Successful resolution alone cannot establish citation correctness or equivalence between publication versions.", "layers": [ { "id": "citation-match", "name": "Citation match", "description": "Compare the retrieved item with the citation the agent is trying to identify.", "findings": [ { "id": "intended-item-agreement", "name": "Intended-item agreement", "description": "Assess agreement using record metadata beyond the abbreviated clues in the code.", "questions": [ { "text": "Do title, authors, year, publication and locator in the returned record agree with the intended citation?", "kind": "boundary", "id": "intended-item-agreement-q01" }, { "text": "Could the returned item instead be an erratum, abstract, proceedings contribution or another version requiring a distinct link?", "kind": "boundary", "id": "intended-item-agreement-q02" } ] } ] }, { "id": "identifier-crosswalks", "name": "Identifier crosswalks", "description": "Qualify links to other bibcodes, DOIs and arXiv identifiers.", "findings": [ { "id": "supported-equivalence", "name": "Supported equivalence", "description": "Record the asserted relationship and its source before using identifiers interchangeably.", "questions": [ { "text": "Which source explicitly connects this bibcode to another identifier, and what relationship does that source assert?", "kind": "provenance", "id": "supported-equivalence-q01" }, { "text": "Does the evidence support the same bibliographic record, another version of the work or merely related material?", "kind": "boundary", "id": "supported-equivalence-q02" } ] } ] } ] }, { "id": "preservation-and-correction", "name": "Preservation and correction", "description": "Guide reuse and repair of bibcodes while retaining the evidence behind earlier references.", "rationale": "An agent must avoid turning a suggested repair or metadata-derived candidate into an unsupported identifier assignment.", "layers": [ { "id": "canonical-code-handling", "name": "Canonical code handling", "description": "Manage differences between supplied codes and service-preferred identifiers.", "findings": [ { "id": "reported-code-relationship", "name": "Reported code relationship", "description": "Treat canonicalisation or replacement as an evidenced service assertion.", "questions": [ { "text": "Does the service explicitly identify a preferred, alternative or replacement bibcode, or has the agent only inferred one?", "kind": "provenance", "id": "reported-code-relationship-q01" }, { "text": "If a preferred code is adopted, how will the original supplied code and the supporting relationship evidence remain traceable?", "kind": "action", "id": "reported-code-relationship-q02" } ] } ] }, { "id": "repair-and-reuse", "name": "Repair and reuse", "description": "Choose actions appropriate to malformed, unresolved or conflicting identifiers.", "findings": [ { "id": "evidence-bounded-action", "name": "Evidence-bounded action", "description": "Permit verified linking and supported repair while keeping unconfirmed candidates explicitly provisional.", "questions": [ { "text": "Can metadata search establish a verified correction, or must the candidate remain unresolved pending review?", "kind": "action", "id": "evidence-bounded-action-q01" }, { "text": "Before placing the bibcode in a citation, request or URL, have its exact characters been preserved and any transport encoding kept separate from the identifier?", "kind": "action", "id": "evidence-bounded-action-q02" } ] } ] } ] } ] }, "openQuestions": [ "Which current ADS, SIMBAD and NED conventions differ, and which service governs interpretation when they disagree?", "What documented rules cover article numbers, extended locators, non-journal items and historical exceptions to conventional positional decoding?", "How do the relevant services expose canonical and alternative bibcodes, and what guarantees apply after record corrections, merges or removals?", "How are collisions, unavailable author names and non-Latin or accented surnames handled under current assignment rules?", "What evidence is sufficient to distinguish a temporarily unresolved bibcode from an unassigned candidate, and how should that evidence expire?" ], "statistics": { "bundles": 5, "layers": 10, "findings": 10, "questions": 20 } }, "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 bibcode, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a bibcode, establish which bibliographic record it identifies, assess the reliability of that identification, and choose justified lookup, linking or correction actions.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted", "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: ADS bibcode.", "1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 65 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 bibcode, 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": [ "ADS bibcode" ] } ], "standing": "Described in 65 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 bibcode from another, and a bibcode 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 bibcode, 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 bibcode, 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 bibcode 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 bibcode, 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 bibcode, 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 bibcode 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 bibcode 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 bibcode, 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 bibcode, 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 bibcode 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 bibcode from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a bibcode, 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 bibcode, 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 bibcode 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 bibcode 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 bibcode between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a bibcode, 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 bibcode, 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 bibcode 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 bibcode, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a bibcode 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 bibcode, 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 bibcode, 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 bibcode 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 bibcode 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 bibcode contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a bibcode, 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 bibcode, 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 bibcode 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 bibcode and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a bibcode, 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 bibcode, 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 bibcode 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 bibcode 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 bibcode, 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 bibcode 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 bibcode 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 bibcode, 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 bibcode, 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 bibcode 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 bibcode and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a bibcode, 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 bibcode, 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 bibcode 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 bibcode is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a bibcode, 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 bibcode, 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 bibcode 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 } } } }