[x3d-public] candidate geoSystem correction to JSON schema
John Carlson
yottzumm at gmail.com
Sat May 20 19:45:45 PDT 2017
For XvlShell, we still have many examples which support it. That’s why I have it in the 3.0 version, not in the 3.3 version. It’s my way of avoiding excess errors.
There’s only one “N” in the whole file—Yes, for UTM.
Make sure you’re validating against the correct version of the schema 3.0 for 3.0; 3.3 for 3.1, 3.2 and 3.3, and you won’t run into too many difficulties, I hope.
John
Sent from Mail for Windows 10
From: Don Brutzman
Sent: Saturday, May 20, 2017 10:34 PM
To: John Carlson; Roy Walmsley
Cc: X3D Graphics public mailing list
Subject: Re: [x3d-public] candidate geoSystem correction to JSON schema
On 5/20/2017 6:48 PM, John Carlson wrote:
> The main additions are @headlight in GeoViewpoint,
OK, allowed in X3D versions 3.0-3.2 but removed in X3D version 3.3.
http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/versionContent.html#GeoViewpoint
> “N”
for geoSystem with UTM i think...
> and “XvlShell,”
We should leave that out. It was experimental for testing DTD extensibility mechanisms in version 3.0 era. But never support past that.
> plus the links to the draft04 metaschema is changed to https (not sure if this is right). Linked version includes required @names.
>
> https://raw.githubusercontent.com/coderextreme/X3DJSONLD/master/src/main/schema/x3d-3.0-JSONSchema.json
>
> You’re welcome.
>
> John
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
>
> *From: *Don Brutzman <mailto:brutzman at nps.edu>
> *Sent: *Saturday, May 20, 2017 9:34 PM
> *To: *John Carlson <mailto:yottzumm at gmail.com>; Roy Walmsley <mailto:roy.walmsley at ntlworld.com>
> *Cc: *X3D Graphics public mailing list <mailto:x3d-public at web3d.org>
> *Subject: *Re: [x3d-public] candidate geoSystem correction to JSON schema
>
> Thank you. I'll stand by for Roy to confirm and check in, then I do predeployment checking.
>
> On 5/20/2017 6:29 PM, John Carlson wrote:
>
> > Don, try this Schema. These are my modifications. Note that I don’t have some of the required @name fields yet in this schema. They will need to be added. Also, are IMPORTs up to date?
>
> >
>
> > Will provide an update when ready.
>
> >
>
> >
>
> > Thanks,
>
> >
>
> > John
>
> >
>
> > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
>
> >
>
> > *From: *Don Brutzman <mailto:brutzman at nps.edu>
>
> > *Sent: *Saturday, May 20, 2017 8:57 PM
>
> > *To: *Roy Walmsley <mailto:roy.walmsley at ntlworld.com>
>
> > *Cc: *X3D Graphics public mailing list <mailto:x3d-public at web3d.org>
>
> > *Subject: *[x3d-public] candidate geoSystem correction to JSON schema
>
> >
>
> > JSON Schema sayeth
>
> >
>
> > "@geoSystem": {
>
> >
>
> > "description": "Attempts to validate all possible combinations",
>
> >
>
> > "oneOf": [
>
> >
>
> > {
>
> >
>
> > "type": "array",
>
> >
>
> > "minItems": 1,
>
> >
>
> > "maxItems": 3,
>
> >
>
> > "items": [
>
> >
>
> > {
>
> >
>
> > "type": "string",
>
> >
>
> > "enum": [
>
> >
>
> > "GD",
>
> >
>
> > "GDC"
>
> >
>
> > ],
>
> >
>
> > "default": "GD"
>
> >
>
> > },
>
> >
>
> > while in X3D abstract specification:
>
> >
>
> > 25.2.2 Spatial reference frames
>
> >
>
> > http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/geodata.html#Spatialreferenceframes
>
> >
>
> > Table 25.2 — Supported spatial reference frames
>
> >
>
> > lists GD GC UTM and is followed by special cases GDC and GCC.
>
> >
>
> > Suggest adding enumeration values for "GC", "GCC", "UTM"
>
> >
>
> > However I do see other entries further down for "UTM" and default "GD" (though GD is not also listed there as an enum value).
>
> >
>
> > Example scene for testing is Squaw.x3d with Squaw.json including
>
> >
>
> > "@geoSystem":["UTM","Z10","N"],
>
> >
>
> > Also Mars.x3d and Mars.json with recent updates at
>
> >
>
> > http://www.web3d.org/x3d/content/examples/Basic/Geospatial/
>
> >
>
> > Not quite sure how you are handling things there, hope you can sort it out OK. TIA.
>
> >
>
> > all the best, Don
>
> >
>
> > --
>
> >
>
> > Don Brutzman Naval Postgraduate School, Code USW/Br brutzman at nps.edu
>
> >
>
> > Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149
>
> >
>
> > X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman
>
> >
>
> > _______________________________________________
>
> >
>
> > x3d-public mailing list
>
> >
>
> > x3d-public at web3d.org
>
> >
>
> > http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
> >
>
> all the best, Don
>
> --
>
> Don Brutzman Naval Postgraduate School, Code USW/Br brutzman at nps.edu
>
> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149
>
> X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman
>
all the best, Don
--
Don Brutzman Naval Postgraduate School, Code USW/Br brutzman at nps.edu
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170520/50624047/attachment-0001.html>
More information about the x3d-public
mailing list