<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body dir="auto">
<div dir="auto">Hi Colin,</div>
<div dir="auto"><br>
</div>
<div dir="auto">I will be happy to update the book and should have the update available on Monday.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Best regards,</div>
<div dir="auto">-Erik</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div id="composer_signature" dir="auto">
<div style="font-size:85%;color:#575757">Sent via my phone</div>
</div>
<div dir="auto"><br>
</div>
<div><br>
</div>
<div style="font-size:100%;color:#000000" dir="auto"></div>
<div style="font-size:100%;color:#000000" dir="auto"></div>
<div style="font-size:100%;color:#000000" dir="auto"></div>
<div style="font-size:100%;color:#000000" dir="auto"></div>
<div style="font-size:100%;color:#000000" dir="auto"></div>
<div style="font-size:100%;color:#000000" dir="auto"><!-- originalMessage -->
<div>-------- Original message --------</div>
<div>From: Colin.Haddow@esa.int </div>
<div>Date: 2/28/20 1:17 AM (GMT-08:00) </div>
<div>To: Marcin.Gnat@dlr.de </div>
<div>Cc: "Barkley, Erik J (US 3970)" <erik.j.barkley@jpl.nasa.gov>, smwg@mailman.ccsds.org
</div>
<div>Subject: [EXTERNAL] RE: [cssm] Updates:- Abstract Event Definition Book, Service Management Common data Entities Book, SMURF Book, UML Model, XML Schema.
</div>
<div><br>
</div>
</div>
<span style="font-size:10pt; font-family:sans-serif">Hi Erik,</span> <br>
<span style="font-size:10pt; font-family:sans-serif"> with respect to the "UNR::" I agree with you, it makes sense to use this as a generic "escape clause" for unregistered values. Will you do the tweaks to the books or do you want me to do it
?</span> <br>
<br>
<span style="font-size:10pt; font-family:sans-serif">Cheers for now,</span> <br>
<br>
<span style="font-size:10pt; font-family:sans-serif">Colin</span> <br>
<span style="font-size:10pt; font-family:sans-serif"><br>
<br>
---------------------------------------------------------------------------------------------------------<br>
Dr. Colin R. Haddow,<br>
HSO-GDI, European Space Agency,<br>
European Space Operations Centre,<br>
Robert-Bosch-Str 5,<br>
64293 Darmstadt,<br>
Germany.<br>
<br>
Phone; +49 6151 90 2896<br>
Fax; +49 6151 90 3010<br>
E-Mail; colin.haddow@esa.int<br>
---------------------------------------------------------------------------------------------------------<br>
</span><br>
<br>
<br>
<br>
<span style="font-size:9pt; color:#5f5f5f; font-family:sans-serif">From: </span><span style="font-size:9pt; font-family:sans-serif"><Marcin.Gnat@dlr.de></span>
<br>
<span style="font-size:9pt; color:#5f5f5f; font-family:sans-serif">To: </span><span style="font-size:9pt; font-family:sans-serif"><erik.j.barkley@jpl.nasa.gov></span>
<br>
<span style="font-size:9pt; color:#5f5f5f; font-family:sans-serif">Cc: </span><span style="font-size:9pt; font-family:sans-serif"><smwg@mailman.ccsds.org>, <Colin.Haddow@esa.int></span>
<br>
<span style="font-size:9pt; color:#5f5f5f; font-family:sans-serif">Date: </span><span style="font-size:9pt; font-family:sans-serif">28/02/2020 07:16</span>
<br>
<span style="font-size:9pt; color:#5f5f5f; font-family:sans-serif">Subject: </span><span style="font-size:9pt; font-family:sans-serif">RE: [cssm] Updates:- Abstract Event Definition Book, Service Management Common data Entities Book, SMURF Book, UML
Model, XML Schema.</span> <br>
<hr noshade="">
<br>
<br>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">Hi Erik,</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">Thanks for the quick reply…</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">I agree on the the „station“ with you. Unfortunately I used that term in the common sense (like coming from “ground station” which typically denotes
the site).</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">But you are right. There is “site” and there are “stations” and/or “apertures” within the site.
</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">Cheers</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">Marcin</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><a name="_MailEndCompose"></a><span style="font-size:12pt; font-family:Times New Roman"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:10pt; font-family:Tahoma"><b>From:</b> Barkley, Erik J (US 3970) [</span><a href="mailto:erik.j.barkley@jpl.nasa.gov"><span style="font-size:10pt; font-family:Tahoma">mailto:erik.j.barkley@jpl.nasa.gov</span></a><span style="font-size:10pt; font-family:Tahoma">]
<b><br>
Sent:</b> Donnerstag, 27. Februar 2020 20:35<b><br>
To:</b> Gnat, Marcin<b><br>
Cc:</b> smwg@mailman.ccsds.org; Colin.Haddow@esa.int<b><br>
Subject:</b> RE: [cssm] Updates:- Abstract Event Definition Book, Service Management Common data Entities Book, SMURF Book, UML Model, XML Schema.</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:12pt; font-family:Times New Roman"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia">Hello Marcin,</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia">Okay, perhaps we can be reasonably fast on agreeing on not stopping an update that has already been applied ;-) The use case you have cited makes
sense to me. Note that I had to do a tiny translation effort re “station”, as indicated below* -- but I think the update is fine.</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia">Colin,</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia">Any thoughts on the use “UNR::” as more generic practice?</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia">Best regard,</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia">-Erik</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia">*A minor note in terms of terminology from the heavily influenced DSN perspective. Each aperture is in fact, for us, considered to be a “station”
(and this is reflected by our DSS abbreviation for Deep Space Station). I think probably the rationale is that there is more than just the aperture to make tracking happen – certainly there is a fair amount of various bits and pieces of hardware in terms of
microwave mirrors, low-noise amplifiers, az/el drive motors, etc. What is a “site” for us is a Deep Space Communications Complex (DSCC). So relative to SANA Sites and Apertures registry, for DSN, the DSCC is the site and DSS is the aperture. And I think
in the example you cited, Svalbard would be the SANA Site and each antenna would then be the individual apertures.
</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; font-family:Calibri"><b>From:</b> Marcin.Gnat@dlr.de <Marcin.Gnat@dlr.de>
<b><br>
Sent:</b> Wednesday, February 26, 2020 23:06<b><br>
To:</b> Barkley, Erik J (US 3970) <erik.j.barkley@jpl.nasa.gov><b><br>
Cc:</b> smwg@mailman.ccsds.org; Colin.Haddow@esa.int<b><br>
Subject:</b> [EXTERNAL] RE: [cssm] Updates:- Abstract Event Definition Book, Service Management Common data Entities Book, SMURF Book, UML Model, XML Schema.</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:12pt; font-family:Times New Roman"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">Hi Erik,</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">Well, maybe not so fast with stopping an update ;-).</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">As you noticed yourself, the registry is not normative on UML diagram. But also registry is a registry, and of course there is no reason to
<b><u>register</u></b> an antenna with no <i>apertureRef</i>. </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">On the other hand we have our system for actual booking, and there is very strong use case in SMURF for
<i>ServicePackage</i> request (and the same for the <i>PlanningInformation</i> request) where users request a support on specific station, but do not want to decide on specific antenna (assuming they all or most of the antennas fulfill the requirements) in
order to increase a chance of getting confirmation. We use this possibility in our daily scheduling all the time (especially with stations like Svalbard where they have multiple antennas). This topic will increase I assume with new space, where as far I know
it is typical to decide on provider side on assigned assets. </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">So, said all that, I do not think there is any inconsistency between registry and SM/UML.</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">Best Regards</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">Marcin</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:12pt; font-family:Times New Roman"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:10pt; font-family:Tahoma"><b>From:</b> Barkley, Erik J (US 3970) [</span><a href="mailto:erik.j.barkley@jpl.nasa.gov"><span style="font-size:10pt; color:blue; font-family:Tahoma"><u>mailto:erik.j.barkley@jpl.nasa.gov</u></span></a><span style="font-size:10pt; font-family:Tahoma">]
<b><br>
Sent:</b> Mittwoch, 26. Februar 2020 23:42<b><br>
To:</b> Gnat, Marcin; </span><a href="mailto:Colin.Haddow@esa.int"><span style="font-size:10pt; color:blue; font-family:Tahoma"><u>Colin.Haddow@esa.int</u></span></a><span style="font-size:10pt; font-family:Tahoma"><b><br>
Cc:</b> </span><a href="mailto:smwg@mailman.ccsds.org"><span style="font-size:10pt; color:blue; font-family:Tahoma"><u>smwg@mailman.ccsds.org</u></span></a><span style="font-size:10pt; font-family:Tahoma"><b><br>
Subject:</b> RE: [cssm] Updates:- Abstract Event Definition Book, Service Management Common data Entities Book, SMURF Book, UML Model, XML Schema.</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:12pt; font-family:Times New Roman"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia">Dear Colin, Marcin,</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia">Well, perhaps not so fast now with Marcin’s suggested update of the ApertureLocation class definition. In the SANA considerations section of the CDE
we have this:</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia">“…</span><span style="font-size:12pt; font-family:Times New Roman">Although the registry allows for Site Name records with no Aperture Name field records,
for effective use with this Recommended Practice, any referenced Site Name needs to contain at least one Aperture Name field….”</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia">So, okay this is effectively a rule on the SANA registry and of course it is not normative on the UML class diagram. But I am curious as to where
in CSSM we plan to use an ApertureLocation with only a siteRef and no apertureRef – I guess it could be for the (what I expect to be relatively rare) request for an off-line service package where maybe only the siteRef really matters ? </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia">Also, Colin, spelunking in the SANA registries section, there is the unregistered values escape clause (which I think is good) but it only says this
applies to the originating organization and user parameters. Would there be any reason why we would not allow for a siteRef or an apertureRef to be of the form “UNR::NewExperimentalAntenna-01”, for example? I suspect this may in fact have been carried over
from original write up in the SSF book, but perhaps I'm not recalling the reason for restricting unregistered values as indicated here. It seems to me use of “UNR::” to indicate/allow (presumably temporary) use of unregistered values should be a general practice…?</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia">Best regards,</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia">-Erik</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:14pt; color:#004080; font-family:Georgia"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; font-family:Calibri"><b>From:</b> SMWG <</span><a href="mailto:smwg-bounces@mailman.ccsds.org"><span style="font-size:11pt; color:blue; font-family:Calibri"><u>smwg-bounces@mailman.ccsds.org</u></span></a><span style="font-size:11pt; font-family:Calibri">>
<b>On Behalf Of </b></span><a href="mailto:Marcin.Gnat@dlr.de"><span style="font-size:11pt; color:blue; font-family:Calibri"><u>Marcin.Gnat@dlr.de</u></span></a><span style="font-size:11pt; font-family:Calibri"><b><br>
Sent:</b> Tuesday, February 25, 2020 04:43<b><br>
To:</b> </span><a href="mailto:Colin.Haddow@esa.int"><span style="font-size:11pt; color:blue; font-family:Calibri"><u>Colin.Haddow@esa.int</u></span></a><span style="font-size:11pt; font-family:Calibri"><b><br>
Cc:</b> </span><a href="mailto:smwg@mailman.ccsds.org"><span style="font-size:11pt; color:blue; font-family:Calibri"><u>smwg@mailman.ccsds.org</u></span></a><span style="font-size:11pt; font-family:Calibri"><b><br>
Subject:</b> [EXTERNAL] Re: [cssm] Updates:- Abstract Event Definition Book, Service Management Common data Entities Book, SMURF Book, UML Model, XML Schema.</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:12pt; font-family:Times New Roman"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">Dear Colin,</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">I just reviewed the docs (it took me only one month, haha), and I spotted one small thing:</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri"> </span></p>
<ul>
<li><span style="font-size:11pt; color:#004080; font-family:Calibri">In the Common Data Entities Book, the figure showing class diagram of the
<b><i>ApertureLocation</i></b> is not in line with the actual table explaining it below (the change was due to RID 4, which was I believ from me). So the table says correctly, that the
<b><i>siteRef</i></b> is obligatory and the <b><i>apertureRef</i></b> is optional. Unfortunately the diagram shows the opposite and I think this is a typo.</span><span style="font-size:12pt; color:#004080; font-family:Times New Roman">
</span>
<ul>
<li><span style="font-size:11pt; color:#004080; font-family:Calibri">By the way, I just noticed, that also in the SMURF there is a diagram on contraints (Figure 3-9) where there is the same mistake.</span></li></ul>
</li><li><span style="font-size:11pt; color:#004080; font-family:Calibri">The formatting of the table 3-7: when listing future possible values, there are some missing “-“ in front of two lower entries.</span></li></ul>
<span style="font-size:11pt; color:#004080; font-family:Calibri"> </span>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">Except that, I reviewed the constraints again (as desired). The basic constraints seem to fine for me (see only comment above). I think we can live
with that for the moment. I hope we will get also some feedback on that out of our prototyping (by the way, I did not hear anything from Anthony since last teleconference).</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">Also the other constraints seem to be okay, I think for DLR primarily the classes
<b><i>StandingOrder</i></b> and <b><i>PassDailyTime</i></b> (when used together) and the
<b><i>AdditionalUser</i></b> will be of some interest. For other classes I can imagine they may be useful for other agencies and for example for deep space missions. As far I can use my imagination, for such use cases they seem to okay. I won’t have however
any easy way to verify that.</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">Best Regards</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri">Marcin</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:11pt; color:#004080; font-family:Calibri"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:12pt; font-family:Times New Roman"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:10pt; font-family:Tahoma"><b>From:</b> SMWG [</span><a href="mailto:smwg-bounces@mailman.ccsds.org"><span style="font-size:10pt; color:blue; font-family:Tahoma"><u>mailto:smwg-bounces@mailman.ccsds.org</u></span></a><span style="font-size:10pt; font-family:Tahoma">]
<b>On Behalf Of </b></span><a href="mailto:Colin.Haddow@esa.int"><span style="font-size:10pt; color:blue; font-family:Tahoma"><u>Colin.Haddow@esa.int</u></span></a><span style="font-size:10pt; font-family:Tahoma"><b><br>
Sent:</b> Donnerstag, 23. Januar 2020 14:54<b><br>
To:</b> CCSDS Service Mgmt WG<b><br>
Subject:</b> [cssm] Updates:- Abstract Event Definition Book, Service Management Common data Entities Book, SMURF Book, UML Model, XML Schema.</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:12pt; font-family:Times New Roman"> </span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:10pt; font-family:Arial">Dear all,
<br>
I've just uploaded the following updates to CWE;</span><span style="font-size:12pt; font-family:Times New Roman">
</span></p>
<ul>
<li><span style="font-size:10pt; font-family:Arial">Abstract Event Definition Book: Contains all RID updates + changes to schema naming convention + SANA Registry paths. Subject to AD review should be ready for publication.</span><span style="font-size:12pt; font-family:Times New Roman">
</span></li><li><span style="font-size:10pt; font-family:Arial">Service Management Common Data Entities Book: Contains all RID updates + changes to schema naming convention + SANA Registry paths. Subject to AD review should be ready for publication.</span><span style="font-size:12pt; font-family:Times New Roman">
</span></li><li><span style="font-size:10pt; font-family:Arial">SMURF Book Contains changes to Basic start and duration constraints as discussed at last telecon (i.e. merge into one constraint), change use of start and end time to
optional in ICS table + changes to schema naming convention + SANA Registry paths. Does
<b><i>not </i></b> (yet) contain any updates at the individual request type level stating how the start and end times in the header should be used. I think this update is perhaps best left until we're a bit further into the prototyping.</span><span style="font-size:12pt; font-family:Times New Roman">
</span></li><li><span style="font-size:10pt; font-family:Arial">XML Schemas: Contains the schemas updated for the new naming convention and changes to the above books.</span><span style="font-size:12pt; font-family:Times New Roman">
</span></li><li><span style="font-size:10pt; font-family:Arial">UML Model Contains the UML model consistent with the changes to the above books.</span><span style="font-size:12pt; font-family:Times New Roman">
</span></li><li><span style="font-size:12pt; font-family:Times New Roman"> </span></li></ul>
<span style="font-size:10pt; font-family:Arial">These can be found at the following URLs</span><span style="font-size:12pt; font-family:Times New Roman">
</span>
<ul>
<li><span style="font-size:10pt; font-family:Arial">Abstract Event Definition Book: </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Abstract%20Event%20Definition/Red%20Book/Drafts/902x13r1_01.1%20-%20Abstract%20Event%20Definition.doc" target="_BLANK"><span style="font-size:10pt; color:blue; font-family:Arial"><u>https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Abstract%20Event%20Definition/Red%20Book/Drafts/902x13r1_01.1%20-%20Abstract%20Event%20Definition.doc</u></span></a><span style="font-size:12pt; font-family:Times New Roman">
</span></li><li><span style="font-size:10pt; font-family:Arial">Service Management Common Data Entities Book</span><span style="font-size:10pt; color:blue; font-family:Arial"> </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Service%20Management%20Common%20Data%20Entities/Red%20Book/Drafts/902x12r1_01.1%20-%20Service%20Management%20Common%20Data%20Entities.doc" target="_BLANK"><span style="font-size:10pt; color:blue; font-family:Arial"><u>https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Service%20Management%20Common%20Data%20Entities/Red%20Book/Drafts/902x12r1_01.1%20-%20Service%20Management%20Common%20Data%20Entities.doc</u></span></a><span style="font-size:12pt; font-family:Times New Roman">
</span></li><li><span style="font-size:10pt; font-family:Arial">SMURF Book</span><span style="font-size:10pt; color:blue; font-family:Arial"> </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Service%20Management%20Utilization%20Request%20Format/White%20Book/Drafts/902x9w0_10%20-%20Service%20Management%20Utilization%20Request%20Formats.doc" target="_BLANK"><span style="font-size:10pt; color:blue; font-family:Arial"><u>https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Service%20Management%20Utilization%20Request%20Format/White%20Book/Drafts/902x9w0_10%20-%20Service%20Management%20Utilization%20Request%20Formats.doc</u></span></a><span style="font-size:12pt; font-family:Times New Roman">
</span></li><li><span style="font-size:10pt; font-family:Arial">XML Schemas </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Schemas/902Schema%2020200123.zip" target="_BLANK"><span style="font-size:10pt; color:blue; font-family:Arial"><u>https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Schemas/902Schema%2020200123.zip</u></span></a><span style="font-size:12pt; font-family:Times New Roman">
</span></li><li><span style="font-size:10pt; font-family:Arial">UML Model </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/UML%20Model/902UmlModel%2020200123.zip" target="_BLANK"><span style="font-size:10pt; color:blue; font-family:Arial"><u>https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/UML%20Model/902UmlModel%2020200123.zip</u></span></a></li></ul>
<span style="font-size:10pt; font-family:Arial">Note that I've not updated the CPIF with the new schema naming convention and SANA Registry paths. As thats currently out for Agency review that should be handled via a RID.</span><span style="font-size:12pt; font-family:Times New Roman">
<br>
</span><span style="font-size:10pt; font-family:Arial"><br>
Cheers for now,</span><span style="font-size:12pt; font-family:Times New Roman"> <br>
</span><span style="font-size:10pt; font-family:Arial"><br>
Colin</span><span style="font-size:12pt; font-family:Times New Roman"> </span><span style="font-size:10pt; font-family:Arial"><br>
<br>
---------------------------------------------------------------------------------------------------------<br>
Dr. Colin R. Haddow,<br>
HSO-GI, European Space Agency,<br>
European Space Operations Centre,<br>
Robert-Bosch-Str 5,<br>
64293 Darmstadt,<br>
Germany.<br>
<br>
Phone; +49 6151 90 2896<br>
Fax; +49 6151 90 3010<br>
E-Mail; </span><a href="mailto:colin.haddow@esa.int"><span style="font-size:10pt; color:blue; font-family:Arial"><u>colin.haddow@esa.int</u></span></a><span style="font-size:10pt; font-family:Arial"><br>
---------------------------------------------------------------------------------------------------------</span>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:10pt; font-family:Courier New">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:10pt; font-family:Courier New">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:10pt; font-family:Courier New">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span></p>
<p style="margin-top:0px; margin-bottom:0px"><span style="font-size:10pt; font-family:Courier New">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (</span><a href="mailto:dpo@esa.int"><span style="font-size:10pt; color:blue; font-family:Courier New"><u>dpo@esa.int</u></span></a><span style="font-size:10pt; font-family:Courier New">).</span></p>
<p style="margin-top:0px; margin-bottom:0px"></p>
<p style="margin-top:0px; margin-bottom:0px"></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</pre>
</body>
</html>