[x3d-public] Mantis 667: Sensor nodes missing description field
Brutzman, Donald (Don) (CIV)
brutzman at nps.edu
Fri Mar 18 17:23:40 PDT 2022
Thanks Joe, helpful. Discerning eyes will see that current X3D Interface
Hierarchy derives directly from this earlier version.
Am also happy to report that all of the 8 object-oriented design principles
listed in that email are holding true today, in X3D Architecture
Specification and X3D Unified Object Model (X3DUOM) just as described in
2009. Have fun with X3D! 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 https://
faculty.nps.edu/brutzman
From: Joseph D Williams <joedwil at earthlink.net>
Sent: Friday, March 18, 2022 1:37 PM
To: Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>; X3D Public Mailing List
(x3d-public at web3d.org) <x3d-public at web3d.org>
Subject: RE: [x3d-public] Mantis 667: Sensor nodes missing description field
NPS WARNING: *external sender* verify before acting.
Hi Don,
Since you mention some history of that diagram, I found this old version:
https://web.archive.org/web/20160328193700/http://hypermultimedia.com/x3d/Qu
ick/NodesIDL6diag.txt
<https://web.archive.org/web/20160328193700/http:/hypermultimedia.com/x3d/Qu
ick/NodesIDL6diag.txt>
At the bottom is some history and some guidelines for its development.
Thanks Again,
Joe
Bug?
| +-
StreamAudioSource
|
EXTRA SPACE
|
+- X3DTriggerNode -+- BooleanTrigger
From: Brutzman, Donald (Don) (CIV) <mailto:brutzman at nps.edu>
Sent: Monday, March 14, 2022 5:41 PM
To: X3D Public Mailing List (x3d-public at web3d.org)
<mailto:x3d-public at web3d.org>
Subject: Re: [x3d-public] Mantis 667: Sensor nodes missing description field
Here are the affected nodes. Of note from a user experience perspective:
descriptions by the author make sensing sensible to the user.
The initial list for X3DSensorNode is taken from relevant node hierarchy
(link follows). I also did a search through schema to find many locations
where the descript field is already found.
<https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01
/concepts.html#InterfaceHierarchy>
https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/
concepts.html#InterfaceHierarchy
Nodes and types affected:
X3DSensorNode
Collision
CollisionSensor
EspduTransform
ReceiverPdu
SignalPdu
TransmitterPdu
X3DEnvironmentalSensorNode
ProximitySensor
GeoProximitySensor
TransformSensor
VisibilitySensor
X3DKeyDeviceSensorNode
KeySensor
StringSensor
X3DNetworkSensorNode
LoadSensor
X3DPickSensorNode
LinePickSensor
PointPickSensor
PrimitivePickSensor
VolumePickSensor
Suggested addition due to interaction:
PickableGroup
Nodes and types unaffected by this change, already including description
field:
TimeSensor
X3DPointingDeviceSensorNode
X3DDragSensorNode
CylinderSensor
PlaneSensor
SphereSensor
X3DTouchSensorNode
GeoTouchSensor
TouchSensor
Additional nodes and types with description field:
X3DScriptNode
X3DSoundNode
X3DTextureNode
X3DTimeDependentNode
X3DTriggerNode
Anchor
Inline
GeoMetadata
all 6 HAnim nodes
three shader nodes
X3DViewpointNode
ViewpointGroup
Viewpoint
X3DTextureProjectorNode
two projector nodes
AcousticProperties
all Sound nodes
all the best, Don
--
Don Brutzman Naval Postgraduate School, Code USW/Br brutzman at nps.edu
<mailto:brutzman at nps.edu>
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149
X3D graphics, virtual worlds, Navy robotics https://
faculty.nps.edu/brutzman
From: Brutzman, Donald (Don) (CIV) <brutzman at nps.edu
<mailto:brutzman at nps.edu> >
Sent: Monday, March 14, 2022 9:53 AM
To: X3D Public Mailing List (x3d-public at web3d.org
<mailto:x3d-public at web3d.org> ) <x3d-public at web3d.org
<mailto:x3d-public at web3d.org> >
Cc: Brutzman, Donald (Don) (CIV) <brutzman at nps.edu <mailto:brutzman at nps.edu>
>
Subject: Mantis 667: Sensor nodes missing description field
Resolution of a simple yet important item seems to have eluded us earlier.
Reported here for possible followup comment.
* Mantis 667: 7.3.7 - Need description field for all X3DSensorNode
* https://www.web3d.org/member-only/mantis/view.php?id=667
Mailing list discussion reported this expected development without further
comment:
*
http://web3d.org/pipermail/x3d-public_web3d.org/2018-December/009765.html
X3D4 Architecture Specification:
* X3D4 Architecture, Core component, 7.3.7 X3DSensorNode
*
https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/
components/core.html#X3DSensorNode
Allowing authors to include a description on each sensor node allows them to
communicate intent to end user, and allows browsers to present such
descriptions as part of the user interaction. Seems sensible and necessary.
As an example, a description field is included in
* X3D4 Architecture, Sound component, 16.4.14 MicrophoneSource
*
https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/
components/sound.html#MicrophoneSource
It also might be be a good security practice for browsers to also notify
users when a sensor is active. We'll consider wording on this.
all the best, Don
--
Don Brutzman Naval Postgraduate School, Code USW/Br
<mailto:brutzman at nps.edu> brutzman at nps.edu
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149
X3D graphics, virtual worlds, Navy robotics https://
faculty.nps.edu/brutzman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20220319/73cfa53c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5353 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20220319/73cfa53c/attachment-0001.p7s>
More information about the x3d-public
mailing list