Media Object Server: Difference between revisions

Revision as of 00:21, 15 May 2024

Latest revision as of 00:25, 15 May 2024

Line 4:

The MOS protocol is based on [[XML]].<ref>{{cite web|last=Qureshi |first=Rizwan |url=http://www.codeproject.com/Articles/34527/MOS-Protocol-Fundamentals |title=MOS Protocol Fundamentals – CodeProject® |publisher=Codeproject.com |date=2009-04-01 |accessdate=2012-05-03}}</ref> It enables the exchange of the following types of messages:<ref>{{cite web|url=http://www.mosprotocol.com/mos_faq.htm#what_does_MOS_do |title=Mos Faq |publisher=Mosprotocol.com |date= |accessdate=2012-05-03}}</ref>

; Descriptive Data for Media Objects. : The MOS "pushes" descriptive information and pointers to the NCSNRCS as objects are created, modified, or deleted in the MOS. This allows the NCSNRCS to be "aware" of the contents of the MOS and enables the NCSNRCS to perform searches on and manipulate the data the MOS has sent.

; Playlist Exchange. : The NCSNRCS can build and transfer playlist information to the MOS. This allows the NCSNRCS to control the sequence that media objects are played or presented by the MOS.

; Status Exchange. : The MOS can inform the NCSNRCS of the status of specific clips or the MOS system in general. The NCSNRCS can notify the MOS of the status of specific playlist items or running orders.

MOS was developed to reduce the need for the development of [[Device driver|device specific drivers]]. By allowing developers to embed functionality and handle events, vendors were relieved of the burden of developing device drivers. It was left to the manufacturers to interface newsroom computer systems. This approach affords broadcasters flexibility to purchase equipment from multiple vendors.<ref>{{cite web|url=http://www.newsmaker.us/TheMOSStory.html |title=Newsmaker |publisher=Newsmaker.us |date= |accessdate=2012-05-03}}</ref> It also limits the need to have [[Computer operator|operators]] in multiple locations throughout the studio as, for example, multiple [[character generator]]s (CG) can be fired from a single control [[workstation]], without needing an operator at each CG console.<ref>{{cite web|url=http://www.enotes.com/topic/Media_Object_Server |title=Media Object Server – eNotes.com Reference |publisher=Enotes.com |date=2002-03-21 |accessdate=2012-05-03}}</ref>