[x3d-public] [x3d] Minutes of Schema/DTD Review meeting 20th July 2015

Tue Jul 21 09:59:25 PDT 2015

Don,

Thanks for the additional comments. That is good amplification.

With respect to the HAnimJoint Mantis issues: Yes, there are three Mantis
issues that might affect the child content model (listed first below). There
are also a further two concerned with non-node fields (listed last).

Details:

Issue 646 (http://www.web3d.org/member-only/mantis/view.php?id=646) HAnim
parenting changes
Issue 647 (http://www.web3d.org/member-only/mantis/view.php?id=647) 26.3.3 -
Geometry Question
Issue 655 (http://www.web3d.org/member-only/mantis/view.php?id=655) 26.3.3 -
Incompatible Signature and Text
Issue 774 (http://www.web3d.org/member-only/mantis/view.php?id=774) 26.3.3
HAnimJoint - llimit/ulimit type values incorrect
Issue 775 (http://www.web3d.org/member-only/mantis/view.php?id=775) 26.3.3
HAnimJoint - stiffness type value incorrect

We decided not to pursue the Mantis issues during the meeting.

Roy

-----Original Message-----
From: Don Brutzman [mailto:brutzman at nps.edu] 
Sent: 21 July 2015 07:20
To: Roy Walmsley; x3d at web3d.org; X3D Graphics public mailing list
Subject: Re: [x3d] Minutes of Schema/DTD Review meeting 20th July 2015

[cc: x3d-public]

Thanks for the excellent minutes Roy.  Here are a few extra points of
interest from our discussion.

On 7/20/2015 11:27 AM, Roy Walmsley wrote:
> Minutes of X3D Schema and DTD Review, Refactoring meeting held 20^th July
2015 at 0800 PDT (1500 UTC).
>
> Attendees: Don Brutzman, Roy Walmsley
>
> 1. _Adding a Filter capability X3DNodeInventoryComparison.xslx_
>
> Roy explained the process of using of setting up and using a filter in the
X3DNodeInventoryComparison Excel spread sheet.

Updated spreadsheet attached.  This and other changes will get published to
web3d.org when the SourceForge recovery is complete, so that we retain full
visibility into all changes at each step.

Coolness: for the X3DOM v1.7 filter, deselect "* not yet implemented" and
you can see all nodes that are suggested so far for an X3D 4.0 HTML Profile.

> _2. Specification comment 516 - 18.4.9 TextureProperties - Inconsistent
hierarchy_
>
> http://web3d.org/mailman/private/x3d_web3d.org/2015-March/002657.html
>
> It was agreed that the TextureProperties node should inherit directly from
X3DNode. The Schema (versions 3.2 and 3.3) were modified to change the
derivation extension from X3DAppearanceChildNode to X3DNode.

This improves the abstract hierarchy, and any autogenerated APIs, but has no
effect on the node field signature or any .x3d scene files.

> _3. Specification comment 521 - HAnimJoint - Inconsistent hierarchy_
>
> http://web3d.org/mailman/private/x3d_web3d.org/2015-March/002662.html
>
> It was agreed that the Schema derivation should not be changed, but that
the comment explaining the difference would be expanded. A more extensive
comment was added to all Schema versions.
>
> It was noted that the child content model was incorrect, as it was missing
the HAnimSite and HAnimDiplacer nodes. This was found to be the case in both
the Schema and the DTD. The missing nodes were added to all versions of the
Schema and the DTD.

This addition to the HAnimJoint content model will likely help H-Anim group
in future models.  Apparently the omission was not a blocker for any of the
current H-Anim example models.

(Just realized something, likely you mentioned this and I misunderstood:
were there any other related Mantis issues regarding HAnimJoint content
model?  Is so let's review to double check.)

> _4. Specification comment 522 - NurbsTextureCoordinate - Inconsistent
hierarchy_
>
> http://web3d.org/mailman/private/x3d_web3d.org/2015-March/002664.html
>
> It was agreed that the Schema should be modified so that the
NurbsTextureCoordinate node was directly derived from X3DNode. All versions
of the Schema were updated. On checking the DTD it was noted that this node
incorrectly appeared in the group TexureCoordinateNodes. It was agreed,
after verifying that it did not impact on Profile content or child model
content of NurbsPatchSurface or NurbsTrimmedSurface, that it should be
removed from the group. This change was made in all versions of the Schema.

This correction also prevents inadvertent application of
NurbsTextureCoordinate outside of a NURBS context, where a TextureCoordinate
or a TextureCoordinateGenerator belongs instead.

> _5. Publication of Schema/DTD changes_
>
> Since the SourceForge website is currently down for technical reasons
publication of the above changes would be delayed until the SourceForge site
is restored.

Status: recovery in progress, our subversion archive maybe back up late in
the week.

	https://twitter.com/sfnet_ops

http://sourceforge.net/blog/sourceforge-infrastructure-and-service-restorati
on/

> _6. Andreas Plesch TextureCoordinateGenerator comment_
>
> http://web3d.org/pipermail/x3d-public_web3d.org/2015-July/003487.html
>
> It was agreed that this comment would be handled by creating a Mantis
issue directly and sending an acknowledgement to Andreas.

plus our comments while viewing the examples Andreas provides:  wow, great
idea, very cool!   8)

For everyone's convenience, links from his message follow.  Recommended
viewing.

http://andreasplesch.github.io/x3dom/GeoElevationGrid_texture/terrain_height
.xhtml

http://andreasplesch.github.io/x3dom/GeoElevationGrid_texture/puddle_slope.x
html

http://andreasplesch.github.io/x3dom/GeoElevationGrid_texture/face_slope.xht
ml

Am hoping the Geospatial working group can take on examination of the
proposed changes.

We also looked at how the TextureCoordinateGenerator (used in these
examples) ought to be permitted by Schema and DTD as an alternative to
NurbsTextureCoordinate node, thus applicable for NURBS nodes as well.

> _7. Specification comment workflow_
>
> Following recent discussions on this topic it was agreed that Roy would
create a member-only wiki page on this topic, and add all comments to date.
A blank page was created.
>
> http://www.web3d.org/member/wiki/specification-comments-workflow
>
> A link to this page is still required. Roy will add some initial content
to this page, based on all comments already received.
>
> In addition it was suggested that making a summary monthly report for
presentation to the X3D WG would be very useful additional step in the
workflow.
>
> Meeting closed 1005 PDT (1705 UTC).
>
> Roy

Agenda from your issue-log spreadsheet:

============================================================================
========================
Spec comment-form number, x3d at web3d.org email number, etc.

528	002670	3/17/2015			19775-1	29.3.1 X3DScriptNode
Inconsistent hierarchy			Schema Outstanding
Partially fixed in Schema
529	002671	3/17/2015			19775-1	29.4.1 Script
Inconsistent hierarchy			Schema Outstanding		See
also comment 2670
530	002672	3/17/2015			19775-1	30.4.3
BooleanTrigger	Inconsistent hierarchy			Schema Outstanding
531	002673	3/17/2015			19775-1	30.4.6
IntegerTrigger	Inconsistent hierarchy			Schema Outstanding
532	002674	3/17/2015			19775-1	30.4.7 TimeTrigger
Inconsistent hierarchy			Schema Outstanding
541	002695	3/19/2015			19775-1	24.3.2 X3DFogObject
Inconsistent hierarchy			Schema Outstanding

http://web3d.org/mailman/private/x3d_web3d.org/
============================================================================
========================

Again thanks for an excellent meeting, "thank goodness it's Monday!"  BCNU
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