<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:2062054303;
mso-list-type:hybrid;
mso-list-template-ids:-620052780 -1 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0D8;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>Nevertheless we might alternatively specify a unique, non-progressive approach:<o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>1' Skeleton</li></ul><p class=MsoListParagraph><o:p> </o:p></p><p class=MsoNormal>With 1 you can do any animation, either with or without “Motion” with geometries as children of Segment(s). Everything is ‘standard’ x3d hierarchy. <o:p></o:p></p><p class=MsoListParagraph><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>2' Skeleton + skin<o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Adding skin makes processing more complicated, but it is just the capability to use a single geometry for surface and also individual geometries as children of Segment(s). Really nothing to do with “Motion” of part 2 unless the author also wants to use the part 2 “Motion” stuff. </p><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>3' Skeleton + motion<o:p></o:p></li></ul><p class=MsoListParagraph><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>4' Skeleton + skin + motion</li></ul><p class=MsoListParagraph><o:p> </o:p></p><p class=MsoNormal>Maybe a level 3 for the Part 2 Motion additions. </p><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>We reviewed different levels possible. Current draft:<o:p></o:p></li></ul><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> 1. Skeleton<o:p></o:p></p><p class=MsoNormal>> 2. Skeleton + skin<o:p></o:p></p><p class=MsoNormal>> 3. Skeleton + skin + motion</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I think best as Level 3 adds “Motion”.. Otherwise hear from implementers.</p><p class=MsoNormal>Since skin is harder for browser than “Motion” we might see 1 and 3 from a browser that does not want to do skin but can do “Motion”. In all cases, the animation interfaces are the joints.</p><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>This deserves further scrutiny by HAnim group. </li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I think part 2 should be distinct added feature. An instance might be Octaga that as far as I inow has not done skin but can easily do motion.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>All Best, </p><p class=MsoNormal>Joe</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:brutzman@nps.edu">Don Brutzman</a><br><b>Sent: </b>Wednesday, June 6, 2018 9:26 AM<br><b>To: </b><a href="mailto:x3d@web3d.org">X3D Graphics Working Group</a><br><b>Cc: </b><a href="mailto:h-anim@web3d.org">Humanoid Animation (H-Anim) Working Group</a>; <a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>[x3d-public] X3D teleconference 5 JUN 2018 minutes: HAnim DIS,X3D Regex, Web3D 2018 and X3Dv4</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Attendees: Anita Havele, Vince Marchetti, Dick Puk, Don Brutzman. Elapsed time 70 minutes - rapid transit!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1. All Web3D members and prospective members are invited to join us this week as we look over lots of progress prior to the annual conference.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> Web3D Teleconference Information</p><p class=MsoNormal> http://www.web3d.org/member/teleconference-information</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>=====================================</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>2. X3D Eye Candy of the Week, from Virginia Tech (VT):</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> Environmental Design & New Media: Wing It</p><p class=MsoNormal> https://vimeo.com/261182193</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>=====================================</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>3. Humanoid Animation (HAnim) Draft International Standard (DIS) submitted to ISO.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>- Volume I, Architecture (extends existing Humanoid)</p><p class=MsoNormal>- Volume II, Motion Data Animation (adds Motion object, BVH-related mocap support)</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> [h-anim] X3D v4.0 component for Humanoid Animation (HAnim), Don Brutzman email 4 June 2018</p><p class=MsoNormal> http://web3d.org/mailman/private/h-anim_web3d.org/2018-June/001640.html</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We discussed renaming of the github archive from "DIS prep" to "DIS". The two specs are now forwarded by SC24 and registered with JTC 1.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Go-forward plan is to copy over the "DIS Prep" (thus freezing it) as "IS Prep" in github. Will discuss at HAnim teleconference 13 June prior to execution.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We reviewed different levels possible. Current draft:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1. Skeleton</p><p class=MsoNormal>2. Skeleton + skin</p><p class=MsoNormal>3. Skeleton + skin + motion</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Nevertheless we might alternatively specify a unique, non-progressive approach:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1' Skeleton</p><p class=MsoNormal>2' Skeleton + skin</p><p class=MsoNormal>3' Skeleton + motion</p><p class=MsoNormal>4' Skeleton + skin + motion</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This deserves further scrutiny by HAnim group.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Still awaiting public deployment of DIS specification via Web3D website.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> All H-Anim Standards</p><p class=MsoNormal> http://www.web3d.org/standards/h-anim</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Next steps: further implementation/examples/evaluation will be ongoing.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We will soon be announcing this accomplishment and supporting assets publicly.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Related opportunities emerging:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> https://twitter.com/Web3DConsortium/status/1004020658982944768</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> Press release: HL7 International @HL7 and Web3D Consortium Formalize Agreement to</p><p class=MsoNormal> Incorporate #X3D Presentation into Electronic Health Record (EHR) Applications,</p><p class=MsoNormal> signing a Statement of Understanding to cooperatively advance their standards.</p><p class=MsoNormal> http://www.web3d.org/news-story/hl7-international-and-web3d-consortium-formalize-agreement-incorporate-3d-presentation</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>=====================================</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>4. Recent dialog/diagnosis of mysterious validation errors.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Email thread starting last week, special thanks to Frederic Vogt:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> [x3d-public] Unexpected behaviour of X3D Validator; X3D regular expressions (regexes)</p><p class=MsoNormal> http://web3d.org/pipermail/x3d-public_web3d.org/2018-June/008911.html</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> X3D Validator</p><p class=MsoNormal> https://savage.nps.edu/X3dValidator</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Major refresh:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> X3D Regular Expressions (regexes)</p><p class=MsoNormal> http://www.web3d.org/specifications/X3dRegularExpressions.html</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Vince reports that MFInt32 problem stack-overflow error still remains when running X3D Schematron locally. He will post the abridged example that is still failing, hopefully that will help our test efforts.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>MFInt32 regex pattern:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> ((\+|\-)?(0|[1-9][0-9]*)?( )?(,)?( )?)*</p><p class=MsoNormal> http://www.web3d.org/specifications/X3dRegularExpressions.html#MFInt32 </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We reviewed the following but didn't see the anti-patterns it refers to:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> Runaway Regular Expressions: Catastrophic Backtracking</p><p class=MsoNormal> https://www.regular-expressions.info/catastrophic.html</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If this testing isolates any unfixable regex vulnerabilities, we should add them to the X3D Resources: Security considerations.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Several more regexes are still needed: SFImage notably. Anyone feeling creative?!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Don is looking at</p><p class=MsoNormal>a. adding regex checking in X3DJSAIL</p><p class=MsoNormal>b. adding context-sensitive links to an online regex checker (if the pattern can be passed as a url parameter)</p><p class=MsoNormal>c. scratch-pad file includes a bounding-box regex, will add that in an "extras" table of some sort.</p><p class=MsoNormal>d. whether DoctypeChecker.java warning can be more explicit when a Byte Order Mark (BOM) is detected as start of file.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>=====================================</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>5. Upcoming work on X3D v4. We will list participation activities that are accessible for consortium and community engagement.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> X3D Version 4</p><p class=MsoNormal> http://www.web3d.org/x3d4</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>- First component complete: HAnim update</p><p class=MsoNormal>- Next component: Projective Texture Mapping (PTM)</p><p class=MsoNormal>- Advanced graphics and compression with glTF</p><p class=MsoNormal>- VR/AR/MAR and WebVR are X3D v4.1, proceeding in parallel to quickly follow X3D v4.0</p><p class=MsoNormal>- many more items, let's highlight what is actionable right now</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>These will be covered at the imminent events of the year, in Poznan Poland:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> VR Hackathon, 17-19 June 2018</p><p class=MsoNormal> http://vrhackathon.web3d.org/poznan-2018-06</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> Web3D 2018 Conference, 20-22 June 2018</p><p class=MsoNormal> https://web3d2018.web3d.org</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> Web3D Workshop on X3D Futures: Adoption of HTML5 & VR/AR on the Web</p><p class=MsoNormal> Presenters: Anita Havele and Don Brutzman</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Member folder:</p><p class=MsoNormal>https://docs.google.com/document/d/1f3a7zo_R4r_6tpPlxJOlbjaZr679tOQOswZDMHq6wt8</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Vince will produce a 1-line summary for the website.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Workshop description:</p><p class=MsoNormal>=====================================</p><p class=MsoNormal>This workshop will discuss many opportunities for involvement. Following the path projected by Web3D 2017's Future of X3D session, multiple Web3D Consortium working groups and community participants continue to build on the architectural stability of the Extensible 3D (X3D) Graphics International Standard. Two open-source implementations currently adapt X3D content for HTML5 integration, with excellent results showing compatible event models for user interaction and model animation. Virtual, Augmented and Mixed Reality (VR/AR/MR), 3D Printing and 3D Scanning are all using X3D on the Web and being explored to good effect. Central to these explorations is an X3D Unified Object Model (X3DUOM) that enables consistent implementation and presentation of content across multiple file encodings (XML, ClassicVRML, JSON, binary) as well as multiple programming language bindings (JavaScript, Java and planned adaptations to C/C++/C# and Python). Second-generation Humanoid Animation (HAnim) is stabilizing motion-capture (mocap) outputs for both general-purpose and human-specific (i.e. medical) usage. Over two decades of progress are steadily evolving to unlock the promise of 3D Graphics within the Web architecture. Quality assurance, validation tools, import/export support, forwards/backwards compatibility,and a large corpus of open-source examples are together ensuring that consistent semantics are emerging for 3D on any platform. This progress report outlines numerous parallel lines of effort and points out individual opportunities to utilize and extend X3D consistently across multiple domains.</p><p class=MsoNormal>=====================================</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>All feedback welcome. Have fun with X3D! 8)</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>all the best, Don</p><p class=MsoNormal>-- </p><p class=MsoNormal>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu</p><p class=MsoNormal>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</p><p class=MsoNormal>X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>x3d-public mailing list</p><p class=MsoNormal>x3d-public@web3d.org</p><p class=MsoNormal>http://web3d.org/mailman/listinfo/x3d-public_web3d.org</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>