<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><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'>Whoops, sent early. I was just trying to bring this issue to attention and get it resolved.</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Note:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>http://www.web3d.org/member-only/mantis/view.php?id=938<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John<o:p></o:p></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<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a><br><b>Sent: </b>Sunday, May 13, 2018 8:14 AM<br><b>To: </b><a href="mailto:andreasplesch@gmail.com">Andreas Plesch</a><br><b>Cc: </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.<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>The object model is expressive enough to list conforming values, yet accept others, but as far as I know (I may be wrong here), it is not expressive enough to express supported geoSystem values. This is a problem. How do we resolve it, and should we, if we are accepting other values? Is it resolved in X3DJSAIL? Should I get rid of Roy's JSON subschema for geoSystem?<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>John<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Sun, May 13, 2018, 7:43 AM John Carlson <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal style='margin-left:4.8pt'>I believe the purpose of schema is to support minimally acceptable files. It should flag files which are questionable. If a file can be brought into conformance easily, shouldn't it be?<o:p></o:p></p><div><p class=MsoNormal style='margin-left:4.8pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:4.8pt'>Yes, you should be able to ignore the results of the schema validation...at your own risk.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:4.8pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:4.8pt'>What is the purpose of the X3D resources examples, but to show a good example practice? Or are we testing tools to make sure certain values are acceptable? If that's the case, then the schema should be updated for ALL versions.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:4.8pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:4.8pt'>John<o:p></o:p></p></div></div><p class=MsoNormal style='margin-left:4.8pt'><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-left:4.8pt'>On Sun, May 13, 2018, 7:31 AM John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='margin-left:9.6pt'>Then the version of the document should be upgraded to 4.0 or above, and the corresponding schema updated. I can upgrade the schema for all versions, since it is hard coded into the schema generator. But really we need support from the object model if possible. Right now, I have to explicitly allow it for all versions, since I use stdin/stdout instead of files. Does the unified object model specify a version # in its contents? When the unified object model supports "N" in a usable fashion, then I can code something into the schema, or delete the requirement to check geoSystem.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:9.6pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:9.6pt'>Thanks, away from computer presently, or I would check.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:9.6pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:9.6pt'>I don't see why Roy went to all the effort to create a schema, if we are going to ignore it?<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:9.6pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:9.6pt'>This applies in many areas...if we merely have supported values, yet others must be accepted, why is there a standard?<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:9.6pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:9.6pt'>I don't believe it's ambiguous in this case of X3D. A missing "N" means Northern Hemisphere.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:9.6pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:9.6pt'>John<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:9.6pt'><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-left:9.6pt'>On Sun, May 13, 2018, 12:46 AM Andreas Plesch <<a href="mailto:andreasplesch@gmail.com" target="_blank">andreasplesch@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='margin-left:.2in'><a href="http://www.web3d.org/documents/specifications/19775-1/V3.2/Part01/components/geodata.html#Specifyingaspatialreference" target="_blank">http://www.web3d.org/specifications/19775-1/V3.2/Part01/components/geodata.html#Specifyingaspatialreference</a><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'>lists the supported strings for the geoSystem MFString field.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'>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.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'>However, previous discussions indicate that schemas are not sufficiently expressive to describe unknown but conforming string values.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'>One resolution was to explicitly allow 'N' in upcoming X3D version, and perhaps silently allow it for 3.3.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'>Outside of X3D UTM zones often have the N hemisphere identifier to avoid ambiguity.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'>Andreas<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.2in'><o:p> </o:p></p></div><div><div><div><p class=MsoNormal style='margin-left:.2in'><o:p> </o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><p class=MsoNormal style='margin-left:19.2pt'>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 <o:p></o:p></p></blockquote></div></div></div></blockquote></div></div></div></blockquote></div></blockquote></div><p class=MsoNormal style='margin-left:.2in'>_______________________________________________<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" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>