Difference between revisions of "Backward compatibility"
Karl Jones (Talk | contribs) |
Karl Jones (Talk | contribs) (→See also) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 17: | Line 17: | ||
== See also == | == See also == | ||
| + | * [[Deprecation]] | ||
* [[Design]] | * [[Design]] | ||
| + | * [[Forward compatibility]] | ||
* [[Industrial design]] | * [[Industrial design]] | ||
* [[Legacy system]] | * [[Legacy system]] | ||
| Line 25: | Line 27: | ||
* [http://en.wikipedia.org/wiki/Backward_compatibility Backward compatibility] @ Wikipedia | * [http://en.wikipedia.org/wiki/Backward_compatibility Backward compatibility] @ Wikipedia | ||
| + | |||
| + | [[Category:Computing]] | ||
| + | [[Category:Design]] | ||
| + | [[Category:Intellectual property]] | ||
| + | [[Category:Telecommunications]] | ||
Latest revision as of 07:09, 21 April 2016
In telecommunications and computing, a product or technology is backward compatible (BC) or downward compatible if it can work with input generated by an older product or technology.
Description
If products designed for the new standard can receive, read, view or play older standards or formats, then the product is said to be backward-compatible; examples of such a standard include data formats and communication protocols.
Breaking changes
Modifications to a system that do not allow backward compatibility are sometimes called "breaking changes."
Forward compatibility
The reverse is forward compatibility, which implies that old devices allow (or are expected to allow) data formats generated by new (or future) devices, perhaps without supporting all new features.
A standard supports forward compatibility if older product versions can receive, read, view or play the new standard.
See also
External links
- Backward compatibility @ Wikipedia
