<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 12 (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 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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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>
<!--[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=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Mario,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>In principle I tend to agree with your notion of using well
recognized industry terms rather than having CCSDS invent equivalent terms. What
gives me pause are the practicalities. The general computer industry moves very
rapidly as compared to space missions. I think that I would be more comfortable
agreeing to recommend that there be a bit of the deliberative process in
governance and adoptions of terminology for CCSDS in general. I think the
largest area for overlap with regard to industry recognized terminology re
CCSDS most likely lies within the service oriented architecture (presumably “SOA”
is an industry-standard term with a lot of effort behind it) realm of computing,
but here again there is in fact no authoritative resource to point to exact
definitions at least that I am aware of. I can readily uncover many
acronyms servers related to computer terms by doing a quick Google search and
therefore have no confidence as to the authority of one site versus another. So,
do we say that <a href="http://www.soaglossary.com/">http://www.soaglossary.com/</a>
is authoritative and CCSDS relies on this? Or do we prefer the much
shorter set of terms found via <a
href="http://www.soa-in-practice.com/soa-glossary.html">http://www.soa-in-practice.com/soa-glossary.html</a>
? Or perhaps we look to sister standards bodies likeW3C, OMG etc., to
help with this? If so, this would then argue for a bit of a liaison type
process as well for maintenance issues etc.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>So at the end of the day, my conclusion is that in fact only
CCSDS can really say what is authoritative with regard to its terminology. It
may be that we borrow rather heavily here and there on some of the
"definitions of the day" but we may have to apply a little bit of
elbow grease so to speak to capture them as formal CCSDS definitions such that
CCSDS books reference a proper glossary, and that we agree on the definition even
though it is “well-recognized”. So, again, in principle I
agree with you but I'm just a little concerned about the practicalities
involved. Now, an ontology for this might be interesting….</span><span
style='font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>As perhaps an interesting related suggestion we could also
perhaps consider getting the robotic mission scenarios identified by RASIG as
part of the general CCSDS vocabulary. There are indeed I believe multiple cases
whereby classifications and profiles of missions would be useful and it would
be nice to see this being used with regard to common terminology.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Best regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>-Erik<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Mario.Merri@esa.int
[mailto:Mario.Merri@esa.int] <br>
<b>Sent:</b> Friday, September 24, 2010 5:48 AM<br>
<b>To:</b> Barkley, Erik J (317H)<br>
<b>Cc:</b> 'Colin.Haddow@esa.int'; CCSDS RA SIG; Leo.Hartman@asc-csa.gc.ca;
Nestor.Peccia@esa.int; Shames, Peter M (313B); roger.thompson@scisys.co.uk;
Sam.Cooper@scisys.co.uk<br>
<b>Subject:</b> RE: RASIG/SM+C Overlap Telecon #1 Notes<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Erik,</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>not to be
pedant, but my point on Red ID 1 was more than just the glossary. Do you agree
with the entire point as described in my email below?</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Ciao</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>__Mario</span> <br>
<br>
<o:p></o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>From:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"Barkley,
Erik J (317H)" <erik.j.barkley@jpl.nasa.gov></span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>To:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"Mario.Merri@esa.int"
<Mario.Merri@esa.int></span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>Cc:</span> <o:p></o:p></p>
</td>
<td style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"'Colin.Haddow@esa.int'"
<Colin.Haddow@esa.int>, CCSDS RA SIG
<CSS-RASG@mailman.ccsds.org>, "Leo.Hartman@asc-csa.gc.ca"
<Leo.Hartman@asc-csa.gc.ca>, "Nestor.Peccia@esa.int" <Nestor.Peccia@esa.int>,
"Shames, Peter M (313B)" <peter.m.shames@jpl.nasa.gov>,
"roger.thompson@scisys.co.uk" <roger.thompson@scisys.co.uk>,
"Sam.Cooper@scisys.co.uk" <Sam.Cooper@scisys.co.uk></span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>Date:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>24/09/2010
09:00</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>Subject:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>RE:
RASIG/SM+C Overlap Telecon #1 Notes</span><o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" noshade style='color:#A0A0A0' align=center>
</div>
<p class=MsoNormal><br>
<br>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080'>Mario,</span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080'>Thanks
very much for the comments. Re Rec ID 1: Glossary update and
maintenance – agree and I will update this in the spreadsheet.</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080'>Re
Rec ID 2: I will see what I can do about the timeframe question.
Obviously sooner is better, but, as we know, resources are not exactly
plentiful in CCSDS so I will have to check with the membership of SMWG and see
what seems reasonable/feasible. Consider this an action on my part.</span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080'>Best
regards,</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080'>-Erik</span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080'> </span>
<br>
<b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Mario.Merri@esa.int
[</span><a href="mailto:Mario.Merri@esa.int"><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>mailto:Mario.Merri@esa.int</span></a><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>] <b><br>
Sent:</b> Thursday, September 23, 2010 9:31 PM<b><br>
To:</b> Barkley, Erik J (317H)<b><br>
Cc:</b> 'Colin.Haddow@esa.int'; CCSDS RA SIG; Leo.Hartman@asc-csa.gc.ca;
Nestor.Peccia@esa.int; Shames, Peter M (313B); roger.thompson@scisys.co.uk;
Sam.Cooper@scisys.co.uk<b><br>
Subject:</b> Re: RASIG/SM+C Overlap Telecon #1 Notes</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
My comments:</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
Rec. ID 1</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
I believe we agreed that on one hand CCSDS has "domain-specific"
terminology (e.g. telemetry, return services) which must be preserved. On the
other hand, when the terminology overlaps with more generic domains (e.g.
services) where the industry standards are worldwide consolidated, we should
give preference the these in order to make the CCSDS specifications clearer and
unambiguous. We also agreed that the revamping of CCSDS glossary is a very much
needed activity which should provide a set of unambiguous terms that are used
across CCSDS specs and that should be maintained under configuration control.
Clearly, we are not there yet and a, once the glossary will be available, a
long-term plan should be made so that all specs could be migrated to use
consistent terminology.</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
Rec. ID 2</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
I know that we have not discussed at the telecon, but it would be nice to
time-frame the agreed exercise to test MAL as a re-factoring technology for SM.
</span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
Ciao</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
__Mario</span> <o:p></o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td width="3%" valign=top style='width:3.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>From:</span> <o:p></o:p></p>
</td>
<td width="96%" valign=top style='width:96.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"Barkley,
Erik J (317H)" <erik.j.barkley@jpl.nasa.gov></span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>To:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"'Mario.Merri@esa.int'"
<Mario.Merri@esa.int>, "Shames, Peter M (313B)"
<peter.m.shames@jpl.nasa.gov>, "Sam.Cooper@scisys.co.uk"
<Sam.Cooper@scisys.co.uk>, "Leo.Hartman@asc-csa.gc.ca"
<Leo.Hartman@asc-csa.gc.ca></span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>Cc:</span> <o:p></o:p></p>
</td>
<td style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>CCSDS
RA SIG <CSS-RASG@mailman.ccsds.org>, "Nestor.Peccia@esa.int"
<Nestor.Peccia@esa.int>, "'Colin.Haddow@esa.int'"
<Colin.Haddow@esa.int>, "roger.thompson@scisys.co.uk"
<roger.thompson@scisys.co.uk></span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>Date:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>24/09/2010
02:21</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>Subject:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>RASIG/SM+C
Overlap Telecon #1 Notes</span><o:p></o:p></p>
</td>
</tr>
</table>
<p><br>
<o:p></o:p></p>
<p class=MsoNormal align=center style='text-align:center'><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" noshade style='color:#A0A0A0' align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<br>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
CCSDS Colleagues,</span> <span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
</span> <span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
Following is a brief summary with regard to our teleconference on Wednesday, 22
September 2010. The bulk of the teleconference conclusions have been
captured in the summaries on the Excel spreadsheet (under the column
"draft conclusions"). Obviously this is just my take so please
provide corrections as you deem necessary.</span> <span style='font-size:10.0pt;
font-family:"Calibri","sans-serif"'><br>
</span> <span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
Best regards,</span> <span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
</span> <span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
-Erik</span> <span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
</span> <span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
---Telecon Summary---</span> <span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
</span> <span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
Attendees: S. Cooper, M. Merri, L. Hartman, P. Shames, E. Barkley</span> <span
style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
</span> <span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
Topics discussed:</span> <span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
Overlaps and SEA AD
Recommendations -- see updated spreadsheet</span> <span style='font-size:10.0pt;
font-family:"Calibri","sans-serif"'><br>
ExoMars Architecture
– key personnel not available for update</span> <span style='font-size:
10.0pt;font-family:"Calibri","sans-serif"'><br>
Telecon Schedule prior
to London – two more telecons to be arranged (done)</span> <span
style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
London face-to-face
meeting – agreed to meeting Tue AM the week of the meetings</span> <span
style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
</span> <span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
</span> <span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
[attachment "d1-SMC-OverlapSolutions-23-Sep-2010.xls" deleted by
Mario Merri/esoc/ESA] </span><o:p></o:p></p>
</div>
</body>
</html>