<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii"><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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>DAI folks: This morning I had an action to get some orientation info on Electronic Data Sheets (EDSs). Ramon Krosley’s text below and the two attachments are the result. Open for discussion at the next telecon. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The PPT addresses a lot of stuff related to Functional Resource Models, but there are several charts on EDSs. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='color:#002060'> -=- Mike<o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Mike Kearney</span><span style='color:#002060'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'>Huntsville, Alabama, USA <o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> <a href="mailto:r.krosley@andropogon.org">r.krosley@andropogon.org</a> <<a href="mailto:r.krosley@andropogon.org">r.krosley@andropogon.org</a>> <br><b>Sent:</b> Tuesday, March 28, 2023 12:27 PM<br><b>To:</b> <a href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a><br><b>Subject:</b> RE: Electronic Data Sheets<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It’s true the EDS describe interfaces at a level of detail that enables generation of software objects. Artemis is using EDS in this way for software components. EDS can also be used to describe software and hardware components for configuration into assemblies. The attached draft green book draft describes how EDS can be applied; some parts of it are more detailed than you may want, but you can disregard those parts. <o:p></o:p></p><p class=MsoNormal>The current schema for EDS allows for semantic tags to be applied to data that passes through interfaces, to describe how to use the data. I think that this information could be useful to DAI, because software artifacts do not generally provide this information explicitly. The information can distinguish a set point (purpose=setpoint) for a control loop from a measurement (purpose=measurement) in that control loop, which is important for interpreting archived data. Units of measure and quantity kinds can be applied to data items to avoid errors that could cause loss of mission, as happened in the Mars Climate Orbiter mission when a command was sent with the wrong unit of measure. These semantic tags are optional.<o:p></o:p></p><p class=MsoNormal>I have attached Peter Shames’ charts, which were used during the discussion of applying EDS in the functional resource model (FRM) in 2021. My thought was that EDS could describe the proxy agents (see chart 12) for adapting the FRM to earth space link terminals in various agencies. The EDS would be used to generate concrete software objects for implementing the proxy agents. John Pietras agreed. Other participants were not so sure. I have not heard of further discussions on this topic for many months. The FRM is written in ASN.1, which describes interfaces abstractly. There are tools for making more concrete descriptions from ASN.1 files, but some folks thought that EDS could also be used to combine the abstraction and concretization information, making FRM more directly applicable to each agency’s software tools.<o:p></o:p></p><p class=MsoNormal>Ramon<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> <a href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a> <<a href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a>> <br><b>Sent:</b> Tuesday, March 28, 2023 9:26 AM<br><b>To:</b> <a href="mailto:r.krosley@andropogon.org">r.krosley@andropogon.org</a><br><b>Cc:</b> 'Frederick Slane' <<a href="mailto:frederick.slane@gmail.com">frederick.slane@gmail.com</a>><br><b>Subject:</b> Electronic Data Sheets<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Ray: When I was at Dubai, I saw a presentation (from Marcin Gnat, I believe) from the Cross Supt Svc Mgt WG that had the attached slide in it. It states that Electronic Data Sheets are being used to describe interfaces. I had previously thought that EDSs were used for operational system configuration, not to describe interfaces. As a result, I’ve started a discussion in DAI about whether we should consider using EDSs to describe interfaces. The problem is… nobody in DAI knows anything about EDSs. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Is there a document that SOIS uses to describe the basic (beginner) concepts of an EDS? <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Is it true that EDSs are used to describe software interfaces? If so, can you fill me in a little bit on how that works? <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='color:#002060'> -=- Mike<o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal>Mike Kearney<span style='color:#002060'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'>Huntsville, Alabama, USA <o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>