{ "model": { "rank": 18680, "code": "thing-q616245", "model_id": "vr.tr.ieee-802", "name": "IEEE 802", "purpose": "Let an agent explain the IEEE 802 family and its working groups, relay the scope and status of major standards from IEEE sources, describe how they relate to networking layers, and route to entries for specific standards.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.KNW", "industry": "", "version": "", "url": "/models/thing/q616245/", "tier": 2, "score": 29, "payload": { "layer": "wikidata", "aliases": [ "IEEE 802.16", "IEEE 802.20", "IEEE 802.10", "IEEE 802.8", "IEEE 802.1", "IEEE 802.22", "IEEE 802.15", "IEEE 802.12", "IEEE 802.3", "IEEE 802.7", "IEEE 802.14", "IEEE 802.6", "IEEE 802.2", "IEEE 802.16c", "IEEE 802.16e", "IEEE 802.16f", "IEEE 802.16m", "IEEE 802.1AB: IEEE Standard for Local and Metropolitan Area Networks: Station and Media Access Control Connectivity and Discovery", "IEEE 802.1AC: IEEE Standard for Local and metropolitan area networks—Media Access Control (MAC) Service Definition", "IEEE 802.1ag", "IEEE 802.1D", "IEEE 802.1ad", "IEEE 802.1AE: IEEE Standard for Local and metropolitan area networks—Media Access Control (MAC) Security", "IEEE 802.15.6", "IEEE 802.3at", "IEEE 802.3ae", "IEEE 802.3an", "IEEE 802.3ab", "IEEE 802.3a", "IEEE 802.3af", "IEEE 802.3ap", "IEEE 802.3aq", "IEEE 802.3as", "IEEE 802.3e", "IEEE 802.3j", "IEEE 802.3y", "IEEE 802.3z", "IEEE 802.3ak" ], "aliasCount": 38, "merged": 38, "knownIn": 29, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q616245", "url": "https://www.wikidata.org/wiki/Q616245", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-13T03:12:16Z", "providers": [ "Claude" ], "breadth": "written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify", "pass": 2, "wave": 3, "engine": "claude" }, "metaModel": { "id": "THING-Q616245", "registryId": "vr.tr.ieee-802", "name": "IEEE 802", "version": "0.2.0-wave.3", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.KNW" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q616245/", "model": { "registry_id": "vr.tr.ieee-802", "name": "IEEE 802", "purpose": "Let an agent explain the IEEE 802 family and its working groups, relay the scope and status of major standards from IEEE sources, describe how they relate to networking layers, and route to entries for specific standards.", "definition": "A family of IEEE standards for local and metropolitan area networks dealing with the physical and data link layers, developed by the IEEE 802 LAN/MAN Standards Committee since 1980, including 802.1 for bridging and management, 802.3 Ethernet, 802.11 Wi-Fi, 802.15 personal area networks including Bluetooth-derived and Zigbee-related standards, 802.16 WiMAX, and less used or disbanded groups such as 802.8 fibre optics, 802.10 security, 802.20 mobile broadband and 802.22 wireless regional networks using TV white spaces.", "what_it_is_for": "Standardising local and metropolitan networks.", "affordances": [ "explain the family and structure", "relay major standards and status", "describe layer relationships", "route to specific standards" ], "distinguishing_features": [ "Physical and data link layers", "Working group numbering", "Ethernet and Wi-Fi", "Long evolution" ], "appearance": "Not a visible object; standards documents.", "visual_identification": [ "IEEE LAN and MAN standards", "802.1, 802.3 Ethernet, 802.11 Wi-Fi, 802.15, 802.16, 802.22 and historical groups such as 802.8, 802.10 and 802.20", "IETF standards cover higher layers; 3GPP covers cellular; ITU covers telecommunications broadly" ], "physical_properties": [ { "quantity": "committee founded", "typical_range": "1980", "unit": "year", "note": "February" }, { "quantity": "active working groups", "typical_range": "about 10", "unit": "count", "note": "varies" } ], "families_and_kinds": [ "802.1 bridging, security and management", "802.3 Ethernet", "802.11 wireless LAN", "802.15 wireless personal area networks", "802.16 broadband wireless access", "802.22 wireless regional area networks", "disbanded or hibernating groups such as 802.8, 802.10 and 802.20" ], "related_models": [ { "relation": "is a kind of", "target": "IEEE standard", "why": "in registry terms" }, { "relation": "includes", "target": "IEEE 802.3", "why": "Ethernet" }, { "relation": "includes", "target": "IEEE 802.11", "why": "Wi-Fi" }, { "relation": "is developed by", "target": "IEEE Standards Association", "why": "through the 802 committee" } ], "identifiers": [ { "scheme": "IEEE", "value_or_pattern": "802", "note": "LAN/MAN Standards Committee" } ], "standards_and_regulation": [ "IEEE Standards Association processes", "ISO/IEC 8802 adoptions of 802 standards", "Radio spectrum regulation affecting wireless standards" ], "failure_modes_and_hazards": [ "Confusing working groups with standards", "Stale status of disbanded groups", "Mixing 802 with IETF and cellular standards" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "understand", "name": "Understand", "description": "What IEEE 802 is.", "rationale": "Definition.", "layers": [ { "id": "definition", "name": "Definition", "description": "Definition and structure.", "findings": [ { "id": "definition-finding", "name": "Definition", "description": "Definition.", "questions": [ { "text": "What is the IEEE 802 family, and how are working groups and standards organised?", "kind": "definition" }, { "text": "Is the question about the family, a specific standard or a non-802 standard?", "kind": "boundary" } ] } ] }, { "id": "layers", "name": "Layers", "description": "Layers.", "findings": [ { "id": "layers-finding", "name": "Layers", "description": "Layers.", "questions": [ { "text": "How do 802 standards split the data link layer into LLC and MAC, and relate to the OSI model?", "kind": "definition" }, { "text": "Which entry fits the specific layer?", "kind": "action" } ] } ] } ] }, { "id": "standards", "name": "Standards", "description": "Major standards.", "rationale": "Standards.", "layers": [ { "id": "wired", "name": "Wired", "description": "Ethernet and bridging.", "findings": [ { "id": "wired-finding", "name": "Wired", "description": "Wired.", "questions": [ { "text": "What do 802.3 Ethernet and 802.1 bridging, VLAN and security standards cover?", "kind": "provenance" }, { "text": "Which references are standard?", "kind": "provenance" } ] } ] }, { "id": "wireless", "name": "Wireless", "description": "Wireless standards.", "findings": [ { "id": "wireless-finding", "name": "Wireless", "description": "Wireless.", "questions": [ { "text": "What do 802.11, 802.15, 802.16 and 802.22 cover, and how have they evolved?", "kind": "provenance" }, { "text": "Which entry fits the specific standard?", "kind": "action" } ] } ] } ] }, { "id": "history", "name": "History", "description": "History and status.", "rationale": "Sources.", "layers": [ { "id": "history", "name": "History", "description": "History.", "findings": [ { "id": "history-finding", "name": "History", "description": "History.", "questions": [ { "text": "How did the 802 committee develop from 1980, and why did groups such as 802.8, 802.10 and 802.20 disband?", "kind": "provenance" }, { "text": "Which sources are cited?", "kind": "provenance" } ] } ] }, { "id": "status", "name": "Status", "description": "Current status.", "findings": [ { "id": "status-finding", "name": "Status", "description": "Status.", "questions": [ { "text": "Which groups are active, and what standards are in development?", "kind": "provenance" }, { "text": "Is the information current?", "kind": "boundary" } ] } ] } ] }, { "id": "context", "name": "Context", "description": "Use and process.", "rationale": "Context.", "layers": [ { "id": "use", "name": "Use", "description": "Use in practice.", "findings": [ { "id": "use-finding", "name": "Use", "description": "Use.", "questions": [ { "text": "How do 802 standards appear in everyday networks and products?", "kind": "provenance" }, { "text": "Which entry fits local area network?", "kind": "action" } ] } ] }, { "id": "process", "name": "Process", "description": "Standards process.", "findings": [ { "id": "process-finding", "name": "Process", "description": "Process.", "questions": [ { "text": "How are 802 standards developed, balloted and adopted internationally?", "kind": "provenance" }, { "text": "Which entry fits IEEE Standards Association?", "kind": "action" } ] } ] } ] } ] }, "openQuestions": [ "Should 802.3 and 802.11 be the primary linked entries?", "How should IEEE sources be linked?", "The registry entry has merged aliases naming subgroups; should they be split off?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "discipline or field of knowledge", "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 IEEE 802, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent explain the IEEE 802 family and its working groups, relay the scope and status of major standards from IEEE sources, describe how they relate to networking layers, and route to entries for specific standards.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: IEEE 802.16, IEEE 802.20, IEEE 802.10, IEEE 802.8, IEEE 802.1, IEEE 802.22, IEEE 802.15, IEEE 802.12, IEEE 802.3, IEEE 802.7, IEEE 802.14, IEEE 802.6.", "38 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 29 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 IEEE 802, 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" ], "howItIsRecognised": [], "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": [ "IEEE 802.16", "IEEE 802.20", "IEEE 802.10", "IEEE 802.8", "IEEE 802.1", "IEEE 802.22", "IEEE 802.15", "IEEE 802.12", "IEEE 802.3", "IEEE 802.7", "IEEE 802.14", "IEEE 802.6" ] } ], "standing": "Described in 29 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 38 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 IEEE 802 from another, and a IEEE 802 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 IEEE 802, 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 IEEE 802, 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 IEEE 802 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 IEEE 802, 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 IEEE 802, 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 IEEE 802 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 IEEE 802 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 IEEE 802, 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 IEEE 802, 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 IEEE 802 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 IEEE 802 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a IEEE 802, 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 IEEE 802, 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 IEEE 802 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 IEEE 802 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 IEEE 802 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a IEEE 802, 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 IEEE 802, 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 IEEE 802 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 IEEE 802, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a IEEE 802 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 IEEE 802, 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 IEEE 802, 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 IEEE 802 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 IEEE 802 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 IEEE 802 contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a IEEE 802, 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 IEEE 802, 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 IEEE 802 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 IEEE 802 and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a IEEE 802, 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 IEEE 802, 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 IEEE 802 is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "subject-and-method", "name": "Subject matter and method", "description": "What IEEE 802 studies and how it establishes anything.", "rationale": "A field is identified by its questions and its methods, and those are what distinguish it from the fields next to it.", "layers": [ { "id": "subject", "name": "Subject matter", "description": "The questions it takes as its own.", "findings": [ { "id": "subject-record", "name": "Questions and objects of study", "description": "What it is about, stated so a neighbouring field can be told apart.", "questions": [ { "id": "subject-record-q01", "text": "What questions and objects does IEEE 802 take as its own?", "kind": "definition" }, { "id": "subject-record-q02", "text": "Which questions does it share with a neighbouring field, and who claims them?", "kind": "boundary" } ] } ] }, { "id": "method", "name": "Method and evidence", "description": "How claims are established and what counts as evidence.", "findings": [ { "id": "method-record", "name": "Methods and standards of evidence", "description": "The methods used and what they are taken to establish.", "questions": [ { "id": "method-record-q01", "text": "By what methods does IEEE 802 establish claims, and what counts as sufficient evidence?", "kind": "provenance" }, { "id": "method-record-q02", "text": "What kind of claim can this field not settle, and where should an agent look instead?", "kind": "action" } ] } ] } ] }, { "id": "institutions-and-classification", "name": "Institutions and classification", "description": "Where IEEE 802 is practised and how catalogues place it.", "rationale": "The institutional footprint is the evidence that a field exists as a field rather than as a topic.", "layers": [ { "id": "institutions", "name": "Institutional markers", "description": "Societies, journals, degrees and departments.", "findings": [ { "id": "institution-record", "name": "Bodies and venues", "description": "Where the field organises itself.", "questions": [ { "id": "institution-record-q01", "text": "Which societies, journals or degrees mark IEEE 802 as an established field?", "kind": "provenance" }, { "id": "institution-record-q02", "text": "What would show that it is emerging or dissolving rather than established?", "kind": "boundary" } ] } ] }, { "id": "classification", "name": "Classification schemes", "description": "Where library and research classifications put it.", "findings": [ { "id": "classification-record", "name": "Codes and their disagreements", "description": "The classification codes that place it, and where they differ.", "questions": [ { "id": "classification-record-q01", "text": "Which classification schemes place IEEE 802, under what codes?", "kind": "definition" }, { "id": "classification-record-q02", "text": "Where do those schemes disagree about its scope?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a IEEE 802 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 IEEE 802 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a IEEE 802, 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 IEEE 802, 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 IEEE 802 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 IEEE 802 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a IEEE 802, 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 IEEE 802, 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 IEEE 802 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 } } } }