[x3d-public] [...] set_Value prefix and value_changed suffix, potential v4 issue

[Don Brutzman]

On 4/24/2017 2:01 AM, Michalis Kamburelis wrote:
> [...] I always understood the X3D specification (the
> http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/concepts.html#FieldSemantics
> section) to mean that "if you want to refer to the input event of the
> xxx inputOutput, you MUST write it set_xxx". (And, analogously, you
> MUST write "xxx_changed" to refer to the output event.)

"Testimony time" - I suspect that we all have slightly different understandings of specification guidance on this issue.  It certainly has confused me a number of times over the years, not sure we've ever fully landed on a consistent comprehension.  Improving clarity is always good!

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