<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:"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;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
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;}
@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:448399491;
mso-list-type:hybrid;
mso-list-template-ids:2083185314 -1 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a><br><b>Sent: </b>Monday, June 10, 2019 4:17 AM<br><b>To: </b><a href="mailto:semantics@web3d.org">semantics@web3d.org</a><br><b>Subject: </b>Dispense of top-level semantic relationships quickly!</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sorry, I joined late. I did post a few things to x3d-public. I think before we invent the future, we need to forget what we know, and look into the past (paraphrase from quote of Alan Kay):<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><ol style='margin-top:0in' start=1 type=1><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>We should use the UML class diagram relationship types (and potentially other diagram elements) as top level relationships between classes. We get IS_A and HAS_A from this. <a href="https://creately.com/blog/diagrams/class-diagram-relationships/">https://creately.com/blog/diagrams/class-diagram-relationships/</a> This will allow us to handle things like XML and X3DUOM schemas, I believe. This would also give us stereotypes from UML, or special icons for classes (I think the was a goal at one point). We do not need to reinvent domain specific visual languages—that is done with stereotypes in UML. Unless of course, you want to create a 3D-4D DSVL.<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>We should use Conceptual Dependency (from Shank, 1969) <a href="https://en.wikipedia.org/wiki/Conceptual_dependency_theory">https://en.wikipedia.org/wiki/Conceptual_dependency_theory</a> <o:p></o:p></li></ol><p class=MsoNormal><a href="https://deepblue.lib.umich.edu/bitstream/handle/2027.42/30278/0000679.pdf;jsessionid=5045F32362513C64F4FBFC0BA441CB6C?sequence=1">https://deepblue.lib.umich.edu/bitstream/handle/2027.42/30278/0000679.pdf;jsessionid=5045F32362513C64F4FBFC0BA441CB6C?sequence=1</a> at least the set of primitive actions (predicates) which are intended for describing the real world in natural language. That is, natural language is close to semantics and how the layman describes reality. This will allow us to describe the semantics of animations which depend on primitive actions (animation “scripts”).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1 and 2 comprise the “top level” of any more concrete or domain-specific predicates. Can we list 10-20 predicates that all of our subsequent predicates will inherit from, and the relationships between the 10-20 predicates?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Are we discussing the semantics of dynamic and static scenes? Do we need separate semantics, or combined semantics?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I do not think that Shank had the answer in 1969. There’s a whole lot more if you consider eco-systems, networks, and worlds. (Actors comes to mind). There’s especially a desire to describe emergent behavior, like eating ½ an apple (thanks to Bart Kosko), breaking a leaf apart (a dream of mine), or dragging one’s hand through the water (thanks to Ted Nelson). How do you describe exceptions in terms of semantics?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Do we want to be able to query large databases of video, such as is used in developing Tesla’s autopilot software? What are people using for that?<o:p></o:p></p><p class=MsoNormal><br>I expect us to blow off the bottom of these stages in complexity, but first, let’s beg, borrow or steal a top level framework.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href="https://en.wikipedia.org/wiki/Model_of_hierarchical_complexity#Stages_of_hierarchical_complexity">https://en.wikipedia.org/wiki/Model_of_hierarchical_complexity#Stages_of_hierarchical_complexity</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Do people feel we should work with a Model-View-Controller or Input-Processing-Storage-Output pattern first? Are we merely talking about View-Controller and Input-Output, or is there some Model/Processing/Storage involved? Shapes and Transforms come to mind for Models. Can we toss all our data into 5 bins? Can we reuse these names, or do we need names like Sensor, Node, Script, Route? Are there cross-bin classes?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have a particular interest in creating a Taxonomy of Sensors or Controllers, if no one else is taking this. Does anyone have references beyond: <a href="https://www.nap.edu/read/4782/chapter/16">https://www.nap.edu/read/4782/chapter/16</a> <a href="https://en.wikipedia.org/wiki/Robotic_sensors#Classification">https://en.wikipedia.org/wiki/Robotic_sensors#Classification</a> I think that adding sensor groups, group/individual oriented sensors and discrete/continual (Thanks Leonard Daly)/continuous sampling are important properties to express.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I can share my knowledge with the group RE: Hypermedia, Stocamedia, Chaomedia, and Quantumedia, and the 3 primitive media types, if needed. These are mainly focused on data generators. In my current role, I am a Senior Systems Generator (trying to go across systems paradigms). Mostly I generate scripts in the short term, but hope to extend this to languages, systems and networks as I work with Gina-Lauren or Christoph Valentin. In a previous life, I worked on Capacity Planning Systems.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As I generate additional systems, I expect the input devices to catch up to me, and then the ways that users and robots interact with the system.<i><o:p></o:p></i></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>