Sensing Information
sensinginformation.com
§1 — Definition
Sensing Data Integration
Sensing Data Integration provides a stable semantic identity for integration of sensing information or data.
§2 — Relationships
Closest related capability
Difference
Relationship
Closest comparison and adjacent concepts.
Related concepts are linked only for plain-language orientation within the three LJP views. The links do not assert standards-derived dependencies, protocol order, execution, or formal predicates. The package uses three LJP-defined views: Sensing Environment, Entities & Topology asks what exists and participates in sensing and how it is arranged; Sensing Objectives, Profiles, Capabilities & Services asks what sensing can be provided against a requirement; and Sensing Information, Performance, Results & Evidence asks what was produced, how well, and what result remains. Its conceptual traverse is Objective, Profile or Requirements, Capabilities, Service Type, Request, Discovery or Selection, Authorization, Sensing Information, Performance, Result, and Evidence. The traverse is Evidence Level E, an LJP synthesis rather than a protocol sequence or executed workflow. Cross-cutting considerations are security, privacy and trust; cooperative or multi-entity sensing; compute or AI as a candidate relationship and LJP synthesis; and performance and evaluation. The three-view organization and semantic capability traverse are an LJP synthesis and do not constitute an official 3GPP architecture or standardized taxonomy. Individual technical concepts are mapped to primary-source specifications and study items according to their verified publication status.
What separates them
Sensing Data Integration identifies integration of sensing information or data; sensinginformation.com identifies an adjacent but distinct concept.
How they work together
Both concepts belong to the LJP package network. Their adjacency is an LJP synthesis and does not assert a standards-defined dependency or executed flow.
See also
§3 — Standards and Authority
Where the terminology comes from.
Informative Technical Report ITU-T YSTR.ISAC-fra (11/2025), clauses 8.5 and 8.6, addresses information extraction, merging, multi-site fusion, processing, and result exposure. It supports the underlying integration area but not a standardized 'Sensing Data Integration' object. Evidence: C; LJP package relationships: E.
§4 — Evaluation
Apply the distinction to the decision at hand.
Use this identity to frame the concept and its evidence boundary before selecting any implementation, supplier, or operating design.
§5 — LJP Foundation
How this capability fits the package.
The domain identifies and describes integration of sensing information or data; it does not perform, operate, execute, expose, manage, transport, process, verify, or implement a network function or standard.
Anchor in Sensing Information, Performance, Results & Evidence. The view asks: What was produced, how well, and what result remains? The package uses three LJP-defined views: Sensing Environment, Entities & Topology asks what exists and participates in sensing and how it is arranged; Sensing Objectives, Profiles, Capabilities & Services asks what sensing can be provided against a requirement; and Sensing Information, Performance, Results & Evidence asks what was produced, how well, and what result remains. Its conceptual traverse is Objective, Profile or Requirements, Capabilities, Service Type, Request, Discovery or Selection, Authorization, Sensing Information, Performance, Result, and Evidence. The traverse is Evidence Level E, an LJP synthesis rather than a protocol sequence or executed workflow. Cross-cutting considerations are security, privacy and trust; cooperative or multi-entity sensing; compute or AI as a candidate relationship and LJP synthesis; and performance and evaluation. The three-view organization and semantic capability traverse are an LJP synthesis and do not constitute an official 3GPP architecture or standardized taxonomy. Individual technical concepts are mapped to primary-source specifications and study items according to their verified publication status.
§6 — Machine-Readable Resources
Public identity and discovery resources.
- Namespace manifesthttps://sensingdataintegration.com/namespace.json
- Public ontologyhttps://sensingdataintegration.com/ontology.jsonld
- LLM summaryhttps://sensingdataintegration.com/llms.txt
- Robots policyhttps://sensingdataintegration.com/robots.txt
- Sitemaphttps://sensingdataintegration.com/sitemap.xml
§7 — Credibility Boundary
What this reference does not claim.
The three-view organization and semantic capability traverse are an LJP synthesis and do not constitute an official 3GPP architecture or standardized taxonomy. Individual technical concepts are mapped to primary-source specifications and study items according to their verified publication status. The domain provides stable semantic identity and authority for a concept. Operational implementations and service providers remain replaceable.
This namespace is an LJP editorial construct. It claims no standards ownership or external endorsement and selects no vendor or implementation; protected methods and transaction materials are not disclosed.