[x3d-public] X3D minutes 22 JAN 2021: specification editors review/commits

[John Carlson]

I don’t know if renumbering is a good idea, it would mess up web searches?

John

On Mon, Jan 25, 2021 at 2:35 PM Don Brutzman <brutzman at nps.edu> wrote:

> Specification editors met today, reviewed next steps, and made some of the
> changes.
>
> a. Confirmed key items and path forward:
>
> On 1/24/2021 10:33 AM, Don Brutzman wrote:
> > [...]
> > Editors Mantis and specification source updates continue.  This takes
> time.  Scrutiny on mailing list and Mantis is appreciated.
> >
> > [1.0]    Mantis Issue Tracker
> >           https://www.web3d.org/member-only/mantis/view_all_bug_page.php
> >
> > Key items to finish include the following.
> >
> > a. Khronos feedback on alphaChannel and Image Based Lighting (IBL) aka
> X3D EnvironmentLight,
> > b. FontStyle/ScreenFontStyle fields accessType inputOutput,
> > c. Geometry 'solid' field as accessType inputOutput for animation
> capability,
> > d. Andreas Plesch feedback on X3D-HTML Guidelines.
>
> b. Confirmed path forward on comments by Khronos for alphaChannel
> (Michalis now writing) and EnvironmentLight (deferred until spring).
>
> c. Confirmed procedures for future work.
>
> d. Applied all changes to FontStyle/ScreenFontStyle for accessType
> inputOutput on all fields.
>
> e. Added following prose to X3D-HTML Guidelines:
>
> "The CSS style attribute is not used to override the
> FontStyle/ScreenFontStyle style field, which is reserved for native X3D
> style definitions. Instead the parent Text node's CSS style attribute can
> be used to override FontStyle/ScreenFontStyle styling, if appropriate and
> supported."
>
> f. Agreed to change 'solid' field to accessType inputOutput throughout.
> Don to followup with specification changes.
>
> I will also apply inputOutput changes to X3D Tooltips, X3DUOM and related
> codebases (Java, Python, Turtle).
>
> [...]
> >>> b. Open issue: whether to include X3DUOM as an informative reference.
> More discussion to follow.
> >>>
> >>> [3.3]    X3D Unified Object Model (X3DUOM)
> >>>          https://www.web3d.org/specifications/X3DUOM.html
> >> Am thinking that this might best go in [3.2] X3D Abstract : Scene
> Access Interface (SAI) itself.  Might fit as an informative annex.
> >>
> >> Reactions welcome.  Dick and I will look at this further.
>
> g. Discussed X3DUOM at some length.
>
> - Noted it is essential to getting JSON, Turtle, Java, Python, C/C++/C#
> correct and consistent.
> - Dick thinks this belongs  in 19775-1 X3D4 Architecture, might be added
> later (with EnvironmentLight),
> - Don thinks might also fit in 19775-2 X3D4 Scene Access Interface (SAI)
> (perhaps for initial review),
> - No one wants to delay imminent completion and submission of 19775-1 X3D4
> Architecture to ISO.
>
> >>> Something to think about: sorting numerically in priority order
> ECMAScript, Java (as is), then python, C#, C++, C
> >> Absent objections, am ready to renumber the proposed
> programming-language bindings in order of specification maturity.
> >>[,,,]
> > 19776-1 XML
> > 19776-2 ClassicVRML
> > 19776-3 Compressed Binary Encoding
> > 19776-4 Efficient Binary Encoding (new)
> > 19776-5 JSON Encoding             (new)
> > 19776-6 Turtle/RDF/OWL Encoding   (new)
> >
> > 19777-1 ECMAScript
> > 19777-2 Java
> > 19777-3 Python (new)
> > 19777-4 C#     (new)
> > 19777-5 C++    (new)
> > 19777-6 C      (needed?)
> >
> > Absent any further suggestions, will update our diagram.
> >
> > [8.2]    X3D Graphics Standards Relationships
> >
> https://www.web3d.org/specifications/X3dSpecificationRelationships.png
>
> h. Dick noted long trail of ISO paperwork already in place with prior
> numbering, and that the existing numbering scheme doesn't affect
> priority/sequencing.
>
> Will keep current numbering scheme (not the same as that above) and have
> revision for next week.
>
> 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
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20210125/cd2b4874/attachment-0001.html>