[x3d-public] A new day, probably no differences from yesterday! -- Autogenerated JSON validation

[John Carlson]

Simple. Do these meta nodes/statements (to the right of the filename 
containing the meta) look right?

$ find /c/x3d-code/www.web3d.org/x3d/content/examples/ -name '*.x3d' 
-print0|xargs -0 grep "<meta.*key="
.../Savage/ModelDetailing/MilitaryCrestsAndSeals/COMDESRON9/COMDESRON9.x3d: 
<meta name='Vizthumbnail' key='Thumb_COMDESRON9_x3d14145131148866881.jpg'/>

.../Savage/ModelDetailing/MilitaryCrestsAndSeals/COMDESRON31/DESRON31Test.x3d: 
<meta name='Vizthumbnail' 
key='Thumb_DESRON31Test_x3d47572691148873503.jpg'/>

.../Savage/ModelDetailing/MilitaryCrestsAndSeals/COMDESRON31/COMDESRON31.x3d: 
<meta name='Vizthumbnail' key='Thumb_COMDESRON31_x3d58303181148874576.jpg'/>

.../Savage/ModelDetailing/MilitaryCrestsAndSeals/CSG11/CSG11.x3d: <meta 
name='Vizthumbnail' key='Thumb_CSG11_x3d14978421148866965.jpg'/>


Sorry I really can't shorten the file names more.  Does putting a line 
between them increase readability?

Thanks for efforts!

John

On 4/2/21 11:17 PM, Don Brutzman wrote:
> On 4/2/2021 12:52 PM, John Carlson wrote:
>> Autogenerated X3D JSON schemas (All X3D JSON schemas have been 
>> validated by Everit).
>
> Do you have multiple schemas getting validated, or multiple X3D JSON 
> scenes getting validated?
>
>> The Savage files need the first meta changed. @key replaced with
>> @content, or we should change the X3DUOM and schemas to support @key.
>
> Not sure what you mean.  X3D architecture meta element has name and 
> content attributes.
>
> * X3D Tooltips: meta
>   https://www.web3d.org/x3d/tooltips/X3dTooltips.html#meta
>
> Sorry but the rest of the message quickly becomes unintelligible for 
> me... can we stay simple please?
>
> No need to race to the raggedy edge of development, please walk us 
> through something simple first.
>
> As before recommend we work on the basics, a simple Shape node or 
> HelloWorld.json for example.
>
> all the best, Don