[x3d-public] X3D meeting minutes, Friday 30 AUG 2018: X3D Specification Relationships diagram, ISO spec version numbers

[Richard F. Puk]

Hi, Don --

I will do it. It is easy. Simply go to "www.iso.org" and search using the number of the standard.

  -- Dick

/******************************************
| Richard F. Puk, Ph.D., President
| Intelligraphics Incorporated
| 7644 Cortina Court
| Carlsbad, CA  92009-8206
| Tel: +1-760-753-9027  Mobile:  +1-760-809-9027
| Email:  puk at igraphics.com
\****************************************** 



-----Original Message-----
From: Don Brutzman [mailto:brutzman at nps.edu] 
Sent: Saturday, September 1, 2018 6:38 AM
To: Richard F. Puk
Cc: X3D Graphics Working Group; X3D Graphics public mailing list
Subject: Re: X3D meeting minutes, Friday 30 AUG 2018: X3D Specification Relationships diagram, ISO spec version numbers

Dick, when convenient can you also check version numbers and dates of the other ISO specifications?

If you might also tell us how you did that, it will be helpful for everyone to know.  Thanks!

On 8/31/2018 9:56 AM, Don Brutzman wrote:
> 1. X3D Specification Relationships diagram update.
> 
> Nontrivial refactoring proposed for X3D v4, all feedback and discussion welcome.
> 
>      [x3d-public] X3D Working Group meeting minutes, 24 August 2018: improved specification relationships diagram
> http://web3d.org/pipermail/x3d-public_web3d.org/2018-August/009366.html
> 
> http://www.web3d.org/specifications/X3dSpecificationRelationships.draft.png
> 
> Comments and improvements:
> a. As reviews continue, we don't foresee any major changes/corrigenda to existing v3.3 file encodings and language bindings.
> b. We do foresee updating all of the file encodings and language bindings following X3D v4.0 and v4.1.
> c. Better references to medical metadata/content and highlighting relationships with DICOM, HL7.
> d. Discussed possible inclusion of joint collaboration work with SC4 on STEP/CAD visualization for top row... maybe someday.
> e.ISO/IEC NP TR 24772-4 "Guidance to Avoid Vulnerabilities in Programming Languages - Part 4, Python" may help us someday
> f. JavaScript is revving fast (v9 now), we will stick with ISO/IEC 22275 ECMAScript and JSON rather than ECMA.
> g. Java is revving every 6 months (now at v10, we are testing v8) with 6-month revision cycle.  No ISO activity on Java noted.
> h. Note that EXI efficiencies for compaction and performance can also be applied to JSON.  Recently approved as W3C Working Group Note:
> 
>      EXI for JSON (EXI4JSON)
>      Daniel Peintner, Siemens AG and Don Brutzman, Web3D Consortium
> https://www.w3.org/TR/exi-for-json
> 
> Updated X3D Specification Relationships diagram attached, will continue to refresh url above as needed.  No outstanding deficiencies noted.
> 
> Looks like we are going in the right direction, and getting "real close now"... Comments welcome, we will review again during next call. Once this round of review is finished, we will publish and announce.


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