XiphWiki - Recent changes [en]

Questionnaire scratch space

2009-11-18T19:42:22Z

Support: There's a missing parenthesis here, possibly a cut-and-paste error?

← Older revision		Revision as of 19:42, 18 November 2009
Line 162:		Line 162:
	=== Support ===		=== Support ===
	It is critical that the organisation takes responsibility for the formal specification throughout its life span. This can be done in several ways such as for example a regular periodic review of the formal specification. The support criteria relates to the level of commitment the organisation has taken to support the formal specification throughout its life:		It is critical that the organisation takes responsibility for the formal specification throughout its life span. This can be done in several ways such as for example a regular periodic review of the formal specification. The support criteria relates to the level of commitment the organisation has taken to support the formal specification throughout its life:
-	* does the organisation provide support until removal of the published formal specification from public domain (Including this process?	+	* does the organisation provide support until removal of the published formal specification from public domain (Including this process?)
	: '''Xiph.Org standards are never removed from the public domain. Xiph endeavors to provide support for as long as the standard remains in use.'''		: '''Xiph.Org standards are never removed from the public domain. Xiph endeavors to provide support for as long as the standard remains in use.'''
	* does the organisation make the formal specification still available even when in non-maintenance mode?		* does the organisation make the formal specification still available even when in non-maintenance mode?

Questionnaire scratch space

2009-11-18T19:37:10Z

typo fix

← Older revision		Revision as of 19:37, 18 November 2009
Line 144:		Line 144:
	Consensus is decision making primarily with regard to the approval of formal specifications and review with interest groups (non-members). The consensus evaluation criterion is evaluated with the following questions:		Consensus is decision making primarily with regard to the approval of formal specifications and review with interest groups (non-members). The consensus evaluation criterion is evaluated with the following questions:
	* Does the organisation have a stated objective of reaching consensus when making decisions on standards?		* Does the organisation have a stated objective of reaching consensus when making decisions on standards?
-	: '''There is no explicitly stated objective of reaching consensus. However, when new contributions are made, the key specification developers will be able to veto on the introduction of a new feature. Generally, differences are discussed openly and new features are adapted until they fit the overall architecture of the standard, at which stage they are introduced into the specification, standard and software.'''	+	: '''There is no explicitly stated objective of reaching consensus. However, when new contributions are made, the key specification developers will be able to veto the introduction of a new feature. Generally, differences are discussed openly and new features are adapted until they fit the overall architecture of the standard, at which stage they are introduced into the specification, standard and software.'''
	* If consensus is not reached, can the standard be approved? (answers are: cannot be approved but referred back to working group/committee, approved with 75% majority, approved with 66% majority, approved with 51% majority, can be decided by a "director" or similar in the organisation).		* If consensus is not reached, can the standard be approved? (answers are: cannot be approved but referred back to working group/committee, approved with 75% majority, approved with 66% majority, approved with 51% majority, can be decided by a "director" or similar in the organisation).
	: '''The standard can be approved without consensus via the decision of a "director" or similar.'''		: '''The standard can be approved without consensus via the decision of a "director" or similar.'''

Questionnaire scratch space

2009-11-18T19:36:35Z

Consensus: missed another number disagreement

← Older revision		Revision as of 19:36, 18 November 2009
(2 intermediate revisions not shown)
Line 55:		Line 55:
	: '''Yes. The underlying technology has been in use for nearly a decade, and most of the concepts have been in widespread use for even longer.'''		: '''Yes. The underlying technology has been in use for nearly a decade, and most of the concepts have been in widespread use for even longer.'''
	* Is the formal specification based upon technology that has not been well-defined and may be relatively new?		* Is the formal specification based upon technology that has not been well-defined and may be relatively new?
-	: '''No. The formal specification is based on technology from the On2 VP3 codec, which is substantially similar to simple block-transform codecs like H.261. This class of codecs is extremely well understood, and has been ~~actively~~ in use for over 20 years.'''	+	: '''No. The formal specification is based on technology from the On2 VP3 codec, which is substantially similar to simple block-transform codecs like H.261. This class of codecs is extremely well understood, and has been in active use for over 20 years.'''
	* Has the formal specification been revised? (Yes/No, Nof)		* Has the formal specification been revised? (Yes/No, Nof)
	: '''The formal specification of the Theora decoder has been stable for years. However, the text of the specification is continuously revised, based on user feedback, to improve the clarity and accuracy of the description of the technology.'''		: '''The formal specification of the Theora decoder has been stable for years. However, the text of the specification is continuously revised, based on user feedback, to improve the clarity and accuracy of the description of the technology.'''
Line 144:		Line 144:
	Consensus is decision making primarily with regard to the approval of formal specifications and review with interest groups (non-members). The consensus evaluation criterion is evaluated with the following questions:		Consensus is decision making primarily with regard to the approval of formal specifications and review with interest groups (non-members). The consensus evaluation criterion is evaluated with the following questions:
	* Does the organisation have a stated objective of reaching consensus when making decisions on standards?		* Does the organisation have a stated objective of reaching consensus when making decisions on standards?
-	: '''There is no explicitly stated objective of reaching consensus. However, when new contributions are made, the key specification developers will be able to veto on the introduction of a new feature. Generally, differences are discussed openly and new features are adapted until they fit the overall architecture of the ~~standards~~, at which stage they are introduced into the specification, ~~standards~~ and software.'''	+	: '''There is no explicitly stated objective of reaching consensus. However, when new contributions are made, the key specification developers will be able to veto on the introduction of a new feature. Generally, differences are discussed openly and new features are adapted until they fit the overall architecture of the standard, at which stage they are introduced into the specification, standard and software.'''
	* If consensus is not reached, can the standard be approved? (answers are: cannot be approved but referred back to working group/committee, approved with 75% majority, approved with 66% majority, approved with 51% majority, can be decided by a "director" or similar in the organisation).		* If consensus is not reached, can the standard be approved? (answers are: cannot be approved but referred back to working group/committee, approved with 75% majority, approved with 66% majority, approved with 51% majority, can be decided by a "director" or similar in the organisation).
	: '''The standard can be approved without consensus via the decision of a "director" or similar.'''		: '''The standard can be approved without consensus via the decision of a "director" or similar.'''

Games that use Theora

2009-11-18T13:38:53Z

Add Ghostbusters http://www.ecto-web.org/~spookcentral/scblog/index.php/2009/08/20/ghostbusters-video-game-pc-unlockables

← Older revision		Revision as of 13:38, 18 November 2009
Line 3:		Line 3:
	* [http://serioussam2.com Serious Sam 2]: Uses Theora for cut scenes.		* [http://serioussam2.com Serious Sam 2]: Uses Theora for cut scenes.
	* [http://www.editingarchive.com/simworld/ SimWorld], uses Theora for splash videos and item catalog preview videos (Also uses Vorbis for audio)		* [http://www.editingarchive.com/simworld/ SimWorld], uses Theora for splash videos and item catalog preview videos (Also uses Vorbis for audio)
		+	* [http://www.atari.com/games/ghostbusters/ Ghostbusters], uses Theora for cutscene videos (certainly on PC; PS3 has Xiph copyright, may just be for Vorbis audio)

	== See also ==		== See also ==
	{{Template:Theora}}		{{Template:Theora}}
-
	[[Category:Theora]]		[[Category:Theora]]

User:Mikevarela

2009-11-17T22:25:49Z

New user account

New page

Questionnaire scratch space

2009-11-17T20:27:39Z

Reverse answer on "conformance governance"

Show changes

Questionnaire scratch space

2009-11-17T01:25:19Z

Interoperability governance:

Questionnaire scratch space

2009-11-16T19:03:58Z

governments are institutional

← Older revision		Revision as of 19:03, 16 November 2009
(One intermediate revision not shown)
Line 44:		Line 44:
	* Does the formal specification show wide adoption?		* Does the formal specification show wide adoption?
	** across different domains? (I.e.: public and private)		** across different domains? (I.e.: public and private)
-	: Yes. In addition to the private companies mentioned in the previous section, Theora has also been specified as the sole format supported by non-profit ~~institutions~~ such as Wikipedia, currently the 6th largest website in the world, or as one of a small number of preferred formats supported by other public ~~organizations~~, such as the Norwegian government.	+	: Yes. In addition to the private companies mentioned in the previous section, Theora has also been specified as the sole format supported by non-profit organizations such as Wikipedia, currently the 6th largest website in the world, or as one of a small number of preferred formats supported by other public institutions, such as the Norwegian government.
	** in an open environment?		** in an open environment?
	: Yes. On open/free operating systems such as those distributed by Novell/SuSE, Canonical, and Red Hat, Theora is the primary default video codec.		: Yes. On open/free operating systems such as those distributed by Novell/SuSE, Canonical, and Red Hat, Theora is the primary default video codec.
Line 57:		Line 57:
	: No. The formal specification is based on technology from the On2 VP3 codec, which is substantially similar to simple block-transform codecs like H.261. This class of codecs is extremely well understood, and has been actively in use for over 20 years.		: No. The formal specification is based on technology from the On2 VP3 codec, which is substantially similar to simple block-transform codecs like H.261. This class of codecs is extremely well understood, and has been actively in use for over 20 years.
	* Has the formal specification been revised? (Yes/No, Nof)		* Has the formal specification been revised? (Yes/No, Nof)
-	: ~~Yes.~~ The specification of the ~~encoder~~ is continuously revised based on user feedback to improve clarity and accuracy~~. The specification~~ of the ~~decoding part has been stable for years~~.	+	: The formal specification of the Theora decoder has been stable for years. However, the text of the specification is continuously revised, based on user feedback, to improve the clarity and accuracy of the description of the technology.
	* Is the formal specification under the auspices of an architectural board? (Yes/No)		* Is the formal specification under the auspices of an architectural board? (Yes/No)
	: No. Although officially maintained by the Xiph.Org Foundation, anyone is free to join this organization, and one need not even be a member to make contributions. However, the core developers will review contributions and make sure they do not contradict the general architecture and they work well with the existing code and the test cases.		: No. Although officially maintained by the Xiph.Org Foundation, anyone is free to join this organization, and one need not even be a member to make contributions. However, the core developers will review contributions and make sure they do not contradict the general architecture and they work well with the existing code and the test cases.

User:Cloudsoar

2009-11-16T18:07:00Z

blocked [[Cloudsoar (Talk | contribs)]] with an expiry time of infinite (account creation disabled, e-mail blocked)

New page

User:DoCK

2009-11-16T18:06:33Z

blocked [[DoCK (Talk | contribs)]] with an expiry time of infinite (account creation disabled, e-mail blocked)

New page

Reporting abuse

2009-11-16T14:06:01Z

Added description of the "ban" and "delete" tags

← Older revision		Revision as of 14:06, 16 November 2009
Line 1:		Line 1:
-	There have been incidents of Wiki spam and other abuse. If you wish to ~~report~~ abuse on the Wiki, you should ~~send a message to~~ the ~~administrators~~.	+	There have been incidents of Wiki spam and other abuse.
		+
		+	If you wish to draw the admins' attention to abuse on the Wiki, you should tag pages for deletion by editing the page and adding the "delete" tag: <pre>{{delete}}</pre>
		+	Abusive users can be tagged on their user pages using the "ban" tag: <pre>{{ban}}</pre>
		+
		+	These do not actually perform the action of deletion or banning; they merely mark the pages as candidates for review.

	[[User:Saoshyant\|Saoshyant]] has indicated that he is the primary admin contact for abuse issues.		[[User:Saoshyant\|Saoshyant]] has indicated that he is the primary admin contact for abuse issues.

Talk:Main Page

2009-11-16T13:53:49Z

Add link to "Reporting Abuse" page on the front page?:

← Older revision		Revision as of 13:53, 16 November 2009
(One intermediate revision not shown)
Line 130:		Line 130:
	== Add link to "Reporting Abuse" page on the front page? ==		== Add link to "Reporting Abuse" page on the front page? ==

-	There's been a bunch of spam recently, but I couldn't find any way to report abuse. I've added a skeleton page, could we add a link to the front page?	+	There's been a bunch of spam recently, but I couldn't find any way to report abuse. I've added a skeleton page at [[Reporting abuse]], could we add a link to the front page?

	== Abuse ==		== Abuse ==

	It's necessary to something about the excesive abuse of this Wiki, link approval is the minimal step for now. Also some additional barriers for registration should be considered. Also a stronger captcha, "3+4" isn't that efficient. [[User:DOS386\|DOS386]] 12:44, 16 November 2009 (UTC)		It's necessary to something about the excesive abuse of this Wiki, link approval is the minimal step for now. Also some additional barriers for registration should be considered. Also a stronger captcha, "3+4" isn't that efficient. [[User:DOS386\|DOS386]] 12:44, 16 November 2009 (UTC)

User:Cloudsoar

2009-11-16T12:46:19Z

New page

User talk:DoCK

2009-11-16T12:45:39Z

New page

Ban this one

Talk:Main Page

2009-11-16T12:44:43Z

yeah

Show changes

User:Cloudsoar

2009-11-16T09:56:59Z

New user account

New page

Talk:Main Page

2009-11-16T07:11:38Z

Show changes

Questionnaire scratch space

2009-11-16T05:25:36Z

Remove lie.

← Older revision		Revision as of 05:25, 16 November 2009
(3 intermediate revisions not shown)
Line 48:		Line 48:
	: Yes. On open/free operating systems such as those distributed by Novell/SuSE, Canonical, and Red Hat, Theora is the primary default video codec.		: Yes. On open/free operating systems such as those distributed by Novell/SuSE, Canonical, and Red Hat, Theora is the primary default video codec.
	** in a similar field? (i.e.: can best practices be identified?)		** in a similar field? (i.e.: can best practices be identified?)
		+	: Yes. Most prominently, Theora has been used for eGovernment video distribution in the United States at [http://metavid.org Metavid]. Metavid is the most comprehensive, interactive archive of video footage from the United States legislature. Metavid does not only distribute video; they also enable citizens to engage by annotating videos and correcting transcripts. Metavid distributes its entire archive in Theora format. Metavid's source code is entirely open and reusable for any purpose, providing instant access to best practices for eGovernment with Theora. Metavid's video display component is also available separately as [http://metavid.org/wiki/Mv_Embed mv_embed], which provides reusable best practices for easy Theora display on the web.
		+	: Another important user of Theora is Wikipedia, which distributes video exclusively in Theora format. Wikipedia's best practices for Theora distribution are encapsulated in [http://www.mediawiki.org/wiki/Extension:OggHandler OggHandler], which can be freely reused by anyone using the open-source MediaWiki software.
	* Has the formal specification been in use and development long enough that most of its initial problems have been overcome?		* Has the formal specification been in use and development long enough that most of its initial problems have been overcome?
	: Yes. Theora was derived from VP3, which was originally released in May 2000. The Theora specification was completed in 2004. Theora has now been used in a wide variety of applications, on the full spectrum of computing devices.		: Yes. Theora was derived from VP3, which was originally released in May 2000. The Theora specification was completed in 2004. Theora has now been used in a wide variety of applications, on the full spectrum of computing devices.
Line 120:		Line 122:
	The interoperability governance evaluation criteria relates to how interoperability is identified and maintained between interoperable formal specifications. In order to do this, the organisation may provide governance for:		The interoperability governance evaluation criteria relates to how interoperability is identified and maintained between interoperable formal specifications. In order to do this, the organisation may provide governance for:
	* open identification in formal specifications,		* open identification in formal specifications,
		+	: Yes. The Xiph codecs can be precisely identified by [http://wiki.xiph.org/index.php/MIMETypesCodecs their MIME types], as formally defined by [http://www.ietf.org/rfc/rfc5334.txt IETF RFC 5334], an open specification.
	* open negotiation in formal specifications,		* open negotiation in formal specifications,
-	* open selection in formal specifications.	+	* open selection in formal specifications.

	=== Meeting and consultation ===		=== Meeting and consultation ===

Questionnaire scratch space

2009-11-16T00:25:34Z

Stop short of declaring FFmpeg "interoperable" until our open bug reports are fixed:

Questionnaire scratch space

2009-11-15T23:46:59Z

clarified consensus seeking process

Show changes

Questionnaire scratch space

2009-11-15T22:50:53Z

Support:

Talk:Main Page

2009-11-15T22:25:47Z

spamicide

Show changes

← Older revision		Revision as of 01:25, 17 November 2009
(One intermediate revision not shown)
Line 48:		Line 48:
	: Yes. On open/free operating systems such as those distributed by Novell/SuSE, Canonical, and Red Hat, Theora is the primary default video codec.		: Yes. On open/free operating systems such as those distributed by Novell/SuSE, Canonical, and Red Hat, Theora is the primary default video codec.
	** in a similar field? (i.e.: can best practices be identified?)		** in a similar field? (i.e.: can best practices be identified?)
-	: Yes. Most prominently, Theora has been used for eGovernment video distribution in the United States at [http://metavid.org Metavid]. Metavid is the most comprehensive, interactive archive of video footage from the United States legislature. Metavid ~~does~~ not only ~~distribute~~ video; they also enable ~~citizens to engage~~ by ~~annotating~~ videos and ~~correcting~~ transcripts. Metavid distributes its entire archive in Theora format. Metavid's source code is entirely open and reusable for any purpose, providing instant access to best practices for eGovernment with Theora. Metavid's video display component is also available separately as [http://metavid.org/wiki/Mv_Embed mv_embed], which provides reusable best practices for easy Theora display on the web.	+	: Yes. Most prominently, Theora has been used for eGovernment video distribution in the United States at [http://metavid.org Metavid]. Metavid is the most comprehensive, interactive archive of video footage from the United States legislature. Metavid not only distributes video; they also enable citizen engagement by allowing them to annotate videos and correct transcripts. Metavid distributes its entire archive in Theora format. Metavid's source code is entirely open and reusable for any purpose, providing instant access to best practices for eGovernment with Theora. Metavid's video display component is also available separately as [http://metavid.org/wiki/Mv_Embed mv_embed], which provides reusable best practices for easy Theora display on the web.
	: Another important user of Theora is Wikipedia, which distributes video exclusively in Theora format. Wikipedia's best practices for Theora distribution are encapsulated in [http://www.mediawiki.org/wiki/Extension:OggHandler OggHandler], which can be freely reused by anyone using the open-source MediaWiki software.		: Another important user of Theora is Wikipedia, which distributes video exclusively in Theora format. Wikipedia's best practices for Theora distribution are encapsulated in [http://www.mediawiki.org/wiki/Extension:OggHandler OggHandler], which can be freely reused by anyone using the open-source MediaWiki software.
	* Has the formal specification been in use and development long enough that most of its initial problems have been overcome?		* Has the formal specification been in use and development long enough that most of its initial problems have been overcome?
Line 122:		Line 122:
	The interoperability governance evaluation criteria relates to how interoperability is identified and maintained between interoperable formal specifications. In order to do this, the organisation may provide governance for:		The interoperability governance evaluation criteria relates to how interoperability is identified and maintained between interoperable formal specifications. In order to do this, the organisation may provide governance for:
	* open identification in formal specifications,		* open identification in formal specifications,
-	: Yes. The Xiph codecs can be precisely identified by [http://wiki.xiph.org/index.php/MIMETypesCodecs their MIME types], as formally defined by [http://~~www~~.ietf.org/~~rfc~~/rfc5334~~.txt~~ IETF RFC 5334], an open specification.	+	: Yes. The Xiph codecs can be precisely identified by [http://wiki.xiph.org/index.php/MIMETypesCodecs their MIME types], as formally defined by [http://tools.ietf.org/html/rfc5334 IETF RFC 5334], an open specification.
	* open negotiation in formal specifications,		* open negotiation in formal specifications,
		+	: Yes. For example, a [http://tools.ietf.org/html/draft-barbato-avt-rtp-theora-01 draft RTP specification] describes how Theora interoperates with the [http://tools.ietf.org/html/rfc3264 Session Description Protocol] (SDP), a mechanism for negotiating the parameters of RTP sessions.
	* open selection in formal specifications.		* open selection in formal specifications.

← Older revision		Revision as of 00:25, 16 November 2009
(2 intermediate revisions not shown)
Line 25:		Line 25:
	: Theora is a video codec, and as such the required products are encoders, decoders, and transmission systems. All three types of products are widely available for Theora.		: Theora is a video codec, and as such the required products are encoders, decoders, and transmission systems. All three types of products are widely available for Theora.
	* How many implementations of the formal specification are there?		* How many implementations of the formal specification are there?
-	: Xiph does not require implementors to acquire any license before implementing the specification. Therefore, we do not have a definitive count of the number of implementations. In addition to the reference implementation, which has been ported to most modern platforms and highly optimized for x86 and ARM CPUs and TI C64x+ DSPs, we are aware of a number of independent, conformant or mostly-conformant implementations. These include two C decoders (ffmpeg and QTheora), a Java decoder (Jheora), a C# decoder, an FPGA decoder, and an FPGA encoder.	+	: Xiph does not require implementors to acquire any license before implementing the specification. Therefore, we do not have a definitive count of the number of implementations. In addition to the reference implementation, which has been ported to most modern platforms and highly optimized for x86 and ARM CPUs and TI C64x+ DSPs, we are aware of a number of independent, conformant or mostly-conformant implementations. These include two C decoders ([http://ffmpeg.org/ FFmpeg] and [http://sourceforge.jp/projects/qtheora/ QTheora]), a Java decoder ([http://www.theora.org/cortado/ Jheora]), a [http://www.wreckedgames.com/downloads/cSharpTheora.zip C# decoder], an [http://svn.xiph.org/trunk/theora-fpga/ FPGA decoder], and an [http://sourceforge.net/projects/elphel/ FPGA encoder].
	* Are there products from different suppliers in the market that implement this formal specification ?		* Are there products from different suppliers in the market that implement this formal specification ?
	: Yes. Corporations such as Atari, Canonical, DailyMotion, Elphel, Fluendo, Google, Mozilla, Novell, Opera, Red Hat, Sun Microsystems, Ubisoft, and countless others have supplied products with an implementation of the Theora standard.		: Yes. Corporations such as Atari, Canonical, DailyMotion, Elphel, Fluendo, Google, Mozilla, Novell, Opera, Red Hat, Sun Microsystems, Ubisoft, and countless others have supplied products with an implementation of the Theora standard.
Line 69:		Line 69:
	: Yes. For example, [http://theora.org/doc/Theora.pdf the Theora specification] provides "non-normative" advice and explanation for implementors of Theora decoders and encoders, including example algorithms for implementing required mathematical transforms. Xiph also maintains [http://wiki.xiph.org/Main_Page a documentation base] for implementors who desire more guidelines beyond the specification itself.		: Yes. For example, [http://theora.org/doc/Theora.pdf the Theora specification] provides "non-normative" advice and explanation for implementors of Theora decoders and encoders, including example algorithms for implementing required mathematical transforms. Xiph also maintains [http://wiki.xiph.org/Main_Page a documentation base] for implementors who desire more guidelines beyond the specification itself.
	* Can other cases where similar systems implement the formal specification be considered as successful implementations and good practices?		* Can other cases where similar systems implement the formal specification be considered as successful implementations and good practices?
-	: Xiph's standards have successfully been implemented by many organisations in a wide variety of environments. We maintain (non-exhaustive) [http://wiki.xiph.org/TheoraSoftwarePlayers lists] of products which implement Theora support, many of them open source, so that others may use them as a reference when preparing their own products~~. A particularly well known, independent, but interoperable implementation is provided by the FFmpeg open source project~~.	+	: Xiph's standards have successfully been implemented by many organisations in a wide variety of environments. We maintain (non-exhaustive) [http://wiki.xiph.org/TheoraSoftwarePlayers lists] of products which implement Theora support, many of them open source, so that others may use them as a reference when preparing their own products.
	* Is its compatibility with related formal specification documented?		* Is its compatibility with related formal specification documented?
	: Yes. For example, [http://theora.org/doc/Theora.pdf the Theora specification] also documents the use of Theora within the [http://www.ietf.org/rfc/rfc3533.txt standard Ogg encapsulation format], and the [http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-00.txt TheoraRTP draft specification] explains how to transmit Theora using the [http://tools.ietf.org/html/rfc3550 RTP standard]. In addition, the specification documents Theora's compatibility with ITU-R B.470, ITU-R B.601, ITU-R B.709, SMPTE-170M, [http://tools.ietf.org/html/rfc2044 UTF-8], ISO 10646, and [http://www.xiph.org/vorbis/doc/Vorbis_I_spec.pdf Ogg Vorbis].		: Yes. For example, [http://theora.org/doc/Theora.pdf the Theora specification] also documents the use of Theora within the [http://www.ietf.org/rfc/rfc3533.txt standard Ogg encapsulation format], and the [http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-00.txt TheoraRTP draft specification] explains how to transmit Theora using the [http://tools.ietf.org/html/rfc3550 RTP standard]. In addition, the specification documents Theora's compatibility with ITU-R B.470, ITU-R B.601, ITU-R B.709, SMPTE-170M, [http://tools.ietf.org/html/rfc2044 UTF-8], ISO 10646, and [http://www.xiph.org/vorbis/doc/Vorbis_I_spec.pdf Ogg Vorbis].
Line 105:		Line 105:
	The following questions allow an assessment of accessibility and conformance safety:		The following questions allow an assessment of accessibility and conformance safety:
	* Does a mechanism that ensures disability support by a formal specification exist? (Y/N)		* Does a mechanism that ensures disability support by a formal specification exist? (Y/N)
-	: Yes. Xiph ensures support for users with disabilities by providing specifications for accessible technologies independent of the codec itself. Notably, the Xiph [http://wiki.xiph.org/OggKate OggKate] codec for time-aligned text and image content provides support for subtitles for internationalisation, captions for the hearing-impaired, and textual audio descriptions for the visually impaired. Further, Ogg supports multiple tracks of audio and video content in one container, such that sign language tracks and audio descriptions can be included into one file. For this to work, Xiph ~~have~~ defined [http://wiki.xiph.org/Ogg_Skeleton Skeleton] which holds metadata about each track encapsulated within ~~the one~~ Ogg file. When Theora is transmitted or stored in an Ogg container, it is automatically compatible with these accessibility measures.	+	: Yes. Xiph ensures support for users with disabilities by providing specifications for accessible technologies independent of the codec itself. Notably, the Xiph [http://wiki.xiph.org/OggKate OggKate] codec for time-aligned text and image content provides support for subtitles for internationalisation, captions for the hearing-impaired, and textual audio descriptions for the visually impaired. Further, Ogg supports multiple tracks of audio and video content in one container, such that sign language tracks and audio descriptions can be included into one file. For this to work, Xiph has defined [http://wiki.xiph.org/Ogg_Skeleton Skeleton] which holds metadata about each track encapsulated within a single Ogg file. When Theora is transmitted or stored in an Ogg container, it is automatically compatible with these accessibility measures.
	* Is conformance governance always part of a standard? (Y/N)		* Is conformance governance always part of a standard? (Y/N)
	: No. Xiph does not normally provide a formal conformance testing process as part of a standard.		: No. Xiph does not normally provide a formal conformance testing process as part of a standard.
	* Is a conformance test offered to implementers? (Y/N)		* Is a conformance test offered to implementers? (Y/N)
-	: Yes. Xiph maintains a suite of [http://v2v.cc/~j/theora_testsuite/ test vectors] ~~that can be used by implementors to confirm basic conformance. Also, Xiph's~~ [http://validator.xiph.org online validation service] ~~is a freely available service~~ that can be used by anyone to check conformance.	+	: Yes. Xiph maintains a freely available suite of [http://v2v.cc/~j/theora_testsuite/ test vectors] and an [http://validator.xiph.org online validation service] that can be used by anyone to check confirm basic conformance, in addition to tools such as the oggz-validate program included with liboggz, which has been widely used for conformance testing.
	* Is conformance validation available to implementers? (Y/N)		* Is conformance validation available to implementers? (Y/N)
-	: Yes. Informal conformance testing is available to implementors upon request, and Xiph has provided such testing for a number of implementations ~~in the past. The oggz tools contain a validation program called oggz-validate which implementers have made massive use of~~ in the past.	+	: Yes. Informal conformance testing is available to implementors upon request, and Xiph has provided such testing for a number of implementations in the past.
	* Is conformance certification available? (Y/N)		* Is conformance certification available? (Y/N)
	: Yes. Xiph does not require certification, but maintains the right to withhold the use of our trademarks from implementors that act in bad faith. Implementors may, however, request explicit permission to use our trademarks with a conforming implementation.		: Yes. Xiph does not require certification, but maintains the right to withhold the use of our trademarks from implementors that act in bad faith. Implementors may, however, request explicit permission to use our trademarks with a conforming implementation.

← Older revision		Revision as of 22:50, 15 November 2009
(6 intermediate revisions not shown)
Line 51:		Line 51:
	: Yes. Theora was derived from VP3, which was originally released in May 2000. The Theora specification was completed in 2004. Theora has now been used in a wide variety of applications, on the full spectrum of computing devices.		: Yes. Theora was derived from VP3, which was originally released in May 2000. The Theora specification was completed in 2004. Theora has now been used in a wide variety of applications, on the full spectrum of computing devices.
	* Is the underlying technology of the standard well-understood? (e.g., a reference model is welldefined, appropriate concepts of the technology are in widespread use, the technology may have been in use for many years, a formal mathematical model is defined, etc.)		* Is the underlying technology of the standard well-understood? (e.g., a reference model is welldefined, appropriate concepts of the technology are in widespread use, the technology may have been in use for many years, a formal mathematical model is defined, etc.)
-	Yes. The underlying technology has been in use for nearly a decade, and most of the concepts have been in widespread use for even longer.	+	: Yes. The underlying technology has been in use for nearly a decade, and most of the concepts have been in widespread use for even longer.
	* Is the formal specification based upon technology that has not been well-defined and may be relatively new?		* Is the formal specification based upon technology that has not been well-defined and may be relatively new?
	: No. The formal specification is based on technology from the On2 VP3 codec, which is substantially similar to simple block-transform codecs like H.261. This class of codecs is extremely well understood, and has been actively in use for over 20 years.		: No. The formal specification is based on technology from the On2 VP3 codec, which is substantially similar to simple block-transform codecs like H.261. This class of codecs is extremely well understood, and has been actively in use for over 20 years.
Line 105:		Line 105:
	The following questions allow an assessment of accessibility and conformance safety:		The following questions allow an assessment of accessibility and conformance safety:
	* Does a mechanism that ensures disability support by a formal specification exist? (Y/N)		* Does a mechanism that ensures disability support by a formal specification exist? (Y/N)
-	: Yes. Xiph~~.org~~ ensures support for users with disabilities by providing specifications for accessible technologies independent of the codec itself. Notable Xiph specifications include [http://wiki.xiph.org/OggKate OggKate] and [http://wiki.xiph.org/index.php/CMML CMML], which provide subtitles for the hearing-impaired, as well as [http://wiki.xiph.org/Ogg_Skeleton Skeleton], which can specify scene description audio tracks for the visually impaired. When Theora is transmitted or stored in an Ogg container, it is automatically compatible with these accessibility measures.	+	: Yes. Xiph ensures support for users with disabilities by providing specifications for accessible technologies independent of the codec itself. Notable Xiph specifications include [http://wiki.xiph.org/OggKate OggKate] and [http://wiki.xiph.org/index.php/CMML CMML], which provide subtitles for the hearing-impaired, as well as [http://wiki.xiph.org/Ogg_Skeleton Skeleton], which can specify scene description audio tracks for the visually impaired. When Theora is transmitted or stored in an Ogg container, it is automatically compatible with these accessibility measures.
	* Is conformance governance always part of a standard? (Y/N)		* Is conformance governance always part of a standard? (Y/N)
		+	: No. Xiph does not normally provide a formal conformance testing process as part of a standard.
	* Is a conformance test offered to implementers? (Y/N)		* Is a conformance test offered to implementers? (Y/N)
		+	: Yes. Xiph maintains a suite of [http://v2v.cc/~j/theora_testsuite/ test vectors] that can be used by implementors to confirm basic conformance.
	* Is conformance validation available to implementers? (Y/N)		* Is conformance validation available to implementers? (Y/N)
		+	: Yes. Informal conformance testing is available to implementors upon request, and Xiph has provided such testing for a number of implementations in the past.
	* Is conformance certification available? (Y/N)		* Is conformance certification available? (Y/N)
		+	: Yes. Xiph does not require certification, but maintains the right to withhold the use of our trademarks from implementors that act in bad faith. Implementors may, however, request explicit permission to use our trademarks with a conforming implementation.
	* Is localisation of a formal specification possible? (Y/N)		* Is localisation of a formal specification possible? (Y/N)
	: Yes. We welcome anyone who wishes to translate Xiph specifications into other languages. We have no policy requiring that the normative specification be written in English.		: Yes. We welcome anyone who wishes to translate Xiph specifications into other languages. We have no policy requiring that the normative specification be written in English.
Line 126:		Line 130:
	: Yes. Standardization occurs almost entirely in internet communications channels, allowing participants with disabilities to engage fully in the standards development process. We also encourage nonexperts and students to assist us as they can, and to learn about Xiph technologies by participating in the standards development process.		: Yes. Standardization occurs almost entirely in internet communications channels, allowing participants with disabilities to engage fully in the standards development process. We also encourage nonexperts and students to assist us as they can, and to learn about Xiph technologies by participating in the standards development process.
	* if meetings are open to all members;		* if meetings are open to all members;
-	: Xiph meetings are open to everyone. We place no restrictions on attendance or participation. For example, anyone ~~interesting~~ in contributing to the Theora specification may join [http://lists.xiph.org/pipermail/theora-dev/ the Theora development mailing list].	+	: Xiph meetings are open to everyone. We charge no fee for and place no restrictions on attendance or participation. For example, anyone interested in contributing to the Theora specification may join [http://lists.xiph.org/pipermail/theora-dev/ the Theora development mailing list].
	* if all can participate in the formal specification creation process;		* if all can participate in the formal specification creation process;
	: Yes. All people are welcome to participate in the specification creation process. No dues or fees are required to participate		: Yes. All people are welcome to participate in the specification creation process. No dues or fees are required to participate
Line 135:		Line 139:
	Consensus is decision making primarily with regard to the approval of formal specifications and review with interest groups (non-members). The consensus evaluation criterion is evaluated with the following questions:		Consensus is decision making primarily with regard to the approval of formal specifications and review with interest groups (non-members). The consensus evaluation criterion is evaluated with the following questions:
	* Does the organisation have a stated objective of reaching consensus when making decisions on standards?		* Does the organisation have a stated objective of reaching consensus when making decisions on standards?
-	* If consensus is not reached, can the standard be approved? (answers are: cannot be approved but referred back to working group/committee, approved with 75% majority, approved with 66% majority, approved with 51% majority, can be decided by a "director" or similar in the organisation).	+	: There is no explicitly stated objective of reaching consensus.
		+	* If consensus is not reached, can the standard be approved? (answers are: cannot be approved but referred back to working group/committee, approved with 75% majority, approved with 66% majority, approved with 51% majority, can be decided by a "director" or similar in the organisation).
		+	: The standard can be approved without consensus via the decision of a "director" or similar.
	* Is there a formal process for external review of standard proposals by interest groups (nonmembers)?		* Is there a formal process for external review of standard proposals by interest groups (nonmembers)?
	: Since anyone may participate in the development process and make proposals, there is no need for a separate formal process to include proposals by nonmembers.		: Since anyone may participate in the development process and make proposals, there is no need for a separate formal process to include proposals by nonmembers.
Line 141:		Line 147:
	=== Due Process ===		=== Due Process ===
	The due process evaluation criteria relates to the level of respect of each member of the organisation with regard to its rights. More specifically, it must be assured that if a member believes an error has been made in the process of defining a formal specification, it must be possible to appeal this to an independent, higher instance. The question is therefore: can a member formally appeal or raise objections to a procedure or to a technical specification to an independent, higher instance?		The due process evaluation criteria relates to the level of respect of each member of the organisation with regard to its rights. More specifically, it must be assured that if a member believes an error has been made in the process of defining a formal specification, it must be possible to appeal this to an independent, higher instance. The question is therefore: can a member formally appeal or raise objections to a procedure or to a technical specification to an independent, higher instance?
		+
		+	: Yes. Even if a member fails an appeal within the organization, because all of the technology Xiph standardizes is open and freely implementable, they are always free to develop their own, competing version. Such competing versions may even still be eligible for standardization under the Xiph umbrella.

	=== Changes to the formal specification ===		=== Changes to the formal specification ===
	The suggested changes made to a formal specification need to be presented, evaluated and approved in the same way as the formal specification was first defined. This criteria therefore applies the above criteria to the changes made to the formal specification(availability of documentation, Intellectual Property Right, accessibility, interoperability governance, meeting and consultation, consensus, due process).		The suggested changes made to a formal specification need to be presented, evaluated and approved in the same way as the formal specification was first defined. This criteria therefore applies the above criteria to the changes made to the formal specification(availability of documentation, Intellectual Property Right, accessibility, interoperability governance, meeting and consultation, consensus, due process).
		+
		+	: The exact same process is used for revisions to the standard as was used for the original development of the standard, and thus the answers to all of the above questions remain the same.

	=== Support ===		=== Support ===
	It is critical that the organisation takes responsibility for the formal specification throughout its life span. This can be done in several ways such as for example a regular periodic review of the formal specification. The support criteria relates to the level of commitment the organisation has taken to support the formal specification throughout its life:		It is critical that the organisation takes responsibility for the formal specification throughout its life span. This can be done in several ways such as for example a regular periodic review of the formal specification. The support criteria relates to the level of commitment the organisation has taken to support the formal specification throughout its life:
	* does the organisation provide support until removal of the published formal specification from public domain (Including this process?		* does the organisation provide support until removal of the published formal specification from public domain (Including this process?
-	: Xiph.~~org~~ standards are never removed from the public domain. Xiph endeavors to provide support for as long as the standard remains in use.	+	: Xiph.Org standards are never removed from the public domain. Xiph endeavors to provide support for as long as the standard remains in use.
	* does the organisation make the formal specification still available even when in non-maintenance mode?		* does the organisation make the formal specification still available even when in non-maintenance mode?
-	: Yes. All Xiph.~~org~~ standards are freely licensed and will always be available.	+	: Yes. All Xiph.Org standards are freely licensed and will always be available.
	* does the organisation add new features and keep the formal specification up-to-date?		* does the organisation add new features and keep the formal specification up-to-date?
-	: Yes. Xiph~~.org~~ maintains its ecosystem of standards on a continuous basis.	+	: Yes. Xiph maintains its ecosystem of standards on a continuous basis.
	* does the organisation rectify problems identified in initial implementations?		* does the organisation rectify problems identified in initial implementations?
-	: Yes. Xiph~~.org~~ maintains [https://trac.xiph.org/report a problem reporting system] that is open to the public, and invites everyone to submit suggestions for improvements. Improvements are made both to the standards documents and to the reference implementations.	+	: Yes. Xiph maintains [https://trac.xiph.org/report a problem reporting system] that is open to the public, and invites everyone to submit suggestions for improvements. Improvements are made both to the standards documents and to the reference implementations.
	* does the organisation only create the formal specification?		* does the organisation only create the formal specification?
-	: No. Xiph~~.org~~ also produces high-quality reusable reference implementations of its standards, released under an open license.	+	: No. Xiph also produces high-quality reusable reference implementations of its standards, released under an open license.


	<strong>This is a draft document. A work in progress. A scratchpad for ideas. It should not be widely circulated in this form.</strong>		<strong>This is a draft document. A work in progress. A scratchpad for ideas. It should not be widely circulated in this form.</strong>