[x3d-public] Invalid geoSystem values in X3D Resources BasicGeospatial examples.

[John Carlson]

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?

How do we get the ball rolling on this?

John

Sent from Mail for Windows 10

From: Andreas Plesch
Sent: Sunday, May 13, 2018 12:46 AM
To: X3D Graphics public mailing list
Subject: Re: [x3d-public] Invalid geoSystem values in X3D Resources BasicGeospatial examples.

http://www.web3d.org/documents/specifications/19775-1/V3.2/Part01/components/geodata.html#Specifyingaspatialreference

lists the supported strings for the geoSystem MFString field.

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.

However, previous discussions indicate that schemas are not sufficiently expressive to describe unknown but conforming string values.

One resolution was to explicitly allow 'N' in upcoming X3D version, and perhaps silently allow it for 3.3.

Outside of X3D UTM zones often have the N hemisphere identifier to avoid ambiguity.

Andreas




Date: Sat, 12 May 2018 19:54:17 -0400
From: John Carlson <yottzumm at gmail.com>
To: Don Brutzman <brutzman at nps.edu>,  X3D Graphics public mailing list
        <x3d-public at web3d.org>
Subject: [x3d-public] Invalid geoSystem values in X3D Resources Basic
        Geospatial examples.
Message-ID: <5af77ea8.1c69fb81.7da1f.13e3 at mx.google.com>
Content-Type: text/plain; charset="utf-8"

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).

Is there a tool which hasn?t been changed which is 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180513/627d7623/attachment.html>