NAB 2013 MOS Group Meeting Notes
Proposal made that should be bidirectional
After brief discussion, this is adopted
2. The meaning of ACK messages
When should it be sent?
When a message is received? When the XML has been validated? When the action has been processed?
A “wait” ACK was proposed
Written MOS Protocol should specify what an ACK means
Suggestion raised for specific exemptions
Shawn Snider (Ross) volunteered to make specific proposals
3. Object and proxy paths
There has been some perceived ambiguity over what the format should be
Decided that the field should be a call that will return the file.
Decided that the character string following the last slash should be the full file name including extension
Discussion of whether to include additional field to designate MIME types
Discussion of permissibility of HTTP client-side redirects
Will be put up for discussion on the board
4. Rest/JSON version of MOS
The proposal of this additional platform for MOS was raised last year.
A few open group discussions have been held since then, with minimal participation and little interest in pursuing work on it.
Consensus of the group was to table the proposal - for now, at least.
5. Replacement of ActiveX as host environment for NCS plug-ins
Raised by Shawn Snider (Ross).
Discussed by the group - with generally positive sentiment
The subject will be posted to MOSPROTOCOL.COM website and MOS Support Board to promote further discussion.