[x3d-public] Inline, X3DUrlObject allowed to add additional filetypes, etc.

[John Carlson]

Should the Inline be checked statically or dynamically for recursion?  What if there’s a switch statement in the Inline which inlines the Inline some of the time?

Should we allow fractals/graftals?  https://www.youtube.com/watch?v=fXu74k-77kg  How does one propose doing it without Inlines?

Thanks,

John

Sent from Mail for Windows 10

From: Brutzman, Donald (Don) (CIV)
Sent: Wednesday, July 10, 2019 4:42 AM
To: Behr, Johannes
Cc: Sturm, Timo; X3D Graphics public mailing list; Vincent Marchetti
Subject: [x3d-public] Inline, X3DUrlObject allowed to add additional filetypes, etc.

[cc: X3D mailing list]

Thanks Johannes for an excellent specification recommendation.  This has been added as Mantis issue 1257.  Dick and I have agreed to include it and will review/refine prose together.  Changes checked into github.  Related changes and issues follow.

Am hoping we have integrated all known changes for X3DUrlObject and Inline.

Comments welcome for weekly working group review this coming Friday.  Status maintained at

	X3Dv4 Implementations Status
	http://www.web3d.org/x3dv4-implementations

----

* Inline allowed to load additional model types
   http://www.web3d.org/member-only/mantis/view.php?id=1257

"The run-time system can support any number of 3D model resource types as long as those follow the abstract model definition [RFC2077], provide a registered content type (e.g. model/x3d-xml, model/gltf-bin, model/stl, etc.), and can be determined with some form of content negotiation [RFC7231]. The run-time system must support at least one X3D type (e.g. model/x3d-xml) but can also support and negotiate any number of X3D encodings and (optionally) non-X3D representation formats."

----

* 9.3.2 X3DUrlObject - Incorrectly restricts to valid X3D files
   http://www.web3d.org/member-only/mantis/view.php?id=1171

"The results are undefined if the URL refers to a file that is not an X3D file, or if the X3D file contains an invalid scene."
to
"The results are undefined if the URL refers to a file that is not a supported file type, or if the file contains invalid content."

----

* 9.4.2 Inline - Security precaution
   http://www.web3d.org/member-only/mantis/view.php?id=744

"Security precaution: it is an error for a model to Inline itself, directly or indirectly, in order to avoid nonterminating recursion. X3D players SHALL NOT honor self-referential Inline loops in order to avoid security vulnerabilities."

----

* Inline - Inline is silent about head, component, unit, and meta statements
   http://www.web3d.org/member-only/mantis/view.php?id=1151

"NOTE  When Inline is used to load a child scene, processing of the Inline content is as specified in the respective PROFILE, COMPONENT, UNIT, IMPORT, and EXPORT statements."

----



On 7/9/2019 1:44 PM, Behr, Johannes wrote:
> Attached is a updated “Inline Section” to be more consistent with the new open definition of model links.
> 
> I would keep all change in the inline section. The X3DUrlObject definition is too ambiguous since it includes also non-Model-links like Audio and Video.
> 
> Best regards
> Johannes
> [...]


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
_______________________________________________
x3d-public mailing list
x3d-public at web3d.org
http://web3d.org/mailman/listinfo/x3d-public_web3d.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190710/408fe3fe/attachment.html>