[x3d-public] inline access from dom -- Inline Trees, Reuse, and Access

[Andreas Plesch]

.

> Inline (and related - some not yet defined) nodes are really important.
> They allow a developer to build a scene in pieces (or multiple
> developers to work on a scene). I cannot foresee a situation where
> something like that does not exist.
>
>
The web community has recognized this as well and came up with web
components. If x3d becomes intergrated into a web page dom, "Inline",
"Macro" and protos will have a lot of overlap with those. In particular, I
think "Inline" is very similar to HTML Imports. It may be difficult to have
traditional X3D compartmentalization along side web components but perhaps
not impossible.


> The details of how to access the internals may change depending on how
> the data is loaded (potentially the data format) and the kind of
> protection that might be needed. For example a model may represent a
> part that should not be modified (because of licensing, etc.). The X3D
> library may need to enforce (to an extent) that restriction by not
> exposing that model to the DOM and user modification. Note that I am not
> arguing for absolute protection or DRM mechanisms.
>
>
Yes, I thought the main motivation for EXPORT may be to control what is
exposed. But then again, the inline node has to be able to be downloaded
and therefore will be subject to any manipulation locally, including
outside of X3D, so this control would be mostly symbolic, as far as I can
see. Is it more useful than limiting to have such a barrier ?

-Andreas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20161011/2fd5e64c/attachment.html>