Glossary and Terminology

A glossary of terms and definitions used in OMSS Core.

The Spec

The current Open Media Streaming Specification, including the current specification version (currently v1.1). When documentation refers to “the spec”, it always refers to the latest published version of the Open Media Streaming Specification.

OMSS Plugin

A plugin that extends the functionality of OMSS Core. Plugins provide additional capabilities, such as new transport protocols, or adding new functionality to the OMSS Server instance.

Resolver

A component that takes an ID and returns metadata about the media associated with that ID. Resolvers are responsible for resolving OMSS IDs to metadata, which can then be used by providers to locate media.

OMSS ID

OMSS identifiers follow the format <namespace>:<value_1>:<value_2>:...:<value_n>. Values can contain any character except colons and whitespaces. If a value or namespace contains a forbidden character, it must be URI-encoded (%3A for colons and %20 for whitespaces).

Namespace

A string that identifies the ID-Provider that issued the OMSS ID. Namespaces are used to differentiate between different ID-Providers and their respective identifier values.

Examples:

• tmdb
• imdb
• omdb

In the ID tmdb:12345, tmdb is the namespace.

Certain namespaces may be reserved by OMSS. These reservations include what values in what order are allowed in a given namespace. See the latest list here.

ID-Provider

A third-party service capable of providing metadata for a given ID. ID-Providers own one or more namespaces and are responsible for issuing the identifier values used throughout OMSS.

Examples include TMDB and IMDb.

Provider

A file within a consumer repository that receives resolver data and returns one or more streaming sources. Providers implement the logic required to locate media using the metadata supplied by resolvers.

OMSS Server

The primary class of OMSS Core responsible for loading, managing, and coordinating OMSS Plugins and other components. The OMSS Server serves as the central runtime responsible for plugin registration, dependency management, and execution.

Consumer

A client application that integrates and uses OMSS Core. Consumers are responsible for invoking resolvers and providers to obtain playable streaming sources for users.

Extractor

An object that can be injected into the OMSS Server that contains the logic required to extract playable media from a specific content hoster. Extractors encapsulate host-specific extraction behavior so it can be reused across multiple providers.