[x3d-public] X3D XML Encoding: example models for Inline EXPORT/IMPORT
Brutzman, Donald (Don) (CIV)
brutzman at nps.edu
Sat Jun 29 16:51:22 PDT 2024
Here is a broader explanation of these important example test scenes, excerpted for minutes of recent ISO standardization meeting including HAnim and X3D. Please note attachment of diagram illustrating the design pattern used in this scene. As ever, questions and potential improvements welcome.
*
https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineImportInlineExportAnimation.png
[cid:c6449ae9-360d-44bd-99a0-9cf12a441dd7]
X3D Scalable Extensibility using Inline EXPORT/ IMPORT Capabilities
The following example is used as part of the X3D Architecture specification.
* X3D encodings, ISO/IEC 19776-1.4, Part 1: XML encoding, clause 4.3.12 IMPORT/EXPORT stathttps://web3d.org/specifications/X3Dv4Draft/ISO-IEC19776-1v4.0-WD1/Part01/concepts.html#IMPORT_EXPORTStatementSyntaxement syntax
This example provides a demonstration of interest showing scalable extensibility of large-scale worlds through Inline loading. It also permits sharing if events between parent and child X3D models through use of the EXPORT and IMPORT statements.
* X3D Example Archives: Basic, X3D Specifications, Inline Export
*
X3D encodings example: demonstrate reuse and adaptation of content instances through Inline IMPORT, EXPORT statements. This scene is simple static geometry.
*
https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineExportIndex.html
[cid:197ec097-760c-4c37-adf8-e705092f5efa]
* X3D Example Archives: Basic, X3D Specifications, Inline Import
* X3D encodings example: demonstrate reuse and adaptation of content instances through Inline IMPORT, EXPORT statements. Essentially this second scene can “reach in” and modify a select part of the first scene. This is an important feature for scalable extensibility.
*
https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineImportIndex.html
[cid:14087a45-b229-481e-867f-e33f50c71652]
As with all Web3D archived examples, direct viewing and editing of these paired scenes is available online. Respective X_ITE and X3DOM links for viewing and editing follow.
*
https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineImportX_ITE.html
*
https://create3000.github.io/x_ite/playground/?url=https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineImport.x3d
*
https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineImportX3dom.xhtml
*
https://andreasplesch.github.io/Library/Viewer/index.html?url=https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineImport.x3d
Have fun with scalable, extensible X3D! 😎
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 https://faculty.nps.edu/brutzman
________________________________
From: Brutzman, Donald (Don) (CIV)
Sent: Saturday, June 01, 2024 10:42 AM
To: X3D Public Mailing List (x3d-public at web3d.org); x3d at web3d.org
Cc: puk at igraphics.com; Brutzman, Donald (Don) (CIV)
Subject: X3D XML Encoding: example models for Inline EXPORT/IMPORT
The X in X3D is Extensible. An important aspect of that is the ability of an X3D model to export a scene sub-graph node, for potential use by a parent model which can load and access it via Inline. The IMPORT/EXPORT statements support the Inline node to establish this capability. Events can then be ROUTEd to and fro between the parent model and the child Inline model.
Bottom line up front (BLUF): it works! Test screenshots for three players:
* https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineImportCastleModelViewer.png
* https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineImportX_ITE.png
* https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineImportX3DOM.png
Details follow. The X3D 4.0 Architecture specification defines this functionality:
* X3D Architecture version 4.0 ISO/IEC 19775-1, clause 4 Concepts, 4.4.6 Import/Export
* https://www.web3d.org/specifications/X3Dv4/ISO-IEC19775-1v4-IS/Part01/concepts.html#ImportExportsemantics
4.4.6 Import/Export semantics
The IMPORT feature allows authors to incorporate content defined within Inline nodes or created programmatically into the namespace of the containing file for the purposes of event routing. In contrast with external prototyping (see 4.4.5 External prototype semantics), which allows access to individual fields of nodes defined as prototypes in external files, IMPORT provides access to all the fields of an externally defined node with a single statement (see 9.2.5 IMPORT statement).
Importing nodes from an Inlined file is accomplished with two statements: IMPORT and EXPORT. The IMPORT statement is used in the containing file to define which nodes of an Inline are to be incorporated into the containing file's namespace. The EXPORT statement is used in the file being Inlined, to control access over which nodes within a file are visible to other files (see 9.2.6 EXPORT statement). EXPORT statements are not allowed in prototype declarations.
Continuing: Dick and I have been working on resolving all issues with the X3D XML Encoding revision to match X3D 4.0. Making good progress, documenting resolution of all issues in Mantis (as usual). We expect to submit this working draft to ISO in the coming weeks. As part of these efforts, we realized that the XML example for X3D Inline/EXPORT/IMPORT was not in our example archives. Implementing and evaluating further revealed an attribute error in the XML Encoding specification prose that implementers were able to figure out correctly.
* Mantis 697, 4.3.12 IMPORT/EXPORT statement syntax - Attribute inconsistency
* https://www.web3d.org/member-only/mantis/view.php?id=697
* X3D XML Encoding version 4.0, clause 4 Concepts, 4.3.12 IMPORT/EXPORT statement syntax
* https://web3d.org/specifications/X3Dv4Draft/ISO-IEC19776-1v4.0-WD1/Part01/concepts.html#IMPORT_EXPORTStatementSyntax
The following XML syntax applies to the IMPORT/EXPORT functionality of X3D.
An IMPORT statement consists of an IMPORT element followed by attributes inlineDEF, importedDEF, exportedDEF, and (optionally) AS.
An EXPORT statement consists of an EXPORT element followed by attributes localDEF and (optionally) AS.
EXAMPLE 15 2 The following depicts the XML encoding of an EXPORT statement within the inlined InlineExport.x3d model:
<!-- file InlineExport.x3d -->
<Transform DEF='T1'> <!-- contained 3D content --> </Transform>
<!-- Hint: EXPORT statement follows node of interest, since localDEF field is similar to USE with type IDREF -->
<EXPORT localDEF='T1' AS='RootTransform'/>
EXAMPLE 16 1 The following depicts the XML encoding of an IMPORT statement within a parent scene that corresponds to a separate Inline model:
<!-- file InlineImport.x3d -->
<Inline DEF='MyInlineModel' url='"InlineExport.x3d"' DEF='I1' url='"someUrl.x3d"'/>
<IMPORT
inlineDEF='MyInlineModel' inlineDEF='I1'
importedDEF='RootTransform' exportedDEF='RootTransform'
AS='MyInlineRootTransform' AS='I1Root'/>
<OrientationInterpolator DEF='MySpinner' key='0 0.3333 0.6667 1' keyValue='0 1 0 0, 0 1 0 2.094395, 0 1 0 4.18879, 0 1 0 0'/>
<ROUTE
fromNode='MySpinner' fromField='value_changed'
toNode='MyInlineRootTransform' toNode='I1Root' toField='set_rotation'/>
I’ve created and added a pair of scenes to the X3D Examples archives to demonstrate this functionality. Note that the child model has a Text description that remains stable, while the geometry can get animated by the parent model. These paired models conclusively demonstrate that everything is working satisfactorily.
* X3D Example Archives: Basic, X3D Specifications, Inline Export
* https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineExport.x3d
* https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineExportIndex.html
* X3D Example Archives: Basic, X3D Specifications, Inline Import
* https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineImport.x3d
* https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineImportIndex.html
* [cid:image001.png at 01DAB410.5BB66F10]
It was great to see this important functionality working in X3DOM, X_ITE, and Castle Model Viewer. Congratulations and thanks!!
Correct authoring support for Inline, EXPORT and IMPORT nodes is also supported in X3D-Edit.
* X3D-Edit is a free, open-source Extensible 3D (X3D) Graphics authoring tool for simple high-quality authoring, editing, import/export, validation and viewing of X3D scenes.
* https://savage.nps.edu/X3D-Edit
Have fun with X3D4 extensibility! 😊
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 https://faculty.nps.edu/brutzman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20240629/ebaded1d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 25818 bytes
Desc: image001.png
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20240629/ebaded1d/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 86402 bytes
Desc: image.png
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20240629/ebaded1d/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 114504 bytes
Desc: image.png
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20240629/ebaded1d/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 119162 bytes
Desc: image.png
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20240629/ebaded1d/attachment-0007.png>
More information about the x3d-public
mailing list