<span style=" font-size:10pt;font-family:sans-serif">Hello<br>
<br>
Having the standard version of the format in the header will allow handling
of backward compatibility.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">I don't think
it is highly critical, as which version shall be used will be part of the
user-provider agreement. So the version information shall already be known
by design.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">But it doesn't
hurt to have it clearly stated in the header.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">I am more worried
by "</span><span style=" font-size:11pt;font-family:Times New Roman">The
version of the information entity. This increments every time an information
entity of the same concrete type, status, and time range is generated (i.e.,
has the same startTime and endTime). NOTE – The version may increment
by 1 every time but is not constrained to do so. The only constraint is
that each version number is greater than the previous.</span><span style=" font-size:10pt;font-family:sans-serif">"<br>
</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Such information
is sensitive to database reset. It requires on its own a complete definition
of its usage to handle discontinuity in the "version" handling.
</span>
<br><span style=" font-size:10pt;font-family:sans-serif">e.g. How do you
trigger a reset of version in case the user/provider DB go out of sync
? How do you handle error detection in its usage.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">That would require
its own standard to be of use.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">As the notion
of entity "version" will only be used for some user/provider,
and its handling will be different for each pair. I think it shall go out
of the standard and inserted as Extended Parameter whenever its presence
is required. Doing so, it will allow to support different "version"
concept in a single implementation as the parameters will have different
names.</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><br>
Regards<br>
________________________________________<br>
Martin UNAL<br>
Ground Operation Manager<br>
Ground Facilities Ops HSO - ONO<br>
H-376<br>
ESOC<br>
Robert-Bosch Strasse 5<br>
64 293 Darmstadt<br>
Germany<br>
Tel +49 6151 90 2959 <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">"Barkley,
Erik J\(US 3970\) via SMWG" <smwg@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"CCSDS
Service Mgmt WG" <smwg@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">08/02/2022
21:25</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">[cssm]
Data format version number?</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">"SMWG"
<smwg-bounces@mailman.ccsds.org></span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia">CSSM
Colleagues,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia">Our
discussion at our latest telecon about versioning the XML Schema in GitHub,
etc. got me thinking as to whether or not we need to include a version
number in the Xml instances with regard to the data format/data entity
itself. Current in the CDE book we have this description for the
version parameter of the SrvMgtHeader class: </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Times New Roman">The
version of the information entity. This increments every time an information
entity of the same concrete type, status, and time range is generated (i.e.,
has the same startTime and endTime). NOTE – The version may increment
by 1 every time but is not constrained to do so. The only constraint is
that each version number is greater than the previous.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia">So
this allows tracking various instances of data entities, but does not identify
that the particular data entity is version 1 or 2, etc of the data format.
Given that this will have to validate against a versioned XML Schema,
it could be argued that format version identifier is not needed. But
then given that XML is about extensibility it seems feasible that an older
instance document could validate against a later schema and so perhaps
the data format version identifier may be of some use. Granted, the XML
instance documents are likely to be rather ephemeral as they are exchanges
about requests for service and/or information/plans being returned at a
particular moment. As mostly an aside, if we were ever to have a JSON version
of our XML instances perhaps the data format version identifier might become
more important?</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia">I
notice that the NAVWG is putting a message Id and version number in as
attributes of the root element – for example, for the OEM (Orbit Ephemeris
Message) the root element is declared like this:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Courier New"><oem
xmlns:xsi="</span><a href="http://www.w3.org/2001/XMLSchema-instance"><span style=" font-size:11pt;font-family:Courier New">http://www.w3.org/2001/XMLSchema-instance</span></a><span style=" font-size:11pt;font-family:Courier New">"</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Courier New">xsi:noNamespaceSchemaLocation="</span><a href="http://sanaregistry.org/r/ndmxml_unqualified/ndmxml-2.0.0-master-2.0.xsd"><span style=" font-size:11pt;font-family:Courier New">http://sanaregistry.org/r/ndmxml_unqualified/ndmxml-2.0.0-master-2.0.xsd</span></a><span style=" font-size:11pt;font-family:Courier New">"</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Courier New">id="CCSDS_OEM_VERS"
version="2.0"></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia">I'm
curious if anyone in the working group has any thoughts or comments about
this.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia">-Erik</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Georgia"> </span><tt><span style=" font-size:10pt">_______________________________________________<br>
SMWG mailing list<br>
SMWG@mailman.ccsds.org<br>
</span></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/smwg"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/smwg</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt></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>