[MOIMS-NAV-EXEC] [CCSDS] NEM Small Prototype

Thu Apr 12 13:32:35 UTC 2018

Hi all.

After the discussions on the possible approach for the NEM we held on Tuesday, I tried a small prototype. I have followed Frank's idea on the definition of the list of events and associated parameters and then also (but partial) the CSS approach that they have taken in their implementation.
The attached files are:

-          Event_User_Definition_File.xml: this is start point of Frank's concept. A simple XML that identifies the list of events. All that is needed in this files is the event mnemonic and in the cases where there are parameters, the list of parameters with their names, types and the mandatory flag. With this information it is possible to construct each event compliant with the UML definition by CSS.

-          Event_User_Definition_File.xsd: the XML schema file that validates the previous one. In this manner the user will always be certain that the produced definition file is compliant with expected structure before transforming it.

-          Event_User_Definition_File.xsl: the XSLT transformation that converts the user definitions into the actual XML schema for the implementation of the events. In this prototype is produces a complete XML schema file but it is possible to produce just the events part in a generic manner such that it can be imported by a high level schema (like our ndm-master and ndm-namespace).

-          Event_Definition_Instance.xsd: the automatically generated events XML schema from the user definition and by the XSLT transformation.

-          Event_Definition_Template.xsd: the XML schema hosting the abstract part of the XML event type and some other common generic definitions (equivalent to our ndm-nav-common and ndm-ccsds-common).

-          NEM_Example.xml: sample file auto-generated compliant with the generated events schema.

Some remarks:

-          The prototype does not adhere to our NDM structure. This would be easy.

-          It does not include the namespaces as we have in or messages. Mandatory but easy.

-          I have built the events as in CSS case; event type is the actual XML tag.

-          The selection of elements vs. attributes is for the moment arbitrary prevailing making the prototype fast over any actual technical criteria.

-          There are elements that are of simple type (e.g. xs:double) but I have also added one case of an extended type (supported by the xs:any in CSS definitions). It seems to be feasible and works.

-          I have noticed that Alain's way of identifying events is not always possible. For instance, 15DEG_AOS is not possible because XML tags cannot start with a digit (XML are necessarily of type NCName that limits it syntax)

The prototype is far from exhaustive in out definitions (in particular for the different types of epoch definitions). It is meant to be just an input to the discussion on how to proceed with the NEM design.

Best regards,
Fran

P Please consider the environment before printing this e-mail.

______________________
This message including any attachments may contain confidential 
information, according to our Information Security Management System,
 and intended solely for a specific individual to whom they are addressed.
 Any unauthorised copy, disclosure or distribution of this message
 is strictly forbidden. If you have received this transmission in error,
 please notify the sender immediately and delete it.

______________________
Este mensaje, y en su caso, cualquier fichero anexo al mismo,
 puede contener informacion clasificada por su emisor como confidencial
 en el marco de su Sistema de Gestion de Seguridad de la 
Informacion siendo para uso exclusivo del destinatario, quedando 
prohibida su divulgacion copia o distribucion a terceros sin la 
autorizacion expresa del remitente. Si Vd. ha recibido este mensaje 
 erroneamente, se ruega lo notifique al remitente y proceda a su borrado. 
Gracias por su colaboracion.

______________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180412/72b267ca/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Event_Definition_Instance.xsd
Type: text/xml
Size: 5387 bytes
Desc: Event_Definition_Instance.xsd
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180412/72b267ca/attachment.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Event_User_Definition_File.xsl
Type: text/xml
Size: 2110 bytes
Desc: Event_User_Definition_File.xsl
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180412/72b267ca/attachment-0001.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Event_User_Definition_File.xml
Type: text/xml
Size: 850 bytes
Desc: Event_User_Definition_File.xml
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180412/72b267ca/attachment-0002.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Event_Definition_Template.xsd
Type: text/xml
Size: 3565 bytes
Desc: Event_Definition_Template.xsd
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180412/72b267ca/attachment-0003.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Event_User_Definition_File.xsd
Type: text/xml
Size: 923 bytes
Desc: Event_User_Definition_File.xsd
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180412/72b267ca/attachment-0004.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NEM_Example.xml
Type: text/xml
Size: 3778 bytes
Desc: NEM_Example.xml
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180412/72b267ca/attachment-0005.xml>