<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1078937046;
mso-list-type:hybrid;
mso-list-template-ids:-893717134 -1 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:3;
mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body lang=EN-US><div class=WordSection1><p class=MsoNormal>The goals of the X3D semantic working group are elsewhere. I am a skeptic of the Semantic Web as well, and would prefer if it was on a firmer footing. In order to do that for X3D will require some non-trivial work. We have at least 4 capabilities we are working on. I am currently interested in the 2<sup>nd</sup> and 3<sup>rd</sup>:</p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>An XML Schema/XML Object Model/JSON Schema/X3D Ontology capability. I call this the non-rendered abstract level.</li><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>An XML document/VRML document/3D Model/JSON document/Java document/JavaScript document/Python document/Knowledge Base/… I call this the non-rendered concrete level.</li><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>The rendered visualization of the above. I call this the rendered abstract level. OSNAP falls under this.</li><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>The rendered, browser display of a scene. I call this the rendered concrete level.</li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>NSM, <a href="https://en.wikipedia.org/wiki/Natural_semantic_metalanguage"><strong><span style='font-family:"Calibri",sans-serif;color:windowtext;text-decoration:none'>https://en.wikipedia.org/wiki/Natural_semantic_metalanguage</span></strong></a> has several capabilities:</p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>A set of atomic meanings/words which are cross language</li><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>A DALIA “parser”. The question is, what do we get out of this parser? My believe is that you get a translation from one language to another. You have declared that syntax and semantics are inseparable. I don’t disagree. There is also semiotics, pragmatics, etc.</li><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>Sets of molecules which define higher or composite meanings.</li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>X3D is similar to NSM in that it has</p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>A set of atomic tags and attributes which are currently single language, but might be considered cross-language (like HTML5 is cross-language).</li><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>Language based parsers which produce DOM documents, JavaScript data structures, Java data structures, …</li><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>PROTOs as a way to define new classes. PROFILEs/components are a way to add atoms to a core set of features.</li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have knowledge that some languages are not hierarchical, I need more information about how NSM is structured through molecules, that is, how are NSM primes collected. I’ve seen some uses of sentences and collections of sentences create meaning. Those are 2 levels of structure. So let’s compare a NSM sentence to an XML element. I believe an NSM prime may be the same as an XML tag for instance. Thus if we were to construct the most primitive X3D without attributes, we would get default shapes and colors, likely all present in the center of the scene. A transform is like a group without attributes. We probably couldn’t get much visual information from that.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So I think we’re both kind of grasping for 3D meanings which are primitive. I believe I brought up Xtranormal, where you put in scripts an out comes a movie after some time. Xtranormal background scenes chosen in advance, I think, not created. You can have some number of actors in the scene whose mouths and standing bodies follow the script. Geometric primitives might be considered primitives in 3D, but often they are broken down into faces or triangles. Triangles would be broken down into 3 line segments or 3 points (although the newer graphics cards are doing raytracing)—the primitive Shape. There are two potential primitives in Material: Color (over a whole triangle) and Texture (more than one color per triangle). These primitives are affected by shading. There are additional primitives, camera/eye point, light, … my brain ran out of steam. Let’s please collect these for discussion.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Point</p><p class=MsoNormal>Segment</p><p class=MsoNormal>Triangle (partial plane)</p><p class=MsoNormal>Animation/Movement</p><p class=MsoNormal>Color</p><p class=MsoNormal>Eye/View</p><p class=MsoNormal>Light</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The above seem very sight oriented, and thus, not prime. I tried again:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sides which contact at a place,</p><p class=MsoNormal>Side,</p><p class=MsoNormal>3 sides that contact in three places,</p><p class=MsoNormal>When, Move</p><p class=MsoNormal>Inside 3 sides see/feel.</p><p class=MsoNormal>Where something sees,</p><p class=MsoNormal>Many Particles/waves that reveal somethings we can see (help here?).</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Oh, I seem that SEE and HEAR are primes. Hmm. How does a blind person have a meaning of see? How does a deaf person have a meaning of hear?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I think we need some way of labelling molecules for bandwidth savings.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I haven’t figured out zero in terms of primes yet.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I think it would be good to put things in terms of NSM, if only for blind people.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I am reminded of the book that Brian Lopez read that defined all its terms, then proceeded with the rest of the book using those terms.<o:p></o:p></p><p class=MsoNormal><br>Should any effort of the X3D semantics group go towards defining stuff up from the ground? What terms do the standards assume people understand? How much of the understanding is in appinfo and description and thus not currently computable?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What is the appropriate technology to build up from NSM into X3D (XML schema for example)? I’m guessing that XML3D would be a good choice? What do you think?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Note that I have no interest in developing this. I am interested in non-rendered concrete and rendered abstract levels. I am interested in rendering and exploring the results of building a firm *<b>semantic</b>* foundation that X3D will sit upon.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I am interested in NSM as far as sign language goes, but unless we have a decomposition of signs into NSM (a very aggressive work), I am more interested in working on the sign/phoneme level (BVH, mocap, interpolation between key frames) than the meaning level. In other words, if we come up with NSM primes in sign language (ASL is fine), I would be very happy!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>While NSM is rigorous, we can also provide a lot of value with the status quo technology. In other words, I don’t want to build a Peano arithmetic, I want to use what’s already in mathematics and language (I’m an application programmer). I’m with you on don’t invent a new language. I am very wary of what happened to Frege when Russell came up with his paradox, and of Godel’s theorems.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In other words, read “I am a Strange Loop” by Douglas Hofstadter. Or look at the symbol for infinity or a moebius strip.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I believe a worthy task would be to better define NSM abstract levels. That is, how do you define the labels for the categories of NSM primes?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I will continue conversing on this, but am mentally tired now.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</p></div></body></html>