<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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt">Hi Pierre,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Thanks for the explanation. That background makes sense to me, and I support the suggestion to give legal ASCII MOCs the same constraints as FITS MOCs by simply removing that sentence.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Tom<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><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:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black"><apps-bounces@ivoa.net> on behalf of Pierre Fernique <Pierre.Fernique@astro.unistra.fr><br>
<b>Date: </b>Tuesday, June 18, 2019 at 10:12 AM<br>
<b>To: </b>Applications WG <apps@ivoa.net><br>
<b>Subject: </b>MOC ASCII well-formed or not.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Hi Tom & apps members,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Concerning your comment on ASCII MOC on the RFC page,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<p class="MsoNormal">Maybe the former was just a legacy from MOC 1.0 where ASCII MOC was
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">less formal, perhaps intended for hand-crafted MOCs not intended for
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">serious use. With ASCII MOC now being formalized, can we remove that
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">sentence and require that ASCII MOCs must be just as well-formed as
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">their FITS counterparts? <o:p></o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As an ASCII MOC is often written by hand (in a Web form for instance, or
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">as an Aladin script command), it was difficult to insure that it is
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">always well formed at this level. Is it an ASCII MOC, yes, but
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">potentially not well formed (ex: 3/1-210) . So the tools which have to
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">manipulate such ASCII MOCs must check before used. At the opposite, FITS
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">MOC is always generated by a code. So there is a real interest to force
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">it to be stored well-formed for accelerating the future reloads.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">That said, you right that it is a little bit inhomogeneous, and the
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">ASCII MOCs will be used in other contexts that just for forms and
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">scripts. So we can considere that an ASCII MOC written by hand is not -
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">strickly speaking an ASCII MOC (not serialized in a file) - and in this
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">consideration - extend the well-formed constraint to all serialized MOC
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">formats (FITS & ASCII) by just removing the sentence.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">How does it sound ?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Cheers<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Pierre<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>