[x3d-public] 2 different schematrons? I'm fairly sure things are up to date, will check into diffs.

[John Carlson]

I had one time where the 3 rubik*.json worked in X3DJSONLD, but it 
didn't last for long.   Seems like things are transiently working????

Will return to debugging X3D-edit.

John

On 6/14/21 2:58 PM, John Carlson wrote:
> I just checked the online X3DJSONLD at 
> https://coderextreme.net/X3DJSONLD/
>
> All three rubik*.json (haven't tested the new.json) work with JSON 
> examples, both x3dom and x_ite.
>
> Only x_ite works with XML examples, x3dom does not work with XML 
> examples, in many cases.
>
> Nothing works locally :(.  The JavaScript appears to be moving very 
> slowly, when I pause and restart.
>
> John
>
> On 6/14/21 12:41 PM, Don Brutzman wrote:
>> John, looking closely at your structure, I think you have IS within a 
>> ProtoDeclare nested within another ProtoDeclare, with the IS reaching 
>> across two levels of prototyping.
>>
>> Pretty convoluted design...  nested prototypes have always been quite 
>> difficult for players to implement.
>>
>> Wondering: is there a need to be so convoluted?  Also wondering if 
>> any of our players work with this?
>>
>> Meanwhile I checked the logic of X3D Schematron rules for fieldValue 
>> checking, namely the rules based on protoFieldFound and 
>> externProtoFieldFound.  No logical errors detected.
>>
>> Not sure why you are getting these Schematron errors but will look at 
>> it further, at the moment they seem to be inappropriate.
>>
>>
>>
>> On 6/11/2021 11:32 AM, John Carlson wrote:
>>> ==========================================
>>>
>>> Standalone June 11 X3D-Edit:  Note that errors are reported. I need 
>>> help figuring out what's wrong.  Attached rubikFurnace.x3d
>>>
>>>
>>> Performing X3D Schematron check...
>>> <ProtoInstance name='anyShape' DEF=''> <fieldValue 
>>> name='xtranslation' value='0 0 0'/> has matching ProtoDeclare but no 
>>> corresponding field match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[2]/ProtoBody/Transform/ProtoInstance[1]/fieldValue, 
>>> error]
>>> <ProtoInstance name='anyShape' DEF=''> <fieldValue 
>>> name='xtranslation' value='2 0 0'/> has matching ProtoDeclare but no 
>>> corresponding field match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[2]/ProtoBody/Transform/ProtoInstance[2]/fieldValue, 
>>> error]
>>> <ProtoInstance name='anyShape' DEF=''> <fieldValue 
>>> name='xtranslation' value='-2 0 0'/> has matching ProtoDeclare but 
>>> no corresponding field match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[2]/ProtoBody/Transform/ProtoInstance[3]/fieldValue, 
>>> error]
>>> <ProtoInstance name='three' DEF=''> <fieldValue name='ytranslation' 
>>> value='0 0 0'/> has matching ProtoDeclare but no corresponding field 
>>> match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[3]/ProtoBody/Transform/ProtoInstance[1]/fieldValue, 
>>> error]
>>> <ProtoInstance name='three' DEF=''> <fieldValue name='ytranslation' 
>>> value='0 2 0'/> has matching ProtoDeclare but no corresponding field 
>>> match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[3]/ProtoBody/Transform/ProtoInstance[2]/fieldValue, 
>>> error]
>>> <ProtoInstance name='three' DEF=''> <fieldValue name='ytranslation' 
>>> value='0 -2 0'/> has matching ProtoDeclare but no corresponding 
>>> field match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[3]/ProtoBody/Transform/ProtoInstance[3]/fieldValue, 
>>> error]
>>> <ProtoInstance name='nine' DEF=''> <fieldValue name='ztranslation' 
>>> value='0 0 0'/> has matching ProtoDeclare but no corresponding field 
>>> match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[4]/ProtoBody/Transform/ProtoInstance[1]/fieldValue, 
>>> error]
>>> <ProtoInstance name='nine' DEF=''> <fieldValue name='ztranslation' 
>>> value='0 0 2'/> has matching ProtoDeclare but no corresponding field 
>>> match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[4]/ProtoBody/Transform/ProtoInstance[2]/fieldValue, 
>>> error]
>>> <ProtoInstance name='nine' DEF=''> <fieldValue name='ztranslation' 
>>> value='0 0 -2'/> has matching ProtoDeclare but no corresponding 
>>> field match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[4]/ProtoBody/Transform/ProtoInstance[3]/fieldValue, 
>>> error]
>>> <ProtoInstance name='twentyseven' DEF=''> <fieldValue 
>>> name='ttranslation' value='0 0 0'/> has matching ProtoDeclare but no 
>>> corresponding field match for this fieldValue 
>>> [/X3D/Scene/ProtoInstance/fieldValue[1], error]
>>> <ProtoInstance name='twentyseven' DEF=''> <fieldValue name='myShape' 
>>> value=''/> has matching ProtoDeclare but no corresponding field 
>>> match for this fieldValue [/X3D/Scene/ProtoInstance/fieldValue[2], 
>>> error]
>>>
>>> --------- X3D Validator checks complete for rubikFurnace.x3d ---------
>>>
>>> ===================================================
>>>
>>> Online validator, https://savage.nps.edu/X3dValidator/ Note hints 
>>> below, errors above, indicating possible difference in version of 
>>> schematron. Suggestion to add version to Schematron/Validation/QA to 
>>> track differences .between local and remote versions.  Note that 
>>> X3D-Edit appears to have a hash in title bar.  Perhaps just have a 
>>> version which is date/time? IDK.
>>>
>>> *7. Performing X3D Schematron 
>>> <http://www.web3d.org/x3d/tools/schematron/X3dSchematron.html> 
>>> check...* <ProtoInstance name='anyShape' DEF=''> <fieldValue 
>>> name='xtranslation' value='0 0 0'/> has matching ProtoDeclare but no 
>>> corresponding field match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[2]/ProtoBody/Transform/ProtoInstance[1]/fieldValue, 
>>> hint] <ProtoInstance name='anyShape' DEF=''> <fieldValue 
>>> name='xtranslation' value='2 0 0'/> has matching ProtoDeclare but no 
>>> corresponding field match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[2]/ProtoBody/Transform/ProtoInstance[2]/fieldValue, 
>>> hint] <ProtoInstance name='anyShape' DEF=''> <fieldValue 
>>> name='xtranslation' value='-2 0 0'/> has matching ProtoDeclare but 
>>> no corresponding field match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[2]/ProtoBody/Transform/ProtoInstance[3]/fieldValue, 
>>> hint] <ProtoInstance name='three' DEF=''> <fieldValue 
>>> name='ytranslation' value='0 0 0'/> has matching ProtoDeclare but no 
>>> corresponding field match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[3]/ProtoBody/Transform/ProtoInstance[1]/fieldValue, 
>>> hint] <ProtoInstance name='three' DEF=''> <fieldValue 
>>> name='ytranslation' value='0 2 0'/> has matching ProtoDeclare but no 
>>> corresponding field match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[3]/ProtoBody/Transform/ProtoInstance[2]/fieldValue, 
>>> hint] <ProtoInstance name='three' DEF=''> <fieldValue 
>>> name='ytranslation' value='0 -2 0'/> has matching ProtoDeclare but 
>>> no corresponding field match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[3]/ProtoBody/Transform/ProtoInstance[3]/fieldValue, 
>>> hint] <ProtoInstance name='nine' DEF=''> <fieldValue 
>>> name='ztranslation' value='0 0 0'/> has matching ProtoDeclare but no 
>>> corresponding field match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[4]/ProtoBody/Transform/ProtoInstance[1]/fieldValue, 
>>> hint] <ProtoInstance name='nine' DEF=''> <fieldValue 
>>> name='ztranslation' value='0 0 2'/> has matching ProtoDeclare but no 
>>> corresponding field match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[4]/ProtoBody/Transform/ProtoInstance[2]/fieldValue, 
>>> hint] <ProtoInstance name='nine' DEF=''> <fieldValue 
>>> name='ztranslation' value='0 0 -2'/> has matching ProtoDeclare but 
>>> no corresponding field match for this fieldValue 
>>> [/X3D/Scene/ProtoDeclare[4]/ProtoBody/Transform/ProtoInstance[3]/fieldValue, 
>>> hint] <ProtoInstance name='twentyseven' DEF=''> <fieldValue 
>>> name='ttranslation' value='0 0 0'/> has matching ProtoDeclare but no 
>>> corresponding field match for this fieldValue 
>>> [/X3D/Scene/ProtoInstance/fieldValue[1], hint] <ProtoInstance 
>>> name='twentyseven' DEF=''> <fieldValue name='myShape' value=''/> has 
>>> matching ProtoDeclare but no corresponding field match for this 
>>> fieldValue [/X3D/Scene/ProtoInstance/fieldValue[2], hint] X3D 
>>> Schematron check: *pass*. Good practice is to fix errors and 
>>> warnings wherever possible, and consider silencing harmless 
>>> informational messages, so that important indicators remain noticeable.
>>>
>>>
>>>
>>> _______________________________________________
>>> x3d-public mailing list
>>> x3d-public at web3d.org
>>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>>
>>
>> all the best, Don