{ "model": { "rank": 4338, "code": "thing-q251212", "model_id": "vr.tr.internet-of-things", "name": "Internet of Things", "purpose": "Enable an AI agent to recognise an Internet of Things system, assess its physical and digital operating state, and determine which observations or interventions are supported and authorised.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q251212/", "tier": 2, "score": 76, "payload": { "layer": "wikidata", "aliases": [ "Internet of vehicles", "Internet of energy", "Internet of Musical Things", "industrial internet of things" ], "aliasCount": 4, "merged": 4, "knownIn": 76, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q251212", "url": "https://www.wikidata.org/wiki/Q251212", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T20:00:17Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 25.6, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a087c0-ab02-7222-a2a7-bbabfe33dd64\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Internet of Things\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 695 things:\n# Batch 004: 10", "usd": 0, "recall": true }, "codex": { "seconds": 72.2, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a087c0-aaf0-7c53-a213-bf0ba4bc4b00\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Internet of Things\nRegistry id: vr.tr.internet-of-things\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this en" } } }, "metaModel": { "id": "THING-Q251212", "registryId": "vr.tr.internet-of-things", "name": "Internet of Things", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q251212/", "model": { "registry_id": "vr.tr.internet-of-things", "name": "Internet of Things", "purpose": "Enable an AI agent to recognise an Internet of Things system, assess its physical and digital operating state, and determine which observations or interventions are supported and authorised.", "definition": "The Internet of Things (IoT) is the interconnection of physical objects equipped with sensing or actuation, processing, and network communication capabilities so that they can exchange data and interact with digital services, directly or through gateways.", "scope_statement": "This model owns the Internet of Things as a kind of networked physical system: identifiable physical things with sensing or actuation, connectivity, and services that exchange and use their data; it covers their integration rather than a particular product, installation, or the Internet itself.", "in_scope": [ "Boundaries and membership of systems connecting physical things to digital services", "Physical sensing, actuation, and the meaning of exchanged observations and commands", "Device identities, connectivity paths, gateways, and interoperability", "Coordination across devices, edge components, and remote services", "Operational health, provisioning, updates, and retirement", "Authority, cybersecurity, privacy, and physical consequences of remote actions" ], "out_of_scope": [ "Internal mechanical or electronic design of individual sensors, actuators, and machines", "General Internet infrastructure and networking independent of connected physical things", "Standalone software services with no sensing or actuation relationship to the physical world", "Domain-specific control objectives belonging to models of buildings, factories, vehicles, or healthcare systems", "Detailed organisational governance and contractual terms belonging to operator and service-provider models", "Digital twins and analytical models beyond their interfaces with connected things" ], "distinguishing_features": [ "The system connects digital information exchange to physical sensing or actuation; a network of software services alone does not satisfy this boundary.", "Physical things participate through distinguishable identities or addressable endpoints, directly or through intermediaries; an inventory of unconnected objects is insufficient.", "Observations or commands pass between physical endpoints and other components; a standalone electronic controller without such exchange falls outside the proposed scope.", "The subject is the integration of connected things and services, rather than one sensor, a communications protocol, or a cloud platform considered independently.", "Connectivity may be intermittent or gateway-mediated; the model must distinguish these arrangements from any claim that every thing is directly Internet-addressable." ], "characteristics": [ { "name": "Physical participation", "kind": "category", "unit_or_values": "sensing; actuation; both; unresolved", "why_it_matters": "Identifies how the system observes or changes the physical world." }, { "name": "System membership", "kind": "relation", "unit_or_values": "physical thing ↔ device endpoint ↔ gateway ↔ service", "why_it_matters": "Separates the thing represented from the components that identify, connect, or operate it." }, { "name": "Connectivity arrangement", "kind": "category", "unit_or_values": "direct; gateway-mediated; intermittently synchronised; mixed", "why_it_matters": "Determines reachability and which intermediaries are necessary for operation." }, { "name": "Observation age", "kind": "measurement", "unit_or_values": "seconds since physical sampling, with clock uncertainty recorded", "why_it_matters": "Prevents a recently received but old observation from being treated as current physical state." }, { "name": "End-to-end action latency", "kind": "measurement", "unit_or_values": "milliseconds or seconds from command issue to confirmed physical response", "why_it_matters": "Supports judgement about whether remote action meets the use case's timing needs." }, { "name": "Operational connectivity", "kind": "state", "unit_or_values": "connected; intermittent; partitioned; offline; unknown", "why_it_matters": "Constrains the observations and interventions currently available." }, { "name": "Control authority", "kind": "relation", "unit_or_values": "principal ↔ permitted endpoint operations ↔ conditions", "why_it_matters": "Distinguishes the technical ability to send a command from permission to cause its physical effect." }, { "name": "Disconnected behaviour", "kind": "category", "unit_or_values": "local continuation; buffered reporting; restricted operation; controlled stop; unspecified", "why_it_matters": "Makes the consequences of losing gateways or remote services explicit." }, { "name": "Energy availability", "kind": "state", "unit_or_values": "externally powered; battery sufficient; battery low; energy-limited; unknown", "why_it_matters": "Explains limits on sampling, communication, updates, and actuation." }, { "name": "Support and update condition", "kind": "state", "unit_or_values": "supported; update pending; update failed; unsupported; unknown", "why_it_matters": "Helps determine whether continued connected operation is maintainable." } ], "affordances": [ "Identify participating physical things and trace their dependencies on gateways and services.", "Interpret observations using their units, sampling times, calibration context, and quality indicators.", "Assess whether connectivity, energy, and service health support the intended operation.", "Request an authorised physical action within recorded limits and verify its outcome.", "Provision, reconfigure, update, or isolate participating endpoints within the agent's authority.", "Retire endpoints by revoking access and resolving retained data and service dependencies." ] }, "sources": [], "structure": { "bundles": [ { "id": "physical-digital-boundary", "name": "Physical-digital boundary", "description": "Establishes what makes the subject an IoT system and which physical things and digital components participate.", "rationale": "Internet of Things names a system concept rather than a single device type, so membership and representation must be explicit.", "layers": [ { "id": "system-extent", "name": "System extent", "description": "Defines the connected physical activity and the boundary around its supporting components.", "findings": [ { "id": "physical-participation", "name": "Physical participation", "description": "Record the physical phenomena sensed or affected and the endpoints through which they enter the system.", "questions": [ { "text": "Which physical things or phenomena does this system observe or change?", "kind": "definition", "id": "physical-participation-q01" }, { "text": "Which devices, gateways, and services belong to this system, and which are external dependencies?", "kind": "boundary", "id": "physical-participation-q02" } ] } ] }, { "id": "identity-and-representation", "name": "Identity and representation", "description": "Connects physical things to device identities and digital representations without assuming a one-to-one mapping.", "findings": [ { "id": "thing-endpoint-mapping", "name": "Thing-to-endpoint mapping", "description": "Record how identifiers refer to physical things, replaceable devices, and service-side representations over time.", "questions": [ { "text": "Does each identifier denote a physical thing, a replaceable device, or a digital representation?", "kind": "definition", "id": "thing-endpoint-mapping-q01" }, { "text": "What evidence establishes the mapping, and how is it revised when a device is replaced or reassigned?", "kind": "provenance", "id": "thing-endpoint-mapping-q02" } ] } ] } ] }, { "id": "physical-observations-and-actions", "name": "Physical observations and actions", "description": "Captures the meaning and evidential limits of sensing and actuation.", "rationale": "Successful message exchange alone cannot establish an accurate observation or a completed physical action.", "layers": [ { "id": "observation-meaning", "name": "Observation meaning", "description": "Makes sensor outputs interpretable as evidence about a physical condition.", "findings": [ { "id": "observation-validity", "name": "Observation validity", "description": "Record measured quantity, units, sampling context, timestamps, and relevant quality or calibration information.", "questions": [ { "text": "What quantity does each observation represent, in which units and at which physical location?", "kind": "measurement", "id": "observation-validity-q01" }, { "text": "What sampling time, uncertainty, calibration history, or quality flag limits its use as evidence of current state?", "kind": "provenance", "id": "observation-validity-q02" } ] } ] }, { "id": "actuation-outcomes", "name": "Actuation outcomes", "description": "Relates digital commands to permitted physical transitions and observable results.", "findings": [ { "id": "command-effect-verification", "name": "Command effect verification", "description": "Distinguish requested, accepted, executed, and physically verified actions, including failed or uncertain outcomes.", "questions": [ { "text": "Which physical transitions can an endpoint perform, and what preconditions and limits apply?", "kind": "action", "id": "command-effect-verification-q01" }, { "text": "What feedback proves the intended physical effect occurred rather than only confirming message receipt?", "kind": "measurement", "id": "command-effect-verification-q02" } ] } ] } ] }, { "id": "connectivity-and-interoperability", "name": "Connectivity and interoperability", "description": "Describes how things exchange information and preserve its meaning across component boundaries.", "rationale": "An endpoint can be reachable while its data or commands remain incompatible with the receiving system.", "layers": [ { "id": "communication-paths", "name": "Communication paths", "description": "Traces direct and mediated connections, including intermittent and constrained links.", "findings": [ { "id": "endpoint-reachability", "name": "Endpoint reachability", "description": "Record the path between a physical endpoint and its consumers or controllers, with dependencies and delivery constraints.", "questions": [ { "text": "Through which local networks, gateways, and remote services do observations and commands travel?", "kind": "boundary", "id": "endpoint-reachability-q01" }, { "text": "What measured latency, loss, disconnection periods, and payload limits constrain those paths?", "kind": "measurement", "id": "endpoint-reachability-q02" } ] } ] }, { "id": "shared-interface-meaning", "name": "Shared interface meaning", "description": "Establishes how components agree on capabilities and message interpretation.", "findings": [ { "id": "interface-compatibility", "name": "Interface compatibility", "description": "Record interface versions, capability descriptions, data meanings, and any translations performed by intermediaries.", "questions": [ { "text": "How do components describe and discover supported observations, commands, units, and interface versions?", "kind": "definition", "id": "interface-compatibility-q01" }, { "text": "Which interface specifications or compatibility tests support interoperability claims across vendors and gateways?", "kind": "provenance", "id": "interface-compatibility-q02" } ] } ] } ] }, { "id": "distributed-operation", "name": "Distributed operation", "description": "Captures the placement of processing and control, and behaviour when distributed components disagree or disconnect.", "rationale": "IoT decisions can span physical devices and remote services whose availability and state differ.", "layers": [ { "id": "processing-and-control-placement", "name": "Processing and control placement", "description": "Assigns operational responsibilities to device, gateway, edge, and remote components.", "findings": [ { "id": "decision-dependencies", "name": "Decision dependencies", "description": "Record where observations are processed and control decisions are made, including dependencies on remote computation.", "questions": [ { "text": "Which sensing, filtering, inference, and control functions run on devices, gateways, or remote services?", "kind": "definition", "id": "decision-dependencies-q01" }, { "text": "Which functions remain available when the gateway or remote service cannot be reached?", "kind": "boundary", "id": "decision-dependencies-q02" } ] } ] }, { "id": "disconnection-and-reconciliation", "name": "Disconnection and reconciliation", "description": "Defines handling of stale state, buffered observations, and commands across interruptions.", "findings": [ { "id": "reconnection-behaviour", "name": "Reconnection behaviour", "description": "Record how components reconcile reported and desired state without replaying obsolete or unsafe actions.", "questions": [ { "text": "How are stale observations, duplicate messages, expired commands, and conflicting state detected?", "kind": "definition", "id": "reconnection-behaviour-q01" }, { "text": "When connectivity returns, which buffered messages may be applied, discarded, or reviewed before execution?", "kind": "action", "id": "reconnection-behaviour-q02" } ] } ] } ] }, { "id": "trust-and-physical-consequences", "name": "Trust and physical consequences", "description": "Connects identity, authority, data handling, and safeguards to the system's physical reach.", "rationale": "Connected sensing can disclose physical activity, while connected control can produce physical consequences.", "layers": [ { "id": "access-and-data-authority", "name": "Access and data authority", "description": "Determines who may connect, observe, control, and receive data.", "findings": [ { "id": "authorised-participation", "name": "Authorised participation", "description": "Record authentication, operation-level permissions, and data destinations for devices, services, people, and agents.", "questions": [ { "text": "How are device and service identities authenticated, and which principals may read, configure, or actuate each endpoint?", "kind": "action", "id": "authorised-participation-q01" }, { "text": "Which observations can reveal people or sensitive physical activity, and what authority governs their collection and onward use?", "kind": "boundary", "id": "authorised-participation-q02" } ] } ] }, { "id": "physical-action-safeguards", "name": "Physical action safeguards", "description": "Captures controls that bound the effects of remote commands and compromised components.", "findings": [ { "id": "local-enforcement-and-isolation", "name": "Local enforcement and isolation", "description": "Record local interlocks, command limits, manual overrides, and isolation behaviour relevant to physical operation.", "questions": [ { "text": "Which physical limits and interlocks are enforced locally even when an authorised remote service issues a command?", "kind": "boundary", "id": "local-enforcement-and-isolation-q01" }, { "text": "How can an endpoint be isolated or control transferred locally, and what physical state results?", "kind": "action", "id": "local-enforcement-and-isolation-q02" } ] } ] } ] }, { "id": "fleet-lifecycle-and-maintainability", "name": "Fleet lifecycle and maintainability", "description": "Tracks connected endpoints from enrolment through maintenance, ownership changes, and retirement.", "rationale": "IoT operation depends on maintaining distributed physical equipment alongside identities, firmware, and services.", "layers": [ { "id": "enrolment-and-maintenance", "name": "Enrolment and maintenance", "description": "Establishes how endpoints enter service and remain observable and maintainable.", "findings": [ { "id": "deployment-readiness", "name": "Deployment readiness", "description": "Record provisioning evidence, installed firmware, configuration, energy constraints, and update recovery capabilities.", "questions": [ { "text": "What checks bind a newly enrolled endpoint to the intended physical thing, owner, and configuration?", "kind": "provenance", "id": "deployment-readiness-q01" }, { "text": "How do available energy, connectivity windows, and recovery mechanisms constrain maintenance and firmware updates?", "kind": "action", "id": "deployment-readiness-q02" } ] } ] }, { "id": "transfer-and-retirement", "name": "Transfer and retirement", "description": "Resolves physical and digital dependencies when endpoints change hands or leave service.", "findings": [ { "id": "end-of-service-resolution", "name": "End-of-service resolution", "description": "Record credential revocation, ownership transfer, retained data, and the effects of discontinued support or services.", "questions": [ { "text": "What must be revoked, erased, retained, or reassigned when a device is retired or ownership changes?", "kind": "action", "id": "end-of-service-resolution-q01" }, { "text": "Which physical functions cease or become restricted if vendor support, certificates, or required remote services end?", "kind": "boundary", "id": "end-of-service-resolution-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This describes IoT as a technological system category, not a single physical device; the PHY.OBJ classification should be reviewed.", "Standards and identifier schemes are recalled, not checked against source documents; their current editions, scope, and applicability require verification.", "There are no useful category-wide typical ranges for dimensions, power, latency, throughput, or operating life; these require a specified device class and deployment." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Internet of Things this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Consumer and smart-home IoT", "Industrial IoT", "Healthcare IoT", "Agricultural IoT", "Smart-city IoT", "Connected transport and logistics IoT" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Internet of Things this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "IPv6 address", "value_or_pattern": "128-bit address conventionally represented as colon-separated hexadecimal groups", "note": "Identifies an IP network interface; not every IoT device uses IP directly, and an address is not necessarily a persistent device identity." }, { "scheme": "IEEE EUI-48 and EUI-64", "value_or_pattern": "48-bit or 64-bit identifier", "note": "Used for interface or equipment identification in relevant technologies; not a universal IoT identification scheme." }, { "scheme": "GS1 Electronic Product Code (EPC)", "value_or_pattern": "Structured identifiers with encodings defined by the GS1 EPC Tag Data Standard", "note": "Used to identify physical objects in applications such as RFID-based tracking; identifies the object rather than necessarily its network endpoint." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Internet of Things this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "ISO/IEC 30141 - Internet of Things reference architecture, issued by ISO and IEC.", "ISO/IEC 20924 - Internet of Things vocabulary, issued by ISO and IEC.", "ETSI EN 303 645 - cybersecurity baseline for consumer Internet of Things, issued by ETSI.", "MQTT Version 5.0 - publish/subscribe messaging protocol standardized by OASIS.", "RFC 7252 - Constrained Application Protocol (CoAP), published by the IETF." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Internet of Things this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Monitoring industrial equipment condition and supporting predictive maintenance.", "Controlling building lighting, heating, ventilation, and energy consumption.", "Tracking goods, vehicles, and cold-chain conditions.", "Monitoring soil and weather conditions to inform irrigation.", "Collecting measurements from connected medical and home-monitoring devices." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Internet of Things this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Compromised credentials, insecure interfaces, or unpatched firmware can permit unauthorized access and control.", "Network or service outages can interrupt monitoring and remote control.", "Sensor drift, poor calibration, or corrupted data can produce incorrect decisions or unsafe actuation.", "Battery depletion, power loss, and environmental damage can disable unattended devices.", "Excessive data collection or weak access controls can expose personal information and enable surveillance." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Internet of Things this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Permitted radio bands, transmit-power limits, and equipment approval requirements differ by jurisdiction.", "Privacy, cybersecurity, and data-transfer obligations differ by jurisdiction and application sector.", "Available network coverage and infrastructure influence connectivity choices and deployment feasibility." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Internet of Things this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "Internet", "difference": "The Internet is the general network infrastructure; IoT concerns connected physical objects and their associated services." }, { "name": "Embedded system", "difference": "An embedded system performs dedicated computing functions within equipment and need not communicate over a network." }, { "name": "Cyber-physical system", "difference": "A cyber-physical system integrates computation with physical processes; Internet connectivity is not required, and feedback control is often central." }, { "name": "Machine-to-machine communication", "difference": "Machine-to-machine communication describes automated exchanges between machines; IoT additionally encompasses connected objects, platforms, applications, and services." }, { "name": "Wireless sensor network", "difference": "A wireless sensor network connects sensing nodes and may remain local; IoT also includes actuators, wired connections, and integration with wider services." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Internet of Things this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already own this concept, requiring the registry entry to link to it rather than establish a separate publication?", "Which authoritative definition should govern whether closed local networks, passive identification tags, and systems without Internet connectivity qualify as Internet of Things?", "How should the PHY / PHY.OBJ placement represent this system-level concept while relating it to its information, activity, and organisational aspects?", "Which standards and issuing bodies should anchor terminology, interoperability, security, and lifecycle expectations, and which requirements depend on deployment sector or jurisdiction?", "What deployment evidence is needed to set acceptable observation age, action latency, disconnected behaviour, and update recovery criteria without inventing universal thresholds?" ], "statistics": { "bundles": 7, "layers": 13, "findings": 20, "questions": 32 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "unclassified", "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 Internet of Things, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise an Internet of Things system, assess its physical and digital operating state, and determine which observations or interventions are supported and authorised.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Internet of vehicles, Internet of energy, Internet of Musical Things, industrial internet of things.", "4 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 76 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 Internet of Things, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Recognised by form and material. The registry holds no appearance data, so what a Internet of Things looks like has to come from research." ], "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": [ "Internet of vehicles", "Internet of energy", "Internet of Musical Things", "industrial internet of things" ] } ], "standing": "Described in 76 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 4 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 Internet of Things from another, and a Internet of Things 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 Internet of Things, 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 Internet of Things, 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 Internet of Things 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 Internet of Things, 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 Internet of Things, 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 Internet of Things 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 Internet of Things 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 Internet of Things, 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 Internet of Things, 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 Internet of Things 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 Internet of Things from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Internet of Things, 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 Internet of Things, 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 Internet of Things is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "form-and-composition", "name": "Form, composition and condition", "description": "What a Internet of Things is made of, what shape and size it takes, and what state it is in.", "rationale": "A physical thing can be measured, and a model that cannot record its measurements cannot support any decision that depends on them.", "layers": [ { "id": "form-and-dimensions", "name": "Form and dimensions", "description": "Shape, size, mass and the ranges these take across examples.", "findings": [ { "id": "measurable-dimensions", "name": "Measurable dimensions and their units", "description": "The quantities worth recording and the units they are recorded in.", "questions": [ { "id": "measurable-dimensions-q01", "text": "What identifies and describes the dimensions of a Internet of Things, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "measurable-dimensions-q02", "text": "Who or what asserted this about the dimensions of a Internet of Things, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "measurable-dimensions-q03", "text": "What may an agent decide or do once the dimensions of a Internet of Things is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "material-and-composition", "name": "Material and composition", "description": "Materials, parts and how they are put together.", "findings": [ { "id": "parts-and-materials", "name": "Parts and materials", "description": "What a Internet of Things is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Internet of Things, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "parts-and-materials-q02", "text": "Who or what asserted this about the composition of a Internet of Things, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "parts-and-materials-q03", "text": "What may an agent decide or do once the composition of a Internet of Things is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "condition-and-integrity", "name": "Condition and integrity", "description": "Wear, damage, health and the difference between working and broken.", "findings": [ { "id": "condition-assessment", "name": "Condition, damage and health", "description": "How the condition of a Internet of Things is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Internet of Things, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "condition-assessment-q02", "text": "Who or what asserted this about the condition of a Internet of Things, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "condition-assessment-q03", "text": "What may an agent decide or do once the condition of a Internet of Things is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "place-and-movement", "name": "Place and movement", "description": "Where a Internet of Things is, how it got there and where it may go (varies).", "rationale": "A thing that can move needs its position recorded with a time, or every later claim about it is about a place it has left.", "layers": [ { "id": "location-and-placement", "name": "Location and placement", "description": "Position, containment and the reference frame the position is given in.", "findings": [ { "id": "position-and-frame", "name": "Position, container and reference frame", "description": "Where a Internet of Things is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Internet of Things, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "position-and-frame-q02", "text": "Who or what asserted this about the location of a Internet of Things, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "position-and-frame-q03", "text": "What may an agent decide or do once the location of a Internet of Things is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "movement-and-transfer", "name": "Movement and transfer", "description": "How a Internet of Things is carried, installed or relocated.", "findings": [ { "id": "movement-events", "name": "Movement events and constraints", "description": "What counts as a movement, what records it and what limits it.", "questions": [ { "id": "movement-events-q01", "text": "What identifies and describes the movement of a Internet of Things, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "movement-events-q02", "text": "Who or what asserted this about the movement of a Internet of Things, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "movement-events-q03", "text": "What may an agent decide or do once the movement of a Internet of Things 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 Internet of Things 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 Internet of Things between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Internet of Things, 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 Internet of Things, 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 Internet of Things 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 Internet of Things, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Internet of Things 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 Internet of Things, 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 Internet of Things, 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 Internet of Things is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "use-and-operation", "name": "Use and operation", "description": "What can be done with a Internet of Things and what it takes to do it.", "rationale": "An agent that can recognise a thing but not act on it has only half a model.", "layers": [ { "id": "intended-use", "name": "Intended use and function", "description": "What a Internet of Things is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Internet of Things performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Internet of Things, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "function-and-purpose-q02", "text": "Who or what asserted this about the use of a Internet of Things, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "function-and-purpose-q03", "text": "What may an agent decide or do once the use of a Internet of Things is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "handling-and-procedure", "name": "Handling and procedure", "description": "The steps, skills and tools involved in using a Internet of Things.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Internet of Things at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Internet of Things, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "procedures-and-skills-q02", "text": "Who or what asserted this about handling a Internet of Things, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "procedures-and-skills-q03", "text": "What may an agent decide or do once handling a Internet of Things is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a Internet of Things 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 Internet of Things and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Internet of Things, 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 Internet of Things, 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 Internet of Things 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 Internet of Things is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Internet of Things, 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 Internet of Things, 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 Internet of Things is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 13, "findings": 15, "questions": 45 } } } }