Chapter Extension - Revision history

Martin.leese: Zapped blank line

2012-10-12T18:03:09Z

Zapped blank line

← Older revision		Revision as of 18:03, 12 October 2012
Line 25:		Line 25:
	CHAPTER002=00:05:00.000		CHAPTER002=00:05:00.000
	CHAPTER002NAME=Chapter 2		CHAPTER002NAME=Chapter 2
-

	== Further Fields ==		== Further Fields ==

Silvia: make chapter spec simpler

2012-10-12T02:51:44Z

make chapter spec simpler

← Older revision		Revision as of 02:51, 12 October 2012
Line 11:		Line 11:
	We therefore propose an extensions to VorbisComment for transporting chapters. We introduce VorbisComment fields called CHAPTERxxx and CHAPTERxxxNAME with xxx being a number between 000 and 999. (1000 chapters are assumed to be sufficient.)		We therefore propose an extensions to VorbisComment for transporting chapters. We introduce VorbisComment fields called CHAPTERxxx and CHAPTERxxxNAME with xxx being a number between 000 and 999. (1000 chapters are assumed to be sufficient.)

-	The value for the CHAPTERxxx field name is the start time of the chapter ~~(Hour:Min:DecimalSeconds), "-->" (U+002D, U+002D, U+003E), and the end time~~ (Hour:Min:DecimalSeconds). See the [[#Examples\|examples]] below.	+	The value for the CHAPTERxxx field name is the start time of the chapter (Hour:Min:DecimalSeconds). See the [[#Examples\|examples]] below.

	The value for the CHAPTERxxxNAME field name is just a text string (8 bit clean UTF-8 encoded values, as is required for VorbisComments).		The value for the CHAPTERxxxNAME field name is just a text string (8 bit clean UTF-8 encoded values, as is required for VorbisComments).
Line 21:		Line 21:
	An example chapter file with two sequential chapters:		An example chapter file with two sequential chapters:

-	CHAPTER001=00:00~~:00.000-->00:05~~:00.000	+	CHAPTER001=00:00:00.000
	CHAPTER001NAME=Chapter 1		CHAPTER001NAME=Chapter 1
-	CHAPTER002=00:05~~:00.000-->00:10~~:00.000	+	CHAPTER002=00:05:00.000
	CHAPTER002NAME=Chapter 2		CHAPTER002NAME=Chapter 2

-	~~Another example chapter file with a chapter and three hierarchically structured subchapters:~~
-
-	~~CHAPTER001=00:00:00.000-->00:06:00.000~~
-	~~CHAPTER001NAME=Chapter 1~~
-	~~CHAPTER002=00:00:00.000-->00:02:00.000~~
-	~~CHAPTER002NAME=Chapter 1.1~~
-	~~CHAPTER003=00:00:02.000-->00:04:00.000~~
-	~~CHAPTER003NAME=Chapter 1.2~~
-	~~CHAPTER004=00:00:04.000-->00:06:00.000~~
-	~~CHAPTER004NAME=Chapter 1.3~~

	== Further Fields ==		== Further Fields ==
Line 47:		Line 37:
	== WebVTT ==		== WebVTT ==

-	A more modern means of specifying chapters ~~is through~~ [http://dev.w3.org/html5/webvtt/#webvtt-file-using-chapter-title-text ~~WebVTT files~~ that use cues with chapter titles].	+	We expect people may also want support for hierarchically structured chapters with subchapters etc. This specification does not support this need. We recommend making use of WebVTT as a chapter format specification to satisfy this need. At a future time we expect a mapping of WebVTT into Ogg to allow for embedding of such files into Ogg, too.
		+
		+	WebVTT is a more modern means of specifying chapters [http://dev.w3.org/html5/webvtt/#webvtt-file-using-chapter-title-text that use cues with chapter titles] and can deal with time overlapping cues.

Martin.leese: /* Further Fields */ Replaced colon to suppress automatic link (to nowhere)

2012-05-06T00:21:38Z

Further Fields: Replaced colon to suppress automatic link (to nowhere)

← Older revision		Revision as of 00:21, 6 May 2012
Line 43:		Line 43:
	* a field to extend chapters with a url to navigate to while listening to a chapter of a podcast:		* a field to extend chapters with a url to navigate to while listening to a chapter of a podcast:

-	CHAPTERxxxURL=http://...	+	CHAPTERxxxURL=http://...<!-- : for colon used to suppress automatic link -->

	== WebVTT ==		== WebVTT ==

	A more modern means of specifying chapters is through [http://dev.w3.org/html5/webvtt/#webvtt-file-using-chapter-title-text WebVTT files that use cues with chapter titles].		A more modern means of specifying chapters is through [http://dev.w3.org/html5/webvtt/#webvtt-file-using-chapter-title-text WebVTT files that use cues with chapter titles].

Martin.leese: /* Further Fields */ Typo

2012-04-11T18:27:08Z

Further Fields: Typo

← Older revision		Revision as of 18:27, 11 April 2012
Line 41:		Line 41:
	Other fields can also be used to support enhanced podcasts:		Other fields can also be used to support enhanced podcasts:

-	* a field to extend chapters with a url to navigate to while listening a chapter of a podcast:	+	* a field to extend chapters with a url to navigate to while listening to a chapter of a podcast:

	CHAPTERxxxURL=http://...		CHAPTERxxxURL=http://...
-

	== WebVTT ==		== WebVTT ==

	A more modern means of specifying chapters is through [http://dev.w3.org/html5/webvtt/#webvtt-file-using-chapter-title-text WebVTT files that use cues with chapter titles].		A more modern means of specifying chapters is through [http://dev.w3.org/html5/webvtt/#webvtt-file-using-chapter-title-text WebVTT files that use cues with chapter titles].

Silvia: added URLs to chapters

2012-04-11T12:32:53Z

added URLs to chapters

← Older revision		Revision as of 12:32, 11 April 2012
Line 36:		Line 36:
	CHAPTER004=00:00:04.000-->00:06:00.000		CHAPTER004=00:00:04.000-->00:06:00.000
	CHAPTER004NAME=Chapter 1.3		CHAPTER004NAME=Chapter 1.3
		+
		+	== Further Fields ==
		+
		+	Other fields can also be used to support enhanced podcasts:
		+
		+	* a field to extend chapters with a url to navigate to while listening a chapter of a podcast:
		+
		+	CHAPTERxxxURL=http://...
		+

	== WebVTT ==		== WebVTT ==

	A more modern means of specifying chapters is through [http://dev.w3.org/html5/webvtt/#webvtt-file-using-chapter-title-text WebVTT files that use cues with chapter titles].		A more modern means of specifying chapters is through [http://dev.w3.org/html5/webvtt/#webvtt-file-using-chapter-title-text WebVTT files that use cues with chapter titles].

Martin.leese: Changed to webvtt-style "-->" timestamp separators (with no whitespace)

2012-03-09T22:16:08Z

Changed to webvtt-style "-->" timestamp separators (with no whitespace)

← Older revision		Revision as of 22:16, 9 March 2012
Line 11:		Line 11:
	We therefore propose an extensions to VorbisComment for transporting chapters. We introduce VorbisComment fields called CHAPTERxxx and CHAPTERxxxNAME with xxx being a number between 000 and 999. (1000 chapters are assumed to be sufficient.)		We therefore propose an extensions to VorbisComment for transporting chapters. We introduce VorbisComment fields called CHAPTERxxx and CHAPTERxxxNAME with xxx being a number between 000 and 999. (1000 chapters are assumed to be sufficient.)

-	The value for the CHAPTERxxx field name is the start time of the chapter (Hour:Min:DecimalSeconds), ~~a dash~~ (U+002D), and the end time (Hour:Min:DecimalSeconds). See the [[#Examples\|examples]] below.	+	The value for the CHAPTERxxx field name is the start time of the chapter (Hour:Min:DecimalSeconds), "-->" (U+002D, U+002D, U+003E), and the end time (Hour:Min:DecimalSeconds). See the [[#Examples\|examples]] below.

	The value for the CHAPTERxxxNAME field name is just a text string (8 bit clean UTF-8 encoded values, as is required for VorbisComments).		The value for the CHAPTERxxxNAME field name is just a text string (8 bit clean UTF-8 encoded values, as is required for VorbisComments).
Line 21:		Line 21:
	An example chapter file with two sequential chapters:		An example chapter file with two sequential chapters:

-	CHAPTER001=00:00:00.000-00:05:00.000	+	CHAPTER001=00:00:00.000-->00:05:00.000
	CHAPTER001NAME=Chapter 1		CHAPTER001NAME=Chapter 1
-	CHAPTER002=00:05:00.000-00:10:00.000	+	CHAPTER002=00:05:00.000-->00:10:00.000
	CHAPTER002NAME=Chapter 2		CHAPTER002NAME=Chapter 2

	Another example chapter file with a chapter and three hierarchically structured subchapters:		Another example chapter file with a chapter and three hierarchically structured subchapters:

-	CHAPTER001=00:00:00.000-00:06:00.000	+	CHAPTER001=00:00:00.000-->00:06:00.000
	CHAPTER001NAME=Chapter 1		CHAPTER001NAME=Chapter 1
-	CHAPTER002=00:00:00.000-00:02:00.000	+	CHAPTER002=00:00:00.000-->00:02:00.000
	CHAPTER002NAME=Chapter 1.1		CHAPTER002NAME=Chapter 1.1
-	CHAPTER003=00:00:02.000-00:04:00.000	+	CHAPTER003=00:00:02.000-->00:04:00.000
	CHAPTER003NAME=Chapter 1.2		CHAPTER003NAME=Chapter 1.2
-	CHAPTER004=00:00:04.000-00:06:00.000	+	CHAPTER004=00:00:04.000-->00:06:00.000
	CHAPTER004NAME=Chapter 1.3		CHAPTER004NAME=Chapter 1.3

Martin.leese: Added section headings and details of format + tidy

2012-03-05T21:08:58Z

Added section headings and details of format + tidy

← Older revision		Revision as of 21:08, 5 March 2012
Line 5:		Line 5:
	Since chapters are used for navigation - in particular to avoid having to listen to large amounts of undesired content in order to get to desired content - it is important that the information about chapters is available at the start of a media file to be able to be displayed without having to decode the media file. Therefore, we regard chapters as header-style metadata.		Since chapters are used for navigation - in particular to avoid having to listen to large amounts of undesired content in order to get to desired content - it is important that the information about chapters is available at the start of a media file to be able to be displayed without having to decode the media file. Therefore, we regard chapters as header-style metadata.

-	Header-style metadata has traditionally been transported in VorbisComment headers inside Ogg.	+	Header-style metadata has traditionally been transported in [[VorbisComment]] headers inside Ogg.

-	We therefore propose an extensions to VorbisComment for transporting chapters. We introduce VorbisComment fields called CHAPTERxxx and CHAPTERxxxNAME with xxx being a number between 000 and 999. We assume 1000 chapters to be sufficient.	+	== Format ==

-	~~An example chapter file~~ with ~~two sequential~~ chapters:	+	We therefore propose an extensions to VorbisComment for transporting chapters. We introduce VorbisComment fields called CHAPTERxxx and CHAPTERxxxNAME with xxx being a number between 000 and 999. (1000 chapters are assumed to be sufficient.)

-	~~CHAPTER001=00~~:00:~~00.000-00~~:05:00.~~000~~	+	The value for the CHAPTERxxx field name is the start time of the chapter (Hour:Min:DecimalSeconds), a dash (U+002D), and the end time (Hour:Min:DecimalSeconds). See the [[#Examples\|examples]] below.
-	~~CHAPTER001NAME=Chapter 1~~	+
-	~~CHAPTER002=00:05:00.000-00:10:00~~.~~000~~	+
-	~~CHAPTER002NAME=Chapter 2~~	+

		+	The value for the CHAPTERxxxNAME field name is just a text string (8 bit clean UTF-8 encoded values, as is required for VorbisComments).

-	~~Another example chapter file with a chapter and three hierarchically structured subchapters~~:	+	This should basically support the same input format that [http://savvyadmin.com/adding-chapters-to-videos-using-mkv-containers/ Matroska chapters] support, too.

-	~~CHAPTER001~~=~~00:00:00.000-00:06:00.000~~	+	== Examples ==
-	~~CHAPTER001NAME~~=~~Chapter 1~~	+
-	~~CHAPTER002~~=~~00:00:00.000-00:02:00.000~~	+
-	~~CHAPTER002NAME~~=~~Chapter 1.1~~	+
-	~~CHAPTER003=00:00:02.000-00:04:00.000~~	+
-	~~CHAPTER003NAME=Chapter 1.2~~	+
-	~~CHAPTER004=00:00:04.000-00:06:00.000~~	+
-	~~CHAPTER004NAME=Chapter 1.3~~	+

		+	An example chapter file with two sequential chapters:

-	~~This should basically support the same input format that [http~~:~~//savvyadmin~~.~~com/adding~~-~~chapters~~-to-~~videos~~-~~using~~-~~mkv~~-~~containers/ Matroska chapters] support, too~~.	+	CHAPTER001=00:00:00.000-00:05:00.000
		+	CHAPTER001NAME=Chapter 1
		+	CHAPTER002=00:05:00.000-00:10:00.000
		+	CHAPTER002NAME=Chapter 2
		+
		+	Another example chapter file with a chapter and three hierarchically structured subchapters:
		+
		+	CHAPTER001=00:00:00.000-00:06:00.000
		+	CHAPTER001NAME=Chapter 1
		+	CHAPTER002=00:00:00.000-00:02:00.000
		+	CHAPTER002NAME=Chapter 1.1
		+	CHAPTER003=00:00:02.000-00:04:00.000
		+	CHAPTER003NAME=Chapter 1.2
		+	CHAPTER004=00:00:04.000-00:06:00.000
		+	CHAPTER004NAME=Chapter 1.3
		+
		+	== WebVTT ==

	A more modern means of specifying chapters is through [http://dev.w3.org/html5/webvtt/#webvtt-file-using-chapter-title-text WebVTT files that use cues with chapter titles].		A more modern means of specifying chapters is through [http://dev.w3.org/html5/webvtt/#webvtt-file-using-chapter-title-text WebVTT files that use cues with chapter titles].

Martin.leese: Fixed broken link

2012-03-05T19:54:41Z

Fixed broken link

← Older revision		Revision as of 19:54, 5 March 2012
Line 1:		Line 1:
-	Chapters are a means of providing direct and semantically relevant navigation points for a media file. On particular use case are so-called http://en.wikipedia.org/wiki/Enhanced_podcast "enhanced podcasts"], i.e. audio files with additional chapter markers.	+	Chapters are a means of providing direct and semantically relevant navigation points for a media file. On particular use case are so-called [http://en.wikipedia.org/wiki/Enhanced_podcast "enhanced podcasts"], i.e. audio files with additional chapter markers.

	Chapters are typically provided for a recorded file, not for a live resource.		Chapters are typically provided for a recorded file, not for a live resource.

Silvia: started specification

2012-03-05T09:48:48Z

started specification

New page

Chapters are a means of providing direct and semantically relevant navigation points for a media file. On particular use case are so-called http://en.wikipedia.org/wiki/Enhanced_podcast "enhanced podcasts"], i.e. audio files with additional chapter markers.

Chapters are typically provided for a recorded file, not for a live resource.

Since chapters are used for navigation - in particular to avoid having to listen to large amounts of undesired content in order to get to desired content - it is important that the information about chapters is available at the start of a media file to be able to be displayed without having to decode the media file. Therefore, we regard chapters as header-style metadata.

Header-style metadata has traditionally been transported in VorbisComment headers inside Ogg.

We therefore propose an extensions to VorbisComment for transporting chapters. We introduce VorbisComment fields called CHAPTERxxx and CHAPTERxxxNAME with xxx being a number between 000 and 999. We assume 1000 chapters to be sufficient.

An example chapter file with two sequential chapters:

CHAPTER001=00:00:00.000-00:05:00.000
CHAPTER001NAME=Chapter 1
CHAPTER002=00:05:00.000-00:10:00.000
CHAPTER002NAME=Chapter 2

Another example chapter file with a chapter and three hierarchically structured subchapters:

CHAPTER001=00:00:00.000-00:06:00.000
CHAPTER001NAME=Chapter 1
CHAPTER002=00:00:00.000-00:02:00.000
CHAPTER002NAME=Chapter 1.1
CHAPTER003=00:00:02.000-00:04:00.000
CHAPTER003NAME=Chapter 1.2
CHAPTER004=00:00:04.000-00:06:00.000
CHAPTER004NAME=Chapter 1.3

This should basically support the same input format that [http://savvyadmin.com/adding-chapters-to-videos-using-mkv-containers/ Matroska chapters] support, too.

A more modern means of specifying chapters is through [http://dev.w3.org/html5/webvtt/#webvtt-file-using-chapter-title-text WebVTT files that use cues with chapter titles].