[x3d-public] [x3d] Spec Comment by brutzman on 19775-1: Abstract X3D Definitions - V3.3 [Mantis 1173]

Roy Walmsley roy.walmsley at ntlworld.com
Sat Sep 9 14:48:48 PDT 2017


Don,

Thank you for submitting the specification comment included below. I have raised Mantis issue 1173 to cover this. Web3D members can view this issue at http://www.web3d.org/member-only/mantis/view.php?id=1173.

All the best,

Roy

-----Original Message-----
From: x3d [mailto:x3d-bounces at web3d.org] On Behalf Of Spec Feedback
Sent: 09 September 2017 17:35
To: x3d at web3d.org
Subject: [x3d] Spec Comment by brutzman on 19775-1: Abstract X3D Definitions - V3.3

-- Submitter indicates that this comment may be public: *Yes* --

Comment on 19775-1: Abstract X3D Definitions - V3.3
3  Terms, definitions, acronyms, and abbreviations http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/glossary.html

-----------------
Subject: Abstract specification definitions of node and statement are insufficient.

Problem: the abstract specification does not provide clear definitions for nodes and statements, resulting in ambiguous distinctions throughout other sections.

The current definition for node is vague:
"3.1.47 node, fundamental component of a scene graph"

Suggested definition, improvements welcome:
"3.1.47 node, fundamental component of a scene graph that defines information regarding animation, display, geometry, graph structure, interaction, object metadata, or rendering.  Nodes are not statements.

No definition for statement is provided.  Suggested:
"3.1.70.5, statement, fundamental component of a scene graph that defines document information, version/profile/component support, routing, and other scene-related information.  Statements are not nodes.

Existing usage of note:
"3.1.87 X3D file, set of X3D nodes and statements as defined in this part of ISO/IEC 19775"

Further action needed: Core component defines multiple capabilities requiring X3D statement support.  Recommend that support for all X3D statements is included as a requirement in Core component, both in prose and in support table.  For example: "All X3D statements are defined as part of Core component level 1."

Table 7.2 — Core component support levels http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/core.html#t-Coresupportlevels
Can add similar table entry "All X3D statements are defined as part of Core component level 1."

Correction needed:
Figure 4.1 — X3D architecture
http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/concepts.html#f-X3DArchitecture
"The abstract structure of the sequence of statements that form an X3D world is specified in 7.2.5 Abstract X3D structure."
should be modified to read "sequence of nodes and statements that form an X3D world"

7.2.5 Abstract X3D structure
http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/core.html#AbstractX3DStructure
7.2.5.1 Organization
should similarly modify
"An X3D world is conceptually defined as a sequence of statements organized conceptually as a file."
to say "as a sequence of nodes and statements"

Needed:
"PROTO instances are nodes."

Suggested:
"Comments are neither nodes nor statements."

This section should also include a paragraph that lists X3D statements, such us "X3D statements include X3D, HEAD, PROFILE, COMPONENT, META, UNIT, Scene, ROUTE, PROTO declare, EXTERNPROTO delare, PROTO interface, PROTO body, field, fieldValue, IS, connect, IMPORT, EXPORT.
Syntax and explicit/implicit definition for these statements can vary among various encodings and language bindings."

Further review of the abstract specification is warranted to see if other clarifications and corrections are needed.

Of note is that clear distinction of nodes and statements is also necessary for proper specification of the X3D Unified Object Model.

These clarifications are not expected to break any existing X3D model content because the existing legacy specification makes no relevant restrictions on use of X3D statements.  Similarly, these clarifications do not require changes (but may inspire improvements) to existing X3D implementations.
-----------------

Submitted on Saturday, 2017,  September 9 - 9:35am by brutzman (brutzman )
IP: 205.155.65.226

See: http://www.web3d.org/node/1694/submission/1460


_______________________________________________
x3d mailing list
x3d at web3d.org
http://web3d.org/mailman/listinfo/x3d_web3d.org




More information about the x3d-public mailing list