BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20260219T073233Z
BEGIN:VTIMEZONE
TZID:Asia/Tokyo
X-MICROSOFT-CDO-TZID:20
BEGIN:STANDARD
DTSTART:20241115T233000
TZOFFSETFROM:+0900
TZOFFSETTO:+0900
TZNAME:JST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:757dc9dc-d7a4-4041-908b-ea1daf5589e2
DTSTAMP:20260219T073233Z
SUMMARY:WebSpatial API for Spatialized HTML/CSS and Spatialized PWAs on spa
 tial and multimodal AI devices
DTSTART;TZID=Asia/Tokyo:20251111T083000
DTEND;TZID=Asia/Tokyo:20251111T093000
DESCRIPTION:https://www.w3.org/events/meetings/757dc9dc-d7a4-4041-908b-ea1d
 af5589e2/\n\nThe strong demand for multimodal interaction capabilities in 
 client-side AI is driving the evolution of next-generation general computi
 ng platforms from screen-based and handheld devices to hands-free wearable
  devices\, such as augmented reality glasses and mixed reality visors (hea
 d-mounted displays).\n\nApps (include Web) on such next-gen platforms must
  be able to:\n\n1. Fully leverage 3D space surrounding the user\, moving b
 eyond the limitations of 2D planes\, breaking free from window borders.\n\
 n2. Work with a new OS architecture based on [Unified Rendering](https://d
 eveloper.picoxr.com/news/multi-app-rendering/) and Shared Space\, in which
  apps no longer render themselves independently\, they can blend in with o
 ther apps in the same shared space\, and use OS-managed spatial containers
  instead of old-style windows or browser tabs.\n\n3. Integrate seamlessly 
 with the real-world environment\, for example\, Apple's recently proposed 
 liquid/frosted glass UI. Instead of using a fixed solid background color o
 r just switching between light and dark modes\, the UI dynamically renders
  a blended material background based on what's behind each part of the int
 erface from the user's perspective\, making it clear and readable no matte
 r the lighting or colors in the environment.\n\n4. In addition to conventi
 onal 2D panel-based and 3D canvas-based GUIs\, apps should be able to incl
 ude real volumetric 3D content that can be viewed from all angles and meas
 ured in real-world units.\n\n5. Whether 2D or 3D\, elements must be capabl
 e of positioning and transformation along the spatial Z-axis\, supporting 
 spatial interaction events to acquire positional and motion data within 3D
  space\, thereby enabling interactions such as dragging\, rotation\, and s
 caling.\n\n6. Don't break away from mainstream GUI development ecosystems\
 , keep using the established view components\, layout systems\, and stylin
 g systems from 2D GUI development (for the web\, that means HTML/CSS). In 
 most application scenarios\, limited 3D development requirements should be
  embedded within the overarching 2D development approach.  For example\, 3
 D container elements should be able to join the X/Y layout system just lik
 e 2D elements\, while supporting full 3D-engine-style development inside. 
 That means in HTML code you can use different Entities (different geometri
 c Entities\, Entities capable of loading 3D model assets\, or Entities cap
 able of hosting 2D HTML or particle effects)\, declare\, load and configur
 e materials and textures\, and work with EntityTransform and physics engin
 e properties.\n\nWithin the existing Immersive Web WG\, the WebXR standard
 \, analogous to OpenXR\, always take over the binocular display and the en
 tire spatial environment\, perform self-contained rendering\, and build in
 teractions from scratch\, thereby failing to satisfy the aforementioned re
 quirements.\n\nThere are some scattered Spatial Web features right now\, l
 ike Model Element\, Immersive Media (Fullscreen API)\, and Interactive Reg
 ions (Hover Effects for Eye-Hand Interactions). They can't systematically 
 meet the needs above\, and they still lag far behind native spatial apps.\
 n\nA systematic solution can only be achieved by equipping existing HTML/C
 SS and PWA technologies with spatial capabilities\, extending the current 
 2D web standards with a minimal set of new APIs (let's call them the WebSp
 atial API). \n\nSuch an approach would enable the open web to gain entry i
 nto the paradigm shift of general computing platforms\, and potentially em
 erge as the optimal application solution for these platforms. This is beca
 use both AI OS and MR OS inherently demand vast numbers of apps that are i
 nstallation-free\, on-demand\, and disposable - characteristics naturally 
 aligned with the web.\n\n**Goal(s):**\nInitiate the discussion and draftin
 g of the WebSpatial API's requirements and standardization.\n\nAgenda\n\n*
 *Materials:**\n- [recording](https://www.w3.org/2025/11/breakouts/recordin
 g-22.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025
 -breakouts/issues/22)
STATUS:CONFIRMED
CREATED:20251028T073614Z
LAST-MODIFIED:20260219T073233Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Floor 4 - 406
CATEGORIES:TPAC 2025,Breakout Sessions
END:VEVENT
END:VCALENDAR