<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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 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><p class=MsoNormal>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.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>One example attached.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2942E5237DTED2.json<o:p></o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2942E5238DTED2.json<o:p></o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2942E5239DTED2.json<o:p></o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2942E5240DTED2.json<o:p></o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2943E5237DTED2.json<o:p></o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2943E5238DTED2.json<o:p></o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2943E5239DTED2.json<o:p></o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2944E5237DTED2.json<o:p></o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2944E5238DTED2.json<o:p></o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2944E5239DTED2.json<o:p></o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2944E5240DTED2.json<o:p></o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2945E5237DTED2.json<o:p></o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2945E5238DTED2.json<o:p></o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2945E5239DTED2.json<o:p></o:p></p><p class=MsoNormal>Savage/Locations/SouthernCaliforniaBorder/N2945E5240DTED2.json<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>http://www.web3d.org/documents/specifications/19775-1/V3.0/Part01/components/geodata.html#GeoMetadata<span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black;background:white'> “The <i>summary</i> 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. </span><a href="http://www.web3d.org/documents/specifications/19775-1/V3.0/Part01/components/geodata.html#t-keywordsandvalues"><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;background:white'>Table 25.5</span></a><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black;background:white'> 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.”<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black;background:white'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black;background:white'>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.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black;background:white'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black;background:white'>John</span></p></div></body></html>