[x3d-public] Yay!

[John Carlson]

For clarification, I do not mean each of the SFStrings is surrounded by “”.
Each SFString is surrounded by \”

The whole group of SFStrings is also surrounded by double quotes.   Like
XML.

I hope this clarification will help.

John

On Thu, Jan 20, 2022 at 11:39 AM John Carlson <yottzumm at gmail.com> wrote:

> Cache is cleared.   Now, AFAICT, we are using XML-like syntax for
> NavigationInfo.type field MFStrings in JSON with “” around outside of all
> the SFStrings in the field.   We definitely are *not* using a JSON array.
> What about url fields?  I think there’s also an MFString in the FontStyle
> node, but I haven’t checked that recently.
>
> Who will be responsible for updating JSON schema for NavigationInfo.type?
>   My guess is there might be lower impact if we hand edit the schema, but
> if we wish to automate we need to choose between changing the python
> generator and creating XSLT.
>
> I will try to estimate impact of the change on the current schema
> generator at the meeting on Friday.
>
> John
>
> On Thu, Jan 20, 2022 at 11:19 AM John Carlson <yottzumm at gmail.com> wrote:
>
>> NavigationInfo.type in JSON has been resolved I think.
>>
>>
>> https://www.web3d.org/x3d/content/examples/ConformanceNist/BindableNodes/NavigationInfo/navigationinfo.json
>>
>> Looks like
>>
>>
>> https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/stylesheets/java/examples/HelloWorldProgramOutput.json
>>
>> But wait, check this one (previously posted):
>>
>>
>> https://www.web3d.org/x3d/content/examples/ConformanceNist/BindableNodes/NavigationInfo/jumpcut_loadurl.json
>>
>> Should I clear my cache?
>>
>> Thanks for clearing up any confusion on my part.
>>
>> John
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20220120/40c6192b/attachment.html>