[x3d-public] [x3d] Spec Comment by vmarchetti on 19776-1: XML Encoding - V3.3

[John Carlson]

I am in agreement with Vince, but I would say XML element tag instead of
XML element name.  I have not read the XML encoding spec.

We may want to say something about concrete node types which inherit from
each other, if this is allowed.

John

On Fri, Jan 26, 2024 at 2:46 PM Joe D Williams <joedwil at earthlink.net>
wrote:

> Thank You Vincent,
>
> At the bottom of the report, the lines showing improper coding was blank
> so here is example.
>
> The sequence:
> Transform DEF='BorderFlower01' .../
> then
> Transform DEF='FlowerSpecial' ...
> Shape USE='BorderFlower01' /
> /
>
> Does not match ShapeChildContentModel
> Contained node's relationship to its parent node is wrong,
> Shape has no children so wrong containerfield for Transform.
> Transform needs containerField=children
> Shape is not a Grouping Node.
>
>
> Thanks Again,
> Joe
> -----Original Message-----
> From: Spec Feedback <spec-comment at web3d.org>
> Sent: Jan 26, 2024 7:36 AM
> To: <x3d at web3d.org>
> Subject: [x3d] Spec Comment by vmarchetti on 19776-1: XML Encoding - V3.3
>
> -- Submitter indicates that this comment may be public: *Yes* --
>
> Comment on 19776-1: XML Encoding - V3.3
> 4.3.4
>
> https://www.web3d.org/documents/specifications/19776-1/V3.3/Part01/concepts.html#DEFAndUSEAttributeSyntax
>
> -----------------
> Recent posts to the X3D-Public mailing list have pointed out that there is
> a
> discrepancy among browsers in how they handle the
> DEF/USE statements if the XML elements in the XML encoding have disparate
> names.
> http://web3d.org/pipermail/x3d-public_web3d.org/2024-January/020212.html
>
> I recommend the XML encoding spec be edited, in the next standard
> submission
> cycle, to clarify that it is invalid for XML elements with different names
> (i.e. encoding different X3D nodes) to have matching values of DEF/USE
> attributes.)
>
> Proposed wording to be added to what is now Section 4.3.4 of the 19776-1
> document at version 3.3:
>
> https://www.web3d.org/documents/specifications/19776-1/V3.3/Part01/concepts.html#DEFAndUSEAttributeSyntax
>
> Suggest adding this text:
>
>
> -----------------------------------------------------------------------------
> It is a validation error when an XML element with a DEF attribute matches
> another element's USE attribute but has a different XML element name.
>
> Example of invalid XML encoding:
>
>
>
>
>
>
>
> ____________________________________________________________________________
>
> -----------------
>
> Submitted on Friday, 2024, January 26 - 10:36am
> by vmarchetti (Vincent Marchetti )
> IP: 76.34.206.25
>
> See: https://www.web3d.org/node/1694/submission/10124
>
>
> _______________________________________________
> x3d mailing list
> x3d at web3d.org
> http://web3d.org/mailman/listinfo/x3d_web3d.org
>
>
>
> _______________________________________________
> x3d mailing list
> x3d at web3d.org
> http://web3d.org/mailman/listinfo/x3d_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20240126/0cb9c8e2/attachment.html>