<div><div dir="auto"><div><a href="https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/specifications/x3d-4.0-JSONSchema.json">https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/specifications/x3d-4.0-JSONSchema.json</a></div></div></div><div dir="auto"><br></div><div dir="auto">I’m pretty sure it was designed to handle existing geoSystem MFString, not create a new regex. But someone could have created a regex without me knowing. There could be parallel reasoning in the schema, as I believe I have enabled regex.</div><div dir="auto"><br></div><div dir="auto">I am thinking I should recheck the schemas, X3DUOM and standard.</div><div dir="auto"><br></div><div dir="auto">I’ve been on paddling in the rapids today, just decided to rest again.</div><div dir="auto"><br></div><div dir="auto">John</div><div dir="auto"><br></div><div dir="auto"><br></div><div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 19, 2020 at 5:05 PM GPU Group <<a href="mailto:gpugroup@gmail.com">gpugroup@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div dir="ltr"><div>Yes right John. Here's a sample of a few geosystems I have handy:</div>geoSystem='"GD" "R1000.0"'<br><div>geoSystem='"GD" "A1737400.0" "F0.0"'<br></div><div>geoSystem='"WM"'<br>geoSystem='"WE""GD"' <br>geoSystem='"GD" "WE" "latitude_first"'<br></div><div>Note they aren't in (key,value) or (fieldname,fieldvalue) pairs explicitly, although some of the SFStrings can be parsed into 2 parts, a key token and a number value. Others have implied keys - implied by the value of the string ie GD, WM, latitude_first</div><div>And geosystems have 1 to n parts</div><div>GC</div><div>GC + GD</div><div>GC + GD + mapping plane</div><div>GC + GD + mapping plane set + mapping plane set member</div><div>GC + GD + local system</div><div>GC + GD + mapping plane + local system</div><div>and a few more permutations. JSON can do key,value and do also hierarchies of key-values. That's why i was wondering if Walmsley had defined a JSON hierarchy to go in an SFString to replace the geoSystem MFString.</div><div>-Doug</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 19, 2020 at 3:28 PM John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div><br></div><div><div dir="auto">I am fairly sure the geoSystem is an MFString. </div><div dir="auto"><br></div><div dir="auto">Schema and examples are on sourceforge.</div><div dir="auto"><br></div><div dir="auto">John</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 19, 2020 at 9:10 AM GPU Group <<a href="mailto:gpugroup@gmail.com" target="_blank">gpugroup@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div dir="ltr">Q. what does Walmsley JSON look like for geoSystem? <div>Q. Did he use json in an SFString field for hierarchical key-values? </div><div>Thanks,</div><div>-Doug</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 18, 2020 at 8:55 PM John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div><div dir="auto">For 1302 geoSystem, I recommend looking at JSON schema as created by Roy Walmsley and copied into the automatically generated schemas wholesale.</div><div dir="auto"><br></div><div dir="auto">If we can convert JSON Schema to XMLSchema, that might be a good solution.</div><div dir="auto"><br></div><div dir="auto">Idk. Maybe try it on a small scale first.</div><div dir="auto"><br></div><div dir="auto">John</div></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 18, 2020 at 9:42 PM Don Brutzman <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">We meet at our regular time and Zoom coordinates, Friday 08-0930 pacific (your time zone may vary).<br>
<br>
---<br>
<br>
1. *Participation Information*<br>
<br>
[1] Web3D Teleconference Information<br>
<a href="https://www.web3d.org/member/teleconference-information" rel="noreferrer" target="_blank">https://www.web3d.org/member/teleconference-information</a><br>
<br>
Please use the following link for all Web3D Consortium Meetings.<br>
<br>
Join URL: <a href="https://us02web.zoom.us/j/81634670698?pwd=a1VPeU5tN01rc21Oa3hScUlHK0Rxdz09" rel="noreferrer" target="_blank">https://us02web.zoom.us/j/81634670698?pwd=a1VPeU5tN01rc21Oa3hScUlHK0Rxdz09</a><br>
<br>
Meeting ID: 81634670698 Meeting Password: 483805<br>
<br>
One tap mobile<br>
US (New York) +1 929 205 6099,,(nine-digit number from Join URL above)#<br>
US (San Jose) +1 669 900 6833,,(nine-digit number from Join URL above)#<br>
<br>
---<br>
<br>
2. *Related work*<br>
<br>
We hope to review and accept Pull Request 8 next week to integrate Physically Based Rendering (PBR) and lighting with glTF support.<br>
<br>
Efi, Thanos, Dick and Don have nearly all node and node type architectural relationships defined for an upgraded Sound component that includes spatialized sound capabilities matching W3C Web Audio API.<br>
<br>
We plan to submit a draft specification for review to Web3D Consortium Board of Directors and membership on 30 June. Following that review the draft document will be released publicly for comment in time for SIGGRAPH 2020.<br>
<br>
Implementations to date include X3DOM, X_ITE and Titania, Castle Game Engine view3dscene and FreeWRL, with possible implementation interest noted by at other major codebases.<br>
<br>
Ongoing releases include X3D4 XML Schema, X3D Unified Object Model (X3DUOM), X3D XML Schema and DOCTYPE, X3D Ontology, X3D JSON encoding, X3DJSAIL (Java), X3DPSAIL (Python x3d.py).<br>
<br>
Summary of current and planned X3D4 nodes and fields is available in<br>
<br>
[1] X3D4 Tooltips<br>
<a href="https://www.web3d.org/x3d/content/X3dTooltips.html" rel="noreferrer" target="_blank">https://www.web3d.org/x3d/content/X3dTooltips.html</a><br>
<br>
---<br>
<br>
3. *Mantis Issues*<br>
<br>
Dick and Don continue making steady progress applying approved changes to the X3D4 Specifications and related assets.<br>
<br>
[2] Mantis: View All Issues<br>
<a href="https://www.web3d.org/member-only/mantis/view_all_bug_page.php" rel="noreferrer" target="_blank">https://www.web3d.org/member-only/mantis/view_all_bug_page.php</a><br>
then select "X3D Project" in upper right corner.<br>
<br>
Reportedly each member and invited expert either has full access into these Mantis issues, or else is being assisted. POC is Executive Director Anita Havele if difficulties persist.<br>
<br>
Draft specification available to members in Github version control:<br>
<br>
[3] Github Web3D Consortium<br>
<a href="https://github.com/Web3dConsortium" rel="noreferrer" target="_blank">https://github.com/Web3dConsortium</a><br>
<br>
[4] Github Web3D Consortium: ISO-IEC 19775-1 - X3D Architecture and base components, Part 1<br>
<a href="https://github.com/Web3DConsortium/X3D/tree/master/ISO-IEC19775/ISO-IEC19775-1/ISO-IEC19775-1v4.0/ISO-IEC19775-1v4-WD1/Part01" rel="noreferrer" target="_blank">https://github.com/Web3DConsortium/X3D/tree/master/ISO-IEC19775/ISO-IEC19775-1/ISO-IEC19775-1v4.0/ISO-IEC19775-1v4-WD1/Part01</a><br>
<br>
This week we are reviewing a large number of issues that are quite close to resolution. Each issue has enjoyed scrutiny and dialog on the x3d-public mailing list and X3D Working Group reviews. We seek to determine consensus on as many as possible in order to allow including the corresponding changes in the forthcoming X3D4 draftrelease.<br>
<br>
Issue list follows, full issue list attached.<br>
<br>
Id Summary<br>
<br>
1310 near and far clipping planes currently not directly specified<br>
<br>
1309 NavigationInfo avatarSize parameters need to be split into separate fields<br>
<br>
1308 creaseAngle support by Triangle nodes<br>
<br>
1307 X3DParticleEmitterNode mass and surfaceArea accessType initializeOnly rather than inputOutput?<br>
<br>
1304 allowing animation of Cone, Cylinder bottom/side/top: accessType inputOutput<br>
<br>
1303 optional support for WebMercator datasets<br>
<br>
1302 geoSystem is difficult to define and parse, consider alternative approach<br>
<br>
1301 check geospatial navigation to see if NavigationInfo modes are sufficient<br>
<br>
1300 Consistently unify metadata model for GeoMetadata and HAnimHumanoid info array<br>
<br>
1299 Annotation Component deferral<br>
<br>
1293 HypersurfaceSensor/MultiTouchSensor for multi-touch environments<br>
<br>
1292 numbering of z order of layers in LayerSet<br>
<br>
1283 XML encoding: change X3D4 MetadataSet default containerField='value' ? <br>
<br>
1281 TwoSidedMaterial deprecation by adding Appearance backMaterial field<br>
<br>
1277 Provide displayBBox field on X3DBoundedObject nodes to display bounding boxes, rename bboxDisplay for consistency<br>
<br>
1276 name types: whitespace constraints, NMTOKEN and SFString<br>
<br>
1275 whether CollisionCollection and RigidBody implement X3DBoundedObject node<br>
<br>
1273 https level support requirements should match http level support<br>
<br>
1272 glTF import needs to include metadata import<br>
<br>
1271 add visible field to X3DBoundedObject<br>
<br>
1269 glTF physically based rendering PBR, advanced material textures and lighting<br>
<br>
1268 add height and width attributes to root X3D node<br>
<br>
1267 Strategies to Improve X3Dv4 Audio and Sound Component<br>
<br>
1266 Make RGB and grayscale textures treatment consistent<br>
<br>
1265 Text size clarification, relative to baseline<br>
<br>
1264 NavigationInfo type TURNTABLE HELICOPTER GAME FREEFLY<br>
<br>
1263 Log capability to record event streams<br>
<br>
1262 new field /refresh/ for Inline, ImageTexture etc.<br>
<br>
1261 PointSet field for Normal node <br>
<br>
1259 Scanning profile needed?<br>
<br>
1258 Layout component needs to be consistently implemented<br>
<br>
1257 Inline allowed to load additional model types<br>
<br>
1255 Projective Texture Mapping Component (PTM)<br>
<br>
1252 PointProperties node specification; PointSet/LineSet/IndexedLineSet can contain Normal<br>
<br>
Today Dick and I located a large number of editorial comments from an in-depth review by Roy Walmsley. We are going through each one-by-one and will elevate any that are functional, rather than simply editorial.<br>
<br>
Thanks for all scrutiny, feedback and implementation efforts. Have fun with X3D4! 8)<br>
<br>
all the best, Don<br>
-- <br>
Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><br>
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<br>
X3D graphics, virtual worlds, navy robotics <a href="http://faculty.nps.edu/brutzman" rel="noreferrer" target="_blank">http://faculty.nps.edu/brutzman</a><br>
_______________________________________________<br>
x3d-public mailing list<br>
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
</blockquote></div></div>
_______________________________________________<br>
x3d-public mailing list<br>
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
</blockquote></div>
</blockquote></div></div>
</blockquote></div>
</blockquote></div></div>