<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;}
.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;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hello,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Re: unique naming and hierarchical structure in HelloWorld.ttl<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks, Don, for this important work.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So my understanding is the hierarchical structure of the document will be retained in the unique names? What happens to nodes named by DEF then? How will they be placed back into the hierarchy for roundtripping?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Who is roundtripping from .ttl to .x3d?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Re: JavaScript API</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Please suggest an appropriate API for parsing X3D model .ttl files with JavaScript. N3.js???</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Is it recommended that I create a JavaScript API for reading in .ttl files using the X3DUOM, similar to X3DLoaderDOM.java? X3DLoaderTTL.js? Or something more like X3DTTLLD.js which translates to a DOM document?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Please provide architecture expertise. Otherwise, I may start applying Daffodil (DFDL) to TTL.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</p><p class=MsoNormal> </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:brutzman@nps.edu">Brutzman, Donald (Don) (CIV)</a><br><b>Sent: </b>Tuesday, October 8, 2019 11:35 AM<br><b>To: </b><a href="mailto:semantics@web3d.org">semantics@web3d.org</a><br><b>Cc: </b><a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Re: [Semantics] Minutes X3D Semantic Web 7 OCT 2019: X3D Ontologyimprovements review, X3dToTurtle.xslt plans</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>each of these improvements have been applied. as expected, unique naming fixed the first query for HelloWorld (which gives 2 nodes now).</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>checked in and updated online.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 10/7/2019 9:14 AM, Brutzman, Donald (Don) (CIV) wrote:</p><p class=MsoNormal>> [...]</p><p class=MsoNormal>> - website:</p><p class=MsoNormal>> </p><p class=MsoNormal>> https://www.web3d.org/x3d/content/semantics/semantics.html</p><p class=MsoNormal>> </p><p class=MsoNormal>> 4. *XSLT*</p><p class=MsoNormal>> </p><p class=MsoNormal>> - We agreed on the naming convention, which allows tracing query results back to the original X3D model.</p><p class=MsoNormal>> </p><p class=MsoNormal>> - We discussed whether base IRI is required. In the HelloWorld.ttl initial example, it is marked</p><p class=MsoNormal>> </p><p class=MsoNormal>> @prefix : <https://www.web3d.org/semantics/scenes/X3dScene1#> .</p><p class=MsoNormal>> </p><p class=MsoNormal>> We might do something with the meta identifier (if it exists), e.g.</p><p class=MsoNormal>> </p><p class=MsoNormal>> <meta content='http://X3dGraphics.com/examples/X3dForWebAuthors/Chapter01TechnicalOverview/HelloWorld.x3d' name='identifier'/></p><p class=MsoNormal>> </p><p class=MsoNormal>> becomes</p><p class=MsoNormal>> </p><p class=MsoNormal>> @prefix : <http://X3dGraphics.com/examples/X3dForWebAuthors/Chapter01TechnicalOverview/HelloWorld.ttl> .</p><p class=MsoNormal>> </p><p class=MsoNormal>> which also matches the Web address where it will exist. This can be automated for all models in X3D Example Archives.</p><p class=MsoNormal>> </p><p class=MsoNormal>> We can have stylesheet switches that omits or overrides such a value, depending on the person/tool converting.</p><p class=MsoNormal>> </p><p class=MsoNormal>> Therefore, over the next week HelloWorld.ttl will change accordingly. Since it is in version control, we can always re-check prior versions.</p><p class=MsoNormal>> </p><p class=MsoNormal>> https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/semantics/examples/HelloWorld.ttl</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>all the best, Don</p><p class=MsoNormal>-- </p><p class=MsoNormal>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu</p><p class=MsoNormal>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</p><p class=MsoNormal>X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman</p><p class=MsoNormal>-- </p><p class=MsoNormal>Semantics mailing list</p><p class=MsoNormal>Semantics@web3d.org</p><p class=MsoNormal>http://web3d.org/mailman/listinfo/semantics_web3d.org</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>