[x3d-public] X3D JSON schema validation problems: double-escape example 2 wasactually OK

[John Carlson]

Ah yes, there are two very similar examples. Perhaps change the text of one to avoid confusion.

John

Sent from Mail for Windows 10

From: Don Brutzman
Sent: Sunday, July 9, 2017 7:23 PM
To: Roy Walmsley; John Carlson
Cc: X3D Graphics public mailing list
Subject: Re: X3D JSON schema validation problems: double-escape example 2 wasactually OK

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, &quot;Immel did it!&quot;"'/>

{ "MetadataString":
   {
	"@name":"escapedQuotesTest2",
	"@value":["escaped quotation marks example 2: He said, "Immel did it!""]
   }
}

This is correct because &quot; 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170709/87b068a0/attachment.html>