[x3d-public] X3D working group minutes 14 June 2019: volume component additions

Fri Jun 14 09:15:33 PDT 2019

0. *Attendees*  Ander Arbelaiz, Jakub Flotynsky, Anita Havele, Vince Marchetti, Dick Puk, and Don Brutzman.

Confirmed: all information in these weekly minutes is releasable publicly.

Members and invited experts are welcome.  We are an open organization. Please let us know if you have an important topic to present or discuss.

The X3D Graphics Working Group addresses all X3D specification issues and coordinates the technical development of future improvements.
	http://www.web3d.org/working-groups/x3d

Each week we report out both public and member-only information - membership has value.  To become a Web3D Consortium member:
	Join the Web3D Consortium
	http://www.web3d.org/join

==================================

1. Teleconference update

We have switched to Zoom channel, to good effect.  It allows use of internet audio, screen sharing and chat with links.

We meet regularly on Fridays 0800-0930 pacific.  To join the teleconference:
	Web3D Teleconference
	http://www.web3d.org/member/teleconference-information

* Friday          08-1000 pacific, Join URL https://zoom.us/j/148206572 for X3D Working Group

One tap mobile
* US (New York) +19292056099,,148206572 #
* US (San Jose) +16699006833,,148206572 #

Dial by your location, using (nine-digit number from Join URL above)

* US (New York) +1 929 205 6099
* US (San Jose) +1 669 900 6833

Please note that these numbers for working group calls each week should be stable, allowing you to set up shortcuts.

We discussed whether to set up Outlook appointments for these?  Vince thinks that ongoing reminders might be possible for Zoom - we will consider including the working-group email addresses as subscribers.

----

Members and invited experts are welcome.  We are an open organization. Please let us know if you have an important topic to present or discuss.

The X3D Graphics Working Group addresses all X3D specification issues and coordinates the technical development of future improvements.
	http://www.web3d.org/working-groups/x3d

Each week we report out both public and member-only information - membership has value.  To become a Web3D Consortium member:
	Join the Web3D Consortium
	http://www.web3d.org/join

==================================

2. *Prior meeting minutes*

	[x3d-public] X3D working group minutes 7 June 2019: tracking implementation support
	http://web3d.org/pipermail/x3d-public_web3d.org/2019-June/010935.html

==================================

3. AccessProblem:  website does not seem to be returning DTDs and extensions properly, am getting all manner of tool errors related to

	http://www.web3d.org/specifications/x3d-3.3.dtd
	http://www.web3d.org/specifications/x3d-3.3-Web3dExtensionsPublic.dtd

Are others also seeing errors when running tools?  Might recent website changes be related?

On 6/14/2019 7:32 AM, vmarchetti at kshell.com wrote:
> Just checked using the 'curl' tool.
> An HTTP request to http://www.web3d.org/specifications/x3d-3.3.dtd is returning an HTTP status code of 302
> and an additional header with the new location https://www.web3d.org/specifications/x3d-3.3.dtd . This is part of
> the procedure for converting the website to https service. Browsers will automatically redirect, the tools do not.
> 
> Action Item for VM: Contact the webmaster about maintaining an exception for the DTD and schema documents (.xsd) files,
> to serve as http protocol with redirection.

This makes good sense - all of our DTDs and Schemas are both URL literals and URI identifiers, so they need to resolve consistently, without redirection from http to https.  Specific failure mode now is that the x3d-3.3.dtd is not redirecting to the required extension file, x3d-3.3-Web3dExtensionsPublic.dtd

Probably most reliable is to exempt everything, or else just *.xsd *.dtd *.json files in

	https://www.web3d.org/specifications/

/Very important/ since this has the potential break the ability of any X3D scene to get used or rendered.  This is a blocker for most all development, and side-effect responses are quite confusing, so is a priority.  We will report on the public mailing list when capability is restored.

Vince chat on invocation:  the following puts the headers in hdr.txt; the body in res.txt.  Example output follows.

	curl -D hdr.txt {url} > res.txt

$ cat header.txt
HTTP/1.1 200 OK
Date: Fri, 14 Jun 2019 15:25:38 GMT
Server: Apache
Last-Modified: Fri, 07 Jun 2019 19:06:48 GMT
Accept-Ranges: bytes
Content-Length: 142537
Content-Type: application/xml-dtd

Don will add a number of these invocations in the build scripts so that our build logs keeps track of such important information.

==================================

4. New volume rendering extension proposals

Ander Arbelaiz Vicomtech (presenting) and Nicholas Polys VT

	New volume rendering extension proposals
	http://web3d.org/pipermail/x3d-public_web3d.org/2019-June/010968.html

Provided assets include slideset,

X3DOM is primary implementation, and it is distributed in developers branch.

Ander showed us an excellent demo with three orthogonal cross-section planes, plus an adjustment for an oblique plane.

* MPRVolumeStyle node:  https://sunrise-lunge.glitch.me
* allowViewPointInside: https://mountain-verse.glitch.me

The allowViewpointInside field is interesting, it helps the author control navigation of users since internal views might be nonsensical or sensitive.  Computational performance is also a factor.

Ander confirmed these extensions are compatible and integrated with existing Volume Rendering component.  As confirmed last January, they are offered without restrictions in accordance with the Web3D Intellectual Property Rights (IPR) policy for royalty-free use.

Either the above examples or other examples will be provided for the Web3D Examples Archives.

	http://www.web3d.org/x3d/content/examples/Basic/VolumeRendering

We discussed whether maturity is now sufficient for inclusion in the draft X3Dv4 specification.  ImageTextureAtlas certainly seems ready, since several years of experience are available.  The additional work is impressive.

TODO: we would like to see more regarding comparison with the DICOM specification for MPR.  One difference is that DICOM addresses non-planar renderings (such as cross sections for blood vessels).

Anita requests that we announce this important progress for X3Dv4 at Web3D 2019 and SIGGRAPH 2019.  News item, tweet, etc. Ander will work together with us to announce.

==================================

5. Following some website adjustments, again updating status to track progress of implementation support for draft X3Dv4 specification.

	http://www.web3d.org/x3dv4-implementations

Next revision will finally organize all of the programming-language updates found in last week's minutes.

==================================

6. Updates requested, status online: draft revision to X3D Node and Statement Inventory Comparison.

	http://www.web3d.org/specifications/X3dNodeInventoryComparison.xlsx
	http://www.web3d.org/specifications/X3dNodeInventoryComparison.pdf

We will add today's new nodes to the spreadsheet.

==================================

7. Next week we will discuss preparations and schedule for Web3D 2019 and SIGGRAPH 2019.  A second technical topic is also welcome.

Information inputs are always welcome.  With much X3D activity occurring there is typically plenty to review each week, ensuring that our progress continues to be clearly recorded and communicated.

Thanks Ander and your colleagues for great work.

Having fun with X3Dv4!  8)

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