IDABC Questionnaire 2009 - Revision history

Derf at 23:31, 6 December 2009

2009-12-06T23:31:58Z

← Older revision		Revision as of 23:31, 6 December 2009
Line 1:		Line 1:
	<strong>A typeset version of this document at of November 24th 2009 is available at [http://www.xiph.org/doc/2009_CAMSS_xiph.pdf]</strong>		<strong>A typeset version of this document as of November 24th 2009 is available at [http://www.xiph.org/doc/2009_CAMSS_xiph.pdf]</strong>

	= Context =		= Context =

Gmaxwell: link to the pdf

2009-11-25T01:27:16Z

link to the pdf

← Older revision		Revision as of 01:27, 25 November 2009
Line 1:		Line 1:
	<strong>A typeset version of this document at of November 24th 2009 is available at [http://www.xiph.org/doc/2009_CAMSS_xiph]</strong>		<strong>A typeset version of this document at of November 24th 2009 is available at [http://www.xiph.org/doc/2009_CAMSS_xiph.pdf]</strong>

	= Context =		= Context =

Gmaxwell: moved Questionnaire scratch space to IDABC Questionnaire 2009: finished

2009-11-25T00:20:41Z

moved Questionnaire scratch space to IDABC Questionnaire 2009: finished

← Older revision		Revision as of 00:20, 25 November 2009
(No difference)

Gmaxwell: This is complete now.

2009-11-25T00:20:04Z

This is complete now.

← Older revision		Revision as of 00:20, 25 November 2009
Line 1:		Line 1:
	<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>A typeset version of this document at of November 24th 2009 is available at [http://www.xiph.org/doc/2009_CAMSS_xiph]</strong>

	= Context =		= Context =
Line 172:		Line 172:
	* does the organisation only create the formal specification?		* does the organisation only create the formal specification?
	: '''No. Xiph 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>~~

Mindspillage: /* Meeting and consultation */ "limited abilities" almost certainly means impairment here; changing language.

2009-11-24T22:33:13Z

Meeting and consultation: "limited abilities" almost certainly means impairment here; changing language.

← Older revision		Revision as of 22:33, 24 November 2009
Line 131:		Line 131:
	The meeting and consultation evaluation criteria relates to the process of defining a formal specification. As formal specifications are usually defined by committees, and these committees normally consist of members of the organisation, this criteria studies how to become a member and which are the financial barriers for this, as well as how are non-members able to have an influence on the process of defining the formal specification. It analyses:		The meeting and consultation evaluation criteria relates to the process of defining a formal specification. As formal specifications are usually defined by committees, and these committees normally consist of members of the organisation, this criteria studies how to become a member and which are the financial barriers for this, as well as how are non-members able to have an influence on the process of defining the formal specification. It analyses:
	* if the organisation is open to all types of companies and organisations and to individuals;		* if the organisation is open to all types of companies and organisations and to individuals;
	: '''Yes. Xiph welcomes representatives from all companies and organizations.'''		: '''Yes. Xiph welcomes representatives from all companies and organizations as well as all individuals.'''
	* if the standardisation process may specifically allow participation of members with limited abilities when relevant;		* if the standardisation process may specifically allow participation of members with limited abilities when relevant;
	: '''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 text-based, accessible internet communications channels, allowing participants with disabilities to engage fully 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 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].'''		: '''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].'''

Mindspillage: /* Intellectual Property Right */ punctuation

2009-11-24T22:21:30Z

Intellectual Property Right: punctuation

← Older revision		Revision as of 22:21, 24 November 2009
Line 93:		Line 93:
	: '''The reference implementations of each codec include all necessary IPR and copyright licenses for that codec, including all documentation, and are freely available to everyone.'''		: '''The reference implementations of each codec include all necessary IPR and copyright licenses for that codec, including all documentation, and are freely available to everyone.'''
	* the organisation’s governance to disclose any IPR from any contributor (ex-ante, online, offline, for free for all, for a fee for all, for members only, not available);		* the organisation’s governance to disclose any IPR from any contributor (ex-ante, online, offline, for free for all, for a fee for all, for members only, not available);
	: '''Xiph does not require the identification of specific patents that may be required to implement a standard, ~~however~~ it does require an open-source compatible, royalty free license from a contributor for any such patents they may own before the corresponding technology can be included in a standard. These licenses are made available online, for free, to all parties.'''		: '''Xiph does not require the identification of specific patents that may be required to implement a standard; however, it does require an open-source compatible, royalty free license from a contributor for any such patents they may own before the corresponding technology can be included in a standard. These licenses are made available online, for free, to all parties.'''
	* the level of IPR set "mandatory" by the organisation (no patent, royalty free patent, patent and RAND with limited liability , patent and classic RAND, patent with explicit licensing, patent with defensive licensing, or none);		* the level of IPR set "mandatory" by the organisation (no patent, royalty free patent, patent and RAND with limited liability , patent and classic RAND, patent with explicit licensing, patent with defensive licensing, or none);
	: '''All standards, specifications, and software published by the Xiph.Org Foundation are required to have "open-source compatible" IPR. This means that a contribution must either be entirely clear of any known patents, or any patents that read upon the contribution must be available under a transferable, irrevocable public nonassertion agreement to all people everywhere. For example, see [http://svn.xiph.org/trunk/theora/LICENSE our On2 patent nonassertion warrant]. Other common "royalty free" patent licenses are either not transferable, revocable under certain conditions (such as patent infringement litigation against the originating party), or otherwise impose restrictions that would prevent distribution under common [http://www.opensource.org/ OSI]-approved licenses. These would not be acceptable.'''		: '''All standards, specifications, and software published by the Xiph.Org Foundation are required to have "open-source compatible" IPR. This means that a contribution must either be entirely clear of any known patents, or any patents that read upon the contribution must be available under a transferable, irrevocable public nonassertion agreement to all people everywhere. For example, see [http://svn.xiph.org/trunk/theora/LICENSE our On2 patent nonassertion warrant]. Other common "royalty free" patent licenses are either not transferable, are revocable under certain conditions (such as patent infringement litigation against the originating party), or otherwise impose restrictions that would prevent distribution under common [http://www.opensource.org/ OSI]-approved licenses. These would not be acceptable.'''
	* the level of IPR "recommended" by the organisation (no patent, royalty free patent, patent and RAND with limited liability, patent and classic RAND, patent with explicit licensing, patent with defensive licensing, or none). [Note: RAND (Reasonable and Non Discriminatory License) is based on a "fairness" concept. Companies agree that if they receive any patents on technologies that become essential to the standard then they agree to allow other groups attempting to implement the standard to use these patents and they agree that the charges for the patents shall be reasonable. "RAND with limited availability" is a version of RAND where the "reasonable charges" have an upper limit.]		* the level of IPR "recommended" by the organisation (no patent, royalty free patent, patent and RAND with limited liability, patent and classic RAND, patent with explicit licensing, patent with defensive licensing, or none). [Note: RAND (Reasonable and Non Discriminatory License) is based on a "fairness" concept. Companies agree that if they receive any patents on technologies that become essential to the standard then they agree to allow other groups attempting to implement the standard to use these patents and they agree that the charges for the patents shall be reasonable. "RAND with limited availability" is a version of RAND where the "reasonable charges" have an upper limit.]
	: '''Xiph's recommended IPR requirements are the same as our mandatory requirements.'''		: '''Xiph's recommended IPR requirements are the same as our mandatory requirements.'''

Rillian: /* Market support */ Latex actually uses three hyphens for an m-dash

2009-11-24T22:11:41Z

Market support: Latex actually uses three hyphens for an m-dash

← Older revision		Revision as of 22:11, 24 November 2009
Line 21:		Line 21:
	=== Market support ===		=== Market support ===
	* Does the standard have strong support in the marketplace?		* Does the standard have strong support in the marketplace?
	: '''Yes. For example, among web browsers, support for Xiph's Ogg, Theora, and Vorbis standards is now included by default in Mozilla Firefox, Google Chrome, and the latest versions of Opera, representing hundreds of millions of installed users just in this market alone. On Windows, DirectShow filters exist which also enable all Windows applications that use the DirectShow framework to use Xiph's Ogg, Theora, and Vorbis standards. A QuickTime component exists which enables use of Xiph's Ogg, Theora, and Vorbis standards in all Mac OS X applications that make use of the QuickTime framework--which includes Safari/Webkit, iMovie, QuickTime, and many others.'''		: '''Yes. For example, among web browsers, support for Xiph's Ogg, Theora, and Vorbis standards is now included by default in Mozilla Firefox, Google Chrome, and the latest versions of Opera, representing hundreds of millions of installed users just in this market alone. On Windows, DirectShow filters exist which also enable all Windows applications that use the DirectShow framework to use Xiph's Ogg, Theora, and Vorbis standards. A QuickTime component exists which enables use of Xiph's Ogg, Theora, and Vorbis standards in all Mac OS X applications that make use of the QuickTime framework---which includes Safari/Webkit, iMovie, QuickTime, and many others.'''
	* What products exist for this formal specification ?		* What products exist for this formal specification ?
	: '''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.'''

Rillian: /* Market support */ try a latex em-dash here

2009-11-24T22:04:53Z

Market support: try a latex em-dash here

← Older revision		Revision as of 22:04, 24 November 2009
Line 21:		Line 21:
	=== Market support ===		=== Market support ===
	* Does the standard have strong support in the marketplace?		* Does the standard have strong support in the marketplace?
	: '''Yes. For example, among web browsers, support for Xiph's Ogg, Theora, and Vorbis standards is now included by default in Mozilla Firefox, Google Chrome, and the latest versions of Opera, representing hundreds of millions of installed users just in this market alone. On Windows, DirectShow filters exist which also enable all Windows applications that use the DirectShow framework to use Xiph's Ogg, Theora, and Vorbis standards. A QuickTime component exists which enables use of Xiph's Ogg, Theora, and Vorbis standards in all Mac OS X applications that make use of the QuickTime framework - which includes Safari/Webkit, iMovie, QuickTime, and many others.'''		: '''Yes. For example, among web browsers, support for Xiph's Ogg, Theora, and Vorbis standards is now included by default in Mozilla Firefox, Google Chrome, and the latest versions of Opera, representing hundreds of millions of installed users just in this market alone. On Windows, DirectShow filters exist which also enable all Windows applications that use the DirectShow framework to use Xiph's Ogg, Theora, and Vorbis standards. A QuickTime component exists which enables use of Xiph's Ogg, Theora, and Vorbis standards in all Mac OS X applications that make use of the QuickTime framework--which includes Safari/Webkit, iMovie, QuickTime, and many others.'''
	* What products exist for this formal specification ?		* What products exist for this formal specification ?
	: '''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.'''

Rillian: /* Accessibility */ implementors are people, even if they're corporations

2009-11-24T21:29:14Z

Accessibility: implementors are people, even if they're corporations

← Older revision		Revision as of 21:29, 24 November 2009
Line 115:		Line 115:
	: '''Yes. Informal conformance testing is available to implementors upon request, and Xiph has provided such testing for a number of implementations 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 who 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.'''

Rillian: /* Accessibility */ I would say 'included in' not 'into'

2009-11-24T21:28:06Z

Accessibility: I would say 'included in' not 'into'

← Older revision		Revision as of 21:28, 24 November 2009
Line 107:		Line 107:
	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 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.'''		: '''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 in 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)
	: '''Yes. Xiph's standards always precisely specify the requirements that an implementation must meet in order to be considered conformant.'''		: '''Yes. Xiph's standards always precisely specify the requirements that an implementation must meet in order to be considered conformant.'''