<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=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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-top:0cm;
margin-right:0cm;
margin-bottom:10.0pt;
margin-left:0cm;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
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;}
span.EmailStyle17
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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 bgcolor="white" lang="EN-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Dear Carey and Fran,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">We at NRCan (GSD) look forward to participating in these discussions. For many years we have been using XML to control the state of our real-time data exchange environment and most recently have adopted XML
to inject meta data into a new RINEX 3 application. Ken MacLeod and Stuart Elson will provide NRCan’s input.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Mark Caissy<o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal">
<b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> Fran Boler [mailto:boler@unavco.org]
<br>
<b>Sent:</b> January 9, 2015 12:01<br>
<b>To:</b> IGS-DCWG@igscb.jpl.nasa.gov<br>
<b>Cc:</b> Yehuda Bock; msquibb@ucsd.edu; David Maggert; Gary Johnston; Gary Mize; Nacho Romero; artur.oruba@gugik.gov.pl; bradke@gfz-potsdam.de; Caissy, Mark; Chuck Meertens<br>
<b>Subject:</b> Invitation to participate - IGS metadata exchange via XML<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:normal">Author: Fran Boler, Carey Noll<br>
<br>
<br>
Dear Colleagues-<br>
<br>
As many of you know, at the IGS workshop in Pasadena this past June there was discussion in the infrastructure and data center breakouts about transmitting IGS site log metadata between data centers using XML, using automated machine-to-machine transfer mechanisms.
With the introduction of the IGS Site Log Manager system, we believe the time is right to do this. Advantages could include more rapid updating of site log information, more consistent information across data centers, and more accurate metadata overall. Several
data centers are committed to moving forward on this effort in the next few months. In order to implement such an exchange the first step will be to agree on the XML schema to be used. SOPAC has had a longstanding geodesy XML project (<a href="http://sopac.ucsd.edu/xmlGeodesy.shtml">http://sopac.ucsd.edu/xmlGeodesy.shtml</a>),
and this is the ideal starting point. We would like to kickoff this effort by requesting feedback on the SOPAC Site Log XML schema.
<br>
<br>
Those who would like to participate in this effort should respond with an email (to IGS-DCWG at igscb.jpl.nasa.gov) as soon as possible indicating your interest.
<b>Please mention your level of involvement as: “observer” or “planning to participate in the discussions” or “planning to participate in discussions and work on implementation”.
</b>(Note: If you, as an igs-dcwg list member, do not have an interest in this topic, you may wish to change your subscriber option to digest for this list, or otherwise amend your subscription as there will be additional traffic during this effort.)<br>
<br>
For those who will be active at this phase, please look at the SOPAC Site Log XML schema and plan to provide comments to this list within one month. Your comments should include any suggested amendments or additions. As a rough timeline we would like to complete
discussions of the schema during February and begin discussing implementation specifics no later than March.<br>
<br>
We wish to be inclusive and therefore ask you to circulate this invitation to interested colleagues. All interested persons should ensure that they are members of the igs-dcwg maillist by visiting
<a href="http://igscb.jpl.nasa.gov/mailman/listinfo/igs-dcwg">http://igscb.jpl.nasa.gov/mailman/listinfo/igs-dcwg</a>.<br>
<br>
Kind regards,<br>
Fran Boler, IGS Governing Board Data Center Representative<br>
Carey Noll, IGS Data Center Working Group Chair<br>
<br>
<span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p></o:p></span></p>
</div>
</body>
</html>