[x3d-public] L.2 Re: Annex L HTML authoring guidelines for X3D4; naming Script versus X3DScript

[Don Brutzman]

Thanks for great feedback.  Accepted majority of words but simply kept "and vice versa" so that future language lawyers don't try to infer anything asymmetric.

On 12/14/2020 4:02 PM, Andreas Plesch wrote:
> 
> Hello Don,
> 
> that looks great. If I may, I will go through the Annex section by
> section, starting with L.2.
> 
> "Harmonize event models so that user interaction within the HTML page
> can also affect the X3D model, and vice versa."
> 
> Although UI events such as a mouse click are most illustrative, I
> think that event harmonization design goals should also include non-UI
> events. For example, x_ite_dom forwards all X3D output events as DOM
> events (which can be received by DOM script API methods). Similarly,
> x3dom has an onoutputchange attribute for all x3d nodes. As a result,
> it is possible to monitor the position of a X3D scene object, for
> example, from the HTML/DOM page.
> 
> So I would suggest to broaden the design goal to:
> 
> "Harmonize event models so that DOM events such as user interaction
> within the HTML page can also affect the X3D model, and X3D events the
> DOM."
> 
> ...continued, -Andreas
> -
> 
> On Mon, Dec 14, 2020 at 5:11 PM Don Brutzman <brutzman at nps.edu> wrote:
>>
>> Thanks for discussion today John.  Clean copy ready for review:
>>
>> * Annex L HTML authoring guidelines for X3D4
>>     https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-WD3/Part01/htmlGuidelines.html
>>
>> Prior issue of discussion was naming Script versus X3DScript.  I put 2 options in the guidelines:
>>
>> * L.4.1 HTML and X3D synchronization
>>
>> "Of note is that both HTML and X3D languages include definitions for a Script node, so disambiguation is necessary. One possible approach is to require that only X3D Script nodes can appear between X3D elements within an HTML page. An alternative approach is that any X3D Script node located within HTML page might be renamed X3DScript to avoid any name collisions."
>>
>> 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
> 
> 
> 
> --
> Andreas Plesch
> Waltham, MA 02453
> 

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