[Sois-app] Additional slide for MILBUS presentation from Fall meeting

[Richard Melvin]

I wrote up an extra slide for that presentation, based on dscussion and
thoughts during the meeting. It shows exactly what the various XML
syntax options on an interface _currently_ imply about the interaction
patterns of that interface.

 

 

 

 

Notes:

*         For generality, the MO patterns are missing the one (EVENT?)
where the remote system just sends you a message without prompting
(which I think is handled as a special  case within MO, but that makes
them hard to reuse outside). 

*         Transaction id shouldn't be unconditionally mandatory, as it
is at present. Ideally should be validated according to the table.

*         One combination of options is meaningless and ideally should
be rejected at validation.

*         There is some redundancy where the same interactions and
messages could be defined as either a parameter or command. That would
be reduced a bit if we made async commands with no input arguments
illegal.

*         There are several patterns it is not possible to represent in
an EDS interface; presumably these would be necessary to handle MTS.

 

The complete presentation is available as:

 

http://cwe.ccsds.org/sois/docs/SOIS-APP/Meeting%20Materials/2014/Fall/SO
IS%20EDS%20and%20MIL-STD-1553.pptx

 

 

 

 



SCISYS UK Limited. Registered in England and Wales No. 4373530.
Registered Office: Methuen Park, Chippenham, Wiltshire SN14 0GB, UK.
 
Before printing, please think about the environment.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sois-app/attachments/20141117/5dd73a5c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 22220 bytes
Desc: image001.png
URL: <http://mailman.ccsds.org/pipermail/sois-app/attachments/20141117/5dd73a5c/attachment.png>