{ "model": { "rank": 3699, "code": "thing-q81945", "model_id": "vr.tr.voice-over-ip", "name": "Voice over IP", "purpose": "Enable an agent to recognise a Voice over IP implementation, assess whether it can deliver usable voice communication, and identify justified configuration, troubleshooting or service actions.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.KNW", "industry": "", "version": "", "url": "/models/thing/q81945/", "tier": 2, "score": 83, "payload": { "layer": "wikidata", "aliases": [ "mobile VoIP", "VoWiMAX", "VoWLAN", "Tuitalk", "Tlenofon" ], "aliasCount": 5, "merged": 5, "knownIn": 83, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q81945", "url": "https://www.wikidata.org/wiki/Q81945", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T14:55:13Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 29.4, "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: 01a07c5c-5cb0-70a0-ad81-8a587202ae77\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Voice over IP\nSense to describe: (none recorded)\nDomain code: INF.KNW\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 004: 1001 r", "usd": 0, "recall": true }, "codex": { "seconds": 91.1, "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: 01a07c5c-5cbd-7f41-be88-bc4a3a5d6241\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Voice over IP\nRegistry id: vr.tr.voice-over-ip\nPlane / domain: INF / INF.KNW\nRegistry definition: (none recorded)\nNames folded into this entry: (none" } } }, "metaModel": { "id": "THING-Q81945", "registryId": "vr.tr.voice-over-ip", "name": "Voice over IP", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.KNW" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q81945/", "model": { "registry_id": "vr.tr.voice-over-ip", "name": "Voice over IP", "purpose": "Enable an agent to recognise a Voice over IP implementation, assess whether it can deliver usable voice communication, and identify justified configuration, troubleshooting or service actions.", "definition": "Voice over IP (VoIP) is a family of technologies for carrying digitized speech in packets over Internet Protocol networks to support voice communication, usually with associated call signalling.", "scope_statement": "This model owns Voice over IP as the technical approach to carrying voice communication over Internet Protocol networks, including the properties of its implementations and services; it does not treat the registry placement in INF / INF.KNW as evidence that VoIP is a standalone academic discipline.", "in_scope": [ "Voice capture, encoding, packet transport, reception and playout across IP networks", "Call signalling, session negotiation and the relationship between signalling and media paths", "Voice quality, network impairments and service continuity", "Endpoint, provider and telephone-network interoperability", "Voice-specific security, operational controls and service capabilities" ], "out_of_scope": [ "General IP network design except where it constrains voice delivery", "Physical telephone and headset construction", "Circuit-switched telephony beyond its interworking boundary with VoIP", "Video conferencing, messaging and collaboration features beyond shared voice dependencies", "Speech recognition, speech synthesis and interpretation of conversation content", "The telecommunications profession or its literature as separate registered things" ], "distinguishing_features": [ "The voice media itself traverses an IP network; IP-based call control alone does not establish that the bearer is VoIP.", "The implementation supports voice session delivery, rather than merely transferring stored audio files.", "Use of a private IP network still qualifies; public Internet carriage is not a defining requirement.", "A telephone number, a physical desk phone or a particular signalling protocol is not required for recognition.", "Where a gateway connects IP voice to circuit-switched telephony, the model distinguishes the IP segment from the converted segment." ], "characteristics": [ { "name": "Implementation boundary", "kind": "category", "unit_or_values": "endpoint pair, enterprise deployment, provider service, interconnection or other explicitly bounded implementation", "why_it_matters": "Determines which components, observations and actions the assessment covers." }, { "name": "Signalling and session negotiation", "kind": "category", "unit_or_values": "protocols, profiles, extensions and versions actually supported and negotiated", "why_it_matters": "Explains whether participants can establish, modify and terminate compatible voice sessions." }, { "name": "Negotiated audio encoding", "kind": "category", "unit_or_values": "codec, clock rate, channel count, packetisation interval and relevant negotiated parameters", "why_it_matters": "Connects endpoint compatibility, bandwidth demand and audio processing requirements." }, { "name": "Media route", "kind": "relation", "unit_or_values": "endpoints linked through direct paths, relays, media anchors, transcoders or gateways", "why_it_matters": "Locates dependencies and explains why media can fail even when call signalling succeeds." }, { "name": "One-way voice delay", "kind": "measurement", "unit_or_values": "milliseconds, with direction, measurement boundaries, method and observation window", "why_it_matters": "Supports assessment of conversational responsiveness without confusing network transit time with full mouth-to-ear delay." }, { "name": "Packet delivery impairment", "kind": "measurement", "unit_or_values": "loss percentage, burst-loss pattern, delay variation in milliseconds and late-discard rate, with definitions and time window", "why_it_matters": "Helps distinguish transport impairment from endpoint or codec problems." }, { "name": "Observed speech quality", "kind": "measurement", "unit_or_values": "named listening or estimation method, score scale, direction and test conditions", "why_it_matters": "Prevents an unexplained quality score from being treated as universally comparable." }, { "name": "Voice session outcome", "kind": "state", "unit_or_values": "unavailable, setup failed, established without audio, one-way audio, degraded, usable or unexpectedly terminated", "why_it_matters": "Separates successful call establishment from successful voice communication." }, { "name": "Protection coverage", "kind": "state", "unit_or_values": "authentication and signalling/media protection recorded separately for each hop and termination point", "why_it_matters": "Makes trust boundaries visible and avoids mistaking hop protection for end-to-end confidentiality." }, { "name": "Calling reachability", "kind": "relation", "unit_or_values": "supported identities, destinations, inbound routes and telephone-network interconnections", "why_it_matters": "Defines whom the service can actually reach and which provider or gateway dependencies apply." } ], "affordances": [ "Trace a failed or degraded call across signalling, media, endpoint and interconnection boundaries.", "Compare negotiated voice capabilities and identify a compatible configuration.", "Assess measured voice quality against an explicitly chosen service target.", "Identify exposed trust boundaries and propose authorised changes to voice access and protection controls.", "Evaluate whether routing, capacity or failover changes preserve required calling capabilities.", "Record unresolved service limitations before recommending adoption or operational changes." ] }, "sources": [], "structure": { "bundles": [ { "id": "voice-service-boundary", "name": "Voice service boundary", "description": "Establishes which IP voice implementation is being modelled and the calling capabilities it actually offers.", "rationale": "VoIP names a technical approach spanning multiple deployment types, so an agent must establish the concrete service boundary before judging it.", "layers": [ { "id": "ip-voice-identity", "name": "IP voice identity", "description": "Identifies where voice media uses IP and separates that from adjacent communication technologies.", "findings": [ { "id": "voice-bearer-boundary", "name": "Voice bearer boundary", "description": "Record the IP-carried voice segments and any transitions to other bearer technologies.", "questions": [ { "text": "Which part of the voice media path is transported over IP, and what evidence establishes that?", "kind": "definition", "id": "voice-bearer-boundary-q01" }, { "text": "Where does responsibility pass to a circuit-switched network, another provider or an independently modelled service?", "kind": "boundary", "id": "voice-bearer-boundary-q02" } ] } ] }, { "id": "calling-capabilities", "name": "Calling capabilities", "description": "Describes reachable parties and supported voice behaviours without assuming public telephone service.", "findings": [ { "id": "reachability-and-feature-contract", "name": "Reachability and feature contract", "description": "Record supported destinations and features, distinguishing advertised support from verified operation.", "questions": [ { "text": "Which internal identities, external voice services and public telephone destinations can users call or receive calls from?", "kind": "boundary", "id": "reachability-and-feature-contract-q01" }, { "text": "Which capabilities, such as transfer, hold, conferencing or emergency calling, have been verified, and against which service documentation?", "kind": "provenance", "id": "reachability-and-feature-contract-q02" } ] } ] } ] }, { "id": "session-control-and-interworking", "name": "Session control and interworking", "description": "Captures how calls are addressed, established, negotiated and connected across technical boundaries.", "rationale": "Voice failures frequently arise from differences between endpoint capabilities, signalling expectations and gateway behaviour.", "layers": [ { "id": "call-establishment", "name": "Call establishment", "description": "Records identity resolution, signalling routes and session lifecycle behaviour.", "findings": [ { "id": "signalling-contract", "name": "Signalling contract", "description": "Record the actual signalling mechanisms, participating control services and negotiated session parameters.", "questions": [ { "text": "How is a called identity resolved to a destination, and which signalling components participate in setup and termination?", "kind": "definition", "id": "signalling-contract-q01" }, { "text": "Which call trace or provider specification establishes the protocols, extensions and session parameters in use?", "kind": "provenance", "id": "signalling-contract-q02" } ] } ] }, { "id": "endpoint-and-gateway-compatibility", "name": "Endpoint and gateway compatibility", "description": "Examines voice negotiation and feature translation between unlike participants.", "findings": [ { "id": "negotiation-and-conversion", "name": "Negotiation and conversion", "description": "Record common audio capabilities and any translation needed for codecs, dialled identities or telephone event signalling.", "questions": [ { "text": "Which codecs and telephone event mechanisms can both sides use, and where are transcoding or other conversions required?", "kind": "boundary", "id": "negotiation-and-conversion-q01" }, { "text": "Which interoperability tests are needed before changing an endpoint, trunk, gateway or negotiated media profile?", "kind": "action", "id": "negotiation-and-conversion-q02" } ] } ] } ] }, { "id": "media-delivery-and-speech-quality", "name": "Media delivery and speech quality", "description": "Follows voice from audio input through packet delivery to audible output and evaluates conversational usability.", "rationale": "A connected call can still deliver poor, missing or one-way audio, so voice delivery requires evidence independent of signalling success.", "layers": [ { "id": "audio-processing-path", "name": "Audio processing path", "description": "Captures encoding, packetisation, buffering and audio processing along each direction of the call.", "findings": [ { "id": "audio-processing-budget", "name": "Audio processing budget", "description": "Record where encoding, buffering, transcoding and endpoint audio behaviour affect delay and intelligibility.", "questions": [ { "text": "What codec, packetisation interval, playout buffering and transcoding steps apply in each direction?", "kind": "definition", "id": "audio-processing-budget-q01" }, { "text": "How are endpoint processing delay, echo and clipping distinguished from packet-network impairments?", "kind": "measurement", "id": "audio-processing-budget-q02" } ] } ] }, { "id": "transport-and-listening-evidence", "name": "Transport and listening evidence", "description": "Relates directional packet observations to measured or reported voice quality.", "findings": [ { "id": "conversational-quality-assessment", "name": "Conversational quality assessment", "description": "Record loss, delay variation, late packets and voice quality with their methods and operating conditions.", "questions": [ { "text": "What are the measured delay, packet loss, burst patterns and late-discard rates for each direction during representative calls?", "kind": "measurement", "id": "conversational-quality-assessment-q01" }, { "text": "Which listening test or quality estimation method supports the usability judgment, and what acceptance target applies?", "kind": "measurement", "id": "conversational-quality-assessment-q02" } ] } ] } ] }, { "id": "network-dependencies-and-continuity", "name": "Network dependencies and continuity", "description": "Records the infrastructure conditions needed for voice paths to remain reachable and adequately provisioned.", "rationale": "VoIP usability depends on media traversal, concurrent traffic and supporting services that may fail independently of the application.", "layers": [ { "id": "media-reachability", "name": "Media reachability", "description": "Makes actual media paths and address-boundary traversal explicit.", "findings": [ { "id": "bidirectional-media-path", "name": "Bidirectional media path", "description": "Record the route in each direction, including address translation, firewall rules, relays and media anchors.", "questions": [ { "text": "Which addresses, ports, transports and traversal mechanisms produce a working media path in each direction?", "kind": "definition", "id": "bidirectional-media-path-q01" }, { "text": "What authorised diagnostic observation would distinguish blocked media, incorrect destination information and an endpoint audio fault?", "kind": "action", "id": "bidirectional-media-path-q02" } ] } ] }, { "id": "capacity-and-failure-behaviour", "name": "Capacity and failure behaviour", "description": "Examines expected call load, competing traffic and dependency failures.", "findings": [ { "id": "voice-continuity-envelope", "name": "Voice continuity envelope", "description": "Record the operating load and failure conditions under which required calling remains available.", "questions": [ { "text": "How many concurrent calls meet the chosen quality target under representative traffic, including packet overhead and any traffic prioritisation?", "kind": "measurement", "id": "voice-continuity-envelope-q01" }, { "text": "What happens to active calls and new calls when power, access connectivity, name resolution, call control or a media relay fails?", "kind": "measurement", "id": "voice-continuity-envelope-q02" } ] } ] } ] }, { "id": "voice-security-and-operational-control", "name": "Voice security and operational control", "description": "Defines the trust boundaries, misuse controls and evidence needed to operate a voice service responsibly.", "rationale": "Call routing, voice confidentiality and diagnostic access expose different risks and require separately recorded controls.", "layers": [ { "id": "identity-and-media-protection", "name": "Identity and media protection", "description": "Separates authentication, caller identity assertions and protection of signalling and speech.", "findings": [ { "id": "voice-trust-boundaries", "name": "Voice trust boundaries", "description": "Record who authenticates each participant, who asserts displayed identity and where protected traffic can be decrypted.", "questions": [ { "text": "How are endpoints and providers authenticated, and what evidence supports trusting a displayed caller identity?", "kind": "provenance", "id": "voice-trust-boundaries-q01" }, { "text": "Where do signalling and media protection terminate, and which intermediaries can access call metadata or intelligible speech?", "kind": "boundary", "id": "voice-trust-boundaries-q02" } ] } ] }, { "id": "abuse-controls-and-diagnostics", "name": "Abuse controls and diagnostics", "description": "Records controls over calling privileges and the handling of voice-related operational evidence.", "findings": [ { "id": "authorised-voice-operations", "name": "Authorised voice operations", "description": "Record controls against unauthorised calling and service disruption, together with permissions for diagnostic data collection.", "questions": [ { "text": "Which destination restrictions, call-rate controls and alerts constrain unauthorised or excessive calling, and how can their effectiveness be tested?", "kind": "action", "id": "authorised-voice-operations-q01" }, { "text": "Which call records, packet captures or recordings may an agent collect, and what access, consent and retention constraints apply?", "kind": "boundary", "id": "authorised-voice-operations-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 VoIP as a technology family, rather than as an academic discipline; the registry records no narrower sense.", "The kinds overlap because they distinguish signalling, deployment and service arrangements.", "Standards are named from recall; jurisdiction-specific obligations and performance targets require verification for a particular deployment." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Voice over IP 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": [ "SIP-based telephony", "H.323-based telephony", "Hosted IP telephony", "On-premises IP PBX telephony", "Application-to-application voice calling", "IP trunking between telephone systems" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Voice over IP 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": "SIP URI", "value_or_pattern": "sip:user@domain", "note": "Identifies a SIP communication resource; it need not correspond to a telephone number." }, { "scheme": "ITU-T E.164", "value_or_pattern": "International telephone number containing at most 15 digits", "note": "Used for telephone-number addressing where VoIP services interconnect with public telephone networks; not required for every VoIP endpoint." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Voice over IP 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": [ "IETF RFC 3261: Session Initiation Protocol (SIP), used for session signalling.", "IETF RFC 3550: Real-time Transport Protocol (RTP), with RTCP for reporting and control.", "IETF RFC 3711: Secure Real-time Transport Protocol (SRTP), providing protection for real-time media.", "ITU-T Recommendation G.711: Pulse code modulation of voice frequencies.", "ITU-T Recommendation H.323: Packet-based multimedia communications systems." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Voice over IP 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": [ "Business telephone systems and contact centres", "Residential telephone service delivered over broadband", "Voice calling within messaging and collaboration applications", "Interconnection of PBXs and telephone service providers", "Remote extensions for employees working away from an office" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Voice over IP this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "G.711 encoded audio bit rate", "typical_range": "64", "unit": "kbit/s per direction, excluding transport overhead" }, { "quantity": "Voice packetization interval", "typical_range": "10-30, depending on codec and configuration", "unit": "ms" }, { "quantity": "One-way mouth-to-ear delay", "typical_range": "Below approximately 150 is a common conversational design target, not a guaranteed operating range", "unit": "ms" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Voice over IP 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": [ "Packet loss, delay variation and excessive latency cause missing speech, distorted audio or difficult conversational turn-taking.", "NAT, firewall or signalling configuration problems can prevent calls or produce one-way audio.", "Loss of local power or network connectivity can interrupt service.", "Inadequate authentication or media protection can enable toll fraud, impersonation or eavesdropping.", "Emergency calls may fail or convey incorrect location information when endpoint location and emergency routing are not maintained." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Voice over IP 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": [ "Emergency calling, location reporting and service availability obligations vary by jurisdiction and service classification.", "Number allocation, number portability and interconnection requirements vary among national telephone systems.", "Some jurisdictions restrict particular VoIP services or require providers to hold telecommunications licences." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Voice over IP 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": "IP telephony", "difference": "Often used synonymously with VoIP; where distinguished, IP telephony includes the complete telephone service and its features, while VoIP describes voice transport technology." }, { "name": "Circuit-switched telephony", "difference": "Carries calls through allocated circuit resources rather than transporting speech as IP packets." }, { "name": "SIP", "difference": "A session signalling protocol; it does not itself encode or transport the voice media." }, { "name": "RTP", "difference": "A real-time media transport protocol used for voice and other media; it is one component of many VoIP systems." }, { "name": "WebRTC", "difference": "A framework for real-time audio, video and data communication that can implement VoIP but also supports non-voice communication." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Voice over IP this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend Voice over IP to denote a technical approach, a service class or a field of knowledge, and does an existing Vercy model already own that concept?", "Which authoritative specifications and implementation documents should anchor the model's signalling, media, traversal and interworking terminology?", "Which deployment contexts and call scenarios should define representative quality targets and capacity tests?", "For any concrete service, which emergency-calling capabilities and jurisdiction-specific obligations apply, and what evidence verifies them?", "Which provider claims about interoperability, failover, caller identity and encryption can be independently verified, and which must remain explicitly unconfirmed?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 19, "questions": 29 } }, "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 Voice over IP, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a Voice over IP implementation, assess whether it can deliver usable voice communication, and identify justified configuration, troubleshooting or service actions.", "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: mobile VoIP, VoWiMAX, VoWLAN, Tuitalk, Tlenofon.", "5 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 83 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 Voice over IP, 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": [ "mobile VoIP", "VoWiMAX", "VoWLAN", "Tuitalk", "Tlenofon" ] } ], "standing": "Described in 83 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 5 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 Voice over IP from another, and a Voice over IP 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 Voice over IP, 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 Voice over IP, 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 Voice over IP 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 Voice over IP, 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 Voice over IP, 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 Voice over IP 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 Voice over IP 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 Voice over IP, 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 Voice over IP, 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 Voice over IP 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 Voice over IP from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Voice over IP, 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 Voice over IP, 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 Voice over IP 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 Voice over IP 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 Voice over IP between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Voice over IP, 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 Voice over IP, 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 Voice over IP 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 Voice over IP, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Voice over IP 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 Voice over IP, 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 Voice over IP, 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 Voice over IP 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 Voice over IP 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 Voice over IP contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a Voice over IP, 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 Voice over IP, 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 Voice over IP 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 Voice over IP and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a Voice over IP, 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 Voice over IP, 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 Voice over IP 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 Voice over IP 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 Voice over IP 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 Voice over IP 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 Voice over IP 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 Voice over IP 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 Voice over IP, 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 Voice over IP 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 Voice over IP and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Voice over IP, 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 Voice over IP, 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 Voice over IP 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 Voice over IP is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Voice over IP, 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 Voice over IP, 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 Voice over IP 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 } } } }