[x3d-public] More detailed X3DUOM changes to get x3d.py beta working again. Potential locations in XML Schema

[John Carlson]

Only name fields appear to be affected.  I$ diff -c /c/x3d-code/
www.web3d.org/specifications/X3dUnifiedObjectModel-4.0.xml
X3dUnifiedObjectModel-4.0.xml
*** /c/x3d-code/www.web3d.org/specifications/X3dUnifiedObjectModel-4.0.xml
    2024-02-12 04:13:50.745568000 -0600
--- X3dUnifiedObjectModel-4.0.xml       2024-02-18 09:33:12.663131500 -0600
***************
*** 9608,9614 ****
                      acceptableNodeTypes="X3DMetadataObject"
                      inheritedFrom="X3DNode"/>
              <field name="name"
!                     type="xs:NMTOKEN"
                      accessType="initializeOnly"
                      baseType="xs:NMTOKEN"/>
              <field name="DEF"
--- 9608,9614 ----
                      acceptableNodeTypes="X3DMetadataObject"
                      inheritedFrom="X3DNode"/>
              <field name="name"
!                     type="SFString"
                      accessType="initializeOnly"
                      baseType="xs:NMTOKEN"/>
              <field name="DEF"
***************
*** 18341,18347 ****
                      inheritedFrom="X3DNode"
                      description="Information about this node can be
contained in a MetadataBoolean, MetadataDouble, MetadataFloat,
MetadataInteger, MetadataString or MetadataSet node."/>
              <field name="name"
!                     type="xs:NMTOKEN"
                      accessType="initializeOnly"
                      inheritedFrom="X3DVertexAttributeNode"
                      baseType="xs:NMTOKEN"
--- 18341,18347 ----
                      inheritedFrom="X3DNode"
                      description="Information about this node can be
contained in a MetadataBoolean, MetadataDouble, MetadataFloat,
MetadataInteger, MetadataString or MetadataSet node."/>
              <field name="name"
!                     type="SFString"
                      accessType="initializeOnly"
                      inheritedFrom="X3DVertexAttributeNode"
                      baseType="xs:NMTOKEN"
***************
*** 27613,27619 ****
                      inheritedFrom="X3DNode"
                      description="Information about this node can be
contained in a MetadataBoolean, MetadataDouble, MetadataFloat,
MetadataInteger, MetadataString or MetadataSet node."/>
              <field name="name"
!                     type="xs:NMTOKEN"
                      accessType="initializeOnly"
                      inheritedFrom="X3DVertexAttributeNode"
                      baseType="xs:NMTOKEN"
--- 27613,27619 ----
                      inheritedFrom="X3DNode"
                      description="Information about this node can be
contained in a MetadataBoolean, MetadataDouble, MetadataFloat,
MetadataInteger, MetadataString or MetadataSet node."/>
              <field name="name"
!                     type="SFString"
                      accessType="initializeOnly"
                      inheritedFrom="X3DVertexAttributeNode"
                      baseType="xs:NMTOKEN"
***************
*** 27676,27682 ****
                      inheritedFrom="X3DNode"
                      description="Information about this node can be
contained in a MetadataBoolean, MetadataDouble, MetadataFloat,
MetadataInteger, MetadataString or MetadataSet node."/>
              <field name="name"
!                     type="xs:NMTOKEN"
                      accessType="initializeOnly"
                      inheritedFrom="X3DVertexAttributeNode"
                      baseType="xs:NMTOKEN"
--- 27676,27682 ----
                      inheritedFrom="X3DNode"
                      description="Information about this node can be
contained in a MetadataBoolean, MetadataDouble, MetadataFloat,
MetadataInteger, MetadataString or MetadataSet node."/>
              <field name="name"
!                     type="SFString"
                      accessType="initializeOnly"
                      inheritedFrom="X3DVertexAttributeNode"
                      baseType="xs:NMTOKEN"

Potential locations in XML Schema that may be causing the issues:

$ grep -n 'attribute.*"name".*NMTOKEN' /c/x3d-code/
www.web3d.org/specifications/x3d-4.0.xsd
6649:                   <xs:appinfo><xs:attribute name="name"
type="xs:NMTOKEN" fixed="initializeOnlyField">
6662:                           <xs:attribute name="name" type="xs:NMTOKEN">
13031:                                  <xs:attribute name="name"
type="xs:NMTOKEN" use="required">
13135:                                  <xs:attribute name="name"
type="xs:NMTOKEN" use="required">
13163:                                  <xs:attribute name="name"
type="xs:NMTOKEN" use="required">
13251:                                  <xs:attribute name="name"
type="xs:NMTOKEN" use="required">
13277:                                  <xs:attribute name="name"
type="xs:NMTOKEN" use="required">
13341:                                  <xs:attribute name="name"
type="xs:NMTOKEN">
19343:                                  <xs:attribute name="name"
type="xs:NMTOKEN">
19466:                                  <xs:attribute name="name"
type="xs:NMTOKEN">
19547:                                  <xs:attribute name="name"
type="xs:NMTOKEN">
19666:                                  <xs:attribute name="name"
type="xs:NMTOKEN">
19715:                                  <xs:attribute name="name"
type="xs:NMTOKEN">
19768:                                  <xs:attribute name="name"
type="xs:NMTOKEN">

Will now look into X3DUOM generation to see if xs:NMTOKEN can be
overridden with SFString in X3DUOM name fields.  If this is not desired, we
need to change the x3d.py generators.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20240218/3c246830/attachment-0001.html>