From bf105a6a55ab8a8a7442502119851b4851f8d063 Mon Sep 17 00:00:00 2001 From: James Sandford Date: Fri, 30 Jan 2026 17:07:02 +0000 Subject: [PATCH 1/2] Add clarification on the meaning of the presence or otherwise of the `container` Flow property, previously only stated in AppNote0006. --- api/schemas/flow-core.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/api/schemas/flow-core.json b/api/schemas/flow-core.json index 2ad77c37..ba8a8146 100644 --- a/api/schemas/flow-core.json +++ b/api/schemas/flow-core.json @@ -85,7 +85,7 @@ }, "container": { - "description": "The container MIME type for Flow Segments. Note that the `type` component of the container MIME type (i.e. the component before the `/`) may be different to the `type` component of the codec MIME type. e.g. An audio Flow may have `audio/aac` coded content may be wrapped in a `video/mp2t` container. Where multiple types exist for a subtype (e.g. `video/mp4`, `audio/mp4`, `application/mp4`), the closest MIME type to the Flow `format` should be used (e.g. `audio/mp4` for a Flow `format` of `urn:x-nmos:format:audio`). Mime types from the [IANA registry](https://www.iana.org/assignments/media-types/media-types.xhtml) should be preferred. Where multiple MIME types are possible, the most common should be preferred. Where this is insufficient, the maintainers of the TAMS repository may create an application note advising which MIME type to use.", + "description": "The container MIME type for Flow Segments. Note that the `type` component of the container MIME type (i.e. the component before the `/`) may be different to the `type` component of the codec MIME type. e.g. An audio Flow may have `audio/aac` coded content may be wrapped in a `video/mp2t` container. Where multiple types exist for a subtype (e.g. `video/mp4`, `audio/mp4`, `application/mp4`), the closest MIME type to the Flow `format` should be used (e.g. `audio/mp4` for a Flow `format` of `urn:x-nmos:format:audio`). Mime types from the [IANA registry](https://www.iana.org/assignments/media-types/media-types.xhtml) should be preferred. Where multiple MIME types are possible, the most common should be preferred. Where this is insufficient, the maintainers of the TAMS repository may create an application note advising which MIME type to use. Where the Flow does not reference any Media Object(s) directly (e.g. an empty Multi Flow that serves only to collect related mono-essence Flows that do reference Media Objects), this property MUST NOT be set.", "$ref": "mime-type.json" }, "avg_bit_rate": From 06d56d189980ecd2fdaa6caa83ca9a5687d5bd7f Mon Sep 17 00:00:00 2001 From: James Sandford Date: Fri, 30 Jan 2026 17:07:26 +0000 Subject: [PATCH 2/2] Fix typo in AppNote0006 --- docs/appnotes/0006-containers-and-mappings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/appnotes/0006-containers-and-mappings.md b/docs/appnotes/0006-containers-and-mappings.md index d40f5545..700fdfcf 100644 --- a/docs/appnotes/0006-containers-and-mappings.md +++ b/docs/appnotes/0006-containers-and-mappings.md @@ -16,7 +16,7 @@ This Application Note applies to TAMS v5.0+. ### Flow `container` Property The Flow `container` property serves 2 purposes. -The `container` property identifies the container type for the Media bjects and its presence flags whether the Flow directly references Media Objects. +The `container` property identifies the container type for the Media Objects and its presence flags whether the Flow directly references Media Objects. The `container` property is a [MIME type](https://datatracker.ietf.org/doc/html/rfc6838). Example values are `video/mp2t` for MPEG-TS, `video/mp4` for MP4 and `application/json` for JSON.