<div dir="auto">+1 for Nicholas’ idea. We will still need to rename the “class” getter, setter, etc in x3dpsail I think.</div><div dir="auto"><br></div><div dir="auto">John</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Dec 21, 2020 at 12:35 PM Don Brutzman <<a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Interesting progress following last Friday's detection and discussion about FontStyle/ScreenFontStyle 'style' field.<br>
<br>
[1] X3D minutes 18 DEC 2020: X3D4 review, ballot in progress, CSS class/style naming collisions, issue resolution continues<br>
<a href="http://web3d.org/pipermail/x3d-public_web3d.org/2020-December/014295.html" rel="noreferrer" target="_blank">http://web3d.org/pipermail/x3d-public_web3d.org/2020-December/014295.html</a><br>
<br>
On 12/18/2020 10:20 AM, Don Brutzman wrote:<br>
> a. FontStyle and ScreenFontStyle have style attribute, which is a name collision for CSS style attribute.<br>
<br>
> Meanwhile<br>
<br>
[2] X3D4 Architecture, Annex L HTML Authoring Guidelines<br>
> <a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-WD3/Part01/htmlGuidelines.html#CSS" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-WD3/Part01/htmlGuidelines.html#CSS</a><br>
> <br>
> How to handle?<br>
> <br>
> Of note is that X3DJSAIL dealt with a similar issue before, a Java-API problem with CSS 'class' colliding with Java reserved word 'class' and renamed it cssClass. Similar approach was likely necessary in Python; such collisions are to be expected for common terms.<br>
> <br>
> X3D4 general goals and priorities:<br>
> a. Retain information in legacy X3D/VRML models.<br>
> b. Retain as much existing common practice as possible.<br>
> c. Minimize field name changes when possible/advisable.<br>
> d. Allow consistent portability of content across all X3D file encodings and language bindings (even if something like a CSS-related value is not expected to be used).<br>
> e. Permit interoperation with HTML and CSS without conflict.<br>
<br>
so far so good. getting specific:<br>
<br>
=====================================================================<br>
[3] X3D4 Architecture, Text component, 15.2.2.2 Font family and style<br>
<a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-WD3/Part01/components/text.html#Fontfamilyandstyle" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-WD3/Part01/components/text.html#Fontfamilyandstyle</a><br>
<br>
Font attributes are defined with the family and style fields. The browser shall map the specified font attributes to an appropriate available font as described below.<br>
[...]<br>
The style field specifies a case-sensitive SFString value that may be "PLAIN" (the default) for default plain type; "BOLD" for boldface type; "ITALIC" for italic type; or "BOLDITALIC" for bold and italic type. An empty style value ("") is identical to "PLAIN". In the case where the requested style is not available, the available style that is closest to the requested style shall be used. For example, some font families specify a Demibold style rather than Bold. In this case, specifying "BOLD" will result in the browser using Demibold as the nearest substitute.<br>
<br>
=====================================================================<br>
[4] X3D4 Architecture, Text component, 15.4.1 FontStyle<br>
<a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-WD3/Part01/components/text.html#FontStyle" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-WD3/Part01/components/text.html#FontStyle</a><br>
<br>
15.4.1 FontStyle<br>
FontStyle : X3DFontStyleNode {<br>
SFNode [in,out] metadata NULL [X3DMetadataObject]<br>
MFString [] family "SERIF"<br>
SFBool [] horizontal TRUE<br>
MFString [] justify "BEGIN" ["BEGIN","END","FIRST","MIDDLE",""]<br>
SFString [] language ""<br>
SFBool [] leftToRight TRUE<br>
SFFloat [] size 1.0 (0,∞)<br>
SFFloat [] spacing 1.0 [0,∞)<br>
SFString [] style "PLAIN" ["PLAIN"|"BOLD"|"ITALIC"|"BOLDITALIC"|""]<br>
SFBool [] topToBottom TRUE<br>
}<br>
=====================================================================<br>
<br>
> It would seem we have three approaches possible here:<br>
> =====================================================<br>
> i. Specialized CSS-field names peculiar to FontStyle and ScreenFontStyle,<br>
<br>
pro: avoids name collision,<br>
con: irregular, makes applying CSS styles harder, seeming showstopper since FontStyle is primary candidate for styling.<br>
<br>
> ii. Change X3D FontStyle and ScreenFontStyle /style/ fields, renaming as /x3dStyle/ or /presentationStyle/ or somesuch, avoiding future naming collisions altogether. This would obviously be part of our differences between X3D3 and X3D4.<br>
pro: avoids name collision,<br>
con: requires translation of field values when converting or loading between X3D3 and X3D4.<br>
<br>
Discussed this with Dick. Viable, but naming remains tricky. Least-worst name that we came up with: 'glyphStyle' might work.<br>
<br>
> iii. Rename reserved words in X3D to cssClass and cssStyle for consistency throughout all of our file encodings and programming-language bindings. Also avoids collision with HTML DOM CSS 'class' and 'style' attributes within the DOM.<br>
<br>
still somewhat problematic. not a bad approach for X3DJSAIL and X3DJSAIL methods (consistently avoiding potential naming collisions with reserved words in Java, Python languages).<br>
<br>
pro: separation of fields,<br>
con: any X3D embedded in HTML no longer has same 'style' attribute, and so seeming showstopper since combined HTML/X3D styling (an expected use case) becomes impractical.<br>
<br>
---<br>
<br>
iv. Simpler representation: booleans.<br>
<br>
The exact same information might be represented as follows. No loss of generality since other values are not permitted.<br>
<br>
SFBool [] bold FALSE<br>
SFBool [] italics FALSE<br>
<br>
pro: simple, identical functionality, no name collisions.<br>
con: requires conversion X3D3-X3D4, possible contrary values if CSS style is also provided.<br>
<br>
---<br>
<br>
Discussion and great idea by Nicholas:<br>
<br>
v. Keep the same field name. Define functionality that FontStyle can parse either classic or new 'style' values compatibly.<br>
<br>
pro: "embracing the collision" for best of both worlds, no X3D3/X3D4 conversion or import problems.<br>
con: none yet seen...<br>
<br>
Here are the classic allowed values for the 'style' field, with CSS equivalents:<br>
<br>
PLAIN font-weight: normal; font-style: normal;<br>
BOLD font-weight: bold; font-style: normal;<br>
ITALICS font-weight: normal; font-style: italic;<br>
BOLDITALICS font-weight: bold; font-style: italic;<br>
<br>
[5] W3C, CSS Fonts Module Level 4, Editor’s Draft, 15 December 2020<br>
<a href="https://drafts.csswg.org/css-fonts" rel="noreferrer" target="_blank">https://drafts.csswg.org/css-fonts</a><br>
<br>
2.2. Font weight: the font-weight property<br>
<a href="https://drafts.csswg.org/css-fonts/#font-weight-prop" rel="noreferrer" target="_blank">https://drafts.csswg.org/css-fonts/#font-weight-prop</a><br>
<br>
2.4. Font style: the font-style property<br>
<a href="https://drafts.csswg.org/css-fonts/#font-style-prop" rel="noreferrer" target="_blank">https://drafts.csswg.org/css-fonts/#font-style-prop</a><br>
<br>
> =====================================================<br>
> <br>
> Of related note is that X3DOM already uses WebFonts to control font and style.<br>
> <br>
> [2.2] X3DOM Text Example<br>
> <a href="https://x3dom.org/x3dom/example/x3dom_text.html" rel="noreferrer" target="_blank">https://x3dom.org/x3dom/example/x3dom_text.html</a><br>
> <br>
> [2.3] Webfonts: W3C Fonts on the Web<br>
> <a href="https://www.w3.org/Fonts" rel="noreferrer" target="_blank">https://www.w3.org/Fonts</a><br>
<br>
So implementability seems to be well established. All of the X3D Example Archives scenes converted to X3DOM HTML include this css.<br>
<br>
[6] X3D Resource, X3D Examples Archives<br>
<a href="https://www.web3d.org/x3d/content/examples/X3dResources.html#Examples" rel="noreferrer" target="_blank">https://www.web3d.org/x3d/content/examples/X3dResources.html#Examples</a><br>
<br>
Other browsers are in good shape with this approach. Might wait to add such functionality at whatever time they want without loss of backwards compatibility with X3D3.<br>
<br>
Something I like: zero barrier to long-term adoption of CSS in X3D, if people want.<br>
<br>
> All insights welcome.<br>
> <br>
> Next steps:<br>
> - document in Mantis,<br>
<br>
[7] Mantis 1335: FontStyle/ScreenFontStyle 'style' field naming collisions with CSS style<br>
<a href="https://www.web3d.org/member-only/mantis/view.php?id=1335" rel="noreferrer" target="_blank">https://www.web3d.org/member-only/mantis/view.php?id=1335</a><br>
<br>
> - continue implementation testing, report back. Temporary testing of option (iii) seems possible now, option (ii) is promising.<br>
<br>
Option v (allow either functionality in FontStyle 'style' field) is most elegant and expressive with least complication. Now available in current validation tools.<br>
<br>
Option ii (rename as classic 'style' as 'glyphStyle') has some interest, and so is implemented in current validation tools, so that for comparison, we can also see corresponding auto-implementation methods in X3DJSAIL Java, X3DPSAIL Python, and X3D Ontology Turtle. However this is temporary and, following review, expect to remove it before the end of the month. All feedback welcome.<br>
<br>
> - Broader discussion is certainly appropriate.<br>
<br>
Thanks + bravo to Dick and Nicholas for close scrutiny. Feedback and improvement always welcome.<br>
<br>
I think we have opened the door to a "best of both worlds" approach. Having fun with X3D4. 8)<br>
<br>
[8] Van Halen - Best of Both Worlds (OFFICIAL VIDEO)<br>
(don't forget to select Loop and Full Screen!)<br>
<a href="https://www.youtube.com/watch?v=yZ7ywrl5oMo" rel="noreferrer" target="_blank">https://www.youtube.com/watch?v=yZ7ywrl5oMo</a><br>
RIP Eddie.<br>
<br>
all the best, Don<br>
-- <br>
Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><br>
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<br>
X3D graphics, virtual worlds, navy robotics <a href="http://faculty.nps.edu/brutzman" rel="noreferrer" target="_blank">http://faculty.nps.edu/brutzman</a><br>
<br>
_______________________________________________<br>
x3d-public mailing list<br>
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
</blockquote></div></div>