<font size=2 face="sans-serif">Hi Miyano-san,</font>
<br><font size=2 face="sans-serif">The Concept book and Guidelines are
in a very advanced shape and close to publication. For the Magenta books,
eventually documenting the CSTS API, I have some question marks in
my mind:</font>
<br>
<ul>
<li><font size=2 face="sans-serif">For SLE the goal was to have interchangeable
software components implementing standardized APIs , but to the best of
my knowledge component exchange has not been exercised (except for proof
of concept)</font>
<li><font size=2 face="sans-serif">Which programming language would you
suggest for APIs? SLE uses C++. Currently ESA is developing a CSTS SFW
implementation in Java 8. However, clearly without standardized APIs.</font>
<li><font size=2 face="sans-serif">Which benefit do you see in standardizing
the APIs?</font>
<li><font size=2 face="sans-serif">Which role do you see for UML / SysML
from the view point of the a standardization body like the CCSDS / CSTS
WG? Is it rather documentation or also standardization?</font>
<li></ul><font size=2 face="sans-serif">I am happy to discuss that in more
detail, in Berlin we should find the time to do that.</font>
<br>
<br><font size=2 face="sans-serif">Best regards,</font>
<br><font size=2 face="sans-serif">Holger</font>
<br>
<br><font size=2 face="sans-serif">Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | S-431<br>
+49 6151 90 2233 | </font><a href=http://www.esa.int/esoc><font size=2 face="sans-serif">http://www.esa.int/esoc</font></a>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">YOSHIKAZU MIYANO <miyano.yoshikazu@jaxa.jp></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">css-csts@mailman.ccsds.org</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">05/09/2018 11:11</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [Css-csts]
WebEx meeting changed: CSTS Telecon #2</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"CSS-CSTS"
<css-csts-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Holger-san,<br>
<br>
Thank you for having a slot. 30 minute(10:45 - 11:15) is enough including<br>
discussion, because developing gateway will take several years and <br>
discussion<br>
will not be concluded just in one workshop.<br>
Before meeting in Berlin, I will send several page slides including<br>
following discussion points to mailing list.<br>
a) Documentation Priorities<br>
Which documents is highly prioritized after current drafts (Concept <br>
Book, Guideline,<br>
TD-CSTS, FF-CSTS) are documented ? When will API books be documented
if <br>
they are<br>
prioritized?<br>
b) MBSE/MBD<br>
If developing gateway is approved within JAXA, I will manage the <br>
development by Model Based<br>
Development in order for agencies to check the projects of UML/SysML <br>
tools. Wiithout<br>
disagreement, JAXA will design the gateway using Enterprise Architect
<br>
by SparxSystems, which is mostly used in Japan Manufacturing Industry<br>
<br>
Regards,<br>
<br>
Miyano<br>
<br>
<br>
<br>
<br>
On 2018/09/05 14:55, Holger.Dreihahn@esa.int wrote:<br>
> Hi Miyano-san,<br>
> Nice to hear from you. Of course you can have a slot on Tuesday morning<br>
> for a presentation, I suggest to use the session after the coffee
break in<br>
> the morning to lunch (10:45 - 12:30). That leaves some room for a<br>
> discussion afterwards. Looking at your summary, there might be indeed
some<br>
> things to discuss.<br>
><br>
> Regards,<br>
> Holger<br>
><br>
> Holger Dreihahn<br>
> European Spacecraft Operations Centre | European Space Agency | S-431<br>
> +49 6151 90 2233 | </font></tt><a href=http://www.esa.int/esoc><tt><font size=2>http://www.esa.int/esoc</font></tt></a><tt><font size=2><br>
><br>
><br>
><br>
> From: YOSHIKAZU MIYANO <miyano.yoshikazu@jaxa.jp><br>
> To: css-csts@mailman.ccsds.org<br>
> Date: 05/09/2018 06:10<br>
> Subject: Re: [Css-csts] WebEx meeting changed:
CSTS Telecon #2<br>
> Sent by: "CSS-CSTS" <css-csts-bounces@mailman.ccsds.org><br>
><br>
><br>
><br>
> Holger-san,<br>
><br>
> I will join tomorrow's telecon as soon as another telecon will be<br>
> finished.<br>
><br>
> Regarding CSTS meeting in Berlin, it possible for me to have<br>
> 10 minute presentation related to MD-CSTS implementation in the morning
of<br>
> Tuesday?<br>
> I wish to have presentation based on following summary, but I hesitate<br>
> to do because MD-CSTS and SFW BB were published last year.<br>
><br>
> Summary:<br>
> JAXA does not decide whether MD-CSTS should be implemented especially
from<br>
> Service<br>
> Provider Side. However, Service User Side in JAXA currently studies
how to<br>
> implement<br>
> MD-CSTS gateway to have interoperability with other agencies.<br>
> Apart from interoperability with legacy systems within JAXA, I recognize<br>
> the following<br>
> issues to decide.<br>
> 1) FR SANA Registry<br>
> The following FR, example described in MD-CSTS BB, should be approved<br>
> from "provisional".<br>
> – Antenna;<br>
> – Forward Space Link Carrier Transmission;<br>
> – Forward TC PLOP, Sync, and Channel Encoding;<br>
> – Forward CLTU Transfer Service Provider;<br>
> – Return Space Link Carrier Reception;<br>
> – Return TM Synchronization and Decoding;<br>
> – Return All Frames Transfer Service Provider;<br>
> – Monitored Data CSTS Provider; and<br>
> – Monitored Data Collection.<br>
> 2)Application Program Interface MB books<br>
> Equivalent books of SLE API MB should be documented in order to be<br>
> interoperable<br>
> between agencies. I wish to confirm whether tech notes such
as FR<br>
> reference model exists<br>
> and whether documents of prototyping in MD-CSTS BB can be applied
to parts<br>
> of API books.<br>
><br>
> Regards,<br>
><br>
> Miyano<br>
><br>
><br>
><br>
><br>
<br>
_______________________________________________<br>
CSS-CSTS mailing list<br>
CSS-CSTS@mailman.ccsds.org<br>
</font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br>
<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>