[MOIMS-NAV-EXEC] [CCSDS] Action 32

Mon Jun 11 17:14:55 UTC 2018

Hi All:
Regarding action 32: Define schema that can be used with an XML editor to define events and parameters that go with it to validate the event description.

Find attached the following files:

-          NEM_Test_20180610.xml: contains the XML file that is meant for users to define the collection of events at high level.

This has the following repetitive structure (I have used ascending node as example) to be generated easily with an XML editor. This is the seed for the generation of the corresponding XML schema to validate the final evnets file consistently with the definitions (fo events and parameters) discussed with the CSS group (Colin Haddow et al.)
        <event type="ASCENDING_NODE">
            <annotation>Date when the satellite is at the ascending node of the orbit (defined by ascending through ITRF equator)</annotation>
            <parameters>
                <parameter name="longitude" type="ndm:longitudeType" mandatory="false">
                    <annotation>Longitude at the time of the event</annotation>
                </parameter>
            </parameters>
        </event>

The fields <annotation> are optional

The block <parameters> is optional (either not present or empty) for events with no parameters

-          NEMUserDefinitionFile.xsd: is the XML schema that validates the previous file. It should be used to validate the user generated file (previous one) prior to attempt the generation of the final events file schema.

-          NEMDefinitions.xsd: has the basic definitions for the implementation of events. Essentially the event and epoch abstract types as defined

-          NEMUserDefinitionFile.xsl: implements the XSL transformation (XSLT) that generates the XML schema file that validates the actual NEM files from NEM_Test_20180610.xml. To test the generation:

o   Use an XML editor like XMLSpy or Oxygen (there may be other, even free, but I have not investigated) to load the NEM_Test_20180610.xml and apply the XSL transformation using NEMUserDefinitionFile.xsl. This will deliver the corresponding XML schema that should be very similar to NEM_Test_20180610.xsd

o   Use Xalan (in a linux console). Put the files in a folder and exert the command:

xalan -in NEM_Test_20180610.xml -xsl NEMUserDefinitionFile.xsl -out test.xsd -indent 2

this should generate a file test.xsd almost identical to NEM_Test_20180610.xsd

-          NEM_Test_20180610.xsd: the XML schema for the validation of the events file created from the NEM_Test_20180610.xml and the XSL transformation in NEMUserDefinitionFile.xsd

-          instance1.xml: This is an example of an events file. Just load it in an XML editor or a web browser like IE to verify its validity. The XML schemas NEM_Test_20180610.xsd (and all other .xsd files) should be in the same folder as instance1.xml

-          ndmxml*.xsd: supporting files to include the schema in the NAVGS workspace and to reuse existing basic defined types.

The basic operation sequences:

-          Create an events user definitions file similar to NEM_Test_20180610.xml

-          Apply the XSL transformation (e.g. with xalan); this generates the actual events XML schema

-          Create an events file similar to instance1.xml

-          Validate the events file with the generated XML schema

The file that closes the actions is essentially NEMUserDefinitionFile.xsd that is complemented with NEMUserDefinitionFile.xsl to generate the final XML schema.
The implementation should be compatible with the principles discussed with CSS although the XML is different as we already saw at the spring meeting in Gaithersburg. This may be a point of discussion with CSS in the next meeting but we are probably one step ahead of them in the actual implementation. We still need to define the list of proposed event acronyms if this is the path to follow.

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/20180611/0bd37278/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NEMDefinitions.xsd
Type: text/xml
Size: 7536 bytes
Desc: NEMDefinitions.xsd
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180611/0bd37278/attachment.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ndmxml-1.0-ccsds-common-revA.XSD
Type: text/xml
Size: 9738 bytes
Desc: ndmxml-1.0-ccsds-common-revA.XSD
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180611/0bd37278/attachment-0001.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ndmxml-1.0-navwg-common-revA.XSD
Type: text/xml
Size: 20726 bytes
Desc: ndmxml-1.0-navwg-common-revA.XSD
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180611/0bd37278/attachment-0002.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NEM_Test_20180610.xml
Type: text/xml
Size: 5414 bytes
Desc: NEM_Test_20180610.xml
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180611/0bd37278/attachment-0003.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NEM_Test_20180610.xsd
Type: text/xml
Size: 13508 bytes
Desc: NEM_Test_20180610.xsd
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180611/0bd37278/attachment-0004.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NEMUserDefinitionFile.xsl
Type: text/xml
Size: 3416 bytes
Desc: NEMUserDefinitionFile.xsl
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180611/0bd37278/attachment-0005.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: instance1.xml
Type: text/xml
Size: 4719 bytes
Desc: instance1.xml
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180611/0bd37278/attachment-0006.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NEMUserDefinitionFile.xsd
Type: text/xml
Size: 1583 bytes
Desc: NEMUserDefinitionFile.xsd
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180611/0bd37278/attachment-0007.xml>