Sensing Request
sensingrequest.com
§1 — Definition
Sensing Service Type
Sensing Service Type provides a stable semantic identity for classification of a requested or offered sensing service.
§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.
What separates them
Sensing Service Type identifies classification of a requested or offered sensing service; sensingrequest.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.
ETSI GR ISC 003 V1.1.1 (2026-02), clause 4.3, defines a sensing service, and ITU-T YSTR.ISAC-fra (11/2025), clause 6.1, lists diverse sensing-service examples. Neither source defines 'Sensing Service Type' as a standardized 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 classification of a requested or offered sensing service; it does not perform, operate, execute, expose, manage, transport, process, verify, or implement a network function or standard.
Primary in Sensing Objectives, Profiles, Capabilities & Services. The view asks: What sensing can be provided against a requirement?
§6 — Machine-Readable Resources
Public identity and discovery resources.
- Namespace manifesthttps://sensingservicetype.com/namespace.json
- Public ontologyhttps://sensingservicetype.com/ontology.jsonld
- LLM summaryhttps://sensingservicetype.com/llms.txt
- Robots policyhttps://sensingservicetype.com/robots.txt
- Sitemaphttps://sensingservicetype.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.