{
  "capabilityNamespaces": [
    {
      "definition": "Sensing Entity provides a stable semantic identity for sensing transmitter and receiver entity identity.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Entity represents concepts associated with sensing transmitter and receiver entity identity. Distinguishing participants helps readers discuss sensing arrangements without treating a descriptive identity as an operating entity. Within Sensing Environment, Entities & Topology, it is the primary identity.",
      "governingQuestion": "What does Sensing Entity represent within the 6G Sensing Fabric?",
      "id": "https://sensingentity.com/#sensing-entity",
      "name": "Sensing Entity",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingtopology.com",
        "difference": "Sensing Entity identifies sensing transmitter and receiver entity identity; sensingtopology.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "monostaticsensing.com",
          "bistaticsensing.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingentity.com/",
      "whyItMatters": "Distinguishing participants helps readers discuss sensing arrangements without treating a descriptive identity as an operating entity."
    },
    {
      "definition": "Sensing Topology provides a stable semantic identity for spatial and configurational relationships among sensing participants.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Topology represents concepts associated with spatial and configurational relationships among sensing participants. Topology language helps compare how participants are arranged while leaving implementation and protocol choices open. Within Sensing Environment, Entities & Topology, it is the primary identity.",
      "governingQuestion": "What does Sensing Topology represent within the 6G Sensing Fabric?",
      "id": "https://sensingtopology.com/#sensing-topology",
      "name": "Sensing Topology",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingentity.com",
        "difference": "Sensing Topology identifies spatial and configurational relationships among sensing participants; sensingentity.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "monostaticsensing.com",
          "multistaticsensing.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingtopology.com/",
      "whyItMatters": "Topology language helps compare how participants are arranged while leaving implementation and protocol choices open."
    },
    {
      "definition": "Monostatic Sensing provides a stable semantic identity for a monostatic sensing configuration.",
      "deploymentStatus": "active",
      "directAnswer": "Monostatic Sensing represents concepts associated with a monostatic sensing configuration. A distinct identity for the monostatic configuration helps separate it from bistatic and multistatic arrangements. Within Sensing Environment, Entities & Topology, it is the primary identity.",
      "governingQuestion": "What does Monostatic Sensing represent within the 6G Sensing Fabric?",
      "id": "https://monostaticsensing.com/#monostatic-sensing",
      "name": "Monostatic Sensing",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "bistaticsensing.com",
        "difference": "Monostatic Sensing identifies a monostatic sensing configuration; bistaticsensing.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "multistaticsensing.com",
          "sensingtopology.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://monostaticsensing.com/",
      "whyItMatters": "A distinct identity for the monostatic configuration helps separate it from bistatic and multistatic arrangements."
    },
    {
      "definition": "Bistatic Sensing provides a stable semantic identity for a bistatic sensing configuration.",
      "deploymentStatus": "active",
      "directAnswer": "Bistatic Sensing represents concepts associated with a bistatic sensing configuration. A distinct identity for the bistatic configuration helps separate transmitter and receiver placement questions from other arrangements. Within Sensing Environment, Entities & Topology, it is the primary identity.",
      "governingQuestion": "What does Bistatic Sensing represent within the 6G Sensing Fabric?",
      "id": "https://bistaticsensing.com/#bistatic-sensing",
      "name": "Bistatic Sensing",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "monostaticsensing.com",
        "difference": "Bistatic Sensing identifies a bistatic sensing configuration; monostaticsensing.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "multistaticsensing.com",
          "sensingtopology.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://bistaticsensing.com/",
      "whyItMatters": "A distinct identity for the bistatic configuration helps separate transmitter and receiver placement questions from other arrangements."
    },
    {
      "definition": "Multistatic Sensing provides a stable semantic identity for a multistatic or cooperative sensing configuration.",
      "deploymentStatus": "active",
      "directAnswer": "Multistatic Sensing represents concepts associated with a multistatic or cooperative sensing configuration. A distinct identity for multistatic sensing helps discuss multiple participating entities without implying one required coordination method. Within Sensing Environment, Entities & Topology, it is the primary identity.",
      "governingQuestion": "What does Multistatic Sensing represent within the 6G Sensing Fabric?",
      "id": "https://multistaticsensing.com/#multistatic-sensing",
      "name": "Multistatic Sensing",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "bistaticsensing.com",
        "difference": "Multistatic Sensing identifies a multistatic or cooperative sensing configuration; bistaticsensing.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensingmesh.com",
          "sensingtopology.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://multistaticsensing.com/",
      "whyItMatters": "A distinct identity for multistatic sensing helps discuss multiple participating entities without implying one required coordination method."
    },
    {
      "definition": "Sensing Infrastructure provides a stable semantic identity for the broader environment that can support sensing activity. The term is LJP descriptive vocabulary and is not presented as established standards terminology.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Infrastructure represents concepts associated with the broader environment that can support sensing activity. This supporting identity provides environmental context without implying an operational platform or established standards term. Within Sensing Environment, Entities & Topology, it is the supporting identity.",
      "governingQuestion": "What does Sensing Infrastructure represent within the 6G Sensing Fabric?",
      "id": "https://sensinginfrastructure.com/#sensing-infrastructure",
      "name": "Sensing Infrastructure",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingentity.com",
        "difference": "Sensing Infrastructure identifies the broader environment that can support sensing activity; sensingentity.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensingtopology.com",
          "sensingmesh.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensinginfrastructure.com/",
      "whyItMatters": "This supporting identity provides environmental context without implying an operational platform or established standards term."
    },
    {
      "definition": "Sensing Mesh provides a stable semantic identity for distributed or cooperative relationships among sensing participants. The term is LJP descriptive vocabulary and is not presented as established standards terminology.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Mesh represents concepts associated with distributed or cooperative relationships among sensing participants. This supporting identity helps describe distributed participation while avoiding claims about a prescribed mesh implementation. Within Sensing Environment, Entities & Topology, it is the supporting identity.",
      "governingQuestion": "What does Sensing Mesh represent within the 6G Sensing Fabric?",
      "id": "https://sensingmesh.com/#sensing-mesh",
      "name": "Sensing Mesh",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "multistaticsensing.com",
        "difference": "Sensing Mesh identifies distributed or cooperative relationships among sensing participants; multistaticsensing.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensingentity.com",
          "sensingtopology.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingmesh.com/",
      "whyItMatters": "This supporting identity helps describe distributed participation while avoiding claims about a prescribed mesh implementation."
    },
    {
      "definition": "Spatial Network Sensing provides a stable semantic identity for the broader spatial-network sensing space. The term is LJP descriptive vocabulary and is not presented as established standards terminology.",
      "deploymentStatus": "active",
      "directAnswer": "Spatial Network Sensing represents concepts associated with the broader spatial-network sensing space. This supporting identity provides spatial context while remaining LJP descriptive vocabulary rather than established standards terminology. Within Sensing Environment, Entities & Topology, it is the supporting identity.",
      "governingQuestion": "What does Spatial Network Sensing represent within the 6G Sensing Fabric?",
      "id": "https://spatialnetworksensing.com/#spatial-network-sensing",
      "name": "Spatial Network Sensing",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingtopology.com",
        "difference": "Spatial Network Sensing identifies the broader spatial-network sensing space; sensingtopology.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensinginfrastructure.com",
          "sensingmesh.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://spatialnetworksensing.com/",
      "whyItMatters": "This supporting identity provides spatial context while remaining LJP descriptive vocabulary rather than established standards terminology."
    },
    {
      "definition": "Sensing Capabilities provides a stable semantic identity for a set or description of sensing capabilities.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Capabilities represents concepts associated with a set or description of sensing capabilities. The View 2 anchor gives readers a stable entry point for discussing what sensing may be provided against a requirement. Within Sensing Objectives, Profiles, Capabilities & Services, it is the anchor identity.",
      "governingQuestion": "What does Sensing Capabilities represent within the 6G Sensing Fabric?",
      "id": "https://sensingcapabilities.com/#sensing-capabilities",
      "name": "Sensing Capabilities",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingcapability.com",
        "difference": "Sensing Capabilities identifies a set or description of sensing capabilities; sensingcapability.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensingobjective.com",
          "sensingprofiles.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingcapabilities.com/",
      "whyItMatters": "The View 2 anchor gives readers a stable entry point for discussing what sensing may be provided against a requirement."
    },
    {
      "definition": "Sensing Objective provides a stable semantic identity for a desired sensing outcome expressed as a public-safe abstraction.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Objective represents concepts associated with a desired sensing outcome expressed as a public-safe abstraction. Separating an objective from a request or service type helps readers frame outcomes without claiming a sensing-intent function. Within Sensing Objectives, Profiles, Capabilities & Services, it is the primary identity.",
      "governingQuestion": "What does Sensing Objective represent within the 6G Sensing Fabric?",
      "id": "https://sensingobjective.com/#sensing-objective",
      "name": "Sensing Objective",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingprofiles.com",
        "difference": "Sensing Objective identifies a desired sensing outcome expressed as a public-safe abstraction; sensingprofiles.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensingrequest.com",
          "sensingcapabilities.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingobjective.com/",
      "whyItMatters": "Separating an objective from a request or service type helps readers frame outcomes without claiming a sensing-intent function."
    },
    {
      "definition": "Sensing Profiles provides a stable semantic identity for an LJP semantic abstraction for requirements, KPIs, and constraints.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Profiles represents concepts associated with an LJP semantic abstraction for requirements, KPIs, and constraints. The abstraction helps group requirement context without claiming a standards construct called a Sensing Profile. Within Sensing Objectives, Profiles, Capabilities & Services, it is the primary identity.",
      "governingQuestion": "What does Sensing Profiles represent within the 6G Sensing Fabric?",
      "id": "https://sensingprofiles.com/#sensing-profiles",
      "name": "Sensing Profiles",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingobjective.com",
        "difference": "Sensing Profiles identifies an LJP semantic abstraction for requirements, KPIs, and constraints; sensingobjective.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensingcapabilities.com",
          "sensingcontextualinformation.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingprofiles.com/",
      "whyItMatters": "The abstraction helps group requirement context without claiming a standards construct called a Sensing Profile."
    },
    {
      "definition": "Sensing Service Type provides a stable semantic identity for classification of a requested or offered sensing service.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Service Type represents concepts associated with classification of a requested or offered sensing service. A separate service-type identity helps distinguish classification from objectives, capabilities, requests, and authorization boundaries. Within Sensing Objectives, Profiles, Capabilities & Services, it is the primary identity.",
      "governingQuestion": "What does Sensing Service Type represent within the 6G Sensing Fabric?",
      "id": "https://sensingservicetype.com/#sensing-service-type",
      "name": "Sensing Service Type",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingrequest.com",
        "difference": "Sensing Service Type identifies classification of a requested or offered sensing service; sensingrequest.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensingcapabilities.com",
          "sensingobjective.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingservicetype.com/",
      "whyItMatters": "A separate service-type identity helps distinguish classification from objectives, capabilities, requests, and authorization boundaries."
    },
    {
      "definition": "Sensing Request provides a stable semantic identity for a request associated with a sensing service.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Request represents concepts associated with a request associated with a sensing service. A request identity helps distinguish the expression of a need from the capability, service type, selection, or result. Within Sensing Objectives, Profiles, Capabilities & Services, it is the primary identity.",
      "governingQuestion": "What does Sensing Request represent within the 6G Sensing Fabric?",
      "id": "https://sensingrequest.com/#sensing-request",
      "name": "Sensing Request",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingservicetype.com",
        "difference": "Sensing Request identifies a request associated with a sensing service; sensingservicetype.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "trpdiscoveryandselection.com",
          "sensingauthorization.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingrequest.com/",
      "whyItMatters": "A request identity helps distinguish the expression of a need from the capability, service type, selection, or result."
    },
    {
      "definition": "TRP Discovery and Selection provides a stable semantic identity for considering TRPs within the broader, developing area of sensing-entity discovery and selection; no TRP-specific standardized procedure is claimed.",
      "deploymentStatus": "active",
      "directAnswer": "TRP Discovery and Selection provides a bounded identity for considering TRPs within the broader, developing area of sensing-entity discovery and selection. Current sources establish TRPs as possible sensing nodes and establish sensing-entity discovery and selection, but they do not establish a standardized TRP-specific discovery-and-selection procedure. Within Sensing Objectives, Profiles, Capabilities & Services, it remains the primary identity.",
      "governingQuestion": "What does TRP Discovery and Selection represent within the 6G Sensing Fabric?",
      "id": "https://trpdiscoveryandselection.com/#trp-discovery-and-selection",
      "name": "TRP Discovery and Selection",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingrequest.com",
        "difference": "TRP Discovery and Selection identifies a bounded TRP-related question within sensing-entity discovery and selection; sensingrequest.com identifies an adjacent but distinct request concept.",
        "relationship": "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": [
          "sensingauthorization.com",
          "sensingcontextualinformation.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://trpdiscoveryandselection.com/",
      "whyItMatters": "This identity provides a bounded place to discuss discovery and selection without claiming a particular procedure or protocol flow."
    },
    {
      "definition": "Sensing Authorization provides a stable semantic identity for an authorization boundary associated with sensing activity or service.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Authorization represents concepts associated with an authorization boundary associated with sensing activity or service. A distinct boundary identity helps separate permission context from objectives, requests, selection, and operational behavior. Within Sensing Objectives, Profiles, Capabilities & Services, it is the primary identity.",
      "governingQuestion": "What does Sensing Authorization represent within the 6G Sensing Fabric?",
      "id": "https://sensingauthorization.com/#sensing-authorization",
      "name": "Sensing Authorization",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingrequest.com",
        "difference": "Sensing Authorization identifies an authorization boundary associated with sensing activity or service; sensingrequest.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "trpdiscoveryandselection.com",
          "sensingcontextualinformation.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingauthorization.com/",
      "whyItMatters": "A distinct boundary identity helps separate permission context from objectives, requests, selection, and operational behavior."
    },
    {
      "definition": "Sensing Capability provides a stable semantic identity for an individual sensing capability identity. The term is LJP descriptive vocabulary and is not presented as established standards terminology.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Capability represents concepts associated with an individual sensing capability identity. The singular term supports the plural anchor and remains less prominent; the distinction is LJP descriptive vocabulary. Within Sensing Objectives, Profiles, Capabilities & Services, it is the supporting identity.",
      "governingQuestion": "What does Sensing Capability represent within the 6G Sensing Fabric?",
      "id": "https://sensingcapability.com/#sensing-capability",
      "name": "Sensing Capability",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingcapabilities.com",
        "difference": "Sensing Capability identifies an individual sensing capability identity; sensingcapabilities.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensingprofiles.com",
          "sensingservicetype.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingcapability.com/",
      "whyItMatters": "The singular term supports the plural anchor and remains less prominent; the distinction is LJP descriptive vocabulary."
    },
    {
      "definition": "Sensing Contextual Information provides a stable semantic identity for context that may influence requirements or selection. The term is LJP descriptive vocabulary and is not presented as established standards terminology.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Contextual Information represents concepts associated with context that may influence requirements or selection. This supporting identity helps describe relevant context without presenting the phrase as established standards terminology. Within Sensing Objectives, Profiles, Capabilities & Services, it is the supporting identity.",
      "governingQuestion": "What does Sensing Contextual Information represent within the 6G Sensing Fabric?",
      "id": "https://sensingcontextualinformation.com/#sensing-contextual-information",
      "name": "Sensing Contextual Information",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingprofiles.com",
        "difference": "Sensing Contextual Information identifies context that may influence requirements or selection; sensingprofiles.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "trpdiscoveryandselection.com",
          "sensingauthorization.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingcontextualinformation.com/",
      "whyItMatters": "This supporting identity helps describe relevant context without presenting the phrase as established standards terminology."
    },
    {
      "definition": "Sensing Data Integration provides a stable semantic identity for integration of sensing information or data.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Data Integration represents concepts associated with integration of sensing information or data. The View 3 anchor gives readers a stable entry point for discussing information, performance, results, and evidence. Within Sensing Information, Performance, Results & Evidence, it is the anchor identity.",
      "governingQuestion": "What does Sensing Data Integration represent within the 6G Sensing Fabric?",
      "id": "https://sensingdataintegration.com/#sensing-data-integration",
      "name": "Sensing Data Integration",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensinginformation.com",
        "difference": "Sensing Data Integration identifies integration of sensing information or data; sensinginformation.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensingdatatransmission.com",
          "sensingresult.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingdataintegration.com/",
      "whyItMatters": "The View 3 anchor gives readers a stable entry point for discussing information, performance, results, and evidence."
    },
    {
      "definition": "Sensing Information provides a stable semantic identity for information representation associated with sensing.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Information represents concepts associated with information representation associated with sensing. A distinct information identity helps separate representation from transport, integration, performance, and results. Within Sensing Information, Performance, Results & Evidence, it is the primary identity.",
      "governingQuestion": "What does Sensing Information represent within the 6G Sensing Fabric?",
      "id": "https://sensinginformation.com/#sensing-information",
      "name": "Sensing Information",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingdataintegration.com",
        "difference": "Sensing Information identifies information representation associated with sensing; sensingdataintegration.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensingdatatransmission.com",
          "sensingmetadata.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensinginformation.com/",
      "whyItMatters": "A distinct information identity helps separate representation from transport, integration, performance, and results."
    },
    {
      "definition": "Sensing Data Transmission provides a stable semantic identity for transport or transmission of sensing data.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Data Transmission represents concepts associated with transport or transmission of sensing data. A separate transport identity helps distinguish movement of data from its representation, integration, evaluation, or result. Within Sensing Information, Performance, Results & Evidence, it is the primary identity.",
      "governingQuestion": "What does Sensing Data Transmission represent within the 6G Sensing Fabric?",
      "id": "https://sensingdatatransmission.com/#sensing-data-transmission",
      "name": "Sensing Data Transmission",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensinginformation.com",
        "difference": "Sensing Data Transmission identifies transport or transmission of sensing data; sensinginformation.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensingdataintegration.com",
          "sensingperformance.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingdatatransmission.com/",
      "whyItMatters": "A separate transport identity helps distinguish movement of data from its representation, integration, evaluation, or result."
    },
    {
      "definition": "Sensing Performance provides a stable semantic identity for performance or KPI evaluation associated with sensing.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Performance represents concepts associated with performance or KPI evaluation associated with sensing. A performance identity helps separate evaluation from information, transmission, results, and evidence. Within Sensing Information, Performance, Results & Evidence, it is the primary identity.",
      "governingQuestion": "What does Sensing Performance represent within the 6G Sensing Fabric?",
      "id": "https://sensingperformance.com/#sensing-performance",
      "name": "Sensing Performance",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingresult.com",
        "difference": "Sensing Performance identifies performance or KPI evaluation associated with sensing; sensingresult.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensinginformation.com",
          "sensingdataintegration.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingperformance.com/",
      "whyItMatters": "A performance identity helps separate evaluation from information, transmission, results, and evidence."
    },
    {
      "definition": "Sensing Result provides a stable semantic identity for the identity of a sensing result.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Result represents concepts associated with the identity of a sensing result. A distinct result identity helps readers separate what remains from the information, performance evaluation, and supporting evidence. Within Sensing Information, Performance, Results & Evidence, it is the primary identity.",
      "governingQuestion": "What does Sensing Result represent within the 6G Sensing Fabric?",
      "id": "https://sensingresult.com/#sensing-result",
      "name": "Sensing Result",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingperformance.com",
        "difference": "Sensing Result identifies the identity of a sensing result; sensingperformance.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensingevidence.com",
          "sensinginformation.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingresult.com/",
      "whyItMatters": "A distinct result identity helps readers separate what remains from the information, performance evaluation, and supporting evidence."
    },
    {
      "definition": "Sensing Evidence provides a stable semantic identity for evidence associated with sensing operations, results or provenance.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Evidence represents concepts associated with evidence associated with sensing operations, results or provenance. This bounded identity provides public orientation to evidence and provenance without describing implementation detail. Within Sensing Information, Performance, Results & Evidence, it is the primary identity.",
      "governingQuestion": "What does Sensing Evidence represent within the 6G Sensing Fabric?",
      "id": "https://sensingevidence.com/#sensing-evidence",
      "name": "Sensing Evidence",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensingresult.com",
        "difference": "Sensing Evidence identifies evidence associated with sensing operations, results or provenance; sensingresult.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensingperformance.com",
          "sensingmetadata.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingevidence.com/",
      "whyItMatters": "This bounded identity provides public orientation to evidence and provenance without describing implementation detail."
    },
    {
      "definition": "Sensing Metadata provides a stable semantic identity for descriptive context for sensing data. The term is LJP descriptive vocabulary and is not presented as established standards terminology.",
      "deploymentStatus": "active",
      "directAnswer": "Sensing Metadata represents concepts associated with descriptive context for sensing data. This supporting identity helps discuss descriptive context while remaining LJP descriptive vocabulary rather than established standards terminology. Within Sensing Information, Performance, Results & Evidence, it is the supporting identity.",
      "governingQuestion": "What does Sensing Metadata represent within the 6G Sensing Fabric?",
      "id": "https://sensingmetadata.com/#sensing-metadata",
      "name": "Sensing Metadata",
      "publicationStatus": "published",
      "relationshipContext": "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.",
      "relationshipPresentation": {
        "closest_related": "sensinginformation.com",
        "difference": "Sensing Metadata identifies descriptive context for sensing data; sensinginformation.com identifies an adjacent but distinct concept.",
        "relationship": "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": [
          "sensingdataintegration.com",
          "sensingresult.com"
        ]
      },
      "role": "capability-namespace",
      "semanticAuthority": "repository-governed-source",
      "url": "https://sensingmetadata.com/",
      "whyItMatters": "This supporting identity helps discuss descriptive context while remaining LJP descriptive vocabulary rather than established standards terminology."
    }
  ],
  "credibilityBoundary": "Implementation-neutral public orientation; no certification, endorsement, regulatory determination, or performance guarantee.",
  "editorialModel": "2.2",
  "lastModified": "2026-09-20",
  "manifestType": "ljp.public-package-namespace",
  "manifestVersion": "1.0",
  "package": {
    "authorityContext": "ETSI GR ISC 003 V1.1.1 (2026-02), clauses 4 and 5, and informative Technical Report ITU-T YSTR.ISAC-fra (11/2025), clauses 6 to 8, support underlying sensing-node, capability, request, data-processing, performance, and result concepts. ETSI ISG ISAC performs pre-standardisation work; its reports are not normative 3GPP architecture. The three-view package and traverse remain LJP synthesis, Evidence Level E.",
    "authorityReferences": [
      {
        "applies_to": "sensingnode.com",
        "document_id": "ETSI GR ISC 003 V1.1.1 (2026-02)",
        "evidence_role": "primary_authority",
        "id": "etsi-gr-isc-003-package",
        "organization": "ETSI",
        "public_authorized": true,
        "publication_context": "Published ETSI Group Report; pre-standardisation material, not normative 3GPP architecture.",
        "relevance": "Supports published ETSI terminology for sensing modes, entities, service requests, results, and architecture context.",
        "scope_note": "Does not establish the LJP three-view organization or conceptual traverse.",
        "title": "Integrated Sensing And Communications (ISAC); System and RAN Architectures",
        "url": "https://www.etsi.org/deliver/etsi_gr/ISC/001_099/003/01.01.01_60/gr_ISC003v010101p.pdf"
      },
      {
        "applies_to": "sensingnode.com",
        "document_id": "ITU-T YSTR.ISAC-fra (11/2025)",
        "evidence_role": "supporting_source",
        "id": "itu-ystr-isac-fra-package",
        "organization": "ITU",
        "public_authorized": true,
        "publication_context": "Published ITU technical report.",
        "relevance": "Supports underlying sensing capability, request, processing, performance, and result concepts.",
        "scope_note": "Does not endorse LJP identities or package relationships.",
        "title": "Considerations on integrated sensing and communication in IMT-2020 networks and beyond",
        "url": "https://www.itu.int/epublications/publication/itu-t-ystr-isac-fra-2025-11-considerations-on-integrated-sensing-and-communication-in-imt-2020-networks-and-beyond"
      }
    ],
    "definition": "Sensing Node provides the View 1 anchor and a stable semantic identity for sensing participation within the LJP 6G Sensing Fabric.",
    "deploymentStatus": "active",
    "domainContext": "The package provides public semantic identities for sensing participants, arrangements, requirements, capabilities, information, performance, results, and evidence. Domains represent concepts associated with those subjects; they are not operational nodes, functions, services, or control systems.",
    "id": "https://sensingnode.com/#6g-sensing-fabric",
    "name": "6G Sensing Fabric",
    "namespaceName": "6G Sensing Fabric",
    "publicationStatus": "published",
    "relationshipContext": "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.",
    "role": "canonical-package-namespace",
    "semanticAuthority": "repository-governed-source",
    "url": "https://sensingnode.com/",
    "whyItMatters": "Clear boundaries among sensing concepts help readers compare terminology, evidence posture, and adjacent ideas without turning an LJP domain name into a standards claim or implementation claim."
  },
  "principle": "Publish the map, not the machine.",
  "publicResources": {
    "buyerWalkthrough": "https://sensingnode.com/storyboard",
    "llms": "https://sensingnode.com/llms.txt",
    "namespaceManifest": "https://sensingnode.com/namespace.json",
    "ontology": "https://sensingnode.com/ontology.jsonld",
    "overview": "https://sensingnode.com/",
    "robots": "https://sensingnode.com/robots.txt",
    "sitemap": "https://sensingnode.com/sitemap.xml"
  },
  "publisher": {
    "contact": "support@ljpassetgroup.com",
    "id": "https://ljpassetgroup.com/#org",
    "name": "LJP Asset Group LLC",
    "url": "https://ljpassetgroup.com/"
  },
  "supportingNamespaces": [],
  "version": "2.2.2"
}