<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:"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;}
.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;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>The Mantis issue is confirmed, but not assigned. I assume this means that the issue is accepted as a change, but not assigned yet? I can accept assignment for the JSON schema part. I should be able to handle the XML schema too (if it’s merely adding an “N”—I don’t know about additional enumeration values accepted yet, and the JSON schema won’t benefit in the short term, but I can delete the enum entirely, if necessary), if I am allowed to check in. Let me know which versions you want me to modify. Someone else will have to modify the standard. I’m not sure where that’s located? GitHub? I assume the standard comes first, and then the schemas? IDRK. Is the standard generated from the Unified Object Model yet?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>How do we get the ball rolling on this?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</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:andreasplesch@gmail.com">Andreas Plesch</a><br><b>Sent: </b>Sunday, May 13, 2018 12:46 AM<br><b>To: </b><a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Re: [x3d-public] Invalid geoSystem values in X3D Resources BasicGeospatial examples.</p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal><a href="http://www.web3d.org/documents/specifications/19775-1/V3.2/Part01/components/geodata.html#Specifyingaspatialreference">http://www.web3d.org/documents/specifications/19775-1/V3.2/Part01/components/geodata.html#Specifyingaspatialreference</a></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>lists the supported strings for the geoSystem MFString field.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The prose choosing 'supported' over 'legal' or 'conforming' could be taken to mean that other than listed strings may be allowed to be supported as well by some browsers.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>However, previous discussions indicate that schemas are not sufficiently expressive to describe unknown but conforming string values.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>One resolution was to explicitly allow 'N' in upcoming X3D version, and perhaps silently allow it for 3.3.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Outside of X3D UTM zones often have the N hemisphere identifier to avoid ambiguity.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Andreas</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div><p class=MsoNormal style='margin-left:4.8pt'>Date: Sat, 12 May 2018 19:54:17 -0400<br>From: John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>><br>To: Don Brutzman <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>>, X3D Graphics public mailing list<br> <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br>Subject: [x3d-public] Invalid geoSystem values in X3D Resources Basic<br> Geospatial examples.<br>Message-ID: <<a href="mailto:5af77ea8.1c69fb81.7da1f.13e3@mx.google.com" target="_blank">5af77ea8.1c69fb81.7da1f.13e3@mx.google.com</a>><br>Content-Type: text/plain; charset="utf-8"<br><br>Don, These files contain "N" in geoSystem, which I believe is not valid, and should be removed (default is Northern Hemisphere, in the standard, I believe. "S" can be specified?not in this case).<br><br>Is there a tool which hasn?t been changed which is </p><p class=MsoNormal><o:p> </o:p></p></div></body></html>