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

Don Brutzman brutzman at nps.edu
Sat Apr 3 11:27:09 PDT 2021


all fixed, emails crossed, likewise thanks

On 4/3/2021 11:01 AM, John Carlson wrote:
> 
> 
> Simple. Do these meta nodes/statements (to the right of the filename
> containing the meta) look right?
> 
> $ find /c/x3d-code/https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.web3d.org%2Fx3d%2Fcontent%2Fexamples%2F&data=04%7C01%7Cbrutzman%40nps.edu%7C284655e9a398414e50d708d8f6cb21f8%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637530699601857909%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=S0%2FItNQON%2FfEyFHRjAbtQ6z4zwi111%2BWm%2FNzYohxVU4%3D&reserved=0-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://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.web3d.org%2Fx3d%2Ftooltips%2FX3dTooltips.html%23meta&data=04%7C01%7Cbrutzman%40nps.edu%7C284655e9a398414e50d708d8f6cb21f8%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637530699601867903%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=YR%2BJEyhDzrYKYWQp5YPksuumwxL7TAJthovMo0SIepE%3D&reserved=0
>>
>> 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

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



More information about the x3d-public mailing list