[x3d-public] Volume rendering spec.

[Roy Walmsley]

Hi Andreas,

 

I have checked and can tell you that this issue has already been noted. For reference it is Mantis issue 916. This comment was:

 

-------------------------------------

 

Subject: misnamed nodes and incorrect field in support table

1. "X3DVolumeNode" needs to corrected as "X3DVolumeDataNode"

2. "CompositeVolumeStyle" (entry in level 3) needs to corrected as "ComposedVolumeStyle".

3. ComposedVolumeStyle entry at level 3 indicates: "ordered field is always treated as FALSE. All other fields fully supported."

However there is no "ordered" field, and so this line should be rewritten as "All fields fully supported."

 

-------------------------------------

 

All three of the points noted will be corrected as submitted.

 

There are no current plans to introduce an ‘ordered’ field. If you think that is desirable, then it would be appropriate to raise a specification comment.

 

All the best,

 

Roy

 

From: x3d-public [mailto:x3d-public-bounces at web3d.org] On Behalf Of Andreas Plesch
Sent: 10 January 2018 18:01
To: X3D Graphics public mailing list <x3d-public at web3d.org>
Subject: [x3d-public] Volume rendering spec.

 

Before I submit a spec. comment I would like to explore if there are more appropriate resolutions to the following issues:

 

Table 41.7 ( http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/volume.html#t-supportlevels ) lists CompositeVolumeStyle in level 3. However, a style with this name is not defined in the Volume Rendering component. There is a ComposedVolumeStyle but this style is a level 2 style in the table.

 

A proposed resolution is to remove the row which lists CompositeVolumeStyle from Table 41.7


Table 41.7 refers to an ordered field in the support column for ComposedVolumeStyle. However, the node signature at section 41.4.4 ( http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/volume.html#ComposedVolumeStyle ) does not have an ordered field.

 

A proposed resolution is to replace the comment in the support column for ComposedVolumeStyle with 'All fields fully supported'.

 

Alternatively, it is possible that there used to be an ordered field and that it should be reintroduced. Then level 3 would support this field.

 

Andreas

 

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