[x3d-public] X3DSingleTextureTransformNode has no concrete nodes. X3DUOM, X3D Schema

[Holger Seelig]

I think what John wants to reveal is that the X3DUOM file has wrong inheritance for actually X3DSingleTextureTransformNode, all Michalis has already mentioned. 

That should be fixed.

X3DUOM
https://www.web3d.org/specifications/X3dUnifiedObjectModel-4.0.xml

Best regards,
Holger

—
Holger Seelig
holger.seelig at yahoo.de


> Am 22.08.2025 um 20:36 schrieb John Carlson via x3d-public <x3d-public at web3d.org>:
> 
> Or alternatively,
> 
> <AdditionalInheritance baseType="X3DSingleTextureTransformNode"/> in the nodes Michalis mentioned.
> 
> TextureTransform 
> TextureTransform3D 
> TextureTransformMatrix3D 
> 
> I guess I need to take a break.
> 
> XML schema hurts my brain.
> 
> John
> 
> On Fri, Aug 22, 2025 at 1:27 PM John Carlson <yottzumm at gmail.com <mailto:yottzumm at gmail.com>> wrote:
>> For example, from X3DUOM
>> 
>> <ConcreteNode name="MultiTextureTransform">
>>          <InterfaceDefinition specificationUrl="https://www.web3d.org/specifications/X3Dv4/ISO-IEC19775-1v4-IS/Part01/components/texturing.html#MultiTextureTransform"
>>                               appinfo="MultiTextureTransform contains multiple TextureTransform nodes, each provided for use by corresponding ImageTexture MovieTexture or PixelTexture nodes within a sibling MultiTexture node.">
>>             <componentInfo name="Texturing" level="2"/>
>>             <Inheritance baseType="X3DTextureTransformNode"/>
>> 
>> [ snip ]
>> 
>>             <field name="textureTransform"
>>                    type="MFNode"
>>                    accessType="inputOutput"
>>                    acceptableNodeTypes="X3DSingleTextureTransformNode"
>>                    description="Zero or more contained TextureTransform nodes, for each of the different texture channels, that define 2D transformation applied to texture coordinates."/>
>> 
>> [ snip ]
>> 
>>             <containerField default="textureTransform" type="xs:NMTOKEN"/>
>>             <ContentModel>
>>                <GroupContentModel name="ChildContentModelCore" minOccurs="0"/>                                                                                                                      <NodeContentModel name="TextureTransform"/>
>>                <NodeContentModel name="ProtoInstance"/>                                                                                                                                          </ContentModel>
>> 
>> 
>> 
>> ===========================================================================
>> 
>> What I would like to see is more acceptableNodetypes on the textureTransform field, however that's accomplished!
>> 
>> 
>> Thanks!
>> 
>> John
>> 
>> On Fri, Aug 22, 2025 at 1:18 PM John Carlson <yottzumm at gmail.com <mailto:yottzumm at gmail.com>> wrote:
>>> I think that X3D XML schema may have something, but I don't understand transfer to X3DUOM yet.
>>> 
>>> Help is desired.
>>> 
>>> Thanks,
>>> 
>>> John
>>> 
>>> On Fri, Aug 22, 2025 at 1:01 PM John Carlson <yottzumm at gmail.com <mailto:yottzumm at gmail.com>> wrote:
>>>> Just to be aware, X3DSingleTextureTransformNode has no ConcreteNodes implementing it.  This affects X3D JSON, X3DUOM and X3D schema.
>>>> 
>>>> This especially affects users of MultiTextureTransform.
>>>> 
>>>> Thanks,
>>>> 
>>>> 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/20250822/e22a1f48/attachment.html>