<strong>FIMS</strong> <strong>Media</strong> <strong>SOA</strong> <strong>Framework</strong> Phase1 (Preliminary)of “Elapsed Time” or “Elapsed Units” from the “BOT (Beginning of Tape) is very difficult in practice. The BOTposition itself may be not precise enough. In those cases, typically, the position on material source (e.g. thetape) is indicated by the “TimeCode”, which is a label recorded together with the EditUnit.Although the “TimeCode” mechanism does not provide any certainty about the uniqueness of the pointon the Timeline (the same TimeCode might be repeated) and neither it provides reliable information onDuration (“TimeCode” is not constrained to be continuous), this is the way on which legacy production systemsrely for editing and for saving EDLs (Editing Decision Lists).This is the reason why <strong>FIMS</strong> also supports the indication of TimeCodes for all the cases where the Timelinepositioning deals with material sources.However, it is recommended to also provide, if available, the information in terms of elapsed time or edit units.3.2.7 SecurityANSI INCITS 359-2004 - American National Standard for Information Technology – Role Based AccessControlISO/IEC 27001:2005 - Information technology -- Security techniques -- Information securitymanagement systems -- RequirementsISO/IEC 27002:2005 - Information technology - Security techniques - Code of practice for informationsecurity management (Re-designation of ISO/IEC 17799:2005)MPAA - CONTENT SECURITY - Best Practices - Digital Services 12/31/2009MPAA - CONTENT SECURITY - Best Practices - Post-Production Services (Large) 12/31/2009MPAA - CONTENT SECURITY - Best Practices - Post-Production Services (Small) 12/31/2009MPAA - CONTENT SECURITY - Best Practices - Replication 12/31/2009CategoryTransport protocolsStandardsHTTP 1.0 and 1.1, HTTPS, JMS, FTP, SMTP, and UDPSecurity 3DES, AES, RSAv1.5, SHA-1, MD5, PKCS#12, MPKI, JKS, SSL3.0, and TLS 1.0XML & WebServices<strong>SOA</strong>P 1.1, <strong>SOA</strong>P w/ Attachments, XSLT 1.0, XPath 1.0, XSD 1.0, 1.1, XKMS, WS-IBasic Profile 1.0, WSDL 1.1Private committee documentWorking Draft for review by <strong>FIMS</strong> Rev v1, Nov-16-2010 Page 10 of 89
<strong>FIMS</strong> <strong>Media</strong> <strong>SOA</strong> <strong>Framework</strong> Phase1 (Preliminary)4 OverviewThis specification defines a common approach to the integration of software components in modern mediaproduction facilities is believed to be a fundamental need of the entire media industry.The specification is based on an overall framework for integration of reusable components for multimediacontent production which would support the business functions of the professional media industry. Thisframework for media services includes specific detailed definitions of common media processes.The focus of this specification is on Service Oriented Architecture (<strong>SOA</strong>), and reflects a move by the mediaindustry toward systems that use this approach. <strong>Media</strong> companies are moving towards more rapid adoption ofthese systems because of a need to increase agility in a market where user requirements are changing rapidly.In addition to the need for agility, these companies require the increased maintainability, scalability andextensibility that a Service Oriented approach would provide.To properly exploit this technology a common framework should be adopted to help ensure integrationinteroperability, interchangeability and reusability of services. This will drastically reduce integration costs, allowusers to more freely choose the most appropriate products on the market at any given time, improvemaintainability, and aid in the adoption of new technologies.Private committee documentWorking Draft for review by <strong>FIMS</strong> Rev v1, Nov-16-2010 Page 11 of 89