<div dir="auto">What I meant to say is appinfo is an SFString, but I don’t know if that’s enough information for the classic encoding. Anyone?</div><div dir="auto"><br></div><div dir="auto">John</div><div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, Aug 19, 2025 at 11:17 AM John Carlson <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir="auto">Sorry, I the previous message contained 2 large images.</div><div dir="auto"><br></div><div dir="auto">The direct links are:</div></div><div dir="auto"><div dir="auto"><br></div><div dir="auto"><div dir="auto"><a href="https://www.web3d.org/x3d/content/X3dTooltips.html#ProtoDeclare.appinfo" target="_blank">https://www.web3d.org/x3d/content/X3dTooltips.html#ProtoDeclare.appinfo</a></div></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><a href="https://www.web3d.org/x3d/content/X3dTooltips.html#field.appinfo" style="font-family:'uictfonttextstylebody';font-size:23px;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">https://www.web3d.org/x3d/content/X3dTooltips.html#field.appinfo</a></div></div><div dir="auto"><br></div><div dir="auto">John </div><div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <strong class="gmail_sendername" dir="auto">John Carlson</strong> <span dir="auto"><<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>></span><br>Date: Tue, Aug 19, 2025 at 10:54 AM<br>Subject: Re: [x3d-public] appinfo attribute/field<br>To: Michalis Kamburelis <<a href="mailto:michalis.kambi@gmail.com" target="_blank">michalis.kambi@gmail.com</a>><br>CC: Extensible 3D (X3D) Graphics public discussion <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br></div><br><br><div dir="auto">Michalis:</div><div dir="auto"><br></div><div dir="auto">Tooltips may help again here, they are SFStrings. I don’t know the meaning of CDATA or #IMPLIED though, see attached images. The issue you mentioned contains direct links, FMI.</div><div dir="auto"><br></div><div dir="auto">Thanks,</div><div dir="auto"><br></div><div dir="auto">John</div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Aug 19, 2025 at 10:46 AM Michalis Kamburelis <<a href="mailto:michalis.kambi@gmail.com" target="_blank">michalis.kambi@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Let me add another question to this thread: Where is the specification<br>
of how to *encode* appinfo information in the X3D classic encoding?<br>
<br>
To add some background/context to this question:<br>
<br>
- Thanks to John pointing out in<br>
<a href="https://github.com/castle-engine/castle-engine/issues/688" rel="noreferrer" target="_blank">https://github.com/castle-engine/castle-engine/issues/688</a> , in CGE we<br>
lack support for "appinfo" attribute in ProtoDeclare / field.<br>
<br>
- I found a mention of new "appinfo" and "documentation" in the<br>
abstract X3D 4.0 spec:<br>
<a href="https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/concepts.html#PROTOinterfacedeclsemantics," rel="noreferrer" target="_blank">https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/concepts.html#PROTOinterfacedeclsemantics<br>
,</a>"""Prototype and field declarations may optionally include appinfo<br>
functional descriptions (i.e., tooltip summary) and a documentation<br>
url providing a link to further related information."""<br>
<br>
- However, as the above is the "abstract" part of the spec ("X3D<br>
Abstract : Architecture and base components") so it naturally doesn't<br>
say how these "appinfo" and "documentation" are actually encoded. The<br>
official XML encoding and classic encoding specs are now at 3.3<br>
version -- so they don't mention how to encode this new X3D 4.0<br>
feature.<br>
<br>
- For XML encoding, it seems straightforward, judging from the<br>
testcase in <a href="https://github.com/castle-engine/castle-engine/issues/688" rel="noreferrer" target="_blank">https://github.com/castle-engine/castle-engine/issues/688</a><br>
. They are just XML attributes.<br>
<br>
<ProtoDeclare appinfo='...' name='...' ...><br>
<br>
<field appinfo='...' ...>'<br>
<br>
OK, so XML encoding is simple enough:)<br>
<br>
- We need to know how to encode this information in X3D classic, to<br>
enable lossless conversion between X3D encodings (classic, XML etc.).<br>
<br>
- If there is a spec, and/or a clear example of how to do this in X3D<br>
classic encoding, please point me to it :) Thank you!<br>
<br>
Regards,<br>
Michalis<br>
</blockquote></div></div>
</div></div>
</div>
</blockquote></div></div>