<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hi Scott <div>Which presentation are you referring to?</div><div>I was in WG12 meetings last week.</div><div>Thanks</div><div>Tom Thurman<br><br><div dir="ltr">Sent from my iPhone</div><div dir="ltr"><br><blockquote type="cite">On Jun 29, 2023, at 7:27 AM, Martin Hardwick <hardwick@steptools.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>Hi Scott,</p>
<p>I am also trying to sort it out. Clearly the end-user is very
reluctant to use any kind of naming scheme which means that any
connection between STEP, MTConnect and QIF will have to be
represented by up to three UUID's.</p>
<p>In principle, this is OK, but trying to manage things by UUID
number is going to be tedious/difficult. <br>
</p>
<p>I note that the Internet made IP addresses manageable by giving
its address numbers equivalent domain names, and by allowing
descriptive text strings to be included in URL's.</p>
<p>Perhaps we need to do the same. Perhaps JSON is a solution.
Perhaps every new UUID needs to be registered with every entity
that is listening.</p>
<p>ST-UUID/MT-UUID/QP-UUID where ST-UUID is the prototype
definition, MT-UUID is the twin instance, and QP-UUID is a
measurement<br>
</p>
<p>And it would be nice to know that ST-UUID is the definition of a
distance dimension (which one?), MT-UUID is a product that has
been machined (which one?), and QP-UUID is a measure of the
dimension (which one?).<br>
</p>
<p>Martin<br>
</p>
<div class="moz-cite-prefix">On 6/28/2023 11:47 AM, Truitt, Scott
wrote:<br>
</div>
<blockquote type="cite" cite="mid:PH2P110MB08762A65D255B6313C312B3A9924A@PH2P110MB0876.NAMP110.PROD.OUTLOOK.COM">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style>@font-face { font-family: "Cambria Math"; }
@font-face { font-family: Calibri; }
p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif; }
span.EmailStyle17 { font-family: Calibri, sans-serif; color: windowtext; }
.MsoChpDefault { font-family: Calibri, sans-serif; }
div.WordSection1 { page: WordSection1; }</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Martin,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In my effort to understand what was
presented today I tried to imagine what the data structure
would look like for a given instance. I use the Json format,
it’s what understand, to map it out in my head. Just wanted to
send to see if I’m on the right train of thought.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#595959">Scott
Truitt<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#595959">Sr.
Project Manager<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#595959">Advanced
Technology International<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#7F7F7F">315
Sigma Drive<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#7F7F7F">Summerville,
SC 29486<br>
843.760.4620<o:p></o:p></span></p>
<p class="MsoNormal"><img alt="image001.png" src="cid:part1.cuLlYURK.f9qln1Q3@steptools.com"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<hr>
<font size="1" face="Arial" color="Gray"><br>
Business Sensitive Communication: The contents of this
communication and any attachments hereto are intended solely for
the addressee(s) and may contain ATI proprietary and/or business
sensitive information. It is strictly forbidden to use, copy, or
share any part of this communication or the attachments other
than for the intended business purpose or with the express
consent of the sender. If you have received this communication
in error, please notify the sender and delete all copies of this
communication and any attachments.<br>
</font>
</blockquote>
<pre class="moz-signature" cols="72">--
Martin Hardwick
President STEP Tools, Inc.
Cell: 518 253-0596
"There are billions of STEP files and millions of STEP-NC files"</pre>
<span>_______________________________________________</span><br><span>step-manufacturing mailing list</span><br><span>step-manufacturing@steptools.com</span><br><span>http://lists.steptools.com/mailman/listinfo/step-manufacturing</span><br></div></blockquote></div></body></html>