[x3d-public] SAI

[Andreas Plesch]

Hi John,

though perhaps not too late, I did not really expect a change in name, just
pointing out the potential for confusion and trying out what a different
name would lead to in an abstract way.

x_ite already implements the existing SAI very completely. There is nothing
really to do from what I can tell. It may be possible to decouple the x_ite
in memory scene representation and runtime management/event flow from webgl
rendering, and run on node.js. But I am not sure how useful that would be..

Andreas

On Thu, Jan 23, 2020, 4:17 PM John Carlson <yottzumm at gmail.com> wrote:

> I don’t think we’re apt to change X3DJSAIL’s name.   We do have to name
> the similar Ecmascript or JavaScript project.   It is likely we will use
> X_ITE for SAI—not sure about X3DOM.   It would be nice if it was
> independent of Angular, React, Vue, so any proprietary or open source
> framework could be used alongside.
>
> I kind of like X3DJS-B “jazz-b”—Similar to JAX-B.  Or just X3D Jazz.
>
> On Thu, Jan 23, 2020 at 8:29 AM Andreas Plesch <andreasplesch at gmail.com>
> wrote:
>
>> Just clarifying that I was referring to UOM based effort to generate
>> functionality for many languages led by Don. More below.
>>
>> On Wed, Jan 22, 2020, 4:00 PM Joseph D Williams <joedwil at earthlink.net>
>> wrote:
>>
>>>
>>>
>>> *From: *Andreas Plesch <andreasplesch at gmail.com>
>>> *Sent: *Saturday, January 18, 2020 6:56 PM
>>> *To: *Joe D Williams <joedwil at earthlink.net>
>>> *Cc: *X3D Graphics public mailing list <x3d-public at web3d.org>
>>> *Subject: *Re: [x3d-public] X3D minutes, 17 JAN 2020: X3Dv4
>>> progress,renamehidden as visible, name types, Mantis issue resolution
>>>
>>>
>>>
>>> On Sat, Jan 18, 2020, 7:41 PM Joseph D Williams <joedwil at earthlink.net>
>>> wrote:
>>>
>>>
>>>
>>> ·  Ecmascript Scene Programming Interface.
>>>
>>>
>>>
>>> Otherwise known as ECMAScript language bindings for our X3D scene
>>> authoring interface (SAI).
>>>
>>> Thanks for All,
>>>
>>> Joe
>>>
>>>
>>>
>>> I am trying out different names since this effort has a different focus
>>> than the existing SAI.
>>>
>>> This is more about construction or description, so SCI or SDI were other
>>> attempts.
>>>
>>> Andreas
>>>
>>
>> Fine, Andreas,
>>>
>>> I was concerned about the ‘Programming’ part of that name. Of course,
>>> for most uses it is eventually a runtime programming system but as you
>>> said, your goal might be above all that because you are describing the
>>> construction of a scene and its contents at an abstraction or possibly a
>>> automated concretization level for scene contents and interactivity at a
>>> level hopefully far above the style of actual x3d user code. So, scene
>>> description or scene construction at a very high level very isolated from
>>> x3d user code are closer..
>>>
>> This isolation from x3d user code is why I am a bit concerned with the
>> potential for confusion when the JSAIL effort reuses the phrase SAI. For
>> me, SAI sometimes reads as Scene Access Interface.
>>
>> And, yes, you are discussing an ‘interface’ in the best sense, but how
>>> does this work? What descriptors or constructors are you presenting to the
>>> user? Is there a better word than Interface?
>>>
>> Perhaps just 'library' ? X3DJSDL X3D Java Scene Description Library ?
>>
>>
>>
>>>
>>> Thanks and Best,
>>>
>>> Joe
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>> _______________________________________________
>> x3d-public mailing list
>> x3d-public at web3d.org
>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>
> ---on the phone---
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200123/b4a8752c/attachment-0001.html>