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

[John Carlson]

Here’s the some of schema in question:

                                            "additionalItems": {
                                                    "type": "string",
                                                    "enum": [
                                                            "S"
                                                    ]
                                            }
       

I don’t see why we can’t make it:

                                            "additionalItems": {
                                                    "type": "string"
                                            }

This is even present for NavigationInfo @type to describe unknown values. Roy? This might apply to more than just geoSystem, and give us more clarity in the schema.  Note that it only applies to arrays, I think. Note that we already have

                   additionalEnumerationValuesAllowed="true"

in the object model. We would merely set this on the geoSystem fields, to let me know more values are allowed.

Or even:
                                            "additionalItems": {
                                                    "type": "string",
                                                    "enum": [
                                                            "S",
                                                            "N"
                                                    ]
                                            }

We just need a decision on Mantis 938.  Or better, some action on XML schema, which will filter down to the object model, and then I can see we are serious about it.

Basically, I am hampered from modifying the JSON schema, because I see no action in either the XML schema or the Object Model, thus I am reluctant to change the JSON schema.

Hence the pushback on document authors.

Thanks,

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/f141da63/attachment.html>