[x3d-public] Somewhat significant change to X3DUOM 3.3 causes X3D JSON schema 3.3 to reject files

[Don Brutzman]

Thanks John.  Yes there are a few differences in field names from X3D3 to X3D4, for improved object-model consistency.  Summarized at

* X3D Scene Authoring Hints: Field name changes planned for improved consistency
   https://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#fieldNameChanges

We should be able to confirm correctness of X3DUOM 3.3 next week, am thinking that prior-version names/synonyms should be something to include in X3DUOM 4.0 as well.


On 5/27/2021 11:12 PM, John Carlson wrote:
> Report (still on old version of X3DJSAIL):
> 
> These files are the one's I'm trying to get translations working for:
> 
> /X3DJSONLD/src/main/data$ grep -l ComposedCubeMapTexture *.x3d| grep -v new
> 
> ball.x3d
> bubbles.x3d
> bub.x3d
> flowerproto.x3d
> flowers4.x3d
> flowers7.x3d
> flowers.x3d
> geo.x3d
> mirror2.x3d
> mirror.x3d
> 
> Here are the JSON files that don't parse:
> 
> ~/X3DJSONLD/src/main/data$ for i in *.json; do jsonlint $i 2> /dev/null 1> /dev/null|| echo $i; done
> ball.new.json
> bubbles.new.json
> bub.new.json
> flowerproto.new.json
> flowers4.new.json
> flowers7.new.json
> flowers.new.json
> geo.new.json
> mirror2.new.json
> mirror.new.json
> SpatialAudioCameraAnimation.json
> SplitChannels.json
> text.new.json
> 
> 
> The new.json files are created from my generated Java code.  So either my code is wrong, or there's something wrong with X3DJSAIL.
> 
> 
> My code looks like this:
> 
> 
> .setTexture(new ComposedCubeMapTexture().setDEF("texture")
>                  .setBackTexture(new ImageTexture().setUrl(new MFString6().getArray()))
>                  .setBottomTexture(new ImageTexture().setUrl(new MFString7().getArray()))
>                  .setFrontTexture(new ImageTexture().setUrl(new MFString8().getArray()))
>                  .setLeftTexture(new ImageTexture().setUrl(new MFString9().getArray()))
>                  .setRightTexture(new ImageTexture().setUrl(new MFString10().getArray()))
>                  .setTopTexture(new ImageTexture().setUrl(new MFString11().getArray())))
> 
> 
> with setUSE below.
> 
> 
> John
> 
> On 5/27/21 10:52 PM, John Carlson wrote:
>> A somewhat significant change to X3DUOM 3.3 causes generated X3D JSON schema 3.3 to reject files.
>>
>> That is, there is no longer a bottomTexture, topTexture, frontTexture, etc. for ComposedCubeMapTexture.  Instead, "Texture" is left off of these fields.
>>
>>
>> 4.0 has the Texture added.
>>
>>
>> 2 suggestions:
>>
>> Update your files to X3D4.
>>
>> OR:
>>
>> Add these fields to X3DUOM 3.3 or find some way to get the old fields into X3D JSON schema 3.3 during schema generation (help!).
>>
>> I am not sure what the standard or the browsers do at this point.
>>
>> I'm upgrading my files to X3D4 and see if they work in various browsers.
>>
>> Help!
>>
>> John
>>
> 
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org

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