ESP Wiki is looking for moderators and active contributors!

Difference between revisions of "Use software and functionality from 20 years ago"

m (moved Use software from 20 years ago to Use software and functionality from 20 years ago: broaden the name so I can merge in the "video formats from 20 years ago" article)
(Soon to be patent-free: S3TC texture compression)
 
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{navbox}}'''Using software from 20 years ago''' is the only way to surely avoid [[software patents]].
+
{{navbox}}'''Using software from 20 years ago''' is the only way to surely avoid [[software patents]].  Using standards, ideas, and functionality from 20 years ago is quite safe but doesn't guarantee your software is safe from patent holders.
  
 
==A real case: H.261 video==
 
==A real case: H.261 video==
:''See: [[Video formats from 20 years ago]]''
 
  
 
The situation regarding [[audio-video patents]] has gotten so bad that [[Nokia]] actually recommended that the [[w3c]] consider using a 1988 video format for the [[HTML5]] standard.  From a 2007 Nokia position paper:
 
The situation regarding [[audio-video patents]] has gotten so bad that [[Nokia]] actually recommended that the [[w3c]] consider using a 1988 video format for the [[HTML5]] standard.  From a 2007 Nokia position paper:
Line 11: Line 10:
  
 
That is to say, the "commercial advantage" of avoiding patent problems is big enough to partly justify using software from 20 years ago!
 
That is to say, the "commercial advantage" of avoiding patent problems is big enough to partly justify using software from 20 years ago!
 +
 +
A 1990 version of that spec[http://www.itu.int/rec/T-REC-H.261/recommendation.asp?lang=en&parent=T-REC-H.261-199012-S] filled in some definitions missing from the version published in (or before) November 1988[http://www.itu.int/rec/T-REC-H.261/recommendation.asp?lang=en&parent=T-REC-H.261-198811-S].
  
 
==Distinction: software, not protocols or formats==
 
==Distinction: software, not protocols or formats==
 +
 +
Using 20 year old formats doesn't mean that you will definitely avoid all patents.  Your software will surely contain optimisations and whatever features you think are useful.  Some of those optimisations and features may have been developed ''after'' the format was finalised, and thus could be patented.  The only way to surely avoid patent risk, is to use ''software'' from 20 years ago.
  
 
If you take a slightly different approach and decide to only use ''protocols'' or ''formats'' that are at least 20 years old, you may still encounter patent problems.  Let's take a video format for example.  Someone might have defined the video format in 1990 and written a player for this format.  In 2010, the software from 1990 cannot possibly be the target of patent litigation.  However, another player written in the year 2000 might have included a new algorithm to play the same video but using less memory.  If ''that'' new algorithm was patented, then it will be valid until 2020.  So using a format from 1990 isn't enough to guarantee that you're free from patent risk.  To be 100% safe, you have to use ''software'' that was written 20 years ago.
 
If you take a slightly different approach and decide to only use ''protocols'' or ''formats'' that are at least 20 years old, you may still encounter patent problems.  Let's take a video format for example.  Someone might have defined the video format in 1990 and written a player for this format.  In 2010, the software from 1990 cannot possibly be the target of patent litigation.  However, another player written in the year 2000 might have included a new algorithm to play the same video but using less memory.  If ''that'' new algorithm was patented, then it will be valid until 2020.  So using a format from 1990 isn't enough to guarantee that you're free from patent risk.  To be 100% safe, you have to use ''software'' that was written 20 years ago.
 +
 +
==Formats already patent-free==
 +
 +
I have to check all these...
 +
 +
* H.261
 +
* MPEG-1 or MPEG-2 Audio Layer III (MP3)
 +
 +
==Soon to be patent-free==
 +
* MPEG-2
 +
* S3TC
  
 
==Related pages on {{SITENAME}}==
 
==Related pages on {{SITENAME}}==
 
 
* [[How to avoid software patents]]
 
* [[How to avoid software patents]]
 
* [[Campaigns to avoid certain patented ideas]]
 
* [[Campaigns to avoid certain patented ideas]]
 
* [[Incompatible timespans]]
 
* [[Incompatible timespans]]
* [[Video formats from 20 years ago]]
+
* [[MPEG LA]]
 +
* [[Audio-video patents]]
 +
* [[WebM and VP8]] and [[Ogg Theora]] — modern but hopefully patent-free
  
 
==External links==
 
==External links==
 +
 +
* [http://www.kuro5hin.org/story/2008/7/18/232618/312 Patent Status of MPEG-1,H.261 and MPEG-2]
 +
* [http://scratchpad.wikia.com/wiki/Draft_Update_on_Patent_Status Draft update of Kuro5hin article]
  
 
Examples of software that's 20 years old:
 
Examples of software that's 20 years old:

Latest revision as of 07:01, 11 October 2017

Using software from 20 years ago is the only way to surely avoid software patents. Using standards, ideas, and functionality from 20 years ago is quite safe but doesn't guarantee your software is safe from patent holders.

A real case: H.261 video

The situation regarding audio-video patents has gotten so bad that Nokia actually recommended that the w3c consider using a 1988 video format for the HTML5 standard. From a 2007 Nokia position paper:

A second alternative would be the reference, as a baseline, of older media compression standards, of which one can be reasonably sure that related patents are expired (or are close to expiration). One example for these codecs is ITU-T Rec. H.261, which (in its first version) was ratified in November 1988. While not competitive with today’s state of the art codecs, it’s in the author’s personal experience not that far in its performance from Ogg Theora [...] The disadvantage of this approach is clearly the use of technologies that are two decades old, but that may be at least partly offset by the commercial advantage.[1]

That is to say, the "commercial advantage" of avoiding patent problems is big enough to partly justify using software from 20 years ago!

A 1990 version of that spec[1] filled in some definitions missing from the version published in (or before) November 1988[2].

Distinction: software, not protocols or formats

Using 20 year old formats doesn't mean that you will definitely avoid all patents. Your software will surely contain optimisations and whatever features you think are useful. Some of those optimisations and features may have been developed after the format was finalised, and thus could be patented. The only way to surely avoid patent risk, is to use software from 20 years ago.

If you take a slightly different approach and decide to only use protocols or formats that are at least 20 years old, you may still encounter patent problems. Let's take a video format for example. Someone might have defined the video format in 1990 and written a player for this format. In 2010, the software from 1990 cannot possibly be the target of patent litigation. However, another player written in the year 2000 might have included a new algorithm to play the same video but using less memory. If that new algorithm was patented, then it will be valid until 2020. So using a format from 1990 isn't enough to guarantee that you're free from patent risk. To be 100% safe, you have to use software that was written 20 years ago.

Formats already patent-free

I have to check all these...

  • H.261
  • MPEG-1 or MPEG-2 Audio Layer III (MP3)

Soon to be patent-free

  • MPEG-2
  • S3TC

Related pages on ESP Wiki

External links

Examples of software that's 20 years old:

References