[x3d-public] problem with GeoMetadata summary field, Savage JSON data.

[John Carlson]

The following Savage files generated from X3dToJson.xslt (I think) have problems with GeoMetadata summary field. X3D is wrong, should be 2 SFStrings in the MFString, I think.  JSON Schema says minItems 2.  The abstract specification says there should always be an even number of strings, so I believe the X3D XML and X3D JSON examples are wrong. (xml corresponding to these json files as well). Please fix the XML, and I will regenerate the JSON.

One example attached.

Savage/Locations/SouthernCaliforniaBorder/N2942E5237DTED2.json
Savage/Locations/SouthernCaliforniaBorder/N2942E5238DTED2.json
Savage/Locations/SouthernCaliforniaBorder/N2942E5239DTED2.json
Savage/Locations/SouthernCaliforniaBorder/N2942E5240DTED2.json
Savage/Locations/SouthernCaliforniaBorder/N2943E5237DTED2.json
Savage/Locations/SouthernCaliforniaBorder/N2943E5238DTED2.json
Savage/Locations/SouthernCaliforniaBorder/N2943E5239DTED2.json
Savage/Locations/SouthernCaliforniaBorder/N2944E5237DTED2.json
Savage/Locations/SouthernCaliforniaBorder/N2944E5238DTED2.json
Savage/Locations/SouthernCaliforniaBorder/N2944E5239DTED2.json
Savage/Locations/SouthernCaliforniaBorder/N2944E5240DTED2.json
Savage/Locations/SouthernCaliforniaBorder/N2945E5237DTED2.json
Savage/Locations/SouthernCaliforniaBorder/N2945E5238DTED2.json
Savage/Locations/SouthernCaliforniaBorder/N2945E5239DTED2.json
Savage/Locations/SouthernCaliforniaBorder/N2945E5240DTED2.json

http://www.web3d.org/documents/specifications/19775-1/V3.0/Part01/components/geodata.html#GeoMetadata “The summary string array contains a set of keyword/value pairs, with each keyword and its subsequent value contained in a separate string; i.e., there should always be an even (or zero) number of strings. This provides a simple, extensible mechanism to include metadata elements that are human-readable and easy to parse. Table 25.5 specifies a number of keywords and the format that should be used to describe their values. If an unknown keyword is found, it (and its associated value) are ignored.”

JSON schema development is going well. All files that validate with version 3.3 also validate with the new version.    We obviously need more negative examples? Got some? I will email the schema next.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170719/699fe0c7/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: N2942E5237DTED2.json
Type: application/json
Size: 40786 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170719/699fe0c7/attachment-0001.json>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: N2942E5237DTED2.x3d
Type: application/octet-stream
Size: 38199 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170719/699fe0c7/attachment-0001.obj>