1     Definition 2     Functional Requirements 3     Syntax
4     Semantics 5    Conformance Testing 6     Performance Assessment

1      Definition

The Interaction Potential Data Type quantifies how strongly an object invites or supports interaction within a Virtual Space. It provides a numeric score in the [0–1] range and an optional classification describing the dominant interaction mode (physical, visual, semantic). It supplements or refines Affordance‑based interpretation by indicating the likelihood or salience of an interaction opportunity.

2      Functional Requirements

  • Scalar Potential – The Data Type shall include a PotentialScore in the range [0..1] indicating the estimated strength, likelihood, or salience of an interaction opportunity.
  • Interaction Classification – The Data Type shall optionally describe the primary type of interaction invited or supported: Physical, Visual, Semantic, or None.
  • Contextual Support – Interaction Potential shall be usable by scene‑analysis, affordance‑reasoning, conversational, or multimodal interpretation systems.
  • Extensibility – Future versions may refine the classification categories or add new interaction dimensions without breaking compatibility.

3      Syntax

https://schemas.mpai.community/OSD/V1.5/data/InteractionPotential.json

4      Semantics

Table 1 provides the semantics of the components of Interaction Potential.

Table 1 – Semantics of Interaction Potential

Label Description
Header Interaction Potential Header – Standard “OSD-IAP-Vx,y”.
MInstanceID ID of Virtual Space the Interaction Potential refers to.
InteractionPotentialID Identifier of this Interaction Potential instance.
PotentialScore Numeric value in the range [0..1] representing the likelihood,
intensity, or strength of interaction that the object may support or invite.
InteractionType Classification of the dominant mode of interaction associated with the object.
One of:
• Physical – bodily or spatial interaction
• Visual – visually guided selection or engagement
• Semantic – meaning‑ or context‑driven engagement
• None – no significant interaction potential detected
DataExchangeMetadata Metadata optionally supporting regulated or controlled exchange of Interaction Potential Data, as defined by AIF V3.0.
Trace Provenance trace including Source AIM, timestamps, and details needed for auditability and reproducibility (AIF V3.0).
DescrMetadata Descriptive Metadata (max 2048 characters) providing human‑readable notes, context, or indexing information.

5     Conformance Testing

A Data instance Conforms with V1.5 Spatial Cue (OSD-SCU) if:

  1. Its JSON Object validates against its JSON Schema.
  2. Any included  JSON Object validates against its JSON Schema.
  3. All Data in the JSON Object:
    1. Have the specified Data Types.
    2. Conform with the Qualifiers signaled in their JSON Schemas.

6     Performance Assessment