[x3d-public] Not quite automated. JinLO4.scaled1_Final.x3d under Sunrize; X32D Schematron improvement
Don Brutzman
don.brutzman at gmail.com
Tue Oct 21 12:49:35 PDT 2025
Thanks for confirmation Joe, again thanks for identification John. The
erroneous X3D Schematron diagnostic rule is now removed.
- X3D Schematron Validation and Quality Assurance (QA)
- X3D Schematron helps authors by providing quality assurance to ensure
intended results in X3D scenes and metadata.
- https://www.web3d.org/x3d/tools/schematron/X3dSchematron.html
- version control:
-
https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/tools/schematron/X3dSchematronValidityChecks.sch
- https://sourceforge.net/p/x3d/code/37700/
This improvement will also be deployed and easily accessible in future
releases of X3D-Edit.
Have fun with X3D and HAnim! 😀
all the best, Don
--
X3D Graphics, Maritime Robotics, Distributed Simulation
Relative Motion Consulting https://RelativeMotion.info
On Tue, Oct 21, 2025 at 9:58 AM Joe D Williams <joedwil at earthlink.net>
wrote:
> > has contained Shape geometry, but needs an intermediate Transform with
> translation value matching parent HAnimJoint/translation\
>
>
>
> for the Jin scaled version, the Shapes are drawn in place as child of
> Segment, same space as Joint, so no intermediate Transform in Segment is
> needed.
>
>
> Thanks,Joe
>
> -----Original Message-----
> From: Don Brutzman <don.brutzman at gmail.com>
> Sent: Oct 21, 2025 8:44 AM
> To: John Carlson <yottzumm at gmail.com>
> Cc: Extensible 3D (X3D) Graphics public discussion <x3d-public at web3d.org>,
> Joe D Williams <joedwil at earthlink.net>
> Subject: Re: [x3d-public] Not quite automated. JinLO4.scaled1_Final.x3d
> under Sunrize
>
>
> John, re-explaining: to understand this rule you have to read the output
> message. It does not talk about validity but is prompting an adjustment to
> match parent offset of the center field. It appears to be bad guidance,
> since the model works OK.
>
> You do not need to modify X3D XML Schematron. My message also reported
> that I was fixing it, the only question remaining was whether the rule
> deserved be adapted instead of deleted.
>
> all the best, Don
> --
> X3D Graphics, Maritime Robotics, Distributed Simulation
> Relative Motion Consulting https://RelativeMotion.info
>
> On Tue, Oct 21, 2025 at 2:51 AM John Carlson <yottzumm at gmail.com> wrote:
>
>> The Schematron rule should apply to HAnimJoint, that is, parent =
>> HAnimJoint and child = Shape is not allowed. Parent = HAnimSegment and
>> child = Shape is allowed.
>>
>> I am not savvy enough on Schematron to correct the rule.
>>
>> On Mon, Oct 20, 2025 at 8:57 PM Don Brutzman <don.brutzman at gmail.com>
>> wrote:
>>
>>> The JinLOA4.scaled1.x3d model looks good and animates without warnings
>>> in Castle Viewer.
>>>
>>> The Schematron diagnostic you referred to was
>>>
>>> - <HAnimSegment DEF='hanim_pelvis' name='pelvis'/> has contained
>>> Shape geometry, but needs an intermediate Transform with translation value
>>> matching parent HAnimJoint/translation='0 0.707175 -0.015921' in order to
>>> be in the right location
>>> [/X3D/Scene/HAnimHumanoid/HAnimJoint[1]/HAnimJoint/HAnimSegment, error]
>>>
>>> I think this is probably a bogus warning based on a prior
>>> misunderstanding, especially since this model seems to work satisfactorily
>>> now.
>>>
>>> Here was the offending schematron rule. Joe, if you think this rule
>>> should be modified instead of scrapped, please let me know. Otherwise it
>>> will be removed from the ruleset.
>>>
>>> - <report test="(parent::HAnimJoint) and (Shape) and
>>> not(Transform/Shape) and not(../@containerField='skeleton')" role="error">
>>> - <<name/> DEF='<value-of select='@DEF'/>' name='<value-of
>>> select='@name'/>'/> has contained Shape geometry, but needs an
>>> intermediate Transform with translation value matching parent
>>> HAnimJoint/translation='<value-of select="../@center"/>' in order to be in
>>> the right location
>>> - </report>
>>>
>>> all the best, Don
>>> --
>>> X3D Graphics, Maritime Robotics, Distributed Simulation
>>> Relative Motion Consulting https://RelativeMotion.info
>>>
>>>
>>> On Mon, Oct 20, 2025 at 10:55 AM John Carlson via x3d-public <
>>> x3d-public at web3d.org> wrote:
>>>
>>>
>>>> I couldn't quite produce an automated LayerSet/Layer HUD menu for
>>>> HAnimUtilityKit. I may back out and use a ProximitySensor if I can't make
>>>> progress, yet maintain the MenuItem proto.
>>>>
>>>> While I succeeded at knocking out most of the problems by hand, the
>>>> menu doesn't quite work for my *Final.x3d file. The other attached .x3d
>>>> file is the source, which works.
>>>>
>>>> I am tired, and frustrated, mostly about my misunderstanding of Python
>>>> ElementTree, which frustrated me from automation, I'll probably reinstall
>>>> or something.
>>>>
>>>> Anyway, if anyone want to spot my error, I tried X3D-Edit and
>>>> X3DJSAIL's CommandLine to spot bugs. X3DJSAIL validates successfully,
>>>> despite errors, X3D-Edit throws a set of surprising errors
>>>> about HAnimSegment requiring a Group/Transform and not a direct shape child.
>>>>
>>>> Note until the file is completely fixed, I recommend X_ITE/Sunrize. but
>>>> more work is needed.
>>>>
>>>> I'm thinking there's probably an issue with ProtoInterface field
>>>> accessType again. Does any tool report these? The other thing I thought
>>>> was that multiple animations are targeting the same interpolators, but
>>>> that's questionable.
>>>>
>>>> I did get HAnimUtillityKit nearly working with Aaron's model, so that's
>>>> progress.
>>>>
>>>> Using Haiku was a big black hole of time, I'll probably go back to
>>>> Sonnet.
>>>>
>>>> If all else fails, Reach for X3D-Edit and X3DJSAIL! Sooner, the better!
>>>>
>>>> Attached!
>>>>
>>>> John
>>>>
>>> _______________________________________________
>>>> x3d-public mailing list
>>>> x3d-public at web3d.org
>>>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20251021/5d147d5d/attachment-0001.html>
More information about the x3d-public
mailing list