[x3d-public] X3D meeting agenda 1 OCT 2021: TimeSensor pause, resume, cycleInterval resolution review

Fri Oct 1 08:14:37 PDT 2021

Additional agenda item: review resolution prose for PROFILE and COMPONENT handling by topmost parent scene across Inline scenes.

  *   Mantis 1151: 09.4.2 Inline - Inline is silent about head, component, unit, and meta statements
  *   https://www.web3d.org/member-only/mantis/view.php?id=1151

now published at

  *   X3D Architecture, Clause 7 Core Component, 7.2.5.3 PROFILE statement
  *   https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#PROFILEStatement

7.2.5.3 PROFILE statement

Every X3D application shall declare a profile at the beginning of execution. This declaration tells the browser the exact set of components and their support levels that are required for the application to run, allowing for a browser to dynamically load the appropriate components if it so desires, and providing a mechanism for strict conformance should the browser choose to enforce it. If a browser supports the combination of declared profile and components profiles, components, and component support levels (see 7.2.5.4 COMPONENT statement<https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#COMPONENTStatement>), it may proceed with presenting the world; otherwise, it shall fail.

Each PROFILE is equivalent to a precise combination of COMPONENT statements including names and levels. The Full profile defined to be the superset of all components and component support levels. The Core profile is defined to be the minimum set of all components and component support levels.

The profile is declared via a PROFILE statement immediately following the Header statement at the top of the file. The form of the PROFILE statement is:

PROFILE <name>

where name is a string that does not contain whitespace.

The following profiles are defined in this standard:

  1.  Core (see A Core profile<https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/coreprofile.html>),
  2.  Interchange (see B Interchange profile<https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/interchange.html>),
  3.  Interactive (see C Interactive profile<https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/interactive.html>),
  4.  MPEG-4 interactive (see D MPEG-4 interactive profile<https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/MPEG4interactive.html>),

  1.  Immersive (see E Immersive profile<https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/immersive.html>),

  1.  Full (see F Full profile<https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/fullProfile.html>),
  2.  CADInterchange (see H CAD interchange profile<https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/CADInterchange.html>) and
  3.  MedicalInterchange (see M MedicalInterchange profile<https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/MedicalInterchange.html>).

The profile name is implicitly qualified by the version number of the standard (see 7.2.5.2 Header statement<https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#HeaderStatement>). Browsers shall use both the profile name and the version number to determine the specific characteristics of the profile.

For an X3D model that includes references to Inline nodes, the topmost model defines the maximum capabilities of the combined models. The combination of defined PROFILE and COMPONENT statements in the parent model shall be equivalent to (or a superset of) the union of components and component support levels identified by the PROFILE and COMPONENT statements specified in each contained Inline scene.
all the best, Don
--
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman

From: Brutzman, Donald (Don) (CIV)<mailto:brutzman at nps.edu>
Sent: Tuesday, September 28, 2021 11:45 AM
To: X3D Public<mailto:x3d-public at web3d.org>
Cc: Richard F. Puk<mailto:puk at igraphics.com>; Athanasios Malamos<mailto:athanasios.malamos at gmail.com>; Eftychia Lakka<mailto:efilakka at gmail.com>
Subject: X3D meeting agenda 1 OCT 2021: TimeSensor pause, resume, cycleInterval resolution review

Regular meeting this Friday on Web3D Consortium teleconference line.

Dick and I made excellent progress resolving multiple long-standing Mantis issues regarding pause, resume, cycleInterval changes.  We further built on prior mantis/mailing-list comments to require consistent determinism when loading Inline models as part of initial scene definition, independent of intermediate network delays.  Interesting.

Issue commentary online (for Web3D members) at

  *   https://www.web3d.org/member-only/mantis/view_all_bug_page.php
  *   Mantis 1080: 08.4.1 TimeSensor - TimeSensor cycleInterval needs to be modifiable when running
  *   Mantis 1106: 08.2.4.4 Pausing time - Settings on resuming after pause

We request review, all comments welcome.  Proposed changes are publicly visible online at

  *   X3D Architecture, Time component
  *   https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/time.html

Looking further ahead:  the following long-standing issue to make TimeSensor cycleTime outputOnly event part of X3DTimeDependentNode, and thus consistently part of AudioClip MovieTexture and relevant new Audio nodes.  Makes sense for media synchronization, seems feasible and useful to authors, appears do-able without loss of backwards compatibility.  We did not resolve this functional improvement today, but might address it during upcoming CD balloting by ISO member nations.

  *   Mantis 8.3.1 X3DTimeDependentNode: include TimeSensor outputOnly field cycleTime?

We will also discuss this during the X3D Audio call Wednesday.  If everyone wants to proceed, we will consider adoption on Friday.

As ever, time is of the essence.  No really.

Have fun with X3D4 animation and interaction!  8)

all the best, Don
--
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20211001/c946d3c1/attachment-0001.html>