Skip to content

Portable Identity Profile XR

This page defines a non-normative integration lane for Portable Identity Profile behavior across XR experiences.

Boundary: normative vs non-normative

Normative contract: Specification and Conformance
Non-normative guidance: this page

What this lane enables

portable profile projection across XR surfaces,
avatar and wearable pointer portability,
consent-gated voice/recording/disclosure behavior,
pairwise identity privacy posture,
revocation-aware trust handling for high-risk interactions.

Suggested keys (non-normative)

Suggested facet names:

portableProfile
avatarProfile
capabilityProfile
deviceStateProfile
policyProfile

Suggested pointer names:

portableIdentity.profile
portableIdentity.avatar
portableIdentity.wearables
portableIdentity.translationProfile
portableIdentity.proofBundle

Suggested consent keys:

portableIdentity.profilePublic
portableIdentity.voiceCapture
portableIdentity.translationEnabled
portableIdentity.analyticsShare
portableIdentity.recording.faceVisible

Scenario mapping

Scenario A: conversational AR/MR session

enforce TTL/signature policy,
apply language/voice preferences,
gate mic and capture by consent.

Scenario B: immersive retail/commerce world

resolve avatar/wearable pointers,
enforce profile/publicity consents,
apply revocation-aware checks for trust-sensitive actions.

Scenario C: cross-world portability

use pairwise subjects where feasible,
project supported overlays,
ignore unknown fields safely.

Consumer behavior

Validate required UM fields and version.
Enforce freshness (expiresAt) and signature policy.
Read supported Portable Identity Profile keys only.
Enforce consent with default deny behavior.
Ignore unsupported fields safely.

Issuer behavior

Keep core UM required fields valid.
Use pointers for large avatar/wearable artifacts.
Emit explicit consent decisions for sensitive actions.
Apply pairwise subject strategy where privacy requires it.
Include v0.2 signature metadata for trust-sensitive uses.

Next