[x3d-public] Yay!

John Carlson yottzumm at gmail.com
Thu Jan 20 11:02:33 PST 2022


If you want to find Navigation.type in the X3D JSON schema, look for
EXAMINE.

Thanks!

John

On Thu, Jan 20, 2022 at 12:42 PM John Carlson <yottzumm at gmail.com> wrote:

> I have not been able to figure out how to change the X3D JSON schema
> generator to convert NavigationInfo.type from array to string.  The changes
> so far that I've made have no effect on the schemas.
>
> Hmmm!  Python assistance anyone?  See link in previous email.
>
> Or do we replace Python with XSLT?
>
> I could go either way,or toss JSON except for glTF.
>
> The schema folder is next to the python folder.
>
> You would run the schema generator with:
>
> $ python generateSchemas.py
>
> In the python folder (see link).
>
> And then look for changes in the schema folder.
>
> John
>
> On Thu, Jan 20, 2022 at 11:43 AM John Carlson <yottzumm at gmail.com> wrote:
>
>> Python experts are welcome to estimate changes, too, see:
>>
>>
>> https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/python/etgenerateJSONschema2020-12.py
>>
>> 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/7b027d78/attachment.html>


More information about the x3d-public mailing list