DOCSEARCHbyAlgolia
Submit Docs

MovieLabs Documentation

website·Indexed 35 days ago

https://mc.movielabs.com

Technical specifications and standards for media creation, featuring the Ontology for Media Creation (versions 1.0 through 2.7) and the Common Security Architecture for Production (versions 1.0 through 1.2). Documentation covers CG assets, camera metadata, narrative and production objects, zero-trust security architectures, and identity management.

Tokens
403.2K
Snippets
686
Records
2.6K
Agent score
51%

What's inside MovieLabs

  1. Overview of the Ontology for Media Creation (OMC)

    v2.0
    The Ontology for Media Creation (OMC) provides consistent naming, definitions, and relationship models for production workflows. It is designed to enable interoperability between software, organizations, and people by providing common data models and schemas for data exchange in media production.

  2. Overview of the MovieLabs Security Architecture Framework

    v1.0
    The MovieLabs security architecture is a framework for building implementations divided into two primary groupings: core security components that secure production workflows, and supporting security components (typically provided by hyper-scale cloud providers or security-as-a-service vendors) that provide requisite functionality to the core components. The architecture is designed so that users in a production workflow rarely interact directly with security components; instead, core security components connect to the workflow management system to determine and authorize activities based on defined interfaces.

  3. Overview of MovieLabs Common Security Architecture for Production (CSAP)

    v1.2
    The Common Security Architecture for Production (CSAP) is a workflow-driven, zero-trust security architecture designed for cloud production. It employs a 'deny-by-default' security posture where authorization policies are dynamically created in response to the immediate requirements of a Software-Defined Workflow (SDW). In this model, the workflow management core of the SDW initiates the creation of the authorization policies that permit specific activities.

  4. Overview of the MovieLabs Security Architecture framework

    v1.0

    The MovieLabs Security Architecture is a framework designed to protect cloud production workflows where assets and processing are stored and run in the cloud. It is structured into five parts to guide implementers, studios, and auditors:

    • Part 1: Architecture Description: General overview and goals.
    • Part 2: Interfaces: Canonical forms of interfaces between modules.
    • Part 3: Security Levels: A metric-based approach to scaling security.
    • Part 4: Security and the Software-Defined Workflow: Application of security to workflows managed via a service bus.
    • Part 5: Implementation Considerations: Options for implementing the architecture.

  5. Overview of the MovieLabs Visual Language for Media Creation (VLMC)

    v1.0
    The MovieLabs Visual Language for Media Creation (VLMC, or Visual Language) provides a common language—defining concepts and grammar—to express ideas in workflow diagrams. It is designed to facilitate Human-to-Human, Machine-to-Human (e.g., status dashboards), and Human-to-Machine (e.g., programming automated workflows) communication. It is intended for users drawing workflow diagrams, those conveying production concepts, and developers creating software to view or modify these workflows.

  6. Overview of the MovieLabs Cloud Security Architecture Framework (CSAP)

    v1.1

    The Cloud Security Architecture Framework (CSAP) provides a reference architecture for securing assets and processes in cloud workflows for movie and TV content production. It is designed for internet-accessible compute and storage infrastructure, whether hosted by hyperscale providers, private data centers, or on-premises solutions. The framework is divided into six parts:

    1. Architecture Description: High-level overview and goals.
    2. Interfaces: Canonical forms of interfaces between modules.
    3. Security Levels: Metric-based approach to scaling security.
    4. Securing Software-Defined Workflows: Application of the architecture to service-bus managed workflows.
    5. Implementation Considerations: Options for implementing the architecture.
    6. Policy Description Language: Specifications for defining policies.

  7. Overview of MovieLabs Visual Language for Media Creation

    v1.0
    The MovieLabs Visual Language for Media Creation is a standardized communication system designed for consistent diagramming across studios, service vendors, software developers, and tools companies. It defines a specific set of shapes, labels, icons, lines, and arrowheads to ensure diagrams are universally understood within the media creation pipeline. The language is closely linked to a common ontology to maintain semantic consistency.

  8. Overview of the Ontology for Media Creation (OMC)

    v1.0
    The Ontology for Media Creation (OMC) provides consistent naming, definitions, and relationship models for production workflows. It is designed to enable interoperability between software supporting collaboration and automation in media production by providing common data models and schemas for data exchange.

  9. Overview of Camera Metadata in MovieLabs Ontology

    Camera Metadata is classified as a type of Digital Asset. It describes the shooting configuration of a camera (e.g., log vs. linear color) and is essential for the correct interpretation of image data downstream. This metadata is used to determine the correct LUT (Look-Up Table) to apply to log images to avoid 'flat' results. It may include information from the camera body, attached lenses (such as aperture and focus distance), recorders, and external inputs like timecode.

  10. Overview of the MovieLabs Cloud Security Architecture (CSAP)

    v1.2

    The Cloud Security Architecture (CSAP) is a framework designed to protect cloud-based media production where assets and processing are stored and run in the cloud. It focuses on ensuring that only authenticated and authorized activity (such as network connections) occurs via Policy Enforcement Points. The architecture is divided into several parts:

    • Part 1: Architecture Description
    • Part 2: Interfaces (canonical forms between modules)
    • Part 3: Security Levels (metric-based scaling)
    • Part 4: Securing Software-Defined Workflows (service bus management)
    • Part 5: Implementation Considerations
    • Part 6: Policy Description

  11. Overview of CSAP v1.3 Architecture Parts

    The Content Security Architecture Panel (CSAP) v1.3 is organized into six functional parts to guide the implementation of security in media creation workflows:

    • Part 1: Architecture Description: The primary architecture document.
    • Part 2: Interfaces: Defines canonical interfaces between modules.
    • Part 3: Security Levels: Provides a metric-based approach to scaling security.
    • Part 4: Securing Software-Defined Workflow: Application of security architecture to service-bus managed workflows.
    • Part 5: Implementation Considerations: Practical guidance on implementing CSAP, divided into three sub-sections:
      • 5A (Starting Out): General guidance, CSAP Implementation Basics, and the Zero-trust Foundation (ZTF).
      • 5B (CSAP Core): Implementation of Identity, Authentication, Authorization, and Authorization Rule Distribution Services (ARDS), and User Experience.
      • 5C (Approaches): Guidance on Network usage, Access Controls, and End-to-End security on untrusted infrastructure.
    • Part 6: Policy Description: Defines policies and rules (Note: Not published as of July 2023).

  12. Overview of the CSAP Zero-Trust Architecture

    v1.2
    The Collaboration-oriented Security Architecture for Production (CSAP) is a zero-trust security architecture designed to protect assets, processes, and workflows in media production. It focuses on intrinsic security, meaning it protects production artifacts regardless of whether the underlying infrastructure is trusted. CSAP operates on a 'deny-by-default' principle where authorization rules are used specifically to enable activity.