[x3d-public] X3D JSON schema validation problems: double-escape example 2 was actually OK
Don Brutzman
brutzman at nps.edu
Sun Jul 9 16:22:09 PDT 2017
On 7/9/2017 3:55 PM, Don Brutzman wrote:
> p.s. John it looks like MetadataString "@value conversion is incorrectly encoding " as " instead of \" (though #comment and other values look OK), will work on it.
actually this is OK, it was testing something different.
<MetadataString name='escapedQuotesTest2' containerField='value' value='"escaped quotation marks example 2: He said, "Immel did it!""'/>
{ "MetadataString":
{
"@name":"escapedQuotesTest2",
"@value":["escaped quotation marks example 2: He said, "Immel did it!""]
}
}
This is correct because " in XML encoding is an ampersand character & followed by literal characters quot;
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
More information about the x3d-public
mailing list