[x3d-public] HAnim2: X3DUOM to LOA[0-4] Humanoid example

[John Carlson]

I am currently having problems resolving DEF/USE on included files.  
That is, I need a namespace, but if I don't Inline, I will have 
conflicting namespaces.

I am unsure how to resolve this problem, since with multiple DEF 
occurrences, and renaming following DEFs to USE, there is excess fields 
in some of the USEs.

The validator is a useful tool to find such occurrences, such that they 
may be fixed.    Currently, the problem is that I am including the 
separate hands/feet files. I need to look at standard or X3DUOM to see 
if hands/feet data is available there, and base my efforts there.

Or I can mess with the DOM documents for hands and feet.

Interesting.  I didn't know how to spell "occurrences."

John

On 3/28/21 6:47 PM, Don Brutzman wrote:
> Thanks for thinking ahead on this John.
>
> Regarding HAnim skeleton hierarchy: Yes, if you look in X3DUOM, you 
> will find that each joint and segment name also indicates its parent.
>
> Next steps:
>
> a. partially complete, is to get all of the default LOA4 values are in 
> the x3d schema and X3DUOM.
>
> b. save out LOA3 example and update it with LOA4 joints/segments/sites
>
> c. continue building test cases for X3D Schematron and X3dTidy.
>
> Given the immense amount of detail involved, difficulties in thorough 
> validation, and importance of the human skeleton for medical use, I 
> think it is critically important that we have correct examples that 
> are thorough and repeatable.
>
> Not as glamorous or some other tasks, but it is crucial to have a 
> stable basis and testable framework if we are to proceed successfully 
> & scalably.  More work is needed.
>
> Looking forward to further progress together.
>
> On 3/27/2021 5:32 PM, John Carlson wrote:
>>
>>
>> If no one else is pursuing this, I will begin X3DUOM to LOA[0-4]
>> Humanoid examples generation.
>>
>> Rationale:
>>
>> As we pursue the various X3D standards, it appears like the ISO standard
>> is becoming a second or third step after the X3D XML schema, X3DUOM, 
>> etc.
>>
>> I agree with this approach, so I think I should write code to support
>> it, and move HAnim examples up the food chain from ISO standard to 
>> X3DUOM.
>>
>> I am more familiar with X3DUOM than X3D XML schema.
>>
>> One question:  is the HAnim skeleton hierarchy present in X3DUOM?
>>
>> I am not setting any deadlines at this point.
>>
>> Thanks!
>>
>> John
>>
>
> all the best, Don